yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] KryptosXLayer2:
My steps performed just now:

Odin NB1 using filename ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.md5 which should be overwriting the problematic SS recovery

Waited for NB1 to boot, restarted device in Download mode

Flashed ONLY the AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 and CSC_ATT_I337ATTEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 files to boot MK2

Rooted MK2 using SafeRoot, following each of the steps after it rebooted, all the way to the end of the command window

Installed Safestrap-JFLTEATT-3.71.apk, installed recovery

Rebooted to recovery.....

.

.

.

.

SAME problematic SS recovery

What do I need to do in order to completely wipe recovery and get a working SS on my device?
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
[MENTION=674617]KryptosXLayer2[/MENTION] I believed that only for downgrade to MK2 .....u need full NB1 odin posted by [MENTION=4708661]muniz_ri[/MENTION] from the link that I sent u earlier or here the mirror link http://d-h.st/1O8 ....u need to start from scratch and reboot to stock recovery.....do factory reset.... reboot to system.

Swyped From MK2 Dark Venom SS Edition
[AT&T Samsung Galaxy S 4 Android Development] KryptosXLayer2:
Conflicting statements, you said that the NB1 md5 file I listed in step one is what I need to start with, but the way I just listed those steps was for downgrading to MK2, which is the same thing, right? What am I not understanding?

EDIT - okay, I think you mean that I need to follow your steps in the first post instead of the ones in the fourth post, and flash the PIT and AP files, then reboot into stock recovery and factory reset, right?

---------- Post added at 02:40 PM ---------- Previous post was at 02:08 PM ----------

Followed everything you said, [MENTION=2284570]ted77usa[/MENTION], I'm STILL getting the wrong recovery booting up.... SS is not coming up on this device, just the TWRP even after flashing NB1, flashing PIT and AP files, rebooting to stock recovery and doing a factory reset, rooting using SafeRoot, and installing SS 3.71

How can I go even further back than this to destroy whatever messed up recovery I'm seeing in the system? SS is just not loading and I can't figure out why.... [MENTION=4243514]Hashcode[/MENTION], any thoughts on this?
[AT&T Samsung Galaxy S 4 Android Development] dave5777:
Did you Odin the all in one nb1 tar? That will wipe everything except microsd.
[AT&T Samsung Galaxy S 4 Android Development] KryptosXLayer2:
Yes, file name is ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.md5, that's what I've been working with since the beginning
[AT&T Samsung Galaxy S 4 Android Development] dave5777:
[MENTION=2284570]ted77usa[/MENTION] what would selecting repartition in Odin do? Something on his system is not getting wiped.
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
[MENTION=2924695]dave5777[/MENTION] Technically YES. .. but [MENTION=674617]KryptosXLayer2[/MENTION] need to load PIT files for NB1 NOT MK2 PIT file and I dont think I have NB1 PIT file. ....maybe someone else do... [emoji85] I think for now try to get back to stock NB1 first via ODIN from [MENTION=4708661]muniz_ri[/MENTION] NB1 Full ODIN tar thread And then before reboot to system do Full wipe/factory reset couples time from stock recovery and then reboot to system see if that would get him back to stock NB1 first.

Swyped From MK2 Dark Venom SS Edition
[AT&T Samsung Galaxy S 4 Android Development] KryptosXLayer2:
Isn't the point of flashing the MK2 files on top of NB1 to trick it into thinking it can use custom recovery and flash a rooted NB1? I can get to stock NB1 with no problem, my goal is to get SS working to flash other ROMs
[AT&T Samsung Galaxy S 4 Android Development] dave5777:
Yes, I don't know if you're familiar with Einstein's definition of insanity, I think you need to start fresh and go back to stock unrooted nb1 and then downgrade again.
[AT&T Samsung Galaxy S 4 Android Development] KryptosXLayer2:
After this weekend, I'm VERY well versed in that definition! :cool: Working on it for 7 hours Friday night, 5 hours last night, and off and on in order to not lose my mind today, so yeah, this has pretty much wrecked my weekend....

I'm on NB1 right now, booted up at the first screen - problem with your thought of downgrading (do you mean the first post or the fourth post when saying "downgrading," specifically?) is that I've done both now about a half dozen times each.... continuing to do either will certainly drive me insane!!!
[AT&T Samsung Galaxy S 4 Android Development] Maribou:
You seem to have a themed version of SS TWRP, I am going to assume that the theme you have is what is causing SS TWRP to look like that.

