yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 General] ted77usa:
I wish I could ....that would make alot of MK2 users happy.... including me....:thumbup::D:thumbup:.....but we might have new method to install 4.4 Kitkat using SS.....me and [MENTION=833788]rebel1699[/MENTION] been working on it for couples day.....PM me if u guys would like to try it when is ready .....:thumbup::cool::thumbup:

Swyped From MK2 Dark Venom SS Edition
[AT&T Samsung Galaxy S 4 General] Kamaole:
Is it not already possible?
[AT&T Samsung Galaxy S 4 General] waqas.qamar:
Can we downgrade to MK2 with guide and then use odin to flash full MK2 package again to have official FNB1 4.4.2 when root would available for FNB1.?
[AT&T Samsung Galaxy S 4 General] rebel1699:
Not yet, no. If you are fully upgraded to mld, you have no root, and ergo, no safestrap. [MENTION=2284570]ted77usa[/MENTION] and i are working on a way for people that currently have an mk2 bootloader to load custom prerooted 4.4 roms through safestrap.
[AT&T Samsung Galaxy S 4 General] Kamaole:
Oh I got ya. Your working on a way to install without ever upgrading in the first place.
[AT&T Samsung Galaxy S 4 General] :
So we would be able to go into SS and flash a custom 4.4 rom?
[AT&T Samsung Galaxy S 4 General] atomicspaceindian:
Thanks for the quick reply. I would be delighted to help. Plus, Safestrap doesnt install kernels, so you would either be already on 4.4 or you cant do anything...
[AT&T Samsung Galaxy S 4 General] Maribou:
The downgrade method keeps parts of 4.4. So if you tried to flash the full MK2 odin package it would fail.

It is not possible to have a full downgrade at this point in time.
[AT&T Samsung Galaxy S 4 General] DeadlySin9:
You'll have to sideload the OTA to go back to 4.4. Since it isn't a full downgrade you'll have to use the unbrick method in this thread.

Well we can downgrade to MK2 to get root and safestrap, and we have the kernel extracted already so that won't be an issue. We can just flash ROM and then head into download mode to flash the kernel.
[AT&T Samsung Galaxy S 4 General] rebel1699:
Exactly. I have the odin packages built, and will be ready for testing tonight or in the morning.
[AT&T Samsung Galaxy S 4 General] waqas.qamar:
Thanks man if i downgrade it and then i will easily go back to FNB1 by sideload just or use unbrick method to go back to FNB1?
[AT&T Samsung Galaxy S 4 General] :
So if I understand what youre saying, rooted mk2 users will be able to install a 4.4 rom via SS?
[AT&T Samsung Galaxy S 4 General] DeadlySin9:
I believe you'll need the whole unbrick method. Make sure to back up your data and internal storage first.

I say you'll probably need it because the downgrade doesn't include the modem and i don't believe it includes the cache either.

If you do want to try it manually and possibly not lose data, you'd have to flash the CP MK2 TAR, and then the unbrick part 2 tar to downgrade modem and cache. No guarantees that it will work though.

I believe you'll need to take the 4.4 update through sideload or OTA first in order to get the 4.4 bootloader which will trust the kernel. Though as we've established you can downgrade the system to MK2 and restore a backup of whatever you were running.
[AT&T Samsung Galaxy S 4 General] rebel1699:
Thats the plan. Still have a lot of testing to do.
[AT&T Samsung Galaxy S 4 General] :
What type of roms would we will be able to flash? Touch wiz based?

I see. But isn't that when you downgraded you lost wifi or sound?
[AT&T Samsung Galaxy S 4 General] dave5777:
I downgraded and I'm running black box with sound and Wi-Fi :)
[AT&T Samsung Galaxy S 4 General] DeadlySin9:
Only TW based, since it's still the stock kernel as usual. And as Dave said we can get Wi-Fi and sound and all.

Sent from Black<3's I337 running Foxhound ROM
[AT&T Samsung Galaxy S 4 General] :
Wouldn't I be able to flash touchwiz based roms on 4.3 already? Does it make a difference that you're on the international version though?

