yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
Yes Verizon forum for the latest version. I also ran it on slot 1...no problems except for titanium backup, couldn't restore data. Recommend backing your apps/data with Helium & restore it that way.
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
Something I might share...for some reason. ...When I delete partition 2 and then reformat a lot of roms seem to boot when if I just do a full wipe and flash I get bootlooped...
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
u mean by deleting slot that was created before first and do full wipe on top of it right?......:cool:
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
Ok...so you have the rom slot partitioned and flash a rom . You try it and like it but you want to try another.So,you do the full factory reset on the rom slot and flash.i found that if I started all over again every time...meaning delete the slot completely and re partition and then flash the zip that the chances of it booting were much greater.this was not the case with 3.65 and 4.2.2.But this is beta so...
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
That's what I mean......:thumbup:

SWYPED_FROM_S4_MF3_REDVENOM
[AT&T Samsung Galaxy S 4 Android Development] punkcell:
That's what's been working for me.
[AT&T Samsung Galaxy S 4 Android Development] rabshear:
Yes, the ROM I flashed was the VZW variety based on 4.3. And I did have to go in and redo my APN to get mobile data working. Didn't realize it wasn't working right in my first post. After that all was well. I totally understand, though, that this isn't something the newer folks shouldn't undertake. I could have easily bricked my phone by doing this. I just happened to get lucky with the right combination of things. But I should stress that I made the decision to do this based on a LOT of reading in this and other forums. I would recommend others do the same before rolling the dice.
[AT&T Samsung Galaxy S 4 Android Development] mdaudioguy:
What was so tricky about it?

Seems to me like you -

1. started with MK2 stock,

2. obtained root,

3. installed SS 3.7,

4. flashed the Verizon Hyperdrive ROM to the stock slot,

5. and adjusted your APN settings.

Am I missing anything?
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
Yeah, actually a few people have successfully flashed Hyperdrive RLS11 to the stock slot, and yes, it is in the Verizon forums. All of the others are 4.2.2.

I would say yes, you're missing the fact that people don't always read. If you flash to ROM Slot 1 and it doesn't boot, you're fine, as your stock ROM is still in place in the Stock Slot. Conversely, if you attempt flash to the Stock Slot and it doesn't boot, you get to go through the fun of frantically trying to save your device. It may not have felt risky for you and I, but that doesn't mean it's not risky.

I actually have nothing in the ROM slot, though perhaps the advice remains applicable. My issue occurs when attempting to backup the Stock ROM (in the stock slot) in the first place. The backup procedure completes and claims success, but I get the error "E: Unable to locate ' /boot' partition for backup"

I will certainly try running the system check on the stock slot, hopefully it works.

Sent from my Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] DevilDog512:
Ya I thought it was rom slot 1. Have you tried uninstalling safe strap and reinstalling? I've had this error before too and resolved it like that. If it's the rom slot the other method works. I had custom roms on 3.65 in Stock slot but haven't tried on this one yet. Beta and all doesn't seem wise to tempt fate.

Sent from my SAMSUNG-SGH-I337
[AT&T Samsung Galaxy S 4 Android Development] Atrix2destroyer:
mk2

Is this getting updated for MK2?
[AT&T Samsung Galaxy S 4 Android Development] HORiZUN:
I really wish this device could use custom kernels. I dusted off my HTC Amaze 4G last night, installed 4.4 on it.

Oh, how I miss an unlocked device.
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
It's working for MK2 now, though technically still in Beta

Sent from my Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
Another log file: Dark Carnage ROM. Same black screen results as before. Did get Darthstalker working, however.
[AT&T Samsung Galaxy S 4 Android Development] ddubz:
Odin for ucuemk2

Hash says there is an Odin tar for ucuemk2 where can I find this

---------- Post added at 08:42 PM ---------- Previous post was at 08:36 PM ----------

Anyone tried echoe rom 4.3 with mk2 4.3
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
This is the complete backup log:

Updating partition details...
Full SELinux support is present.
Running boot script...

Finished running boot script.
Updating partition details...
* Total number of partitions to back up: 2
* Total size of all data: 4825MB
* Available space: 6477MB

