yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] k1mu:
Some library or other file that programs need to work right was apparently removed.

You need to flash a factory no-wipe ROM to undo whatever you did once the phone was rooted. That'll get it back to stock and working right.

I agree that VZ puts a bunch of junk on the phone - I don't need their "NFL Mobile" app wasting my storage space, for example. However, removing bloat can and does screw phones up.
[Verizon Samsung Galaxy S 4] dean2900:
I do not to be annoying. I am using low maintenance. Take a look at my history and you will see the previous post was my only one in 7 years since a member.

I wiped the phone and the cache and didn't have a backup as I really don't keep much on my phone and those apps are easy to rodownload and have all pictures/videos and other files installed on the SDCard,

I guess I am confused on how to flash no-ripe ROM since the bootloader is locked on 4.3. Maybe I misunderstood what you were saying to do.

Thanks,

Dean
[Verizon Samsung Galaxy S 4] k1mu:
Dean, What build is your phone running?

Open Settings/More/About phone and scroll down to Build number.

Once I know that, I can point you to the proper thread to recover your phone.
[Verizon Samsung Galaxy S 4] dean2900:
i535VRUCML1
[Verizon Samsung Galaxy S 4] k1mu:
OK, so go here to get the stock ROM for your phone.

Download and unzip. Install ODIN and flash with the .tar.gz in the PDA slot.

Instructions for flashing can be found here. Be careful to only flash a ML1 ROM image.
[Verizon Samsung Galaxy S 4] dean2900:
Thanks will do. I already have Odin installed. Just wanted to make sure I use a good rom!

Dean
[Verizon Samsung Galaxy S 4] k1mu:
Just to make sure it's clear: that ROM image will wipe your phone. All of your data, apps, etc. will be gone. Once you're re-flashed, you can recover from Google some of what you lost, but you will lose data.

Before you flash, see if it's possible to back things up to your external SD card. Probably not, if things are that flaky.
[Verizon Samsung Galaxy S 4] dean2900:
I keep worthwhile app data on my Nexus 7. I really only have 5 apps I need and prefer to wipe. I choose not to have google reinstall apps. It is better to download manually and make sure they are compatible with the new phone build.
[Verizon Samsung Galaxy S 4] oreice:
does this not work in windows 8.1?
[Verizon Samsung Galaxy S 4] dean2900:
I have a working -phone! Thanks so much! I love Odin!

I do have another question in case anyone has run into it. My SDCard is no longer showing up. This happened also with the OTA update and it just fixed itself on it's own from what I can tell.

Thanks again,

Dean
[Verizon Samsung Galaxy S 4] imafriend123:
Alright. Sorry for so many questions. Thank so much!

[Edit] HOLY CRAP. IT WORKED. You're a God. Thanks so much!
[Verizon Samsung Galaxy S 4] godrick15:
need help unrooting. Status reads "custom"

I rooted my phone with this method and everything was fine. I had SuperSu and it disabled Knox. But I decided to unroot my phone because I now want to flash Cyanogenmod. I followed the instructions from the op, unrooted via SuperSu...although I didn't uninstall Busybox, Winam, etc because I never downloaded them.

So now I'm trying to use another method to root. I tried Odin to install philz but it's always failing. I tried Odin 3.07 and 3.03. I don't any other way to root my phone. All drivers and Kies are installed on my PC. In Download Mode it reads.......

Odin Mode

Custom binary download: no

Current binary: Samsung Official

System status: Custom

Know warranty void: 0

AP swrev: a2