I been curious about testing out new roms. And since SS appears to let you have slots, I might as well give them a try
[AT&T Samsung Galaxy S 4 General] rebel1699:
He is not on an international version. The prop file for the black box rom just has it listed as a GT-i9505. Safestrap does not work on international models or doestic carrier models with an unlocked bootloader.
[AT&T Samsung Galaxy S 4 General] Kamaole:
Discovered something kind of odd. So I decided to try and upgrade back to 4.4.2 after downgrading and read that the best way to do it was use the unbrick method, then take the update.zip. After flashing the first part, my phone completely booted, I was still rooted, and my wifi worked without using bypasslkm (I patched it once the last boot but not after). What could be the cause of this?

Edit: Rebooted again, wifi's still working, checked bl version, still nb1 (no surprise there)

Edit again: Root was actually lost, just had supersu still installed.
[AT&T Samsung Galaxy S 4 General] muniz_ri:
Are you saying that you booted into NB1 and were able to keep root access?
[AT&T Samsung Galaxy S 4 General] Kamaole:
No, my phone booted into mk2 after flashing the 4.4 unbrick part 1 tar, and my phone connected to wifi without having to use the bypasslkm workaround
[AT&T Samsung Galaxy S 4 General] muniz_ri:
nvm, forgot that the unbrick file contains mk2.
[AT&T Samsung Galaxy S 4 General] DeadlySin9:
That's nothing special. Since the downgrade method already had the system, that has no effect. It also flashes the modem, which we know gives it WiFi. Now, if you also kept sound and phone usage, then that might be new. Though that shouldn't make sense, as that's the same as flashing the AP and CP package when downgrading which is what we did originally. So if sound and phone are both working correctly, then that's and interesting development. Otherwise, it's already known information.
[AT&T Samsung Galaxy S 4 General] Kamaole:
Well in that case... nevermind. My audio has gone to **** after downgrading from mld to mk2 and was never fixed after that.
[AT&T Samsung Galaxy S 4 General] dave5777:
After taking the nb1 update and then using the mk2 downgrade method and ran SS I was able to use the nb1 unbrick to get back to stock. In case anyone has reservations about flashing pit files. :) I'm going to sell this locked down pos and get a nexus 5.
[AT&T Samsung Galaxy S 4 General] Maribou:
I don't know if this will matter or help anyone but I downgraded to MK2, and installed Hyperdrive on the stock slot.

I then added the bypasslkm file to the /system/etc/init.d/ folder and edited the install-recovery.sh.

Hyperdrive boots right up, and connects to WiFi with no problems.
[AT&T Samsung Galaxy S 4 General] ted77usa:
I337UCUFNB1 4,4 Stock Odin Tar & System Dump

OP UPDATED.....Added [MENTION=4708661]muniz_ri[/MENTION] I337UCUFNB1 4,4 Stock Odin Tar & System Dump.....:good:
[AT&T Samsung Galaxy S 4 General] cnewsgrp:
I am thinking same. Will probably hold on for few days. Disappointed with Samsung.
[AT&T Samsung Galaxy S 4 General] Maribou:
Deleted. Because I was being rude and it was uncalled for. I apologize.
[AT&T Samsung Galaxy S 4 General] dave5777:
I didn't say that Samsung made it a pos. I agree it's all att. I only paid $36 for mine. When I got mine it was when they where pushing mf3 and Loki still worked on MDL but mine came with mf3. I've been around XDA long enough to know to do research before I buy a phone.

Moral of the story never buy a carrier branded phone.
[AT&T Samsung Galaxy S 4 General] Maribou:
Yeah, I knew when I bought it that it was going to be locked down, and my next purchase will be an unbranded like you said.

I just see a bunch of post about how much people hate this POS and I'm like WTF?

This phone is amazing! :D

---------- Post added at 10:16 AM ---------- Previous post was at 09:49 AM ----------

Working great.

Was on the MK2 downgrade method, and updated using [MENTION=4708661]muniz_ri[/MENTION] 's 4.4 Odin tar.

