yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] kevin527:
I did the downgrade and everything worked fine except when I try to make a call my screen just flashes and blinks. I can't make any calls out or get any calls.
[Verizon Samsung Galaxy S 4] Sethnelson1:
Worked Great

Thanks! Everything works now. Back to 4.3 for now.

FYI for those downgrading/upgrading.

I was unable to flash the emergency stock MK2 image in ODIN after downgrading from 4.4.2. from this thread: http://xdaforums.com/showthread.php?t=2578209.

I was able to downgrade according to the OPs instructions by using ODIN and pushing files to the phone with EF Explorer and running the commands with terminal emulator on the phone. WIFI works just fine.

I am able to flash hyperdrive RLS 15 after the OPs downgrade instructions.

I just dont know why I can't do the emergency OIDIN wipe after all this....
[Verizon Samsung Galaxy S 4] klabit87:
If you have flashed the kk leak or have used surge's upgrade method you cannot use the emergency stock mk2 image.

This is due to the upgraded aboot. Even after performing the downgrade the kk leak aboot is still there.
[Verizon Samsung Galaxy S 4] DjSkreem:
well guess i did sumthing wrong then idk would be cool if we could mod the rom and get stuff like the s5 weather clock, s5 system ui and rip out bloat ware but for now im good when root becomes available some way imma move my S5 files apk boot animation and sound over and hopefully not crash my os. all i want is the verizon logo gone replaced with the S5 boot and shutdown screen, the s5 weather clock and stock apps and the system ui / touchwizz
[Verizon Samsung Galaxy S 4] Sir_Eagle:
Curious about two things:

1) If you downgrade, then upgrade as described, can you uninstall Safe Strap afterwords?

2) Surge, are you working on a root for KK without having to downgrade?
[Verizon Samsung Galaxy S 4] Sethnelson1:
[/QUOTE] 3. For sound to work you must use the VRUFNC2 NON-HLOS.bin. To get WiFi to work you must download bypasslkm from here extract the bypasslkm binary and push it to /data/local/tmp then open terminal emulator or use adb shell and type

su
cd /data/local/tmp
chmod 755 bypasslkm
./bypasslkm

Credits:

Hashcode

bajasur

BeansTown106

jeboo

ted77usa

muniz_ri

rebel1699

Maribou

sextape

Chainfire

ryanbg[/QUOTE]

Do I have to run this command every time I reboot to get wifi?
[Verizon Samsung Galaxy S 4] BoxBeatdown:
3. For sound to work you must use the VRUFNC2 NON-HLOS.bin. To get WiFi to work you must download bypasslkm from here extract the bypasslkm binary and push it to /data/local/tmp then open terminal emulator or use adb shell and type

su
cd /data/local/tmp
chmod 755 bypasslkm
./bypasslkm

Credits:

Hashcode

bajasur

BeansTown106

jeboo

ted77usa

muniz_ri

rebel1699

Maribou

sextape

Chainfire

ryanbg[/QUOTE]

Do I have to run this command every time I reboot to get wifi?[/QUOTE]

I believe so. if you go to the bypasslkm thread, the OP says that you have to redo the exploit each time you boot.
[Verizon Samsung Galaxy S 4] klabit87:
You could get script manager from the play store (it's free) and get the commands setup as a script that you can set to run at startup.

Just as a temporary resolve until official update drops and everybody eventually (and hopefully) moves up to kk.
[Verizon Samsung Galaxy S 4] BoxBeatdown:
Any way you could help me set up said script? i have no experience with scripting:eek:
[Verizon Samsung Galaxy S 4] klabit87:
yeah its been a while since i have played with any of it so give me a little bit.
[Verizon Samsung Galaxy S 4] bobbyt23:
What is everybody talking about with the sound and wifi not working unless you flash something? I didn't do anything extra and the sound/wifi works perfectly.
[Verizon Samsung Galaxy S 4] scootier:
When you downgrade back to 4.3 you have to do these things.
[Verizon Samsung Galaxy S 4] marcviado:
Great job! :) Followed instructions my 1st try and everything booted up just fine. of course the only known issue occured the force close on first boot. other than that everything is up and running
[Verizon Samsung Galaxy S 4] klabit87:
I have the script and instructions ready for anybody that wants to test. I already pm'd you [MENTION=5784227]BoxBeatdown[/MENTION]