Is the reason why i can't use Odin is because it still says "custom?" Any help would be appreciated
[Verizon Samsung Galaxy S 4] WordsworthESP:
Wait, what? You unrooted your phone to flash CyanogenMod? I'm afraid you need to do some reading... a lot of reading, actually. This is not a ROM, and you couldn't flash CM without being rooted anyhow. Also, if your bootloader is locked (and you're on MF3 or a newer build) you can't flash CM regardless.

To answer your question about the custom flag, you have to undo any and everything that made your device custom. Anything added to any area within /device, a different boot animation, etc. You have to be completely 100% stock. Read the thread, there are more detailed instructions here. Though I should state, for the record, that none of this... or any other version of root, is going to help you flash CM.

If you don't want to ruin your device, I recommend you slow down, relax and read. Read & search through the forums for your device variant/carrier, there's a lot you need to know before attempting whatever it is you're trying to do.

Sent from my Hyperdriven S4
[Verizon Samsung Galaxy S 4] godrick15:
I think you misunderstood the question. The OP mentioned that you cannot flash custom roms using Saferoot, which I used. At first, I just wanted root access.

Now, I want root access with the added ability to flash CM. Which I couldn't do before with this method, because OP clearly states it will brick my phone. So I unrooted my device, from this method as directed by OP's 2nd post.

>Unroot by wiht Supersu

Now my phone status is still custom and Odin is not letting me flash custom recovery. I dont care about Custom showing up. I'm worried more about Odin not working.
[Verizon Samsung Galaxy S 4] yake:
This is my final (?) report about trying to root my GS4 LTE running a stock 4.3 VJUEMKE (ZTO):

- Initial attempt to use Saferoot. Failed with an 'unsupported device' message.

- Factory reset via menu, than tried Saferoot again: another failure.

- Factory reset via recovery, than tried Saferoot: another failure.

- Tried to find some hope using Universal Root de La Vega: after some research, did not attempted since it should flag the knox counter.

- Flashed stock 4.3 and tried Saferoot again, but again with no luck.

- Tried to find some no wipe rom to flash and reset security policies: no luck.

Did I missed anything? Otherwise I will only wait for a ( who knows) another safe root method, or simply wait until my warranty expires, 6 months from now.

Thanks!

Enviado de meu GT-I9505 usando Tapatalk
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Custom recovery is INCOMPATIBLE WITH YOUR PHONE...Period. it's not about the custom flag it's about the permanently locked bootloader, if you aren't being careful (you aren't, by the way, as far as what you have written) you are going to end up with a permanently bricked phone
[Verizon Samsung Galaxy S 4] k1mu:
There's no reason it shouldn't. However, I wouldn't put Windows 8 on anything that I had to use regularly so I can't tell you for sure.
[Verizon Samsung Galaxy S 4] k1mu:
Saferoot installs busybox, so you must uninstall it go get rid of custom. Read post #2 for how to remove busybox, which will require you to re-root.

However, you are wasting your time and doing things that probably do not apply to your phone. You're also risking voiding the warranty.

No. ODIN will work fine even though custom is set. What won't work is trying to flash a custom recovery. You can't do what you want to do.
[Verizon Samsung Galaxy S 4] k1mu:
I've clarified the OP to state that you can't flash custom recovery on a phone with a locked bootloader. It doesn't matter how you root it.
[Verizon Samsung Galaxy S 4] k1mu:
No, you didn't miss anything. If it says "unsupported device" then it's patched and isn't rootable using saferoot.

Root de la Vega was patched fairly quickly - anything later than MI1 is not vulnerable.
[Verizon Samsung Galaxy S 4] SysAdmNj:
I'm trying to remove this root and I cant get the "#" after i su from adb shell. adb devices recognizes my device, adb is working I just cant su I just get a "shell" prompt. Now if I skip this step and try to unroot from the super su app, am I risking warranty?
[Verizon Samsung Galaxy S 4] k1mu:
No, you're not risking your warranty, but you won't be able to clear the "Custom" flag if you leave busybox installed.

Is your device actually rooted? What happens if you open a root-required app like Titanium Backup?

If root is working, open SuperSU and then tap on the ADB Shell entry. tap on "Forget" and try to "su" again at the shell. Does SuperSU now prompt for permission?
[Verizon Samsung Galaxy S 4] SysAdmNj:
It definitely didnt. So I reset my device and still see custom. I'm attempting to root it again and I get a security message "supersu attempting to access system on your android device without authorization...... " on samsung galaxy s4 mini. Not sure where in security I disable that.
[Verizon Samsung Galaxy S 4] k1mu:
You've taken the security policy update that actively blocks SuperSU. The only way I know of to work around that is to re-flash the FACTORY STOCK rom. Not a "stock deoxdex", but stock, unmodified, Samsung factory. (Modified ROMs will set the warranty void flag.)
[Verizon Samsung Galaxy S 4] tarster:
So I have a question, I rooted the phone and it seems like I cant receive mms messages, I searched for mms in the thread and didn't come up with something, is there something I am missing here? I have been rooting for along time but this is a first that I root and lose mms, the MMS show up on my phone but they don't download, and I click download and they just time out.
[Verizon Samsung Galaxy S 4] tarster:
So it would appear that after I removed busy box, rebooted my phone and then temp unrooted my phone via superuser instead of su app, never liked supersu before, always had issues with it.. yet everyone seems to put it in as the go to superuser app... anyways.. after a temp unroot, I can recieve mms again... wierd..

Edit: So I updated the SuperSU app and installed the new binarys, removed superuser. and my MMS still work.... wierd.. so I am going to try installing busybox from the play store and see if it still works or might break something..