Thanks guys. :good:
[AT&T Samsung Galaxy S 4 General] Michael3214:
[MENTION=2284570]ted77usa[/MENTION], just wanted to thank you and whoever pulled the debrick.IMG in the attempt to help me recover my brick. I tried multiple combos, but I haven't been able to resurrect it from its current state of qhsusb_dload. And just to clarify, what I flashed had nothing to do with any of the zips/tars available in this thread. Looks like its going to a service center.
[AT&T Samsung Galaxy S 4 General] Maribou:
Sorry to hear that buddy. :(

Hopefully you can get everything sorted out, and get back to hacking away at the replacement. :)
[AT&T Samsung Galaxy S 4 General] ted77usa:
[MENTION=2231960]Michael3214[/MENTION]

Thanks to [MENTION=833788]rebel1699[/MENTION] that pulled Debrick.img for u.....and he might have another method that might help you.

Swyped From MK2 Dark Venom SS Edition
[AT&T Samsung Galaxy S 4 General] cnewsgrp:
Edited. Apologies for posting off topic.
[AT&T Samsung Galaxy S 4 General] Maribou:
All I was saying is I have seen so many people calling this phone a POS, and it's not the phones fault. I wasn't trying to be rude, and looking back at it I guess my comment was. I apologize for that. Let's just move forward and enjoy what we have.

:)
[AT&T Samsung Galaxy S 4 General] Michael3214:
I appreciate all the help. [MENTION=833788]rebel1699[/MENTION] thanks for the .IMG file. Always willing to try another method.
[AT&T Samsung Galaxy S 4 General] rebel1699:
No problem. My thinking is the zip you sent grabs the first 128Mb. All the S3 pulls about 80Mb to 120Mb. The S4 pulled all 128Mb. I am thinking there is more, and is not grabbing enough. Im going to see if i can extend it.
[AT&T Samsung Galaxy S 4 General] Surge1223:
I have a zip that makes a 384 mb debrick.img. After flashing the zip the debrick.img will be located at /sdcard/debrick.img and will be 384 MB. The pic attached shows the debrick img is partitioned the same etc

Edit: Forgot to attach a link lol

Download it here