I only need 1, maybe 2 confirmed tests before public post.

PM if interested. Will post as soon as confirmed.
[Verizon Samsung Galaxy S 4] Shotjas:
I want to make 100% sure here, so I'm going to ask the stupid question(s). On the downgrade, do we reboot the phone into download mode, then do step 1 in Odin? I would logically think yes, considering that anything we flash in Odin, we normally are in download mode already, correct?

edit

I gave up trying to downgrade, flash and get the pre-root working. Just went ahead and re-flashed the leak (non-rooted) and will be happy with it. Too many issues with the cache and an error saying "No OS installed" - however I followed the directions explicitly, even downloaded the files 3 times (they have a tendency to corrupt often enough). Still no dice.
[Verizon Samsung Galaxy S 4] Surge1223:
Thanks :) Rom slots are an issue at the moment because of the new Selinux policies and properties that make sure all references to /system are rerouted properly --thus is straight from Hash

Hash told me to install NC2 with the ATT 3.72 SS apk when NC2 first leaked. I asked him once why he had diff versions of SS for vzw and att s4 since our mounts are the same...I believe he said something about it being related to apn and build.prop diffs. ill have to double check.

Hmm...thats strange. I doubt the recursive perms on /system were wrong in the updater script. What were the perms on the version file? When making roms on 4.4.2 I have to delete a few knox files from /system but I dont think that would cause it since SS recovery itself still works. The only other things that come to mind are not having su enabled at boot or not having /data completely wiped before installing the ota root zip or nc5 root rom, since then selinux policies would be applied to the /data files and restorecon would be a solution. ill have to ask Hash..
[Verizon Samsung Galaxy S 4] muniz_ri:
Guys, let me know if you can offer any help on the safestrap apk fc issue affecting my keeproot ota zips. I have tried everything I can think of. My ROMs don't have this issue only the ota zips.
[Verizon Samsung Galaxy S 4] hunteditor:
Anything Different for 32G?

Okay, we've already established I'm a complete noob and moron :eek: for taking the update, but I'd like to advance my noobishness a bit further and ask if there's anything I need to do differently for the 32 gig version of the phone.

I attempted the downgrade method, got to MK2 (no sound or phone function) rooted okay and then ODINed the NC5 with root.

After that was stuck on red Verizon screen no matter how many wipes.

Was easily able to re-ODIN the stock OTA and have a functioning phone again, so no emergency or worries (other than being stuck in moron mode with an unrooted phone).

Would like to retry but thought maybe something about the 32 gig version might be causing my Verizon screen lockup.

Any thoughts?
[Verizon Samsung Galaxy S 4] punkwhan:
My auto-rotate suddenly stopped working.

All I did was removed or froze some of Samsung apps in TB.

Would that affect the auto-rotate?

I didn't have the problem with it for the first several days of installing the rooted NC5 deodexed.

Any idea?

Thanks.
[Verizon Samsung Galaxy S 4] Beakhole:
Wipe

You may want to reboot back into SS and wipe data, cache, and dalvik cache. That might get you past the Verizon boot screen.
[Verizon Samsung Galaxy S 4] albertdc:
As above, but be sure you are doing that in the "advanced" menu of wipe in SS, not the wipe option that you see right off the bat.
[Verizon Samsung Galaxy S 4] Beakhole:
...

'Tis the truth.
[Verizon Samsung Galaxy S 4] hunteditor:
Well, for whatever reason I'm up and running now. I had done the advanced wipe previously, but perhaps doing it before the last ODIN uploads was the trick.

Thanks for the help!!!!!
[Verizon Samsung Galaxy S 4] EinGlo:
SD card permissions lost !!!!
[Verizon Samsung Galaxy S 4] k1mu:
The original permissions on /system/etc/safestrap were 700. Changing that to 755 didn't help.