[BACKUP STARTED]
* Backup Folder: /external_sd/TWRP/BACKUPS/0c5
Backing up System...
Breaking backup file into multiple archives...
* Generating md5...
* MD5 Created.
Backing up Data...
Breaking backup file into multiple archives...
* Generating md5...
* MD5 Created.
[B][I][COLOR="Red"]E:Unable to locate '/boot' partition for backup[/COLOR][/I][/B]
Average backup rate for file systems: 3 MB/sec
Average backup rate for imaged drives: 0 MB/sec
[3105 MB TOTAL BACKED UP]
Updating partition details...
[BACKUP COMPLETED IN 1943 SECONDS]

I receive the error every time I attempt a backup, with or without compression. SS/TWRP doesn't really seem to "act" like it's an issue. Is this simply related to the locked bootloader?

Edit

: After some research, I'm pretty sure my initial reaction was correct and it's related to the locked bootloader, and therefore not an issue (in this context.) Apparently, when TWRP can't mount the boot partition, it's a result of incompatibilities with the bootloader, which would make perfect sense in this situation. Though I would like to request any user who makes a backup in the near future to glance over their backup log and see if they have the same error, just to be on the safe side, unless Hashcode stops by and learns me up. ;)
[AT&T Samsung Galaxy S 4 Android Development] Mosch26:
Pretty sure that the /boot partition is the kernel. Due to the locked bootloader, the kernel cannot be accessed for a backup which leads to the error when backing up with Safestrap. Or at least that's what I think. It honestly makes sense to not back up the kernel or /boot partition to save some space. Why would you want to backup something you cant restore? :p
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
There is no MK2 ODIN for us. The only way to restore it is by using the MJ6-MJ9 upgrade method but using the MK2 update zip instead.
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
Yeah, I'm pretty sure that's the case. However, I wanted to make absolutely sure before I wiped the stock slot, as I'm obviously no developer. After research confirmed this, I feel confident enough to proceed.

So onto my next question, do we know if backup compression is working? I remember it having some issues when the S4 was first released, but I'm not certain of they've been ironed out. I'm currently looking for the corresponding TWRP thread.
[AT&T Samsung Galaxy S 4 Android Development] ddubz:
usb not working after update

updated to 4.3 rooted and installed safestrap 3.70 and usb works for uploading to pc but i cant download anything to phone or to ext. sd card.

i get error saying phone cant find any software on pc that recognizes phone. Pc says can't copy, device has stopped responding or has been disconnected. Can any one help me with this
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
I highly doubt that has anything to do with Safestrap. Have you tried downloading Kies or better yet tried using Kies Air?

Edit

: If you're on Hyperdrive like your info indicates, you need to read and post in that thread as it's unrelated to Safestrap. If you're not, more information is needed.

Just for kicks, have you tried changing your USB connection mode?

Sent from my Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] ddubz:
just like i said i am on ucuemk2 stock rooted with safestrap 3.70 installed no of my sig thats all old stuff

---------- Post added at 10:44 PM ---------- Previous post was at 10:39 PM ----------

i have tried kies with my old one but have read it may need to be reinstalled for 4.3 i will try reinstalling and i have never used kies air. i have always been able to plug phone into computer and it would install drivers just fine. i downloaded samsung usb drivers and installed anyways. like i said pc recognizes phone.

---------- Post added at 11:06 PM ---------- Previous post was at 10:44 PM ----------

never mind prob solved
[AT&T Samsung Galaxy S 4 Android Development] jasonyump:
Just a bit off topic but a thought for those wanting to use the stock GPE 4.3 ROM. Have you tried replacing the kernel included in the rom with the att MK2 one?

x
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
Safestrap doesn't flash kernels anyways, so that wouldn't make a difference.
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
Right. We're just flashing (I believe) carrier specific modules, not the actual kernel. The kernel resides in the boot partition which is locked down tight.

(You learn something every day! :) )

Sent from my Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
Just a thought..... could we push boot. Img manually before or after flashing the rom using adb/fastboot command or heimdall command....... instead of reboot system after flashing rom.......adb reboot download.....

SWYPED_FROM_S4_MF3_REDVENOM
[AT&T Samsung Galaxy S 4 Android Development] ddubz:
echoe rom art v7

Confirm echoe rom v7 att is working with mk2 and safestrap 3.70