Flash in recovery (either Safestrap or a loki'd recovery doesnt matter)
[AT&T Samsung Galaxy S 4 General] TodWulff:
bypasslkm: scripting help request

First, thanks to [MENTION=2284570]ted77usa[/MENTION] and those referenced in the OP for the help is getting my NB1 upgraded I337 downgraded back to MK2. I was then able to restore a SS TWRP backup and am virtually back to where I was pre-NB1, sans WiFi functionality.

I have gotten the bypasslkm binary, placing it in the /data/local/tmp folder and, when executed via adb, wifi can be toggled on/off after same, during that session. However, with a reboot, I have to adb back into the device and rerun the bypasslkm binary.

What I am struggling with is getting a script setup to autorun the binary at boot, after the rest of the OS loads.

Can someone either tell me what script I should edit or create (adding the following one-liner to it) to get the binary to do its magic every time, during the right point in the boot process, so that the device will function as expected (i.e. WiFi connecting once the OS is booted)?

/data/local/tmp/bypasslkm

Please and Thanks, in advance. Peace.

-t
[AT&T Samsung Galaxy S 4 General] Maribou:
Are you on a stock ROM, or a custom one?

If you are on a custom ROM that has init.d support:

Move the bypasslkm file to /system/etc/init.d

navigate back to /system/etc and look for a file called install-recovery.sh

Open the file with root explorer, or another file manager with root access in text editor mode, and add this to the bottom of the file:

# init.d support
busybox run-parts /system/etc/init.d/

Press return, and save and exit.

Reboot your phone, and if all goes well you should have WiFi up and running after every reboot.

Good luck.:good:
[AT&T Samsung Galaxy S 4 General] TodWulff:
Hey Maribou. Thanks for the quick reply. I will be putting a SS compatible custom ROM on here in a SS ROM-slot so that guidance will likely be helpful for same.

However, the device's stock slot had MK2 on it and I derped hard and let it upgrade the stock slot with an unrootable NB1. Ugh. I followed the OP guidance and got it downgraded to MK2 (with an NB1 kernel, I presume.?.).

So, for this discussion, that is what I am dealing with. I suspect that the rooted MK2 stock slot doesn't have init.d support, but I honestly don't know what I don't know, so...

Suggestions on getting the stock slot to automagically execute the bypasslkm exploit binary, to restore pre-NB1 upgrade functionality would be appreciated.

Or, can I, given current scenario, flash a full I337MK2 Stock ROM via ODIN to restore it to its pre-NB1 state (I'll do a twrp nandroid of it now and then try that...)?

Again, thank you.

-t
[AT&T Samsung Galaxy S 4 General] Maribou:
I feel your pain about the upgrade. I knew before hand not to upgrade and I did it anyway. :(

I wouldn't try flashing the MK2 stock ROM through Odin because it will fail. Even though you downgraded to MK2, your phone is still on NB1 bootloader.

Since you are on stock, you will have to do a little bit of work to get init.d support up and running. I haven't tried adding init.d support to stock, but I can give you a link if you would like to try it. Most of the guides I found want you to flash a zip file to add init.d support. This guide however does not.

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

I have also heard of people using this App: https://play.google.com/store/apps/details?id=com.androguide.universal.init.d

I have never used it though.

Maybe there is an easier way, or someone with a little more knowledge on this topic could help us out here.
[AT&T Samsung Galaxy S 4 General] dave5777:
Did you get bypasslkm to run from init.d on Black Box? I haven't had any luck.
[AT&T Samsung Galaxy S 4 General] Maribou:
You know, I didn't even flash BlackBox earlier. It was on my list of things to do but I ended up flashing SHOstock instead. :)

It says it supports init.d so it should work, but it is still in beta phase.

If I get some free time tomorrow I might try giving it a go and see if I can't get it to work.

---------- Post added at 01:39 AM ---------- Previous post was at 12:57 AM ----------

SuperSU updated the binary and It reverted the install-recovery.sh script back to default for some reason and I lost WiFi after the reboot.

Adding the line

busybox run-parts /system/etc/init.d/ section to the install-recovery.sh script fixed it.

[MENTION=2924695]dave5777[/MENTION] , did you make sure the string you entered was exactly like this in the install-recover.sh script?

busybox run-parts /system/etc/init.d/

Because it was failing to start for me earlier, and I noticed that autocorrect had made it look like this:

busy box run - parts /system/etc/init.d/

It was adding spaces between the words which was causing it to fail.
[AT&T Samsung Galaxy S 4 General] dave5777:
I got it to work by using the install-recovery.sh from another rom. Now I just need a script to toggle wifi on at boot.
[AT&T Samsung Galaxy S 4 General] ted77usa:
According to [MENTION=833788]rebel1699[/MENTION] BlackBox used bbx script instead of busy box ..... [MENTION=2924695]dave5777[/MENTION] u need to update the script to bbx instead to get to work....:D

Swyped From MK2 Dark Venom SS Edition
[AT&T Samsung Galaxy S 4 General] Maribou:
Well busybox is installed on blackbox so using the busybox run-parts /system/etc/init.d/ should work right?
[AT&T Samsung Galaxy S 4 General] dave5777:
I got it to work using a different install-recovery.sh :)
[AT&T Samsung Galaxy S 4 General] Maribou:
Is it starting for you after every reboot? Or are you having to toggle it on after reboot. It should turn it on and connect automatically.
[AT&T Samsung Galaxy S 4 General] dave5777:
I have to toggle it.
[AT&T Samsung Galaxy S 4 General] Maribou:
That's weird. It starts for me. I'm going to install blackbox and play around for a bit.
[AT&T Samsung Galaxy S 4 General] DraKuL71:
I resolved it a different way, Using Script Manager I added bypasslkm to run at boot with SU rights. Then I created a script also within SManager that executes the following command to turn on wifi:

svc wifi enable

I set that too to run at boot and bam, at each boot bypasslkm runs followed by wifion (that's what I named the script I created) and it boots with wifi switched on within a few seconds after the lockscreen shows up. Hope this helps folks.
[AT&T Samsung Galaxy S 4 General] dave5777:
Yeah I posted that earlier in this thread. I would rather use init.d that runs earlier than a app at boot.
[AT&T Samsung Galaxy S 4 General] Maribou:
Well BlackBox boots for me, but it wont make it past the WiFi screen. I tried all kinds of different options and it was still a no go. :(

Sorry [MENTION=2924695]dave5777[/MENTION]
[AT&T Samsung Galaxy S 4 General] dave5777:
If it doesn't boot you need to wipe data in ss
[AT&T Samsung Galaxy S 4 General] Maribou:
I did that and it boots. I get past the language selection screen, but when I get to WiFi screen it wont let me do anything at all. It just sits there.
[AT&T Samsung Galaxy S 4 General] dave5777:
[MENTION=5757007]DraKuL71[/MENTION] I added your SVC wifi enable to init.d now Wi-Fi is turned on boot.

---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------

I sounds like it's hanging on Wi-Fi. I restored a black box I made before I took the nb1. You might have to push bypasslkm
[AT&T Samsung Galaxy S 4 General] Maribou:
I was thinking the same thing. I might try later on tonight.
[AT&T Samsung Galaxy S 4 General] dave5777:
It should only request Wi-Fi if you don't have network on boot. Maybe try letting it sit for 5 minutes before entering setup.
[AT&T Samsung Galaxy S 4 General] TodWulff:
Yep... ;)

Maribou, you are d bomb. I made use of the app tht you politely suggested that you had heard about. While it is likely not the most elegant from a savvy scripter's perspective, for those newer to the environment, it made the process pretty painless.

The following images are a rendition of my setup now, which works well, wifi fixed and toggled on at boot, and can be subsequently toggled on/off at will manually, as the user desires.

Test validating no native init.d support:

Turned on and Script created:

Script:

Logged Results:

Thank you, kind sir! :good: (<-- hoping that the gender assumption wasn't incorrect - no offense intended)

Now, to get back to finding a good rom for a SS slot... :highfive:

-t
[AT&T Samsung Galaxy S 4 General] Maribou:
Nice! I'm glad you got it sorted out. :good:

LOL about the gender assumption. You are correct. I am an old man. :laugh:
[AT&T Samsung Galaxy S 4 General] dave5777:
I made a backup of BB2.3 with bypasslkm Wi-Fi enabled on boot. I'll post it here after I upload it.
[AT&T Samsung Galaxy S 4 General] Maribou:
Awesome Dave! Thank you.:good:
[AT&T Samsung Galaxy S 4 General] dave5777:
For everyone who downgraded from NB1 and wants to run Black Box 2.3 Just extract this in you TWRP backup dir and restore to stock slot.

You'll have to add apn. You will have WIFI on boot ;)

https://mega.co.nz/#!9Y9STQaD!l5HY7NCNA0jkNB4mze2Y6-UWHeCp4D6L5LNLWbBS7JM

Here's TodWulff's nb1wififix https://www.dropbox.com/s/wnbvsrh0wtfx0jx/nb1wififix

delete the bypasslkm from /etc/init.d/

Then move nb1wififix to the same Dir. Fix permissions to 755

Then go to system and move bypasslkm to /data/local/tmp/
[AT&T Samsung Galaxy S 4 General] numbR7:
So, QUESTION: You can pretty much try any 4.3 ROMs without worry?
[AT&T Samsung Galaxy S 4 General] Maribou:
[MENTION=2924695]dave5777[/MENTION] your backup worked perfectly!

WiFi booted for me as soon as it started up. That's weird that you are having to toggle it on.
[AT&T Samsung Galaxy S 4 General] dave5777:
Lol no I fixed it that's why I made a backup to share. :)
[AT&T Samsung Galaxy S 4 General] DraKuL71:
I encountered a ROM that absolutely refuses to have its wifi turn on.

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

Bypasslkm takes and exits without error but the wifi reuses to engage. It's a vzw ported Safestrap supported ROM from what I could see and it loads just fine with no other issues. Flashing the ATT MK2 modules after flashing the ROM didn't do the trick. Anyone else who's a downgraded NB1->MK2 user used this ROM and gotten wifi to work on it? If I finally get it working I'll post how. Still messing with it for the 5th or 6th time now :fingers-crossed:
[AT&T Samsung Galaxy S 4 General] Maribou:
Well thank you then. :)

I actually really like this rom so far.
[AT&T Samsung Galaxy S 4 General] techfanatic9:
If we stop at step 5 will we be completed unrooted?
[AT&T Samsung Galaxy S 4 General] TodWulff:
Inquiring Minds wanna know... ;)

(Sorry if this is too off-topic, given the OP context...)

Hey Dave. Thanks for dropping that backup for us to leech on. A few quick and related questions:

1) Is it a correct presumption that this will also work in a ROM-slot as well as the stock slot?

1a) If so, do the MK2 modules need to be flashed once your backup is restored to a ROM-slot?