I got it to work for adb shell and terminal emulator, but Safestrap just couldn't run.

In SafestrapActivity.java, routine setupControls, change the recovery-check.sh invocation to

String[] arrayOfString = ExecuteAsRootBase.executecmd("su -c " + getFilesDir().toString() +

"/recovery-check.sh " + getFilesDir().toString()).split(":");

The only change here is from "sh " to "su -c ".
[Verizon Samsung Galaxy S 4] jrv331:
Not sure what happened but Im stuck at the samsung boot logo and cant get past it. Several battery pulls later Im still there. Really need some help here.

Thanks
[Verizon Samsung Galaxy S 4] Scottchy014:
A couple things might have done this.

1. Are you on SS 3.72?

2. Did you wipe your "System" along with dalvik, cache, and data?

3. If you've done these correctly, go into stock recovery and do a factory reset.

I may be missing something else, but this should get you started. Otherwise, you can always do the downgrade MK2 method and start over. Good luck!

Sent from my Nexus 7 2013 running AICP
[Verizon Samsung Galaxy S 4] jrv331:
I believe that the problem is that I accidently wiped my stock partition then rebooted the phone. I cant get past the samsung boot logo. I'm downloading the downgrade file now. Looked for a mk2 recovery image but cant find one. ( that doesnt require sign up for raptor)
[Verizon Samsung Galaxy S 4] clkinsler:
Which version did you flash Deodex or Odex? I had the same issue (not doing the OTA update) but stuck on the Verizon screen flashing Odex. I started from scratch flashing the Deodex and it worked perfectly. Good luck
[Verizon Samsung Galaxy S 4] Scottchy014:
[MENTION=3297222]jrv331[/MENTION] The downgrade file (.zip) will have everything you need. Just extract everything on your computer and run it in Odin (AP slot). I'm actually in the process of recording a video so those who want to downgrade can visually see it.

Sent from my Nexus 7 2013 running AICP
[Verizon Samsung Galaxy S 4] Surge1223:
The perms on my /system/etc/safestrap dir is chmod 700 root:root. All the files and folders in /system/etc/safrstrap/ are chmod 755 root:shell. However, all the files within the three folders in /system/etc/safestrap (flags, res, rootfs) are chmod 600 root:root.
[Verizon Samsung Galaxy S 4] jrv331:
[MENTION=241865]Scott[/MENTION]

Do I use the AP in Odin for all three files?

1. Flash I545VRUEMK2_Downgrade.tar.md5 -->

2. flash I545VRUEMK2_System.tar.md5 -->

3. flash the I545VRUEMK2_cache.tar.md5 -->

Thanks
[Verizon Samsung Galaxy S 4] k1mu:
That's consistent with what I saw.

For example, try, from a non-root shell (terminal emulator)

$ cd /data/data/com.hashcode.safestrap/files

$ ./busybox ls

That "busybox" binary is 755, but I can't run it. Root can.

Safestrap runs /data/data/com.hashcode.safestrap/files/recovery-check.sh with the path:

sh /data/data/com.hashcode/safestrap/files/recovery-check.sh /data/data/com.hashcode.safestrap/files/

That should return "3.72:0" or "3.72:1" where the "3.72" comes from reading the /system/etc/safestrap/flags/version contents. Since it can't read that file without root, the recovery-check.sh returns ":0" or ":1", with no version string, which causes Safestrap to crash because it can't convert "" to a float..

Maybe it's time to take this to PM? Not likely that this is very interesting to most people here.
[Verizon Samsung Galaxy S 4] Scottchy014:
Yes

Sent from my Nexus 7 2013 running AICP
[Verizon Samsung Galaxy S 4] V0latyle:
I just reflashed and am going to test this. I had a feeling it could be one of the Samsung apps. Stupid TouchWiz framework. I want my AOSP nao, dammit!

Edit: Another possibility is the toggles zip, or the flashlight zip.
[Verizon Samsung Galaxy S 4] jrv331:
[MENTION=2410857]Scottchy[/MENTION], thanks for the help, up and running again. Im sure I'll mess something else up trying out roms.
[Verizon Samsung Galaxy S 4] zombolt:
I followed the directions and everything worked perfectly. Thanks for all your hard work.

