yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] UnboundDemon:
If i have xposed installed, can i just uninstall it and get OTA? Tho kitkat is not available yet where i live but it should be soon and i've been reseaerching on how to get it without dealing with unrooting or flashing the devixe

Sent from my Samsung Galaxy S4 GT-I9500 - stock ROM, JB 4.3 - Rooted - Xposed framework
[Verizon Samsung Galaxy S 4] k1mu:
That's a pretty common question with no real answer.

OTAs update the files on your device to the target release by editing them with a "patch". The patch contains the information necessary to change the original file to the new one. If the original file is gone (removed by "debloating"), edited (like the files changed by installing xposed, installing Safestrap, etc.), frozen, tampered with, edited, etc. the OTA will fail.

Normally,a failure won't do anything serious. It'll detect that files aren't original, then fail. You might be quick enough to figure out what file failed and restore that from stock, but then the OTA will fail on the next file and so on.. lots of time spent restoring and recovering.

That's why it's recommended to restore to stock unrooted prior to an OTA. You're giving up root, after all, so just go back to stock first and avoid the aggravation. After all, installing a no-wipe MK2 isn't particularly hard.
[Verizon Samsung Galaxy S 4] jrkelley14:
I was able to use the SafeRoot process on my brand new S4 w/ MK2 firmware, but I am now having a problem getting any response from the LED for notifications. The LED won't light up or flash no matter what settings I use, and it won't even light up when the battery is charging (even though I know it is charging because the meter goes up). Has anyone seen this issue before? It is a brand new phone, so I am pretty sure the LED still works. Wondering if something went wrong in the root process that disabled the LED. Any ideas? Thanks again for the directions. *Other than the LED, it works great!
[Verizon Samsung Galaxy S 4] JerryGNYC:
Disclaimer: I'm on Sprint with MK5... :)

I really don't think Saferoot will do anything to LED operation. Go into Settings / My Device / LED indicator, and make sure they're all checked. If they are, uncheck them, reboot, then reenable them and see what happens.

And FWIW, is Powersaving mode turned on or off?
[Verizon Samsung Galaxy S 4] patrickslee:
Thanks for this. It's awesome.

My understanding so far with the warranty bit is that if anything non-stock is flashed via Odin with knox bootloader installed, the efuse will be set.

But what if we don't use Odin? Consider the following senario:

Root via Saferoot

Install custom recovery by using the

dd

command in

adb shell

Install custom ROM with the custom recovery

Would step 2 and/or 3 trigger the bit? These steps are done without the booloader's knowledge so it has no way to check what has been done.

Has anyone tried these?
[Verizon Samsung Galaxy S 4] jrkelley14:
Thanks for the suggestion, but I've already tried lots of combinations of checking/unchecking options and rebooting and nothing makes that LED come on. **I guess I'll have to use ODIN to completely restore and see if that changes anything.

Power saving mode has been off the entire time. *Thanks again for the help.
[Verizon Samsung Galaxy S 4] snoop1979:
for Sprint Galaxy S4 Mini SPH-L520 only works on MK2 not on NA7
[Verizon Samsung Galaxy S 4] jkeuclid:
[MENTION=3940199]k1mu[/MENTION], I've been using saferoot now since I got my new AT&T Samsung Galaxy S4 Active SGH-i537, rooted 4.3 ML2 using Sunderwear's method, then took the KK OTA 4.4.2 and again rooted with Sunderwear's method . My question to you is the saferoot listed in the OP installs Busybox 1.19.xx, but I have another version that installs Busybox 1.21.1. Also, will there be a new version of saferoot for 4.4.2+ perhaps?
[Verizon Samsung Galaxy S 4] dbpaddler:
Here you go. It'll trip Knox, but it flashes through Odin so it bypasses the security software that blocks Saferoot. That's the only way if you're on NA7. Knox pretty much sucks. I'm still debating if I'm keeping mine or not. Doesn't seem like there are many options for a better than average smaller phone.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
No, the exploit used in "saferoot" will likely be (already is?) patched and will not work with 4.4.x
[Verizon Samsung Galaxy S 4] creative21:
Does it works on xperia sp?
[Verizon Samsung Galaxy S 4] JerryGNYC:
It can't hurt to try it... let us know.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
It began on an Xperia, but you'd probably be better off asking surge (mentioned in post one) or the xperia board here at XDA
[Verizon Samsung Galaxy S 4] konnorrigby:
if you don't have a computer handy and you still want root, check it check it here

me and PlayfulGod made this nifty app
[Verizon Samsung Galaxy S 4] k1mu:
Attempting to overwrite the bootloader using 'dd' (i.e. bypassing ODIN) won't work. Neither will using Rom Manager, Goo Manager, or anything else that tries to do the equivalent.