Because SS recovery should not look anything like that. Have you tried not using the theme?

Also, I have never themed TWRP before, but I would assume it stores the theme data on your SD card/Cards . Might be worth looking into.
[AT&T Samsung Galaxy S 4 Android Development] KryptosXLayer2:
You are correct in assuming I've used a theme before with TWRP, and this absolutely is something worth looking into.... I've removed my MicroSD from the device to see if the downgrade process may finally work when TWRP isn't trying to access the theme from the Ext SD card, great idea and hopefully this will work! Will report back shortly....

---------- Post added at 06:22 PM ---------- Previous post was at 06:03 PM ----------

I truly cannot believe it, [MENTION=4980764]Maribou[/MENTION] was absolutely right in assuming the theme in TWRP on my external MicroSD card was causing the issue - downgraded to MK2, rooted, and installed SS for the LAST TIME (hopefully, fingers crossed, hah) and when it rebooted into recovery, it looked like SS normally should with the Boot Options section!

HUGE thank you to [MENTION=4980764]Maribou[/MENTION], good looking out!!! :good: :good:

I think this should also be brought to [MENTION=4243514]Hashcode[/MENTION]'s attention, as it may be an issue for those who have a themed TWRP on their external MicroSD card trying to get SS running - or maybe I'm the only idiot theming TWRP, who knows, haha
[AT&T Samsung Galaxy S 4 Android Development] Maribou:
Glad to see you got it figured out bro. :good:.
[AT&T Samsung Galaxy S 4 Android Development] Dhs92:
Bit lost on the bootloader race, where are we at right now progress wise?

Sent from my PurifieD Galaxy S4
[AT&T Samsung Galaxy S 4 Android Development] NighthawkXL:
There are a few theories being floated around over in the Verizon forums, but nothing concrete yet. For the most part the reason we aren't seeing a sort of "progress report" is due to the nature of the project. We wouldn't want to tip Samsung off that we are nearing a exploit only to have it closed in some rushed OTA update. [MENTION=4939386]Surge1223[/MENTION], and [MENTION=766721]ryanbg[/MENTION] are the one's spearheading most of the work with help from others in the community like [MENTION=2471504]jeboo[/MENTION] among others. I suggest subscribing to this thread...

Progress on kexec for Safestrap is apparently ongoing but Hashcode is working on multiple projects, give him some time. Last we heard there was a issue flushing the cache.

An here we are today, while all of this work is being done we find the process that allows us to run 4.4.2 ROM's on a base MK2 (4.3) platform. It's certainly getting interesting around here, hopefully a breakthrough is only a matter of time.
[AT&T Samsung Galaxy S 4 Android Development] Dhs92:
Interesting.. Thanks for the reply

Sent from my PurifieD Galaxy S4
[AT&T Samsung Galaxy S 4 Android Development] Galaxy*$4:
thats some good news, but wouldnt people on custom roms be fine if samsung was to rush an update to us?
[AT&T Samsung Galaxy S 4 Android Development] endofwed:
I successfully installed a google edition 4.2.2 rom on slot 1 but when i tired to go back to the stock rom, it loads a black screen...(no lights, no anything, i think it pretty much just shuts down)

Did i brick my stock rom?

any help?

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

steps i took:

(i activated the stock rom, then i went into reboot menu and restarted it, i get then the safestrap: disabled screen, it then proceeds to a black screen)

I have mf3 and am using safestrap 3.65

what would happen if i do a wipe (factory reset to clear the data,cache, and dalvik) on the stock rom. will this fix the problem?
[AT&T Samsung Galaxy S 4 Android Development] tmaddison93:
safestrap says that installled correctly and i see installed on there but when i hit boot recovery it goes to lock screen and then boots normally. what did i do wrong? i have samsung galaxy s4 sgh-i337. is there another method where i can get it to boot to install the stocked root. i am on mk2 now and i am rooted
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
Yes, but if they're checking in then A) they could quickly sneak an OTA to everyone before we get a chance to get on a custom ROM, and B) They could still patch it in the Verizon update.
[AT&T Samsung Galaxy S 4 Android Development] gwell1:
I have a dumb question. I am running 4.2.2. Mf3. Can I install a rom thats based on 4.3?
[AT&T Samsung Galaxy S 4 Android Development] endofwed:
as of right now, no.
[AT&T Samsung Galaxy S 4 Android Development] l Frosty l:
At my best buy they don't care. They only care when someone tries to return or exchange it. That's when its a whole nother issue
[AT&T Samsung Galaxy S 4 Android Development] slyguy2000:
No will not void warranty if you take it to Best Buy...
[AT&T Samsung Galaxy S 4 Android Development] ceo.mtcl:
Delete. wrong section.
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
I see your signature, i537...is this the phone that bricked?