On rom slot 1
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
It wouldn't make a difference. The only boot.img we can push are signed Samsung ones from I337 firmwares. We can't push the GPE kernel until someone figures out how to load up a kexec module.
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
Confirmed working X-Note from the i9505 forum.
[AT&T Samsung Galaxy S 4 Android Development] mdaudioguy:
ROM Slot 1 or Stock slot?
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
Slot 1
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
I tried this really quick...how do you like it??
[AT&T Samsung Galaxy S 4 Android Development] kalmoa:
No sound issues here. Just make sure to flash the MF3 KERNEL MODULE after your flash your ROM. I am currently using the MDOB ROM, the counterpart to goldeneye. Found here: http://xdaforums.com/showthread.php?t=2280556

Everything working flawlessly so far. Besides the fact that MDOB uses the stock kernel and Goldeneye doesn't, what's the difference in these ROMs?
[AT&T Samsung Galaxy S 4 Android Development] zeyoner:
Are you doing this with the phone booted into stock? I would assume that the commands would have to be entered while the phone is booted into the stock ROM/Base ROM not the SS ROM.
[AT&T Samsung Galaxy S 4 Android Development] haremmon:
MDOB is straight up AT&T stock with bloatwares (samsung, at&t, google) removed, I believe its in the description.

Goldeneye is based off the international i9505 Stock rom. (also bloatwares removed and few tads different here n there). Also in the description.
[AT&T Samsung Galaxy S 4 Android Development] zeyoner:
In other words kalmoa. Read the OP of each ROM next time.
[AT&T Samsung Galaxy S 4 Android Development] kalmoa:
Thanks for the clarification. My question was more geared toward the actual performance, which is why I mentioned the change in kernel. I realize they both have bloatware removed and both of them have almost identical features and possible add-ons. Besides that, is there a significant difference in one ROM that would be preferred over the other?

Sorry, I realized my question sounded too vague. As I stated above, it was more about performance and stability.
[AT&T Samsung Galaxy S 4 Android Development] zeyoner:
After using an other slot to flash SHOstock 2.2 (My favorite TW ROM) phone access via usb works. So it looks like it's something with [ROM] Google Edition 4.2.2 [Clean][Slim][280MB][2013.09.07]
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
I am very happy with the work that Hash (and others) did to make this happen. That said, I will probably not be using that feature for the obvious issue of limited storage. My GPlay Music alone takes 1.5 gb's, and I have few other apps I need that uses more than 4gbs... sad... But I will stick around in case of fix.
[AT&T Samsung Galaxy S 4 Android Development] kalmoa:
Was thinking of flashing that ROM instead of MDOB... would you recommend SHOstock over MDOB, and why?
[AT&T Samsung Galaxy S 4 Android Development] Phoneguy589:
Not sure if I'm doing something wrong. I installed the apk and opened the recovery with no issues. Stock is highlighted but when I choose a rom slot, it allows me to click on it and choose a data size but I don't see an activate button. The only thing highlighted is stock. I wanted to try to install a rom on my daughters s4 active. I did a nandroid of the stock rom that it came with. Do I install over stock or do I need to reinstall the recovery? Any help would be great.

Sent from my At&t Galaxy S4
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
You have to choose the size and create the slot before you can activate it. Do NOT flash the stock slot yet.
[AT&T Samsung Galaxy S 4 Android Development] Phoneguy589:
I do choose a size, 2gb, and the create slot button is Grey and doesn't do anything.

Sent from my At&t Galaxy S4
[AT&T Samsung Galaxy S 4 Android Development] rebel1699:
Do you have enough free space to support the size you chose?
[AT&T Samsung Galaxy S 4 Android Development] Phoneguy589:
It says free space 0.

Sent from my At&t Galaxy S4
[AT&T Samsung Galaxy S 4 Android Development] shmigadiga:
odex. I flashed rom, loki patch, then the safestrap patch and rebooted.
[AT&T Samsung Galaxy S 4 Android Development] rebel1699:
You do not have to flash the loki patch. It is just a waste of time. Loki has absolutely nothing to do with mf3 or safestrap. That is why flashing loki is not a part of the op instructions.
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
Ok there's the answer...you need to delete some apps, music, etc in your stock rom.
[AT&T Samsung Galaxy S 4 Android Development] loociddreemr:
I want this for my MDL on ATT as well. Doesn't boot as previously mentioned. After the splash screen, it stays black. I used this on my RAZR and loved it. I find it much more convenient and useful than other recoveries. I'm actually debating on getting taking the update just to use this.