edit 2: it would appear as everything is working now... must have been a glitch or something.. still very odd.
[Verizon Samsung Galaxy S 4] zyclops1:
anyone tried with i9505XXUEMKE Fw? im afraid of knox 1x0 please tell me if anyone did it without a problem thanks :)
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
No need to fear; as has been made quite clear this method doesn't trup knox counter;the script either succeeds or it doesn't.
[Verizon Samsung Galaxy S 4] zyclops1:
How to revert back to stock?
[Verizon Samsung Galaxy S 4] Mistertac:
Sure does that's unfortunately what I have. I miss windows 2000 Pro. Lol

Id even take XP Pro.
[Verizon Samsung Galaxy S 4] dcharleyultra:
Are you kidding? It's mentioned many times throughout this thread, starting with the second post.
[Verizon Samsung Galaxy S 4] Mistertac:
You mean how to unroot? If that's the case remove busybox then unroot with supersu. That's one of the ways at least. Depending on how much you modify your phone after rooting ...sometimes just using Odin is easier.

---------- Post added at 08:25 AM ---------- Previous post was at 08:19 AM ----------

Also ... K1mu.. Why don't you get a donation address? With all the people you've helped including myself, and with the constant support you're giving, I need to buy ya a beer or two. Your root method was one of the easiest.
[Verizon Samsung Galaxy S 4] zyclops1:
Nope I mean did I need special firmware
[Verizon Samsung Galaxy S 4] hmoobguy:
SuperSU install New Binary - Boot Loops

Question here on using Saferoot method, I am on the Verizon i605 and after I completed the saferoot and performed the SuperSU install new binary (standard not TWRP) option, my phone just continues to do a boot loop. It will shut off and boot to the main screen and reboot. Any ideas as to why? I followed exactly what the video did. The question comes down to the SuperSU installing the normal binary.

http://www.youtube.com/watch?v=uii_mYm8IGE&feature=youtu.be frame 6min 14seconds.

Flashing Odin with the correct image did not fix this. I had to do a Verizon repair to get my phone back to normal.
[Verizon Samsung Galaxy S 4] k1mu:
To be able to help here, I'd need more info on what you saw.

What build are you using on your i605?

SuperSU said that it needed to update the binary, and when you told it to use the "standard" update technique, what happened? Did it immediately reboot, did a message from Knox or anything else show up before it rebooted?

What did you flash on your phone from ODIN? Saferoot only changes things in /system, so a no-wipe ODIN flash will remove all traces of it being installed. It's hard for me to figure out why re-flashing didn't fix it unless you flashed the wrong ROM image.
[Verizon Samsung Galaxy S 4] hmoobguy:
Thanks for the reply.

Build JSS15J.I605VRUEMJ9

I don't recall at the moment, but I think when clicked on the "standard" technique the phone did not reboot, Knox dialogue message never came up. So I rebooted the phone. This was last night so forgive me if I don't have all the details.

I tried flashing ODIN back only after the phone kept doing the boot loop (stock image I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5) . That did not help. I had to use the Verizon update/repair tool to wipe and restore my phone to factory.
[Verizon Samsung Galaxy S 4] k1mu:
If you've disabled Knox earlier on this phone, it won't come back unless you install a full-wipe ROM. So, not having that prompt is perfectly OK.

Well, it's too late to tell what was making it unhappy. It would have been nice to have a logcat dump while it was booting.
[Verizon Samsung Galaxy S 4] hmoobguy:
This is the first time I've ran through this root process so Knox could have not been disabled. I did see Knox was being disabled through the CMD window (not 100% sure if it was successful). I should've taken a screen capture of it.

I don't wanna run though this again just to have the same boot loop. Only reason I need root atm is so I can remove annoying ads.
[Verizon Samsung Galaxy S 4] alundra212:
Hey guys!

Does anyone know if triangle away works after rooting with this method?
[Verizon Samsung Galaxy S 4] hmoobguy:
Success this time

I retired it this evening and it worked. :good:

After installing SuperSU, Knox dialogue did pop up on the phone, so I chose to disabled it, then SuperSU updated itself. (pressed any key on cmd window). After this it proceeded to ask to install Binary (and I selected Standard), no reboot this time. And most importantly, no boot loops.

Confirmed with Root with root checker.
[Verizon Samsung Galaxy S 4] k1mu:
What are you trying to do? Rooting using Saferoot does NOT increment the flash counter, so you don't need to reset it.