Quick question: is it possible to use xposed on the deodexed rom? And how do I do it?
[Verizon Samsung Galaxy S 4] Scottchy014:
For those of you who would like to see how to downgrade back to MK2, I have a video for you. Verizon Galaxy S4 KitKat**DOWNGRADE** to Jellybean. Good luck!
[Verizon Samsung Galaxy S 4] pjrmax403:
Reboot file

How's it going Surge?

I was going to copy the Reboot file from my Rooted MK2 so I could copy it back after Installation of NC5, But Solid Explorer won't do it.

Any Ideas?
[Verizon Samsung Galaxy S 4] aholeinthewor1d:
OK so I started out with an s4 from a friend on stock NC5..followed the guide last week and downgraded to mk2 then rooted and then flashed the prerooted NC5...everything went perfect first try and I've been using it all week with no problems..then yesterday I put my SIM back in my gs5 to use for a couple hours before returning it...then I returned it and put it back in the s4 to continue using it like I've been....now all of a sudden Wi-Fi will not connect...I have heard of this happening but not sure how it would randomly start out of no where..
[Verizon Samsung Galaxy S 4] JeeperDon:
On the extended power/on/off/restart menu... when I hit the Recovery item, which has the Safestrap logo, I get regular recovery, not SS recovery. Is it going to the wrong place, or is it not the right logo there? I do have the SS app on the phone, though it's not needed when SS was installed via MK2 before the upgrade.
[Verizon Samsung Galaxy S 4] lazer9:
I think that's just how it works even with SS Recovery installed, that feature leads to the Stock Recovery.
[Verizon Samsung Galaxy S 4] gadget!:
From what I have read that's because you are using an unsupported safestrap version.

If you want to get into recovery (non stock) just reboot normally and when the safestrap menu comes up hit recovery.

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] tadiv:
The same thing happens to me - it's simpler to just "Restart" and select "RECOVERY" from the SS start-up graphic during the boot sequence...
[Verizon Samsung Galaxy S 4] JeeperDon:
Thank you, I suspect the winning answer. [Thanks to our runners up for stating the obvious of how to bypass the broken part. :D]

So, if it is indeed broken, it would be nice, for cleanliness, to not have that option in the power menu list, or to change the icon. [I know this point is my OCD kicking in, but I think it's a common trait in programmers.]
[Verizon Samsung Galaxy S 4] Beakhole:
Reboot back into SS and do Advanced wipe. Wipe data, cache, and dalvik cache. That might do the trick.

---------- Post added at 04:06 PM ---------- Previous post was at 03:59 PM ----------

Maybe give this a try.
[Verizon Samsung Galaxy S 4] michaelg117:
How does one hide the persistent Data icon..?
[Verizon Samsung Galaxy S 4] sinner822:
Samsung data connection icon fix is your easiest way.

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] budding_developer:
surge1223, I have to again thank you for a great piece of work.

Downloaded everything earlier today, and proceeded to follow your instructions on the brand new S4 I just got from Verizon that came with MK2.

Rooted with SafeRoot, then installed Safestrap. Used Safestrap to flash the modified stock ROM over stock, then flashed the other files in Odin.

It worked like a charm, and now I am in possession of a new S4 with a fully rooted & de-Odex'ed installation of the stock NC5 "Kit Kat" firmware. I didn't need to worry about any of your "caveats", as modems and wifi came right up first shot.

Again, thanks for the great work!!
[Verizon Samsung Galaxy S 4] michaelg117:
Worked great. Much thanks
[Verizon Samsung Galaxy S 4] XRSTOY1:
Can't get past Custom Logo

How di you downgrade? I can't get tp SS to flash the first part? I might have made a big mistake, I wanted to do a reset so I did it in safe strap I wipes data, cache ,and system and now I'm stuck at the custom logo screen can someone please help me out?
[Verizon Samsung Galaxy S 4] k1mu:
What build and bootloader were you running when you wiped system? If MK2, you can re-flash MK2 by booting into downloader mode.