Hash,

Can we find a work around?
[AT&T Samsung Galaxy S 4 Android Development] rebel1699:
Since the kernel you have is mdl, you would need an mdl modules.zip to flash to the roms in slots. Remember, this does not have kexec. It is all running on the internal kernel, so the modules need to match. Hash has also said he is working on a version for those with unlocked bootloaders that uses kexec. So essentially, it would be a propor recovery (on the recovery partition) and a multiple boot setup.
[AT&T Samsung Galaxy S 4 Android Development] upndwn4par:
[MENTION=4243514]Hashcode[/MENTION]

Thanks for bringing Safestrap to the S4. This is excellent work. Anyone who bought a MF3 device owes you a huge debt of gratitude.

Two questions:

1) Can you explain warning #2?

I don't understand your concerns about flashing stock MF3.

2) On your VZW thread there is a warning about "remove ongoing wifi notification". Does that apply to AT&T?
[AT&T Samsung Galaxy S 4 Android Development] rebel1699:
Im not hash, but i can help.

Rule #2 is explaining that if you are on mf3 and try to flash a rom to the stock slot, you will most likely brick your phone. If that happens, your only chance to recover is by taking it to best buy, if there is one near you, to have it completely flashed back to stock. There is no odin mf3 flashable for you to do it yourself at home like verizon has for me7.

I dont think the wifi ongoing notification applies to At&t.
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
I like it, not my favorite ROM but it's good. I do recommend it. Also restoring works fine with Titanium. Also I want to point out someone besides myself suggested using Helium if you can't restore app data with Titanium. That app worked great for me :)
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
I like Hyperdrive RLS11, but being on AT&T there were some dialer/number storage issues since there's currently no compatibility pack for it. Basically, it sees and makes local numbers/local calls as if they were international.

Sent from my Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] mdaudioguy:
Wish I'd noticed the lack of a compatability pack before I made the leap, although I'm not sure what the issue is. Running Hyperdrive RLS11 in stock slot and everything *seems* ok... Calls and texts are coming in and going out. Everything else seems fine, too. I'm spending some time getting used to this ROM, since it's new to me.
[AT&T Samsung Galaxy S 4 Android Development] Psych0t1c20:
So if we want to use the new version of SS we have to first upgrade to MK2? Kinda confused.
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
Yes
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
4.2.2 already has a stable version. The test build is MK2 only, you do not have to update. Hashcode will probably update it for kexec, but if not wait for the next release.
[AT&T Samsung Galaxy S 4 Android Development] Galaxy*$4:
try fixing your apn settings i had the same issue but on 4.2 (didnt have a compatibilty pack) and it fixed mine
[AT&T Samsung Galaxy S 4 Android Development] jh64dsb877r:
Anyone looking through the thread for the MK2 modules, should check out post #838. It's pretty far back in the thread, so probably worth reposting (took me awhile to find it).

Be sure to thank Easton999GS.

Remember, the modules won't do you much good unless you're also on MK2 and testing Safestrap 3.70.
[AT&T Samsung Galaxy S 4 Android Development] nsnsmj:
Now I've searched the thread, read plenty of posts, and even watched some videos about safestrap, but I can't seem to find the specific answer I'm looking for (it's possible I might've overlooked something). I understand how safestràp works and how to install it. The ROM slot sizes; 3GB being the max(?); is that 3GB all the available space I would have for internal storage (for apps) with that ROM?
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
I'd already changed the APN before I noticed it. I received incoming calls fine, the number was just formatted oddly. It was when I tried to call out to a number that was stored in the format Facebook and Android uses that would give me that issue. I'll screenshot it next time I attempt to flash it.

Back on topic, one odd thing I've noticed with this version of Safestrap is ROMs like Goldeneye that claim to use stock kernel and should work with SS, still don't. Hyperdrive and DarthStalker are the only two that seem to work, and I don't care for DS at all. It's really just heavily themed, no mobile data toggle, even. Maybe this issue is purely on the ROM side, but I've even tried to remove the Loki from the zip and flash to no avail.