My understanding is that the attempt to write the flash partition is blocked, so nothing happens (no new bootloader, but no Knox Warranty Void). However, I can't say this from personal experience. Many have tried, many have failed. I wouldn't recommend trying it.
[Verizon Samsung Galaxy S 4] k1mu:
I really need to update the version of busybox included with Saferoot. It's easily updated from the Play Store later, but still should be up-to-date.

If I can get some time I'll consider making it easy for the user to root without busybox being installed as well.
[Verizon Samsung Galaxy S 4] k1mu:
Wow. Great job. It's actually quite possible that this may work on some of the phones where Knox blocks Saferoot over USB.
[Verizon Samsung Galaxy S 4] konnorrigby:
Quite. The source is on github. It executes the same as adb would just without adb
[Verizon Samsung Galaxy S 4] viasat:
[MENTION=3999967]konnorrigby[/MENTION]

First,thank you for your .apk,it's working great on my tab3 8" wi-fi (T310) with android 4.2.2 on it.

Now,my question is: Does it install busybox or only SuperSu? I need only root access,I don't want busybox install(if it's possible,of course...)

Thanks a lot again!!
[Verizon Samsung Galaxy S 4] konnorrigby:
It does install busy box. I can give an option for it not too though
[Verizon Samsung Galaxy S 4] viasat:
If it's not too much trouble for you,I'll be happy with an version that let me to choose yes or no for busybox install.

Thanks a lot again!

Best regards!
[Verizon Samsung Galaxy S 4] Mistertac:
K1mu you should work your magic somehow on the S5. Huge bounty.

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

Or team up with Surge, you guys are crazy smart

Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] spc_hicks09:
I know we shouldn't ask questions here about the Note 2, but I'm in a bit of a pickle here. I used this method to root my Note 2 on MJ9 (4.3) and now I can't even turn on my wifi. Any suggestions as to what could've caused that or how to fix it?

EDIT: I haven't installed Safestrap or any ROMs. All I did was root.
[Verizon Samsung Galaxy S 4] k1mu:
Weird. There's nothing that Saferoot modifies, so it's hard to understand why rooting it causes the WiFi to be disabled.

What happens if you unroot using the provided script?
[Verizon Samsung Galaxy S 4] k1mu:
Unfortunately, I don't have an S5, and it's going to be quite a while before my next phone on VZ.
[Verizon Samsung Galaxy S 4] spc_hicks09:
I unrooted and Wifi still didn't work anymore. Believe me, I thought it was odd too. Never heard of any root exploit breaking Wifi. I can confirm it was working before that. Wondering if it had anything to do with having Wifi on when the process was going? I have no idea what happened. Have a couple buddies with Note 2's an they used your method as well with no ill effects.

Going to Odin back, then run the method again.
[Verizon Samsung Galaxy S 4] viasat:
It will be great to have a version without busybox,at least for me,because I want only root on stock rom,for little things like ad-away,root explorer...

If you'll have time for it,I will be grateful!!

Thanks a lot!

Cheers!
[Verizon Samsung Galaxy S 4] tadiv:
OTA update failed / seeking safestrap