If you're on NC2 or NC5, you'll need to find a factory stock NC5 ROM and flash that in downloader mode.
[Verizon Samsung Galaxy S 4] pscshuler:
I hear you JeeperDon, I keep hitting it out of habit. Wish I knew how to remove it as well as Airplane mode, I use the tile toggle & personally find the menu too congested especially after adding the Scree Record menu item. Just the OCD in me! :rolleyes:
[Verizon Samsung Galaxy S 4] XRSTOY1:
Mk2

I'm on MK2 so which files do I need Surge1223 downgrade file? if so which one goes where in Odin? I tried to flash I545VRUEMK2_Downgrade.tar in stock recovery it failed. is this the correct way?
[Verizon Samsung Galaxy S 4] Surge1223:
Lol usually im in the business of adding features...but to each his own. Ill upload the stock one soon. The plan was to add the icon first, figure out the java later.

P.S. It doesn't look to cluttered me. Plus who doesnt love a flashlight?
[Verizon Samsung Galaxy S 4] pscshuler:
Lol true Surge, I just hate scrolling for my volume buttons ;)
[Verizon Samsung Galaxy S 4] XRSTOY1:
stuck on custom logo

Surge1223 ,can you please help I upgraded to NC5 and did a full wipe in SS everything but my sd card now I can't get past the custom lock screen. I tried to do the downgrade and flash I545VRUEMK2_Downgrade.tar in stock recovery but it failed. I'm trying to odin the system file now what slot do I use in Oden? Now I get past the custom lock screen to a black screen with nothing I installed the system in the Ap slot
[Verizon Samsung Galaxy S 4] tadiv:
You have to flash I545VRUEMK2_Downgrade.tar.md5, I545VRUEMK2_System.tar.md5 and I545VRUEMK2_cache.tar.md5 with Odin (once each in the AP slot) while the phone is in download mode. Then, in 4.3, you can root, install SS 3.72, and flash the NC5 stuff ending up rooted with 4.4.2.
[Verizon Samsung Galaxy S 4] cobra7361:
[MENTION=4939386]Surge1223[/MENTION]

When i upgrade do i unistall SS 3.71 then install 3.72 or install 3.72 and then unistall 3.71?

Or does it matter?

I know this is a newb question...just in the newest video he starts off on 3.72...

Thank u for all ur hard work and dedication....much appreciated
[Verizon Samsung Galaxy S 4] XRSTOY1:
It worked

Thank you your a life saver
[Verizon Samsung Galaxy S 4] pscshuler:
All I did was uninstall 3.71 in the SS recovery screen, uninstall the app. Then install 3.72, install the recovery in the app & reboot. This is assuming you already deleted all the slots 1st.
[Verizon Samsung Galaxy S 4] tadiv:
You are welcome - glad I was able to help. :cowboy:

---------- Post added at 09:26 AM ---------- Previous post was at 09:16 AM ----------

After rooting in 4.3, SS 3.72 is what I installed for the rest of the process. While the recovery portion of SS was still in place when I booted into 4.4.2 (NC5) the first time, the app was not there - I re-installed it and all was good - it even detected properly that its recovery was in place. See this post for my steps (this was with the "original" v2 ROM - but replacing that ROM file with either I545VRUFNC5-Stock-Root-Deodex.zip or I545VRUFNC5-Stock-Root-Odex.zip will do the trick today - I'm running I545VRUFNC5-Stock-Root-Deodex.zip and lovin' it).

Tom
[Verizon Samsung Galaxy S 4] Sir_Eagle:
Rooted. No problems following all instructions to downgrade, root, install SS, upgrade with root.
[Verizon Samsung Galaxy S 4] socha818:
Problems

So I i was on the NC2 for a while and wanted to upgrade to the NC5. I booted to safestrap, cleared the files, then realized that I put the unziped file of NC5 stock deodex. So I said **** and rebooted system.