If you flashed on a s4 active, yes you will brick...

---------- Post added at 10:21 PM ---------- Previous post was at 09:42 PM ----------

Bobocat rom from i9505 forum works great, no issues no setting apn settings up...have root..
[AT&T Samsung Galaxy S 4 Android Development] customhdrider:
Works like a charm! Thanks for all involved with this and for sharing it with the community
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
Downloads section has a new Safestrap version:

Safestrap-JFLTEATT-3.6x-B09.apk

CHANGELOG:

No more wipe error on /cache

Reworded the /boot not found message as INFO

Boot partition should be protected in stock now. (In past versions, a boot.img file in a .zip being flashed to stock would overwrite the actual boot partition and force the use of ODIN to restore the stock boot partition).

3rd and 4th CPUs are reattached correctly after 2nd-init (this was reflected in lower benchmarks)

Installation scripts were debugged a bit. But still seeing some users not getting a clean uninstall. :/ I'll work on this more.

TWRP update to 2.6.3.0 (See change log here: http://www.teamw.in/project/twrp2). And if you like TWRP don't forget to let them know.

From a local build stand point, this update was HUGE for me. I redesigned how the recovery files are built in order to support / maintain more devices in a better manner. This portion was not reflected in the change log but hopefully helps keep the builds consistent across several devices in the same family (VZW, ATT, ATT-ACTIVE).

INSTRUCTIONS FOR UPGRADING

Boot to your stock ROM

Install the new APK via file manager

Make sure to agree to the warning about replacing the existing APK

Once you're in the new APK (you'll note 3.60 in the lower left corner), use the "Install Recovery" button.

That's it. Now you can reboot into recovery and go right back into your ROM slot.
[AT&T Samsung Galaxy S 4 Android Development] jan g:
hi hashcode

thanks great work bro.. wolking fine for me.....i testing all new funtions

(wipe and delvi cache, work fine

deletet slot ,fine

intal rom ,fine

remplacing apk .fine

go back stok rom. fine.

ect..

super great work thanks.....:good:
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
Omega works great. Love this rom!
[AT&T Samsung Galaxy S 4 Android Development] jt1998:
So I want to try install a customer rom and recovery for the first time. I'm a newbie and iPhone convert. I've done a custom ROM & root with my android Asus infinity tablet and it went fine. I'm a little nervous about this phone since it just seems more difficult as I have the Mf3 s4 from AT&T.

Since I need to put in SD card into the s4, is there a size that is recommended? I purchased a 64 gigabyte one, but it hasn't arrived yet.
[AT&T Samsung Galaxy S 4 Android Development] mrro82:
64 is a good size but it has nothing to do with SS besides where you can store your roms for flashing to save room on the internal.
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
You should not be in this thread. You need to read the "pinned" threads in the General and Q&A sections to learn about your phone first. The fact that you are asking about an external SD card in this thread tells me that you shouldn't be doing ANYTHING to your phone yet. You said you were a noob so I suggest you take my advice and then, after learning about your phone and what it is you are doing to it, come back here and enjoy the development section. You will be glad if you do so and you will regret it if you don't. Good luck.
[AT&T Samsung Galaxy S 4 Android Development] jt1998:
I have been reading. I understand the SS works w internal storage just asking about my external SD card too like above poster answered.

Samsung -SGH -I337UCUMF3 4.2.2. stock/unrooted
[AT&T Samsung Galaxy S 4 Android Development] trikar21b:
[deleted]
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
I posted this on the at&t active Safestrap thread but figured, I should echo this to all the dev threads.

---

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

- Customizable partition sizes (system, data and cache)

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

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

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

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

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

And, of course work on kexec to get custom kernel support.
[AT&T Samsung Galaxy S 4 Android Development] kejar31:
Hash as always is "The Man"... Nice to see you around these parts man :)
[AT&T Samsung Galaxy S 4 Android Development] Rosbif22:
Installed and everything seems to have worked fine. However, it would appear that I lost root and can't figure out how to get it back. Am using Alpha ROM 8.5.
[AT&T Samsung Galaxy S 4 Android Development] azz72:
so for the first time i did the rom slot and wiped everything. i installed the rom {blood vemon} with the mf3 kernal and all i get is the damn the samsung s4 screen.. so is it soft brick or is there anything i can do
[AT&T Samsung Galaxy S 4 Android Development] trikar21b:
Is the reason why 4.3 ROMs won't work because we don't have an official kernel from AT&T and Samsung for 4.3?