I purchased my Samsung Galaxy S4 second-hand yesterday - rooted it today with this method (thanks, it worked great!) and then was prompted for an OTA update. That update, noted as "update_SCH-I545_MK2_to_NC5" failed (maybe I'm happy about that...) Since I'm still rooted on MK2 and I searched this post for an answer but did not find it, where can I find safestrap?

Thanks,

Tom

---------- Post added at 04:12 PM ---------- Previous post was at 03:51 PM ----------

I found it at http://goo.im/devs/Hashcode/jfltevzw/safestrap
[Verizon Samsung Galaxy S 4] blaine07:
Will this wipe phone?

Thanks!
[Verizon Samsung Galaxy S 4] jwendt79:
Rooting will not wipe anything. If you are talking about safestrap..that's a no too
[Verizon Samsung Galaxy S 4] spc_hicks09:
Odin back to stock, WiFi kicked in. Turned off WiFi when rooting, WiFi came back on afterwards. All setup! Not sure if having WiFi on when running the process had anything to do with it or not but that was definitely weird.
[Verizon Samsung Galaxy S 4] pckarma112:
It is

My wifi was on when I used this method. Just thinking about it. Most people have wifi at home and it would be on to save data of course. It doesn't make sense that saferoot would cause this. Otherwise, there would be alot more posts like this.
[Verizon Samsung Galaxy S 4] spc_hicks09:
Yeah I'm sure it was just a one in a million fluke. Very very strange because no root method touches anything that has to do with WiFi. I searched the thread and only found 1 other post about it. Thanks everyone for the concern though!
[Verizon Samsung Galaxy S 4] k1mu:
Can someone point me to an updated pre-built busybox? The ones on busybox.net aren't current.

Oh, and as far as your 4.4.2 question: at this point, probably not. It's going to depend on what's discovered with 4.4.x.
[Verizon Samsung Galaxy S 4] jkeuclid:
k1mu, try here, and understood on future saferoot development, thanks.
[Verizon Samsung Galaxy S 4] GodspeedFx:
I used this method to root my phone (MK2) and it works fine--my question is, last night I tried to do the OTA update (which I assume is kitkat) and it downloaded fine (wifi, 30Mbps cable). I chose to install it, phone rebooted, started installing and about 20 seconds later it says failed and then restarts normally.

Do I have a problem or do I just need to unroot before I do the OTA update?

Thanks in advance!

*edit* nevermind, noticed that OP said it's best to odin back to stock and then do the OTA update.

Thanks again for all the hard work k1mu!

*edit2* still errored out after unrooting.. I don't remember if I put a debloated rom on here or not o_O
[Verizon Samsung Galaxy S 4] chkenwing:
I just tried this on my 4.3 Note 3 N9005 Hong Kong version (16GB)

Doesn't work as it fails so I'm assuming whether it has anything to do with the partition sizes? Are you able to create one that fits the 16GB version for me to test?

My details:

AP: N9005ZHUDMK1

CP: N9005ZHUDMK9

CSC: N9005ZZHDMK1

Build: JSS15J.N9005ZHUDMK1

Android 4.3
[Verizon Samsung Galaxy S 4] WormsCH:
Doesn't work for me.

Galaxy note 3 SM-N9005 (32GB UK)

Android 4.3 Stock

Kernel 3.4.0

Build: JSS15J.N9005XXUDMK2

AP: N9005XXUDMK2

CP: N9005XXUDMJ7

CSC: N9005OXADMK2
[Verizon Samsung Galaxy S 4] k1mu:
The partition sizes aren't important and aren't likely to cause Saferoot to fail.

The most likely cause for Saferoot failing is that your device is patched.

If saferoot says

This device is unsupported

followed by

[*] Unfortunately, rooting failed. Cleaning up.

Then you have a device that's not rootable using saferoot.

If that's NOT what you're seeing, then please capture the output from running it and I'll see what I can suggest.
[Verizon Samsung Galaxy S 4] k1mu:
As above, "Doesn't work for me" isn't going to help with my understanding why.

If it's not "this device is not supported", then please help by posting what Saferoot says when it fails.
[Verizon Samsung Galaxy S 4] WormsCH:
Oh, ok sorry, I'll try again in one hour and I'll post the error message
[Verizon Samsung Galaxy S 4] SHIRI:
Problem

Oh hell, not working here:

GT-I9195, android 4.2.2, version UBML4

It starts and then says the phone is not supported... here is the picture too...

Any ideas anyone???
[Verizon Samsung Galaxy S 4] WormsCH:
--- Samsung Galaxy S4 Android 4.3 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---

[*] Testing adb usability

Plug in your phone and Press any key to continue . . .

[*] Waiting for your phone to appear
[*] Your phone is detected and ready for rooting.

[*] Sending files to your device...

[*] Starting rooting program.
ro.build.product=hlte
ro.build.id=JSS15J
setsockopt() failed: Bad address.
this device is not supported.
kallsyms_addresses search failed.

[*] Checking if rooting succeeded
[*] Unfortunately, rooting failed. Cleaning up.
Press any key to continue . . .

If you need any more information, ask me, I'll give you ;)
[Verizon Samsung Galaxy S 4] SHIRI:
I don't get what you say. I posted the screen.... should i say more? Or not?

Or if it says device not supported, there is no help???
[Verizon Samsung Galaxy S 4] dkephart:
The message you posted says your device is not supported. This technique only works on supported devices. In other words, the feature in the software that allows saferoot to work has been altered in your device's firmware - "fixed" is what Samsung would say.

You need to find a different way to root your device.
[Verizon Samsung Galaxy S 4] E:V:A:
[MENTION=3940199]k1mu[/MENTION] : Is there a way to check if that CVE have already been patched?

Please have a look at THIS post.
[Verizon Samsung Galaxy S 4] dave1977nj:
Thank you for this !!!!!!!!!!!!Works Great!!!!!!!!!!!! :highfive:
[Verizon Samsung Galaxy S 4] winson9929:
Mk8 work great:good::good::good:
[Verizon Samsung Galaxy S 4] k1mu:
I'll reply there as that's not correct. The "setsockopt() failed: bad address" means that it's been patched.

Spending time looking for different kernel addresses would be OK if that initial probe hadn't failed.

As far as the other failures, I'm working on another saferoot release that specifically says that your kernel has been patched along with "this device is not supported".

I truly fail to comprehend how the latter, however, is unclear. It means what it says, which is that your device isn't supported and saferoot won't work. You'll need to look elsewhere, perhaps using CF-Root if your bootloader isn't locked.
[Verizon Samsung Galaxy S 4] bvjens31:
Been a while since I've been in the rooting game, but my VZW S3 has been acting up lately (I know this is in the S4 forum, but I got directed here from an S3 sticky so hopefully I'm OK), so I am doing my research on how to get root/custom ROM back on my phone. Looks like since I'm on 4.3, it's not quite as easy as it used to be. I'm OK with that, it is what it is. I installed Kies 3.2 and it's asking if I want to update firmware from ML1 to NC1. I'm guessing I don't want to do this?? Is NC1 too new to work with Saferoot and Safestrap?