I've run into that issue as well. I'm guessing a lot of users either have the 32GB version or have an ExtSD they use for apps. My ExtSD barely has 2 GB free because of all my music, so I basically use the ROM Slot to verify that a given ROM boots, then flash to Stock Slot if I like it. A lot of people claim Hyperdrive deletes Safestrap when flashing to the Stock Slot, but that wasn't my experience with it. Whatever you do, have a backup of your Stock ROM (compression does work) and make sure you flash a ROM that you're certain boots when flashing to the Stock Slot. Good luck.

Sent from my Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] HORiZUN:
Yes and no. If you install a ROM to a slot (1 or 2), then yes. If you choose to install your ROM to the stock slot, you'll have all the total free space on your device minus the size of the ROM. Flashing to stock is more risky, but has a better payout for the extra GB's in my opinion. It's all up to you. Both ways of using SafeStrap have pros and cons.
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
Maybe try earlier GoldenEye_v12_MJ9 base or MKE base......see if that work.....both is TW4.3_LOKIED stock kernel.... DarthStalker also use Lokied kernel when u flash ATT pack with Aroma installer.....

SWYPED_FROM_S4_MF3_REDVENOM
[AT&T Samsung Galaxy S 4 Android Development] haru3173:
Sorry Im a bit outdated. I'm still on mf3 and I want to know how people where able to get to mk2 and get safestrap working on mk2?
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
Don't worry about it. Your better off with mf3.. for now.. not enough roms work with mk2 ss to want it.
[AT&T Samsung Galaxy S 4 Android Development] ceelo2008:
Does this rom have bluetooth tethering?

---------- Post added at 01:17 AM ---------- Previous post was at 01:15 AM ----------

Anyone know of a room that works with new safe strap and has bluetooth tethering
[AT&T Samsung Galaxy S 4 Android Development] ravi_mytouch:
Safestrapped 3.7 beta. Flashed darthstalker x to rom slot 1.

On tmobile rom, Wifi has not worked at all. When I turn wifi on, it just hangs. I have flashed the att kernel module after flashing the rom.

In att version, wifi takes a long time to connect. Hangs sometimes. Prompts for password every time to connect.

I flashed the att kernel modules after both versions after installing the rom.

Please help.
[AT&T Samsung Galaxy S 4 Android Development] yubby:
hyperdrive Bluetooth tethering works
[AT&T Samsung Galaxy S 4 Android Development] nsnsmj:
Thank you both!

I didn't realize I could flash over the stock slot. Guess I did overlook some things. That would definitely be the ideal method for me then as I'd rather have that extra space. Again, thanks.
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
Merry X'mas everyone. ....... have a joyful holiday

SWYPED_FROM_S4_MF3_REDVENOM
[AT&T Samsung Galaxy S 4 Android Development] mswal2846:
SS 3.7

So I see that 3.7 is in test. Will 3.7 just work on MF3 or only after we upgrade to 4.3?

I've been avoiding booting up my Stock ROM to prevent the upgrade which wants to kickoff automatically.

I currently have Graviton and am quite happy with it I presume that if I let the Stock ROM upgrade, I won't be able to run 4.2.2 Graviton? I would have to go to 4.3 Graviton (or something)?
[AT&T Samsung Galaxy S 4 Android Development] NighthawkXL:
3.70 is designed for Android 4.3, your best staying on 3.65 and using your Graviton as-is for the time being...
[AT&T Samsung Galaxy S 4 Android Development] HORiZUN:
Many of us are staying on MF3 until compatibility with more roms improves on the 3.70 beta.
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
Mmhmm... and Marry Christmas you all :)
[AT&T Samsung Galaxy S 4 Android Development] ddubz:
bluetooth tethering

yes it has bluetooth tethering
[AT&T Samsung Galaxy S 4 Android Development] NighthawkXL:
Couldn't have said it any better myself, I want 4.3, and by that extension 4.4 but I'm content hanging back on 4.2 until things get worked out around here. Hopefully after the holidays we'll see a resurgence in development. I'm sure both Hashcode, and folks like Surge (who's working on the bootloader) are busy with other things for the next few days.
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
I agree. Hyperdrive has a supposedly Safestrap compatible version of RLS12, unfortunately it's not currently booting... at least for me.

Sent from my Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] hovax615@hotmail.com:
Did you download it from the Verizon page under safestrap download link?