yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] mikers1:
Question: If I use this method to root my phone, if/when a custom recovery is ever created for this phone, will I be able to use it at that time after using safe root? If so, how? Would I have to undo this root first?

I'm guessing the answer is that yes, I will be able to install the custom recovery if it is ever created after using this root method. I just want to be sure because in the past when I have rooted, it was always a combination root/custom recovery installation package in one.

Thanks...
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
It's highly unlikely that the bootloader will ever be unlocked thus I doubt custom recovery will be created. Safestrap is the only ROMming available now, and likely the future.
[Verizon Samsung Galaxy S 4] gothicasshole:
Once I got mine running it disabled knox you have to click OK and agree in the su app when it reboots the on screen instructions were clear maybe I got lucky?? Or my experience with rooting and adb?? Oh make it very clear to double click the adb.exe I also downloaded the whole sdk and ran all of jelly bean drivers
[Verizon Samsung Galaxy S 4] decaturbob:
go back a couple pages to post 640....
[Verizon Samsung Galaxy S 4] gj23:
There are Backup and Restore options in the Safestrap application. Although I haven't tried to backup and restore my Stock Rom while on SS 3.71, I did do it from SS 3.65 and it worked flawlessly. (when restoring to the Stock slot, I had issues restoring it to Rom-slot 1) I have been restoring nandroid backups of custom roms while on SS 3.71, but I have to delete the Rom-slot before restoring or it will not boot. There are some people who are running custom roms in their Stock-slot, so maybe you can get one of them to try and restore a nandroid backup of the Stock rom to the Stock slot (if they did one before wiping it)
[Verizon Samsung Galaxy S 4] hondabomdc5:
I dont know if you have read my post or not but here it is....

Hello everyone. I have been pointed to this thread to try and find a issue to my MTP Failure.

Let me explain.

I am currently on ME7 and on the Hyperdrive 10.2 version of that ROM. I want to update to MJ7 so that I can update to the latest HD12. However, there are alot of steps needed like flashing the MJ7 image and doing saferoot and several other things that im sure all of you are aware of. Well, i cant even begin to do any of that because my computer will not see my phone.

I have tried multiple things to try and resolve this issue. Here is my long list of things I have tried.

-I have tried it on 2 personal laptops

-Tried it on my work laptop

- Using the stock cable that came with the phone

-Downloaded drivers straight from Samsung's website

-I have downloaded USBdeview program and uninstalled all samsung drivers and restarted each computer and plugged phone in to install all drivers and everything installs fine except for the MTP

-I have tried with USB Debugging on and off

-I have followed a Youtube video that has you go into the registry files and change a few settings

-I have researched and researched and asked questions in multiple threads on XDA and Google

- I did a FDR on my phone and reinstalled the HD10.2 ROM that I am currently on and wiped data and cache also

-Went into the application manager in settings and found the MTP app and media storage app and cleared the data and cache in those

-Put phone into "safe Mode" and tried installing drivers---still the MTP failed

-Called the Samsung tech support and had them try and help me and i pretty much already did everything that they told me to do and they could not figure it out so they told me to send my phone in and they would do a reflash on my phone...basically make it stock again but im afraid if I do that itll brick my phone since i have a custom ROM on it.

I have been at this for a week and a half. Im tired, defeated, frustrated and just dont now what else to do. It is driving me crazy and i am trying to be as patient as possible. I posted in another thread and someone told me to ask in here so that is why I am asking. I am hoping that somebody in here has some advice/help or a answer for me. Thank you so much for your support. I am looking forward to hearing what yall have to say.

With that said. I read what you said about the option that says revoke usb debugging entry...i dont have that.

Under developer options and the debugging section i have the following

Usb debugging

Include bug reports

Allow mock locations

select app to be debugged

Wait for denugger

Verify apps via USB
[Verizon Samsung Galaxy S 4] rod_ol_fo:
Are you running win8 on your laptops? I'm sure it wouldn't hurt to try this... I use zadig when my win8 laptop doesn't recognize my note 2.

http://xdaforums.com/showthread.php?p=41281284
[Verizon Samsung Galaxy S 4] Smirftsch:
works like a charm on S4, I9505XXUDMH6, without tripping knox. Damn good job!!
[Verizon Samsung Galaxy S 4] hondabomdc5:
No sir. Im running windows 7 on all 3 laptops
[Verizon Samsung Galaxy S 4] k1mu:
What does that mean, "will not see my phone"?