This is the first time I've used Kies. Seems pretty slick, sort of like iTunes for Android. Will Kies work with a rooted/ROM'd S3? I do like the idea of having a multi-boot phone that I can choose which ROM to boot to, and leave the stock one un-touched. That seems very slick! And to not have the knox flag get set in any of this is nice too! Although I used up my 2 insurance claims so not sure I really need to be concerned with warranty anymore!

Nice work mate. :good:
[Verizon Samsung Galaxy S 4] pbman1953:
Is there a version of Safe root being worked on for the NC5 build?

Thanks
[Verizon Samsung Galaxy S 4] solcam:
Success!

Confirmed working on ZTE Boost Mega with stock Rom/kernel.
[Verizon Samsung Galaxy S 4] decaturbob:
What do u think?
[Verizon Samsung Galaxy S 4] pbman1953:
Well that answers the question
[Verizon Samsung Galaxy S 4] decaturbob:
It does. . Devs are looking for a root method and it will take some time..no one can answers when a root method will be found for 4.4 ota kitkat if ever.
[Verizon Samsung Galaxy S 4] mbh017:
Many thanks, it worked fine on my new S4 Black edition (with Android 4.3 MKF) :)
[Verizon Samsung Galaxy S 4] k1mu:
As many times as I've said this, I'll grace you with it again:

Upgrading to NC5 is accepting being unrooted. There is no known vulnerability in 4.4.x that allows rooting a bootloader locked phone.

Let me state that another way: if you upgrade to NC2 or NC5, you're not rootable at the moment and may not be rootable for quite a while.

You're accepting installation of a locked down phone. That's your choice, but there's nothing I or anyone else can do to get you root again until another breakthrough. And those are rare.
[Verizon Samsung Galaxy S 4] k1mu:
Updates:

The installation scripts have been edited to allow you to choose installing busybox or not.

I can't see the value of having root without having root without a complete set of shell programs, but apparently there's non Unix types out there. :laugh:

This version also displays a bit more detail when rooting fails, specifically when it encounters a patched kernel.
[Verizon Samsung Galaxy S 4] pbman1953:
I'm sorry that my question opened such a can of worms. I typically search the Web and XDA site before I stick my neck out to look like a possible idiot. I simply asked the question and I see by the attitude of one the first replies that the response that this may of ruffled a few feathers. That was not my intention.

The XDA site has been real fun and there are some nice people that really like to help some that are not nearly at the level of others. I'm one of the others, a hobbiest and had some enjoyment with the whole rooting experience.

At this point I'm willing to wait for a breakthrough.

Thanks to all the developers for long days and nights to bring some excitement to us all!
[Verizon Samsung Galaxy S 4] k1mu:
Sorry - no need to apologize. There's currently a lot of people flashing NC2 or NC5 without understanding what that means, particularly that it's not rootable.
[Verizon Samsung Galaxy S 4] decaturbob:
We have warning people for a couple months. ..

sent by safestrap enabled bajarom
[Verizon Samsung Galaxy S 4] pbman1953:
On the warning , I can understand that, but once rooted I'd rarely watch the threads here,

Honestly, I'll live with Touchwiz for a while and see what happens. I've learned something about rooting custom roms and mostly my needs.

Even though the custom roms are super cool, I'm ok with a rooted device, Xposed software and Nova Launcher. But, I'll reserve the right to change at any given moment ;)