Now I cannot get past the samsung custom screen. If I pull the battery, I can get to download mode, but cannot get odin to recognized my device. When I plug in my phone it downloads the driver for MSM8960. When I plug it into a charger, it shows the battery "analyzing" screen but never shows what the battery is at. However, I cannot access the device at all through my computer.

I need some major help her.

Am I screwed?
[Verizon Samsung Galaxy S 4] corrupted23:
I am a noobie here too but I would recomment reinstalling the device's drivers... I feel like this happened to me before but can't recall :/
[Verizon Samsung Galaxy S 4] socha818:
Only problem, how can I reinstall the device drivers? I cant get the phone on to install from device.

[MENTION=4939386]Surge1223[/MENTION], Can you Help me please. Have you heard of this issue?
[Verizon Samsung Galaxy S 4] corrupted23:
Thank you Surge, I was able to downgrade from NC5 back to MK and then upgrade keeping root with safestrap and everything (AND I WORKS BEAUTIFULLY) someone must have mentioned before but the instructions were a little not too clear but I managed.

Then loaded up another ROM on Safestrap (Bold move) and ended up w/out root privileges and no-wifi, ha. Guess I'll start all over again <3
[Verizon Samsung Galaxy S 4] crcowan:
Thank you Serge

Followed your instructions to a T. Went from an OTA NC5, back and forward. Everything worked exactly as promised (although I had to vamp a bit to root NC2 as I had forgotten how I did it originally). Thank you for our work and your continued support to this forum!
[Verizon Samsung Galaxy S 4] toknitup420:
im updating from mk2 to nc5. when should i flash the nc5 patch zip. can that be done after initial set up of the device.
[Verizon Samsung Galaxy S 4] Ryukouki:
Heya folks. For me it looks like I'm on the MJ7 baseband, and I was wondering if this guide would still work if I attempted to go from there. If not is there an MK2 build that I can use that doesn't wipe my phone completely? :)
[Verizon Samsung Galaxy S 4] decaturbob:
Its my understanding that MJ7 and MK2 are practically identical
[Verizon Samsung Galaxy S 4] Ryukouki:
I see! Thanks for the answer! ^_^ I'm having second thoughts because I'm hearing there's bluetooth issues since I was thinking of heading to RLS 16. :P
[Verizon Samsung Galaxy S 4] XRSTOY1:
For some reason ADB refuses to see my phone, everything else see it fine, Yes I have all the right things turned on. and settings is there another way to root before safe root?

I've re flashed the software via odin several factory resets and I've tried on several computers ADB see's my S3 no problem.
[Verizon Samsung Galaxy S 4] decaturbob:
sometimes its best to sit out the first wave of flashing a rom especially when we have to do alot to our phones prior to rom flashing. If the dust settles and some work arounds appear to help bluetooth and wifi issue, I'll probably update this week. I am MJ7 basebuild runinng MK2 ROMS (hd15 and Bajarom).

I don't like the fact that safestrap not fully functional with creating and installing to rom slots but can live with it as I can odin back to mk2 if needed
[Verizon Samsung Galaxy S 4] Ryukouki:
Yeah, I'm gonna sit out the wave until I get more reports saying that the ROM is actually stable. At this point I'm a bit more concerned with getting my stuff up to the NC5 so I can do all of that flashy stuff. Was reading Surge's guide, bit more daunting than I thought (maybe it's just me! :() but I might just swallow my fear sometime soon and try my hand at it. :P *grumbles something about wanting MDK back*
[Verizon Samsung Galaxy S 4] decaturbob:
ya, I wish I had mdk but jumped into S4 game a month too late but its ok, I got a mean ass S4 with either bajarom or HD15 running. I need to bug surge soon to see when Bajarom for 4.4 going to be released thats SS compatible
[Verizon Samsung Galaxy S 4] Ryukouki:
See, I was the opposite. I had the joy of having an MDK phone from the start, but a series of unfortunate events and a misinterpretation led me to accidentally odin an MJ7 stock build onto my phone, so bummer me. :confused: Now it's like, DAMMIT, I really wish I had an MDK phone, so much easier to work with.