Plug in your phone. Go to device manager (hold down the windows key and press "Break", then click on "Device Manager".)

What shows up?

If you have USB debugging enabled, and you've given permission, you should have a "Samsung Android Phone" and "Samsung Android USB Interface". Under "Universal Serial Bus Controllers" you should see a "SAMSUNG Mobile USB Composite Device".

Switching between MTP and PTP doesn't change that. All that it does is to change the drive that appears. In MTP, I see a "SCH-I545 Portable Media Player" show up; in PTP, I see "SCH-I545 Digital Camera".

What, if any of the above do you see when you're plugged in?

What phone and build are you on? The "Revoke USB Debugging" is a new 4.3 feature if I'm not mistaken.

So, what is the problem you're trying to solve? Get adb connectivity so you can root, or getting MTP working?
[Verizon Samsung Galaxy S 4] danilo_scala:
thanks friend . waiting for xperia zl (zq) in Brazil 10.4.B.0.569 root
[Verizon Samsung Galaxy S 4] MR H3LLMAN:
I saw a couple people ask but am not entirely sure there was ever a definite answer but will this method work on a VZW Note 3? Used it on my S4 but it appears almost every root method for the Note 3 is either super sketch or it breaks something. Pretty much every link everywhere has been taken down as a result of this. Just got my Note last night and can't live without root and debloating this thing.
[Verizon Samsung Galaxy S 4] k1mu:
Unfortunately, this won't work on the Note 3. See post #475 in this thread.
[Verizon Samsung Galaxy S 4] WordsworthESP:
Try keeping your screen awake so you don't miss the prompt on your device. I missed it a few times by not making sure I kept my display awake.

Sent from my Hyperdriven Samsung S4
[Verizon Samsung Galaxy S 4] k1mu:
The new directions in the OP should help:

Unplug your phone, then unlock/wake it. Watch the phone, then plug it in to your PC. You will hopefully see a prompt asking for permission for ADB - tap the "always allow" and OK. Do that first to make sure that adb will see the phone.
[Verizon Samsung Galaxy S 4] ibizian:
Wont alow delete of APK's

Ok guys I have read just about every post and still I am having issues. I get root check to agree the phone is rooted but every time I attempt to delete any .apk's in the system folder to clear up the wasted space all I get is delete failed.. All I really want to do is reclaim the 6 gigs of junk apk's I have installed and deleted but the systems hordes the files incase you want to use them later...

Any ideas on what I am missing or need to do yet??

Samsung GS4 with the Mk2 version.
[Verizon Samsung Galaxy S 4] k1mu:
This probably should be in the Q&A section.

Be that as it may, you need to make sure that /system is mounted read/write before you try to delete anything.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Imho you shouldn't delete the bloat just disable it, you're less likely to forget to place one back when you update. For storage space use a sd card (also read as "do you really use all those apps")
[Verizon Samsung Galaxy S 4] francescopp:
I9500 ubuemk1

i just rooted my i9500 build JSS15J.I9500UBUEMK1 in download mode i have

ODIN MODE

PRODUCT NAME: GT-I9500

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Custom

WARRANTY BIT: 0

and i don't have the open padlock when the phone is turned on

I had to do the hole rooting twice, because it didn't installed busybox on the first try.

on the second try it went through until the end with no problem

i used windows 8.1 pro with media center

hope this is helpful.

thanks for the root!!
[Verizon Samsung Galaxy S 4] m@ximum:
Can this work with S4 GT-i9500? Firmware XXUEMK8 (android 4.3)?
[Verizon Samsung Galaxy S 4] gothicasshole:
If you have root access why not download busy box from the market?
[Verizon Samsung Galaxy S 4] bastard81:
GREAT!!!!

Just tried on GT N-7100 with official Rom Europera MK9 and it works great!! Knox = 0 :)
[Verizon Samsung Galaxy S 4] kc6wke:
Tried on the Razr HD 9.30.1 OTA and worked Great

Thanks
[Verizon Samsung Galaxy S 4] livinginkaos:
Confirmed to work on the Razr M as well system version 98.30.1 .
[Verizon Samsung Galaxy S 4] aviwdoowks:
Works on msm8960 phones!!

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

---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------

You beat me to it! Lol.

The PW reset @ your site does not work btw...
[Verizon Samsung Galaxy S 4] checkthisSH:
I've only seen one instance of someone getting this to work on Verizon's Galaxy S3 in this thread.