2) Can you point me to where I can get schooled a bit on the APN comment you make above (/me is still learning)?

Thanks in advance.

-t
[AT&T Samsung Galaxy S 4 General] Maribou:
I flashed in the stock slot 1 and it worked fine.

I didn't need to flash the modules because it was a backup I think.

You can find the AT&T APN setting in this post:

http://xdaforums.com/showthread.php?t=2616221
[AT&T Samsung Galaxy S 4 General] ted77usa:
[MENTION=4570798]techfanatic9[/MENTION]

YES....that's why u need to re-root It again:thumbup:

[MENTION=5342478]TodWulff[/MENTION]

Question #1 and #1a...Yes :thumbup: Check this thread http://xdaforums.com/showthread.php?t=2616221 for your question #2

EDIT : [MENTION=4980764]Maribou[/MENTION] .... u beat me .....:thumbup::p:thumbup:
[AT&T Samsung Galaxy S 4 General] dave5777:
For those of us on faux MK2 I don't think we'll be able to flash a ROM and get past setup that doesn't have the Att APN baked in. So restoring a backup is probably our only option.
[AT&T Samsung Galaxy S 4 General] rebel1699:
I still use the pta apn on AT&T.

Name: PTA

apn: pta

Mmsc: http://mmsc.mobile.att.net

