[ROOT] Saferoot: Root for VRUEMJ7, MK2, and Android 4.3

[Craleb]

Ok I don't know what I did (my debugging mode is being retarded) but adb went trough for the second time and I now have custom boot screen. But when I open SuperSU I get "no binary installed this is a problem"

Sent from my SCH-I545 using xda app-developers app

 

[Craleb]

Sent from my SCH-I545 using xda app-developers app

 

[Surge1223]

Ok I don't know what I did (my debugging mode is being retarded) but adb went trough for the second time and I now have custom boot screen. But when I open SuperSU I get "no binary installed this is a problem"

Sent from my SCH-I545 using xda app-developers app

Now try the script in terminal. Then type su at the end

Sent from my SCH-I545 using XDA Premium 4 mobile app

 

[Craleb]

Now try the script in terminal. Then type su at the end

Sent from my SCH-I545 using XDA Premium 4 mobile app

--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---

waiting for device...
1738 KB/s (17800 bytes in 0.010s)
2452 KB/s (100452 bytes in 0.040s)
1790 KB/s (1966976 bytes in 1.073s)
2762 KB/s (1109128 bytes in 0.392s)

getroot start.
ro.build.product=jfltevzw
ro.build.id=JSS15J
Succeeded in getroot!
Remount success!
Copying files..
Error opening /data/local/tmp/install-recovery.sh for read: No such file or dire
ctory
Done.. now reboot to enable root!

removing temporary files...
rm failed for /data/local/tmp/Superuser.apk, No such file or directory

rebooting...
waiting for device...

--- all finished ---
Press any key to continue . . .


^^^^that is what my command promt says. also i can now type su and it works ( i think( it desnt say su doesnt exsist)) but my supersu still cannot install

 

[Craleb]

Before when I typed su it would say it didn't exist or something.. so getting closer!

Sent from my SCH-I545 using xda app-developers app

 

[Surge1223]

Look at my pic. Do you have a # instead of $ like the last two lines in my pic? If so you have root.

Sent from my SCH-I545 using XDA Premium 4 mobile app

 

[Cdubzz20]

In the file he linked, it doesn't have SuperSU like he states, it has just Superuser.apk

 

[Craleb]

Look at my pic. Do you have a # instead of $ like the last two lines in my pic? If so you have root.

Sent from my SCH-I545 using XDA Premium 4 mobile app

Still $


But hey thank you very much for helping me I know you don't have to. But I really appreciate it. It's guys like you that keep this community going

Sent from my SCH-I545 using xda app-developers app

 

[k1mu]

I think I'm doing it wrong? Can someone help my dumb ass. Lol or I can just to adb. Either way haha.

Sent from my SCH-I545 using xda app-developers app

Rats. That means that the terminal emulator user that you're getting doesn't have permission to write to /data/local/tmp

I used the "adb" method to root mine, and assumed that the alternate method would work, but perhaps not.

Let me think about this - I can include the adb program into the installer, I suppose, to allow everyone to use it.

 

[Craleb]

Rats. That means that the terminal emulator user that you're getting doesn't have permission to write to /data/local/tmp

I used the "adb" method to root mine, and assumed that the alternate method would work, but perhaps not.

Let me think about this - I can include the adb program into the installer, I suppose, to allow everyone to use it.

Thanks @k1mu but I have also done the adb method. I posted what it says when I do it a few posts back, in text.
It did give me the custom boot screen and SuperSU app but still don't have root?
Sent from my SCH-I545 using xda app-developers app

 

[Cdubzz20]

Rats. That means that the terminal emulator user that you're getting doesn't have permission to write to /data/local/tmp

I used the "adb" method to root mine, and assumed that the alternate method would work, but perhaps not.

Let me think about this - I can include the adb program into the installer, I suppose, to allow everyone to use it.

That would make it a lot easier, My computer seems to be having an issue making the bridge from your script running through ADB

 

[Surge1223]

I see the problem. Try this, connect to pc open command prompt. Make sure you have adb installed correctly (add it to your path) if you get no errors during the following commands thats good.

cd C:\path to mj7root folder

Then

adb devices

adb shell

adb push files\getroot /data/local/tmp/

adb push files\su /data/local/tmp/

adb push files\SuperUser.apk /data/local/tmp/

adb push files\busybox /data/local/tmp/

adb shell "chmod 0755 /data/local/tmp/getroot"

adb shell "chmod 0755 /data/local/tmp/busybox"

Sent from my SCH-I545 using XDA Premium 4 mobile app

 

[Tada10]

I see the problem. Try this, connect to pc open command prompt.
cd C:\path to mj7root folder

Then

adb devices

adb shell

adb push files\getroot /data/local/tmp/

adb push files\su /data/local/tmp/

adb push files\SuperUser.apk /data/local/tmp/

adb push files\busybox /data/local/tmp/

adb shell "chmod 0755 /data/local/tmp/getroot"

adb shell "chmod 0755 /data/local/tmp/busybox"

Sent from my SCH-I545 using XDA Premium 4 mobile app

Can you help him redo the install.sh also please?

Sent from my Galaxy S4

 

[k1mu]

--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---

waiting for device...
1738 KB/s (17800 bytes in 0.010s)
2452 KB/s (100452 bytes in 0.040s)
1790 KB/s (1966976 bytes in 1.073s)
2762 KB/s (1109128 bytes in 0.392s)

getroot start.
ro.build.product=jfltevzw
ro.build.id=JSS15J
Succeeded in getroot!
Remount success!
Copying files..
Error opening /data/local/tmp/install-recovery.sh for read: No such file or dire
ctory
Done.. now reboot to enable root!

removing temporary files...
rm failed for /data/local/tmp/Superuser.apk, No such file or directory

rebooting...
waiting for device...

--- all finished ---
Press any key to continue . . .


^^^^that is what my command promt says. also i can now type su and it works ( i think( it desnt say su doesnt exsist)) but my supersu still cannot install

The program says:
Error opening /data/local/tmp/install-recovery.sh for read: No such file or directory

That's my mistake - too many edits to the scripts. I've fixed this and will update the original post in a minute or so.

 

[Cdubzz20]

The program says:
Error opening /data/local/tmp/install-recovery.sh for read: No such file or directory

That's my mistake - too many edits to the scripts. I've fixed this and will update the original post in a minute or so.

So all I should need to do is replace the old file with the new one and repeat the steps? Or would it be better to use my computer

Edit: I'm on MJ7

 

[hakisac78]

should i update?

I'm on me7 and want to get rls 11. should i do this update then wait for ss 4.3? then flash rls11? any input would help!

 

[Tada10]

Didn't work on mine



Sent from my Galaxy S4

 

[k1mu]

So all I should need to do is replace the old file with the new one and repeat the steps? Or would it be better to use my computer

Hopefully. I just re-uploaded the .zip file in the original post. The install.bat and install.sh now push the install-recovery.sh file that's required to make this work.

Sorry - making something that's usable once into a more robust technique is a bit of a learning curve for me.

I'm hoping that this can be made to work without requiring ADB to be installed, but we'll see.

Maybe putting the files onto an exFAT sdcard will fix the permission problems - my external sdcard is formatted ext4 because I want the quick recovery that exFAT won't give me.

 

[k1mu]

Didn't work on mine

What format is your sdcard?

 

[Tada10]

What format is your sdcard?

It's Exfat see screenshot



Sent from my Galaxy S4