Has anyone else succesfully rooted their Verizon S3 without any hitches with this method? I intended on rooting and flashing a custom rom long before the 4.3 update, but never got around to it and accepted the OTA without thinking. I just need root to run a few apps and am hopeful this will do the trick.

Thanks
[Verizon Samsung Galaxy S 4] k1mu:
It's a small download and it's harmless if it doesn't work, so give it a shot.
[Verizon Samsung Galaxy S 4] yepyep14u2know:
I'm on Verizon with the GS3 and rooted it shortly after the OTA with the saferoot. No problems, worked correctly on the first try. Been a few weeks now and haven't noticed any problems. TiBU works great and have apps frozen without issues
[Verizon Samsung Galaxy S 4] Craleb:
There is a security policy update that just came to my phone today. is that safe to take or will affect my root.
[Verizon Samsung Galaxy S 4] awskier08:
Worked as easy as eating pie.

awesome job guys. :)

just had to do a adb shell to it before i ran it, it wouldn't see my phone otherwise, A+
[Verizon Samsung Galaxy S 4] aviwdoowks:
I think the op is entitled to a bounty @ the razr hd forum, in Q & A.

---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------

Bounty thread http://xdaforums.com/showthread.php?t=2549684

---------- Post added at 06:50 PM ---------- Previous post was at 06:49 PM ----------

I do think the user who applied it is in there somewhere too.
[Verizon Samsung Galaxy S 4] mochamoo:
Just showed up on my phone as well. Anyone know what it's about?
[Verizon Samsung Galaxy S 4] gothicasshole:
Was it by look out? If so I wouldnt worry about it so much
[Verizon Samsung Galaxy S 4] tshelby73:
It showed up on mine a while ago too and asked the same question. I got no response so I just froze it with titanium. The program is under security settings on the phone that causes it. I didn't want to chance losing root but if I can leave it on I would prefer too.
[Verizon Samsung Galaxy S 4] fascinateguy:
i couldn't get it to work, did you do this on AP fastboot mode? can you please provide the steps?

thanks
[Verizon Samsung Galaxy S 4] kc6wke:
Normal boot mode. make sure you have access to your phone in adb Follow the steps in the OP. Some are saying to install the samsung driver also, But I just had the Moto drivers, ran the install.bat and followed the prompts. worked perfect.
[Verizon Samsung Galaxy S 4] fascinateguy:
Got it, thanks
[Verizon Samsung Galaxy S 4] hondabomdc5:
Just plugged phone in. Says " Installing driver Software" . It installed SAMSUNG Mobile USB Composite Device, USB Mass Storage Device, SAMSUNG Android ADB Interface and SAMSUNG File-Stor Gadget USB Device. Those 4 have a check mark to the right and say Ready to Use.

Now, on my phone in the notification bar it says "connected as installer" . I tap on that and I have the MTP or PTP option to check. I checked the MTP option and then MTP USB Device and SAMSUNG Android ADB Interface installs. The MTP USB Device Failed and the SAMSUNG Android ADB Interface installed and is ready to use.

So i held down the windows key and hit break. I then clicked on device manager. It opened up and i see MTP USB Device under "portable devices" and it has a yellow triangle next to it. I also see Samsung Android Phone and under that SAMSUNG Android ADB Interface.

Under Universal Serial Bus Controllers i see SAMSUNG Mobile USB Composite Device.

My phone is the white 16 GB GS4 for Verizon. I am currently on Hyperdrive ROM RLS10.2 . Android version is 4.2.2. Baseband Version I545VRUAME7. Build Number JDQ39.I545VRUAME7. Hardware Versoin I545.06.

So. If i go and click on "my computer" I do not see my phone under any drive in there. Basically to me my phone isnt being seen by my computer. I should be able to open my computer and see my phone in there and then click on it to see whats on the sd card or on the internal memory but i cant because the MTP USB driver fails.