You can use Triangle Away to clear the "Custom" status if you're careful. From what I've read, some operations for Triangle Away can trip the Knox Warranty Void flag. I haven't done that, so that may just be rumor.

So, again, what do you need to do?
[Verizon Samsung Galaxy S 4] agovinoveritas:
Hi, Just here to say that it also works on the Canadian variant: Note 2 T889V. For sure, so just to add to the list. Cheer!
[Verizon Samsung Galaxy S 4] alundra212:
Yes. All i want to do is reset flash counter because i used to have omega rom but then ran triangle away and flashed stock to get back warranty.

After flashing stock i went to download mode and the counter was official, but after an official samsumg OTA update now it appears as custom. Thats why i wish to run triangle away to clear it.

By the way, is it safe to reflash stock without tripping knox right after i run triangle away?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
As far as I know it is impossible to untrip the knox counter...otherwise why would they even bother putting it there. Take this as a learning experience to research before just trying to jam a ROM into a bootlocked device.
[Verizon Samsung Galaxy S 4] alundra212:
I think you misunderstood me.

My knox counter is untripped (0x0). The only thing i wish to reset is the flash counter (wich is custom at the moment)
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Don't use TA as it may trip the knox. If you (for whatever reason) just want the custom flag gone use wanam or the other methods mentioned copious times in this thread.

To completely remove custom flag unroot via post 2 in this thread.

I gonna be a bit jerky, and well I apologize for that, but if you'd just read this thread you'd have had your questions answered without time wasted or any confusing of others
[Verizon Samsung Galaxy S 4] Peñaran561:
Worked on my phone, but there is one problem that I am having. Why does the battery stats in settings indicate that WiFi is on when I have it off? Any help would be appreciated.
[Verizon Samsung Galaxy S 4] gui.zanotelli:
Not working.

Just tried it, and it does not work for GS4 GT-i9505, VJUEMKE. At least both system status and knox warranty are unchanged (Official and 0x0, respectively)

=/

Thanks anyway.
[Verizon Samsung Galaxy S 4] rosedog:
Let me buy you a beer or two!

OMG This is exactly what I needed! You can put the T-Mobile Galaxy Note 2 SGH-T889, MK7 on this list too!
[Verizon Samsung Galaxy S 4] k1mu:
You're mistaken - the flash counter is zero, as you haven't flashed anything that tripped the Knox Warranty Void flag. Factory signed flashes will not trip either of the flags.

Install Triangle Away. It'll tell you that the flash counter is zero. Using it to reset the flash counter will do nothing to clear the "Custom" flag, and will probably set the warranty void flag. (This I am not sure of, and don't want to experiment with it for no reason.)

The "Custom" flag is set by a scanner that runs at boot time (SysScope) that looks for modified files. If it finds those, it sets the custom flag.

Triangle Away has a "Periodic system modified reset" that seems to remove the "Custom" padlock at boot. It does not clear the "Device status: Custom" in settings, however.

And of course, you can always get rid of Custom status by flashing back to stock.
[Verizon Samsung Galaxy S 4] iphoneandroidworld:
thanks for this tool

i want to know if you will make saferoot to work on 4.4.2 kitkat at least for i9500 and i9505, that would be great
[Verizon Samsung Galaxy S 4] k1mu:
WiFi not connected does not mean WiFi off. Check the WiFi toggle and verify that it's off.
[Verizon Samsung Galaxy S 4] Peñaran561:
WiFi toggle was off when I took the screen shot, but I'll see what else could be causing it. Thank you though. :)
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
As well as the above suggestion, make sure this setting (in wifi advanced) is unchecked

---------- Post added at 03:00 PM ---------- Previous post was at 02:57 PM ----------

But was wifi toggle off the entire time of the history shown in your screenshot?
[Verizon Samsung Galaxy S 4] k1mu:
It's very unlikely to work on KitKat as the vendors have been patching.
[Verizon Samsung Galaxy S 4] social-design-concepts:
Could saferoot be adapted to work on other 3.4.xx kernels?
[Verizon Samsung Galaxy S 4] Peñaran561:
Yes the toggle was off, I'll look into the advanced settings to see if that does it.

---------- Post added at 05:47 PM ---------- Previous post was at 05:19 PM ----------

@Nergal di Cuthah your advice worked boy do I feel dumb for overlooking this simple problem. I find this strange because I don't remember changing any settings to this.
[Verizon Samsung Galaxy S 4] k1mu:
Assuming a similar kernel exploit, yes. However, there's things that saferoot needs that the vendors are starting to lock down. For example, it pushes a rooting program to the device and executes it. Some of the recent security policy updates are denying the ability to run programs installed over ADB. I could update saferoot to work around this (make it a .so along with a GUI app that triggers it).. however, without a phone having problems being rooted, it's pretty hard to know what needs to change. Attempts to debug remotely aren't very productive.
[Verizon Samsung Galaxy S 4] clearyt1:
USB port broken, need to return to stock