Mmsc proxy: proxy.mobile.att.net

Mmsc port: 80

Type: default,mms,supl,hipri

Bearer: unspecified

All the rest are the some. Works on 3G/4G perfectly. Mms and sms all perfect.
[AT&T Samsung Galaxy S 4 General] DeadlySin9:
As long as you don't flash it to the Stock Slot you won't have issues. If you flash one to the stock slot the rules change a bit, but if you do it right you'll be fine. Though there's obvious limitations like no AOSP or ROM's not made for an S4 (duh)
[AT&T Samsung Galaxy S 4 General] ted77usa:
[MENTION=4826098]DeadlySin9[/MENTION] Three on a row :thumbup::p:thumbup:

Swyped from HTC ONE XL BlueICESense-JB
[AT&T Samsung Galaxy S 4 General] Maribou:
I was just about to ask you what ROM you were using, then I noticed your sig. :laugh:
[AT&T Samsung Galaxy S 4 General] TodWulff:
Noice. Really nice.!.

I restored the backup into a ROM-Slot and viola, everything works as expected. Kudos to the ROM's dev team.

The APN settings stuck. The wifi stuffs are also working as expected, so I'll not mess with the ROM's wifi fix, as implemented therein.

It is a nice piece of work. Thank you, folks! :good:

-t

---------- Post added at 12:46 AM ---------- Previous post was at 12:43 AM ----------

Perfect. Nice ROM. Good wifi fix therein. Thanks [MENTION=2924695]dave5777[/MENTION] :good: :D :good:

-t
[AT&T Samsung Galaxy S 4 General] numbR7:
Thanks a lot for the stock slot tip. Haven't done it but given time!? :confused:

EDIT: were can I read about the difference between stock and other slots?
[AT&T Samsung Galaxy S 4 General] dave5777:
I also made a stock MK2 backup rooted with init.d and bypasslkm .

https://mega.co.nz/#!pJFRASgB!M5f_Ogp04dOJUuL9EV0DFFvY62waxeb6ZsxBW44x4Pk

You will have to add apn and move bypasslkm to /data/local/tmp and turn on Universal Init.d
[AT&T Samsung Galaxy S 4 General] Michael3214:
Start here, its the development thread re: Safestrap.

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

The second link is the Safestrap discussion thread.

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