My goal with all this is to get the MTP driver to install and work as it should so that I can go from hyperdrive 10.2 to hyperdrive 12. In order to do that I have to switch from ME7 to MJ7 and i have to be able to use ADB to root my phone once I get to MJ7. I cant do any of that though until i get the MTP USB part to work.
[Verizon Samsung Galaxy S 4] samusishere:
Can someone please give me a hand, I have done everything I possibly can to get this to work with no avail, I've taken all the steps and still nothing. I soft bricked my phone and had to use a no-wipe rom to restore it, everything went fine but I ofcorse lost root, now no matter what I do I can't get it back.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
You need to provide more information than that. How far does the script get? Please post the contents of the commandline (dos) window. Did you remember to walk through the steps exactly as written (most often forgot seem to be: turning on usb debugging, revoking old adb authorizations, switching between MTP and PTP).
[Verizon Samsung Galaxy S 4] samusishere:
Yes I have done all of the steps, When I have my device plugged in and I start the batch file, after I click enter about 2 seconds later the window closes. any ideas I have all of the necessary drivers installed.

I then started the application without the phone connected first and this is what I get

--- 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 . . .

Watch your phone. If you see the "Allow USB debugging?" prompt

Tap on the "Always allow from this computer" checkbox

then tap OK

If this script appears to be stuck at "Waiting for your phone to appear",

then you should tap on the USB icon in the notifications that says

"Connected as a media device". On the"USB computer connection"

page, switch between "Camera" and "Media Device" to see if the

device appears.

[*] Waiting for your phone to appear

* daemon not running. starting it now on port 5037 *

* daemon started successfully *
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Don't double click the script. From the start menu type cmd (if you are on vista 7 or 8 right click the item that appears and choose run as admin)
[Verizon Samsung Galaxy S 4] samusishere:
I was able to get the process to complete, but supersu says installation failed when I'm promted to update, it says in the windows to please reboot and try again.

I click continue in the cmd window and it causes a superuser window to pop asking for me to allow or deny, I allowed and then dialog poped up saying flies have root access, however I still can't get supersu to update, any ideas
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
So supersu is on the device and asking to update the binary? Did it ask to disable knox? Are you getting any knox errors?
[Verizon Samsung Galaxy S 4] samusishere:
no it did not ask to disable knox and yes supersu is on the device however when I try to update binaries it says installation failed.

I left the script running in windows and continued after it said to continue after supersu has updated and it then causes a supersu popup asking for permissions, I confirm it and dialogues at the bottom of the screen appear confirming the permissions, I have no idea what to do from this point, I've rain the script twice more to no avail

This is what currently is happening--- 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=jfltevzw

ro.build.id=JSS15J

Succeeded in getroot!

Remount success!

Copying files..

Done.. reboot to enable root!

[*] Removing temporary files...

[*] Rebooting... Please wait.

[*] Waiting for device to re-appear...

error: protocol fault (no status)

[*] Checking if su is still there

error: device offline

Wait until your phone reboots,then unlock it and Press any key to continue . . .
[Verizon Samsung Galaxy S 4] samusishere:
I've also just realized that ADB is given root access, but supersu is still unable to update binaries, I am getting an installation failed error. Is this maybe because I was rooted before I softbricked my phone and used a no-wipe image to recover?
[Verizon Samsung Galaxy S 4] k1mu:
Yeah, if it's not a Samsung phone those drivers won't work. :)

You need to do whatever is needed to get ADB to connect. Once that's done, you're ready to go.
[Verizon Samsung Galaxy S 4] k1mu:
My guess: when you gave ADB permission on your phone, you didn't check the "Always allow from this computer", so when it rebooted you didn't have ADB access any longer.

Unplug, unlock, plug it in, and re-enable ADB with "Always allow".
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Would he need also revoke usb permissions (pre "plug it in" ) or no?
[Verizon Samsung Galaxy S 4] k1mu:
What kind of phone?

If you can capture the output of the root script it would be helpful in diagnosing the problem.
[Verizon Samsung Galaxy S 4] k1mu:
No - if the permission hasn't been set to always allow, it's going to prompt each time it's connected. (Including across reboots.)
[Verizon Samsung Galaxy S 4] samusishere:
I did check that box, same outcome
[Verizon Samsung Galaxy S 4] k1mu:
OK, that helps to clarify.

This site http://www.suggest-a-fix.com/index.php?/topic/180-windows-wont-install-samsung-mtp-driver/ appears to have a bunch of potential fixes for that problem. That's one of the likely hits from "fix samsung MTP driver".
[Verizon Samsung Galaxy S 4] samusishere:
I have the galexy s4, can you please tell me how to go about doing that?

I have no idea how.
[Verizon Samsung Galaxy S 4] c0bain:
my small report:

GT-I9192

MK4 Build Date 13.11.2013. Exploit works.

ro.build.product=serranods

ro.build.id=JDQ39