Hey, hoping someone in this forum might be able to help--searched and can't find a post about this. Have a company issued VZW S4 that I used this saferoot method for, and installed Safestrap newest recovery (hosed the stock recovery by trying stupidly to flash TWRP).

My USB port is hosed, but phone is under warranty. If I send it back this way I'll get hit for the voided warranty I'm assuming. Hoping there's a way to flash back to unrooted stock and stock recovery with just my SD card or something so I don't get the hit on this.

Any insight or suggestions on this would be GREATLY APPRECIATED!!!
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
I'm pretty sure it's a new feature added in 4.3 and was default set to on.
[Verizon Samsung Galaxy S 4] Scottchy014:
Did you do a nandroid backup? If so, is it on the sd card or computer? I would start by asking, Did you flash TWRP while in Safestrap?
[Verizon Samsung Galaxy S 4] clearyt1:
No, flashed TWRP first and borked my stock recovery (was already on 4.3 and as a noob S4 owner didn't realise you couldn't install a custom recovery). I Installed Safestrap after. Don't have a Nandroid with the stock recovery either, so not sure how to restore to "warranty-valid" status without the use of USB...
[Verizon Samsung Galaxy S 4] k1mu:
You should be able to do this

if you left the stock rom intact

entirely from your phone. You shouldn't have been able to overwrite the stock recovery, so it should still be there.

If that's not true, then you'll need to figure out how to get it onto your SDcard and flash it.

To restore without USB:

Boot into your stock ROM.

Run Safestrap and uninstall the recovery.

I'd reboot at this point.

Now, uninstall Safestrap.

Open a terminal emulator window and clear off the busybox stuff:

$ su (the system prompt ends with "$", you type "su" and Enter - you may need to give permission.)

# mount -o remount,rw /system (the system prompt now reads "#")

# find /system/xbin -type l | xargs rm (that's a lower-case L after '-type')

# rm busybox

Now, on your phone, use the "Full unroot" in SuperSU. It'll remove su and the other changes. Now reboot and you'll be clean.
[Verizon Samsung Galaxy S 4] rebel1699:
Cracked my screen before 4.3 was available. Fixed now, and upgrading. Thanks for the root work fellas.
[Verizon Samsung Galaxy S 4] k1mu:
OK, so I've set this up. :) Guess it's about time, I suppose. Thanks for the kick in the butt.
[Verizon Samsung Galaxy S 4] Mistertac:
Good deal.... Youre a huge help on here!

Sent From My Verizon S4
[Verizon Samsung Galaxy S 4] katodragon:
Successfully rooted and no custom flag on my sprint phone. Still says official. :)
[Verizon Samsung Galaxy S 4] numbR7:
Worked nicely--thanks for saving me from an expensive piece of plastic...
[Verizon Samsung Galaxy S 4] shewantsmyduck:
After browsing this thread yesterday, I decided to flash the MOAR 4.3 Rom on my Verizon s3, everything worked perfectly, until I went to install my apps and it said i had low storage space ... before doing this I have about 6-7gb free and now I cant even install half of my apps. Thinking it was hust MOAR, i wiped and safestrapped Wicked Sensations, really nice rom imo. Booted it up and checked, still really low memory. Is there anything I can do to get my space back?

-Thanks

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

Whoops wrong thread
[Verizon Samsung Galaxy S 4] katodragon:
Has anyone tried this with the new ota 4.4.2 update from Sprint with any luck?
[Verizon Samsung Galaxy S 4] williambs:
Rooted using Saferoot after recovering from softbrick, need Modem

I have the phone up and running and do not have a modem.

Here is where it is at:

CWM installed

SU installed

Android 4.2.2

Baseband M919UVUEMK2

Kernel 3.4.0-440244

Build JDQ39.M919UVUAMDB

I wish to move to 4.4.2 with the phone rooted.

I have tried to move to MDL with odin, but get a FAIL!

Could someone please help.

Thank you
[Verizon Samsung Galaxy S 4] NRadonich:
Thanks, this worked perfectly for my T-Mobile Galaxy S4!
[Verizon Samsung Galaxy S 4] gothicasshole:
Hey when you safestrap and don't put that new rom as your stock your only inside of an 8 gb partition