Thanks
[Verizon Samsung Galaxy S 4] htcp85:
I got a question, just rooted my tmobile s4, and I didn't allow SuperSU about disabling Knox, is something wrong with it. And what can I do also the exploit didn't set the "Custom" flag. Thanks
[Verizon Samsung Galaxy S 4] BROKEN1981:
5-2-2014

new update for s3 on verizon. i took the update lost root. now i cant get safe root to work. what gives???????
[Verizon Samsung Galaxy S 4] dkephart:
Did you read anything in this thread? The Custom flag is set if you use Saferoot. Triangle Away is one solution.

You should have disabled Knox! Why not try again? Why not install SuperSu?

---------- Post added at 08:52 AM ---------- Previous post was at 08:50 AM ----------

Have you read nothing in this thread? Saferoot does not work with Android 4.4.
[Verizon Samsung Galaxy S 4] htcp85:
I used saferoot and like I said custom flag is not set. And SuperSU is installed the only thing is when it asked me to disable knox I click no.
[Verizon Samsung Galaxy S 4] kristinstokes:
phone unrooted itself

i successfully used the saferoot method on my verizon galaxy s3 SCH-I535 running android 4.3 and i successfully used safestrap to install a custom rom. installing the rom on a new partition (or whatever the proper term is) used up too much space on my phone so i deleted the rom and tried to boot back into stock. i did something wrong and bricked my phone. then i successfully used odin to flash back to stock rom. i successfully re-rooted my phone with the same saferoot method i used before (install.bat) and checked using root checker. my phone was successfully rooted. a few days later i was trying to use a program that requires root but it wasnt working. i checked my root status again using root checker and this time it said my phone was NOT rooted. my phone essentially unrooted isself somehow. so i used the tried and true saferoot method again to re-root. ive tried it about 5 times now. i tried uninstalling supersu, rebooting the phone, turning off the phone and taking the battery out. everytime i run the saferoot script it ends with

--- Samsung Galaxy S4 Android 4.3 Root ---

--- Based on the CVE-2013-6282 exploit by cubeundcube ---

Do you want to install Busybox on your device [Y/N]? y

[*] Testing adb usability

Plug in your phone and Press any key to continue . . .

[*] Waiting for your phone to appear

[*] Your phone is detected and ready for rooting.

[*] Sending files to your device...

[*] Starting rooting program.

ro.build.product=d2vzw

ro.build.id=JSS15J

Your kernel is patched!

This device is not supported.

[*] Checking if rooting succeeded

[*] Unfortunately, rooting failed. Cleaning up.

Press any key to continue . . .

what is the world is going on? i dont even want a custom rom or anything i just want root access. help?
[Verizon Samsung Galaxy S 4] khan59:
VZ MK2 - Success! Lessons learned...

k1mu - great work! Once I "learned" a couple things...the process was a snap. :good: To share with everyone here goes...

1) Had previously installed the Android SDK back from my HTC DINC2 playing and had entered the PATH to that older version of adb files into my OS and was initially getting "old version" errors. Removed the path to that install...good to proceed.

2) Bluestack - make sure you stop the services for this Android emulator. I kept having issues running adb and would get stuck on the "waiting for the phone to appear". It would never get past this. If I interrupted the batch and restarted it...I would get further...but no files would ever get copied. I kept thinking I had 2 instances of adb running (visible in task manager) and would do the "kill-server" and start over. No dice. Installed Kies3 on my laptop and confirmed comm's were good to the phone. I then tried the "adb devices" and kept noticing it showed an "emulator" in the list. Assumed it was the adb process itself but then discovered it was the bluestacks emulator. Stopped the services, killed adb and started over.

Done in 5 seconds tops. Magic! :laugh: DOH!

Great support - KEEP READING - I must've read 90+ pages until just enough info popped out. The answers are here, hope this helps keep the first page current with tips. :good:

Cheers!
[Verizon Samsung Galaxy S 4] kristinstokes:
Edit fixed

so i dont kno if anyone has ever had or ever will have this strange problem but i figured id post what i did to fix it just it case it may help someone one day. i used the same method of flashing my phone back to stock rom with odin as i did before when i had bricked my phone. odin said passed and i thought the phone was back to stock but when i hit the power button my home screen and background and icons were exactly the same as before, the phone was NOT back to stock. but i figured what the heck ill run saferoot one more time just to see what happens. this time saferoot worked exactly as it did before and rooted my phone. i checked with root checker and i now have root access once again. i have NO idea how that happened but somehow it worked.
[Verizon Samsung Galaxy S 4] BROKEN1981:
ok so it does not work with 4.4. i get that. BUT, in about phone it says android version 4.3.

did i some how miss read the version?