search kallsyms...

1 2 3 4 5 6

(kallsyms_addresses=c08c2d40)

(kallsyms_num_syms=000146f6)

kernel dump...

1 2 3 4 5 6 7 8 9

prepare_kernel_cred=c009b88c

commit_creds=c009b378

ptmx_fops=c0f26a80

ptmx_open=c03220f0

tty_init_dev=c031a524

tty_release=c031a6a8

tty_fasync=c03195d4

ptm_driver=00000000

Succeeded in getroot!

ML2 Build Date 10.12.2013. Doesn't work.

ro.build.product=serranods

ro.build.id=JDQ39

setsockopt() failed: Bad address.

this device is not supported.

kallsyms_addresses search failed
[Verizon Samsung Galaxy S 4] k1mu:
Which S4? I have the info for the VZ and ATT models.

To grab the log, click on the icon in the upper left corner that says "C:\".

Pick "Edit", "Mark" from that, highlight the text, then "Edit", "Copy". Now you can paste it.
[Verizon Samsung Galaxy S 4] k1mu:
Thanks. Interesting that the build ID doesn't change but it doesn't keep working.

That "setsockopt() failed: Bad address" means that it's patched, unfortunately.
[Verizon Samsung Galaxy S 4] gunz.jones:
Thanks k1mu. Rooted and cleaned up without a hitch.
[Verizon Samsung Galaxy S 4] en11gma:
can this work on the Sprint S4 (sph-l720) with official MK2?

im stock and not rooted and no custom recovery
[Verizon Samsung Galaxy S 4] Sczar:
This been posted before lots of times.

You can try it. If it doesn't work it won't hurt your phone. :)

VZ S4 rooted MK2 SS
[Verizon Samsung Galaxy S 4] en11gma:
if its been asked several times before then you already know the answer i take it?

what is it?
[Verizon Samsung Galaxy S 4] gothicasshole:
Did you download kies? And get the updated drivers from them? You see the drivers preinstalled on the phone are 32 bit im running 64 bit win 7 os so I needed to get the correct drivers from kies and im not sure if it has win8 drivers at all so please down load kies and get your correct drivers then once that is done you need to go to the tools folder and run the adb.exe then run your script
[Verizon Samsung Galaxy S 4] AndroidCraig:
So I updated my VZW Galaxy S4 to MK2 and lost root. So I tried the Saferoot method in the 1st post and no go.

I did a factory reset and still no go.

This is the output from the batch process

--- 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=jfltevzw
ro.build.id=JSS15J
Succeeded in getroot!
Remount success!
Copying files..
Error opening /system/xbin/daemonsu for write: Permission denied
Done.. reboot to enable root!

[*] Removing temporary files...

[*] Rebooting... Please wait.
[*] Waiting for device to re-appear...

[*] Checking if su is still there
Wait until your phone reboots,then unlock it and Press any key to continue . . .

On your phone, open SuperSU and let it update if it asks.
When SuperSU is done updating, Press any key to continue . . .
On your phone, watch for the SuperSU permission popup and give
permission for ADB Shell to gain root permissions.

[*] Disabling Knox
Package com.sec.knox.seandroid new state: disabled
[*] Setting Permissions
Unable to chmod /system/xbin/daemonsu: Operation not permitted
[*] Installing busybox

--- All Finished ---
Press any key to continue . . .

Any ideas why it's having issues with the /system/xbin/daemonsu: portion of the script? I'd really like to get root back.

Thanks
[Verizon Samsung Galaxy S 4] gunz.jones:
Did you remember to setup up debug and allow it from the drop down? It looks like it's not actually gaining root and keeping it.
[Verizon Samsung Galaxy S 4] AndroidCraig:
I do have Debug set up, and I allowed it for the computer. But I'm not sure what dropdown you're talking about. Can you elaborate on that, where is the drop down on the S4 or the PC?
[Verizon Samsung Galaxy S 4] en11gma:
he is talking about "Settings > More > Developer Opions > USB Debugging" = check it on

that is the drop down menu
[Verizon Samsung Galaxy S 4] AndroidCraig:
I've had that set already.
[Verizon Samsung Galaxy S 4] samusishere:
I fixed the problem by re flashing the system again.

It didn't ask to disable knox though, will that become a problem for some root apps?
[Verizon Samsung Galaxy S 4] -Lawless:
Not sure if it was verified before or not but just used it on a Note2 and it worked as well.

thanks again