Also, why won't CM 10.1 work?

Love the Google Edition ROM on this though!! Almost convinced to not sell my S4 for a Nexus 5 when it's announced. :) We'll see what the future holds.
[AT&T Samsung Galaxy S 4 Android Development] rebel1699:
4.3 roms wont work (if youre on a locked mf3) because the stock mf3 kernel is not compatible with them. CM 10.1 will not work for the same reason. Its all about kernel compatibility. However, there are a few devs trying to build a custom 10.1 that IS compatible with the stock kernel. How long it takes, we just cant know.
[AT&T Samsung Galaxy S 4 Android Development] l Frosty l:
Either you:

A: Deleted the wrong slot labeled "Stock ROM"

or

B: Are using an incompatible ROM

However im going with Option A.

You will have to get it (assuming im right) restored via ODIN through a BestBuy that has the Samsung Experience Center.

---------- Post added at 11:48 PM ---------- Previous post was at 11:43 PM ----------

Sounds like your ROM doesn't inject Root . Check the OP of your ROM and see what they say to do. Or Just reroot it as you did before and get SuperSU
[AT&T Samsung Galaxy S 4 Android Development] cave.man1908:
I would like to think that even though SGH-I337 is locked down as tightly as it is, I just don't see development for it dropping off the face of the earth as so many speculate so freely throughout the s4 threads, specifically AT&T threads. Im no developer past the basics, but it does instigate me to dive right into madness of the android world.

Rather than throw in the towel we must persevere and rise to the challenge knowing we come nothing short of success.

I mean c'mon right, who doesnt like stickin it to the man:cool:
[AT&T Samsung Galaxy S 4 Android Development] Weazmeister:
Heh, so I screwed up. I tried to use Shostock 5.0 with the instructions provided to use current safestrap, flash the shostock, flash mldmodules, then odin the tar files provided however it doesn't boo. Here's the screw up part, I formatted partition and now am not able to restore the restore I created. I can't ODIN the 4.2.2 because safestrap is still there and causing problem, how can I wipe it out completely so can ODIN back to the 4.2.2 tar files
[AT&T Samsung Galaxy S 4 Android Development] dave5777:
I you Odin the all in one tar it will wipe everything including safe strap.
[AT&T Samsung Galaxy S 4 Android Development] Weazmeister:
I must have downloaded the wrong one, because I kept on erroring on it. Will re-try download and odin. thanks for the quick reply.
[AT&T Samsung Galaxy S 4 Android Development] dave5777:
Make sure you use the one that matches your kernel. If you took the nb1 update then use nb1 otherwise use mk2.
[AT&T Samsung Galaxy S 4 Android Development] endofwed:
is this the thead your referring to? (1.40 GB)

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

on the qbking website, they also provide a link for the mf3 tar file but it seems to be a different size (1.59 GB)

http://qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4/
[AT&T Samsung Galaxy S 4 Android Development] dave5777:
You never said what Firmware you are on, those tars are both for mf3.

MK2 if that's your Firmware use the All In One http://xdaforums.com/showthread.php?t=2621279

NB1 if that's your Firmware use the stock Odin Tar http://xdaforums.com/showthread.php?t=2674223
[AT&T Samsung Galaxy S 4 Android Development] endofwed:
sorry, i forgot to mention Im running the mf3 firmware
[AT&T Samsung Galaxy S 4 Android Development] dave5777:
You can just odin the MK2 if you can't get MF3 to go. No real advantage staying on mf3.
[AT&T Samsung Galaxy S 4 Android Development] Weazmeister:
Loving the use of SafeStrap to be able to flash 4.4.2 ! Very nice work to the devs that figured out the updater-script and the odin flashing to make it work! Blissfully running Samy Deluxe!
[AT&T Samsung Galaxy S 4 Android Development] rebel1699:
Thank you, and you are welcome. No way I could have done it without the brilliant Safestrap.

Multirom driven Nexus 7
[AT&T Samsung Galaxy S 4 Android Development] Galaxy*$4:
guys does anybody else have this problem i am running this rom which is pretty great http://xdaforums.com/showthread.php?t=2671851&page=9

but the issue i am having is numbers show up xx-xx-xx-xx-xx or like this+xxxxxxxxxx (with no name) instead of like this xxx-xxx-xxxx which is in my phone book. i have had this issue before running non att roms but i always fixed it not sure how i did it though, i got the correct apn from http://xdaforums.com/showthread.php?t=2616221

any ideas phone is set to English

edit, i flashed a tmobile rom, and it showed up like normal so i copied the build from it and pasted over the rom above and it still did the same nothing changed.
[AT&T Samsung Galaxy S 4 Android Development] kevinco1:
Good news, Hash will be releasing an updated version of Safestrap for KK this week....

https://twitter.com/Hashcode0f

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

Ohhh and 16GB slots, YES!!
[AT&T Samsung Galaxy S 4 Android Development] siccfckk:
April fools or what Lol:rolleyes::cool:

Sent from my GT-I9505 using Xparent Skyblue Tapatalk 2
[AT&T Samsung Galaxy S 4 Android Development] dave5777:
No, if you read his Twitter he's been working on Safe Strap last few days ?
[AT&T Samsung Galaxy S 4 Android Development] guut13:
Hyperdrive ROM has a compatibility pack that resolves that issue. Have no idea if it would work on another ROM, but if you are out of ideas you can try flashing it.
[AT&T Samsung Galaxy S 4 Android Development] Maribou:
http://xdaforums.com/showpost.php?p=51574460&postcount=819

Sent from my warranty voided device.
[AT&T Samsung Galaxy S 4 Android Development] Galaxy*$4:
i have that file in my phone but every time i flash it it messes it up, but i think thats also because it may be an older file meant for mf3? just downloaded the file and found out the old one is a 2013 file. thanks for telling me to check that, now i got to flash a rom to a slot (if its works well i will see about using it on my stock slot.
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
Yeah, the Compatibility pack is for 4.3 and doesn't work on 4.4.2. For the record you can't install a 4.4.2 ROM into a slot because Safestrap can't mount it so it won't boot.
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
I'm working on KK support for the S4's today / tomorrow. So I'll keep you posted.
[AT&T Samsung Galaxy S 4 Android Development] Maribou:
This is great news! Thanks again Hash. :D
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
[MENTION=4243514]Hashcode[/MENTION] This is awesome news.... [emoji106] btw since we don't have 4.4 Root method yet only downgrade method to keep root, are you going to modify mount/system on 2nd int'd script per your conversation with my team mate [MENTION=833788]rebel1699[/MENTION]? since after downgrade method we won't be able to mount/system ?

Swyped From MK2 Dark Venom SS Edition
[AT&T Samsung Galaxy S 4 Android Development] t4duzan:
This being April the 2nd, I'm taking that as no joke. Glad to hear of the development for a new SS!
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
Yes, the mount/system is modified for the KK hijack. And system mount is now fixed in Safestrap KK versions.

Would you like to test a new SS build for those running NB1/KK?
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
Yes, the mount/system is modified for the KK hijack. And system mount is now fixed in Safestrap KK versions.

Would you like to test a new SS build for those running NB1/KK?

Right now it only supports flashing to stock, as I need to do some further debugging on rom-slot mounts.
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
Awesome ..... [emoji106] [MENTION=4243514]Hashcode[/MENTION] absolutely Sir.... me and my team mate [MENTION=833788]rebel1699[/MENTION] would love to test it for u.

Swyped From MK2 Dark Venom SS Edition
[AT&T Samsung Galaxy S 4 Android Development] rebel1699:
[MENTION=4243514]Hashcode[/MENTION] could you send me the test build as well? [MENTION=2284570]ted77usa[/MENTION] is usimg mld files method, and i use the nb1 files method. Might be good to test for both.
[AT&T Samsung Galaxy S 4 Android Development] Galaxy*$4:
thank ya, i guess i should update that file, didnt figure i had to. but all is well, and my phone works now. any idea why that is?

i also get incorrect puk code at boot up, but then it goes away shortly after. not sure why that is (on a clean rom with nothing on it)