[Q] Reboot on altering system files - General Questions and Answers

I have two separate issues which I believe are caused by the same thing.
1. When I try to alter platform.xml in the /system/etc/permissions folder via ES File Explorer to enable 3rd party apps to have write capability to the SD card, the edit is unsuccessful and my phone reboots. When I pull a copy of the file to my PC, alter it, and then try to push it via ADB, the same thing happens. I previously used the ADB pull/push method to edit my hosts file and had success with that after doing it while in Recovery, but this time around both ways (in recovery and with the device booted up) result in my device rebooting. For the SD card fix, I've also tried the app that does it for you and encounter the same issue.
2. When attempting to update the SuperSU binary, the update fails my device reboots. This happens with either update method - normal and recovery.
So both issues seem to have the same root cause... my phone will not allow any editing of system files. Anyone have any suggestions?
For reference I'm on a Galaxy Note 4 (model SM-N910T) on T-Mobile.
Baseband version N910TUVU1ANJ7
Android version 4.4.4 (stock ROM)
Kernel version 3.10.0-2796035
Build number KTU84P.N910TUVU1ANJ7
I'm also running Wanam Xposed - not sure if that has anything to do with anything but just fyi.
Thanks

Gakuseinozen said:
I have two separate issues which I believe are caused by the same thing.
1. When I try to alter platform.xml in the /system/etc/permissions folder via ES File Explorer to enable 3rd party apps to have write capability to the SD card, the edit is unsuccessful and my phone reboots. When I pull a copy of the file to my PC, alter it, and then try to push it via ADB, the same thing happens. I previously used the ADB pull/push method to edit my hosts file and had success with that after doing it while in Recovery, but this time around both ways (in recovery and with the device booted up) result in my device rebooting. For the SD card fix, I've also tried the app that does it for you and encounter the same issue.
2. When attempting to update the SuperSU binary, the update fails my device reboots. This happens with either update method - normal and recovery.
So both issues seem to have the same root cause... my phone will not allow any editing of system files. Anyone have any suggestions?
For reference I'm on a Galaxy Note 4 (model SM-N910T) on T-Mobile.
Baseband version N910TUVU1ANJ7
Android version 4.4.4 (stock ROM)
Kernel version 3.10.0-2796035
Build number KTU84P.N910TUVU1ANJ7
I'm also running Wanam Xposed - not sure if that has anything to do with anything but just fyi.
Thanks
Click to expand...
Click to collapse
You probably need to remount /system as rw. Use this in a shell:
Code:
mount -o rw,remount rootfs /

ИΘΘK¡€ said:
You probably need to remount /system as rw. Use this in a shell:
Code:
mount -o rw,remount rootfs /
Click to expand...
Click to collapse
I went into the terminal emulator app, typed su and then the command you listed and even after that I'm still having the same problem. Any other ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Gakuseinozen said:
I went into the terminal emulator app, typed su and then the command you listed and even after that I'm still having the same problem. Any other ideas?
Click to expand...
Click to collapse
Yes, try this:
Code:
mount -o rw,remount /system

ИΘΘK¡€ said:
Yes, try this:
Code:
mount -o rw,remount /system
Click to expand...
Click to collapse
No luck after that one either.

Any more ideas?

ИΘΘK¡€ said:
You probably need to remount /system as rw. Use this in a shell:
Code:
mount -o rw,remount rootfs /
Click to expand...
Click to collapse
Did you try uninstalling the root from the unlockroot pro and rooting it again using the [super su update.zip]
try this it might work

instinctblade said:
Did you try uninstalling the root from the unlockroot pro and rooting it again using the [super su update.zip]
try this it might work
Click to expand...
Click to collapse
Are you saying to un-root and root again? Is 'unlockroot pro' an app?
Thanks

Gakuseinozen said:
Are you saying to un-root and root again? Is 'unlockroot pro' an app?
Thanks
Click to expand...
Click to collapse
Yes "Unlock-Root" is a pc software which can Unroot & Root your device

instinctblade said:
Yes "Unlock-Root" is a pc software which can Unroot & Root your device
Click to expand...
Click to collapse
That wasn't the method I used to root in the first place. Does that matter?

Anyone else have any ideas? I tried posting logs in the SuperSU update failure thread, with the logic that if I get that issue fixed my other issue will be resolved also, but Chainfire hasn't responded to any of the requests in a while.

Gakuseinozen said:
Anyone else have any ideas? I tried posting logs in the SuperSU update failure thread, with the logic that if I get that issue fixed my other issue will be resolved also, but Chainfire hasn't responded to any of the requests in a while.
Click to expand...
Click to collapse
Try older version of supersu? Or could it be something inside the supersu setting? Just a thought.
SGs3n SlimKat9.0(Android-Andi)/F_Kernel1.3(Fred6681)/SuperSU2.4?(ChainFire)/BusyBoxX33(MaxIce)

Naimlaaa said:
Try older version of supersu? Or could it be something inside the supersu setting? Just a thought.
SGs3n SlimKat9.0(Android-Andi)/F_Kernel1.3(Fred6681)/SuperSU2.4?(ChainFire)/BusyBoxX33(MaxIce)
Click to expand...
Click to collapse
Don't think an older version would help since i started having this problem with the version I'm currently running. I also went through the SuperSu settings and tried a few different things but nothing helped. I changed Default access from "grant" to "prompt", changed Mount namespace separation to "all root processes share inits mount namespace" and enabled "trust system user".
Not sure what else I could try really.

instinctblade said:
Did you try uninstalling the root from the unlockroot pro and rooting it again using the [super su update.zip]
try this it might work
Click to expand...
Click to collapse
Did you try this method yet? Also can try VoodooOTA rootkeeper.
And/or remove xposed first?
Im a noob in this but just trying to share some idea though.
SGs3n SlimKat9.0(Android-Andi)/F_Kernel1.3(Fred6681)/SuperSU2.4?(ChainFire)/BusyBoxX33(MaxIce)

Related

Youtube gigngerbread edition on X10

http://forum.xda-developers.com/showthread.php?t=817528
It works fine. Rename it from signed_YouTube.apk to YouTube.apk and replace with one in /system/app. Make sure that permissions are set when overwriting.
Works like a charm and looks quite good, thanks for this!
qwer23
Sent from my rooted X10i using XDA App
yep great mod
widget works great also.
Is it actually working for you ??
I am getting network error 400, both on GSM/3G and on WiFi...
There's some sort of Log-In bug, basically don't sign into your youtube account while using this mod and you should be fine. Hopefully there will be a fix for that soon.
Thanks, looks much better...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...and had no trouble signing in. Did those that have uninstall the old app first?
Yeah looks great!
Thanks 4 share
Sent from my X10i using XDA App
XperiaX10iUser said:
Thanks, looks much better...
...and had no trouble signing in. Did those that have uninstall the old app first?
Click to expand...
Click to collapse
XperiaX10iUser: how'd you go about installing it? I'm still a noob when it comes to ADB and such (and yes, I did read your guide ), and want to make sure I'm not going to mess anything up installing this.
also, google geniewidget.apk (news and weather) also works. this one you can install it thru any file manager.
saltorio said:
XperiaX10iUser: how'd you go about installing it? I'm still a noob when it comes to ADB and such (and yes, I did read your guide ), and want to make sure I'm not going to mess anything up installing this.
Click to expand...
Click to collapse
Ok its easy:
Get to adb (shell):
$su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
#rm /system/app/YouTube.apk
Then go to settings -> applications -> find com.android.youtube.apk and uninstall it
Reboot your phone
Then get to adb (shell):
$su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Install /sdcard/(where the modded .apk is)/signed_youtube.apk /system/app
Reboot phone
I did the permissions with root explorer (rw-r--r--)
How to do that with adb... idk sry
Sent from my X10i using XDA App
saltorio said:
XperiaX10iUser: how'd you go about installing it?
Click to expand...
Click to collapse
This is how I did it, in a command window on the laptop...
cd C:\android-sdk-windows\tools
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell rm system/app/YouTube.apk
adb uninstall com.google.android.youtube
adb push Youtube.apk /sdcard/Youtube.apk
adb shell dd if=/sdcard/Youtube.apk of=/system/app/Youtube.apk
...but if your Tools folder is elsewhere just change the first line.
PoTi_96 said:
Ok its easy:
I did the permissions with root explorer (rw-r--r--)
Click to expand...
Click to collapse
That should be:
# busybox chmod 644 <file>
XperiaX10iUser said:
This is how I did it, in a command window on the laptop...
cd C:\android-sdk-windows\tools
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell rm system/app/YouTube.apk
adb uninstall com.google.android.youtube
adb push Youtube.apk /sdcard/Youtube.apk
adb shell dd if=/sdcard/Youtube.apk of=/system/app/Youtube.apk
...but if your Tools folder is elsewhere just change the first line.
Click to expand...
Click to collapse
Wonderful. Worked beautifully, and I was able to login to my profile OK as well.
Thanks!
it didnt worked for me, failed to install.
fogozito said:
it didnt worked for me, failed to install.
Click to expand...
Click to collapse
Make sure to put the .apk in C:\android-sdk-windows\tools, and that it's named "YouTube.apk"
saltorio said:
Make sure to put the .apk in C:\android-sdk-windows\tools, and that it's named "YouTube.apk"
Click to expand...
Click to collapse
Thanks for that I didn't think I need them in both places.
Strange, after it worked perfectly for several hours it now force closes on start every time. Any suggestions?
Btw. I installed with root explorer. I just renamed the apk to YouTube.apk, then did overwrite the old one and set the same permissions that were set in the original youtube app. I was able to log in, too.
Sent from my rooted X10i using XDA App
Edit: reinstall did solve the problem for now. Let's see if it'll last
I also installed it successfully and it was running fine for a bit then suddenly now it is force closing a lot. I had to reboot the phone because it was stuck in a FC loop when I used the search function on the widget.
Wiping the data and resigning in seems to fix it. I guess there could be something wrong with account handling.
qwer23 said:
Strange, after it worked perfectly for several hours it now force closes on start every time. Any suggestions?
Btw. I installed with root explorer. I just renamed the apk to YouTube.apk, then did overwrite the old one and set the same permissions that were set in the original youtube app. I was able to log in, too.
Sent from my rooted X10i using XDA App
Edit: reinstall did solve the problem for now. Let's see if it'll last
Click to expand...
Click to collapse
sierratango88 said:
I also installed it successfully and it was running fine for a bit then suddenly now it is force closing a lot. I had to reboot the phone because it was stuck in a FC loop when I used the search function on the widget.
Wiping the data and resigning in seems to fix it. I guess there could be something wrong with account handling.
Click to expand...
Click to collapse
Did you guys sign in to your YouTube profile in the app? I know there is a problem being reported in the original thread related to signing in.
I did sign in, and it was worked fine initially, but now I'm seeing the same issue as you guys are reporting.

[HOWTO] Root the Atrix 2(Updated for 2.3.6 FINALLY)

First: I'd like to make it clear I am not claiming this process as my own. This method was created by p3droid over at the MyDroidWorld Forums. I am not a dev, just someone compiling information.
Second: This root method is originally intended for the Droid Bionic and I take no responsibility if this bricks your phone.
Third: This root was discovered by JRW 28 So give him some love with that thanks button.
If you are on 2.3.6:
Install the OTA and upgrade your phone to 2.3.6
Download the 2.3.6 root zip from HERE
Make sure you have the right drivers installed then connect your phone to your PC.
Unzip the file and then double-click "Click-To-Root.bat".
Refer to the trouble shooting step bleow the 2.3.5 method if you are unable to attain root!
If you are on 2.3.5:
Root: I used the Lazy One Click and it worked perfectly, others have had success with the full manual method.
I am a manual man, I don't use 1 clicks so I will post this the only way I know how...
Download the follow file: it contains the exploit, su, Superuser
Download exploit ---> Exploit.zip
1) Unzip contents of folder to your Desktop
2) open a command terminal and navigate to the folder (cd Desktop/Exploit)
3) type the following commands
---> adb push zerg /data/local
---> adb push su /data/local
---> adb push Superuser.apk /data/local
---> adb shell
---> cd /data/local
---> chmod 777 zerg
---> ./zerg
4) Wait for the root to be gained
5) type the following commands
---> adb shell (only type this if you are no longer in [email protected])
---> mount -o rw,remount /dev/null /system
---> cat /data/local/su > /system/bin/su
---> cat /data/local/Superuser.apk > /system/app/Superuser.apk
---> chmod 4755 /system/bin/su
---> chmod 4755 /system/app/Superuser.apk
---> reboot
********************************
Windows Version
For the lazy I made you a 1-click ---> 1-click-exploit.zip
Click to expand...
Click to collapse
Original Thread on MyDroidWorld: http://www.mydroidworld.com/forums/...-your-phone-back-upgrade-path.html#post106072
Important for those using Oneclick:
1.Extract the files from 1-click_exploit.zip.
2.Enable USB debugging. Do so by going into your settings, then to applications, then to development.
3.Set your connection type to charge only. You can change your connection type through the notification bar once your are connected.
4.Make sure you go to Settings, Applications, and check Unknown sources if you haven't done so already.
5.Click runme.bat while your phone is connected. Be patient and let the program do it's thing. YOUR PHONE WILL REBOOT! Do not be alarmed as this is normal. Your phone should now be rooted.
Cheers!
If runme.bat hangs after daemeon starts:
1.First make sure you have USB Debugging, Unknown Sources, and Charge only connection enabled
2.If none of these options work, uninstall your drivers and download and install one of these:
Driver-wise:
Try this if on 32-bit:http://www.mediafire.com/?71c12qc4a1svqza
And this for 64-bit:http://www.mediafire.com/?ysphmaz131d3an9
Proof of Root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a terminal screen showing the Atrix 2 (Codenamed Edison, look it up if you must) accessing root.
Anyone else try?
I'll be uploading a terminal screen in a second accessing root.
Sent from my MB865 using XDA App
Yea I have it working and full SU Access. No wonder the computer doesnt have access to the phones internal memory it is by default set as r/o...Im gonna change it to R/W and see if that changes anything other than allowing R/W access. And after trying notta still only SD Card access like I thought, I assume there is some sorta setting we can edit though. At least that is my assumption. I used the One Click method Worked flawlessly on my device and Very Simple.
built in wifi tether
http://forum.xda-developers.com/showthread.php?t=1160452
this method also works for the Atrix 2
Thanks for the tip!
Sent from my MB865 using XDA App
malickie said:
Yea I have it working and full SU Access. No wonder the computer doesnt have access to the phones internal memory it is by default set as r/o...Im gonna change it to R/W and see if that changes anything other than allowing R/W access. And after trying notta still only SD Card access like I thought, I assume there is some sorta setting we can edit though. At least that is my assumption. I used the One Click method Worked flawlessly on my device and Very Simple.
Click to expand...
Click to collapse
How do you root the phone using the one click method? I've downloaded the zip and extracted it. Do I just connect my phone and then click on the runme.bat? When I connect my phone, any special instructions there or just connect it as if i was going to charge it, then enable usb debugging? Please clarify. Thanks.
Enable USB debugging. Then connect your phone to the computer. In the notification area, click on "USB connection" for more options. Click charge only.
Then double click on runme.bat
Follow instructions. Be patient while phone reboots. It will say (in the command prompt window) you have successfully rooted when it's all done.
It's schweet.
loderjm said:
Enable USB debugging. Then connect your phone to the computer. In the notification area, click on "USB connection" for more options. Click charge only.
Then double click on runme.bat
Follow instructions. Be patient while phone reboots. It will say (in the command prompt window) you have successfully rooted when it's all done.
It's schweet.
Click to expand...
Click to collapse
Thanks for clarifying, worked like a charm! Let the developing begin!!!!
yes it works!!! Thank you so much
Updated/clarified the oneclick method.
Sent from my MB865 using XDA App
So, what's the next step? Do we have to get the BL unlocked in order to get a Recovery installed or what?
Contact a admin and let him know you got some development so you'll get a thread
Sent from my MB860 using xda premium
Requesting this thread be moved -
http://forum.xda-developers.com/forumdisplay.php?f=1376
If you read at the end of my original post I document what I've tried. If your really adventurous you may want to try the bionic bootstrapper but it may brick your phone... I haven't tried that yet, though the similarities between the atrix2 and the bionic lead me to believe it may work.
Sent from my MB865 using XDA App
Calundle said:
Requesting this thread be moved -
http://forum.xda-developers.com/forumdisplay.php?f=1376
Click to expand...
Click to collapse
Thread Moved.
Yes i have tested and it works perfectly.
my only question is which CMW do we flash?
rinnycoop121 said:
Yes i have tested and it works perfectly.
my only question is which CMW do we flash?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1328434
Right now we don't have a CWM of our own to flash. There is a possibility of flashing the Bionics bootstrap recovery but we don't know what the circumstances are gonna be. Someone could result in a bricked A2, what we need is some development help right now
JRW 28 said:
Right now we don't have a CWM of our own to flash. There is a possibility of flashing the Bionics bootstrap recovery but we don't know what the circumstances are gonna be. Someone could result in a bricked A2, what we need is some development help right now
Click to expand...
Click to collapse
i have tried Bionic and Atrix 4G but no good.
wil lnot boot into recovery
---------- Post added at 07:25 PM ---------- Previous post was at 07:23 PM ----------
ok just noticed something, upon running market been getting random restarts.

[Solved] Problem restoring root via OTA rootkeeper

I made a dumb mistake. Sometime back i had mistakenly deleted the contents of the sdcard after voodoo rootkeeper su backup. Forgot about the su backup!
Updated the latest update, without backing up again.
Rootkeeper shows that su copy is available but doesn't restore.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried cold booting, multiple restarts, everything in vain.
Question is, can I restore root from the backup of other users in the forum? Or is it device specific?
Somebody care to upload the contents of the folder if it doesn't give away any personal data?
Thanks.
Sent from my Asus TF300T
Tell us more, please.
Are you on JB or ICS ?
Have you tried to cheched "device rooted" and "root permission granted"
and finally click on "Restore root"
philos64 said:
Tell us more, please.
Are you on JB or ICS ?
Click to expand...
Click to collapse
I am currently in JB (v10.4.2.13).
Tablet is not unlocked
Vodoo OTA Rootkeeper restored fine when I updated from ICS(9.4.3.30) to JB (10.4.2.9).
The check-boxes will be checked by the app not manually AFAIK.
Anyhow gave it a try, not clickable
Stupid of me not to backup before updating
It's possible to have backup of rootkeeper?
I have solved so, removed supersu, instal superuser from market.
Restore root from rootkeeper and all ok.
Remove superuser and reinstall supersu.
Now I have root access.
Inviato dal mio ASUS Transformer Pad TF300T con Tapatalk 2
Root Achieved
Solved the problem.
Followed the steps in the thread posted here
Steps:
Most of the commands are copy-paste from the thread just modified for this specific problem (I do not take credit for these steps).
Download View attachment su.zip from this post (thanks to calisro)
Extract the contents to a folder.
Start a cmd window in that folder and logon to adb
In adb shell type
Code:
/system/usr/we-need-root/su-backup
(check the file availability in that folder and the file name and correct the command accordingly)
Confirm whether you have root. The adb shell prompt should be # not $, also can be confirmed by typing id and should echo something like this "uid=0(root) gid=0(root)"
Remount system as RW:
Code:
mount -o remount,rw /dev/block/mmcblk0p1 /system
Open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
Code:
adb push c:\<some path>\su /sdcard/
Then copy it to /system/bin from the adb session where you got root.
Code:
cat /sdcard/su > /system/bin/su
Change permissions for SU
Code:
chmod 6755 /system/bin/su
Download superuser (NOT SUPERSU) from play store if you do not have it already.
Force superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
congrats. your now re-rooted.
Think, this will solve the problem plaguing few people who could not restore root after latest OTA.
Thanks to calisro for his easy to understand steps (please rep him in the thread, if this helped you)
k1chy said:
Solved the problem.
Followed the steps in the thread posted here
Steps:
Most of the commands are copy-paste from the thread just modified for this specific problem (I do not take credit for these steps).
Download View attachment 1338410 from this post (thanks to calisro)
Extract the contents to a folder.
Start a cmd window in that folder and logon to adb
In adb shell type
Code:
/system/usr/we-need-root/su-backup
(check the file availability in that folder and the file name and correct the command accordingly)
Confirm whether you have root. The adb shell prompt should be # not $, also can be confirmed by typing id and should echo something like this "uid=0(root) gid=0(root)"
Remount system as RW:
Code:
mount -o remount,rw /dev/block/mmcblk0p1 /system
Open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
Code:
adb push c:\<some path>\su /sdcard/
Then copy it to /system/bin from the adb session where you got root.
Code:
cat /sdcard/su > /system/bin/su
Change permissions for SU
Code:
chmod 6755 /system/bin/su
Download superuser (NOT SUPERSU) from play store if you do not have it already.
Force superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
congrats. your now re-rooted.
Think, this will solve the problem plaguing few people who could not restore root after latest OTA.
Thanks to calisro for his easy to understand steps (please rep him in the thread, if this helped you)
Click to expand...
Click to collapse
It works fine.
Thank you k1chy & calisro
nevermind, figured out.
thanks for the tutorial
It will be nice if this was a sticky
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Thank you! The last OTA that my tablet took resulted in me not being able to restore root. OTA RootKeeper kept freezing up and doing nothing. This helped me in restoring root!
Thanks a million
k1chy said:
Think, this will solve the problem plaguing few people who could not restore root after latest OTA.
Thanks to calisro for his easy to understand steps (please rep him in the thread, if this helped you)
Click to expand...
Click to collapse
Thanks a million!!
Couldn't recover root on a Razr M after JB OTA - tried all of the exploits around the forums but NONE worked
- This, however, worked a treat!!! :victory:

[Root/Guide] How-to Root (06/08/2015)

Root for the Verizon Samsung Galaxy S6 SM-G920V (G920VVRU1AOC3///OE2)​Before you begin disable your reactivation lock. There's a chance for it to get stuck ON once your device is rooted, which could cause issues with ROMs (unknown currently, but be safe!)
** You can turn it back on once you're rooted. **
WHATEVER YOU DO DO NOT ACCEPT OTA "G920VVRU2AOF1" OR YOU WILL NOT BE ABLE TO ROOT USING THIS METHOD. IF YOUR PHONE CAME THIS WAY, I'M SORRY THIS WILL NOT WORK.​​-About-
Great job Keen Team! Thank you very much for your work and bringing us root! This method and exploit were found by them and orignally posted here. The purpose of this post is to simply 1) Have a dedicated post for root under OUR forums to make it easier for newer members to get their device rooted, and 2) Simplify the installation of SuperSU for those who don't want Kinguser, while also having detailed instructions so the newer/novice users don't get lost.
-Credits-
Original Exploit/Root Team: Keen Team
Original Poster: @idler1984, over here.
Vulnerability: memeda, wushi
Original idea of exploit: memeda
Exploit: idl3r, Qoobee
Testing & SU management: Kingroot team for help testing and great root manager
ADB Line Commands: @Gunthermic at Post#269
-Steps to a rooted device:-
1) Go to Settings -> About phone -> and verify that your Build number (or Baseband version) is "LRX22G.G920VVRU1AOC3//OE2." SW up until "G920VVRU2AOF1" will work with this method.
2) Go to Settings -> Lock screen and security and enable "Unknown Sources" (*You may turn it back OFF once you're rooted, if you'd like*)
3) Plug your phone into your computer.
4) Scroll to the bottom of this post and download "pingpongroot_<ver>.apk" (currently "pingpongroot_beta6.apk").
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^ (Screenshot of what to look for)
5) Put the APK on your device; install and then open the application on your phone.
6) Install SuperSU when the install pops up, then open it once and return (you'll get errors in SuperSU as you're not rooted yet) to Ping Pong Root and tap "Get root!" -- if your phone reboots on its own during this, open the app and try again. Once the app finishes rooting your device, close the pop up message and reboot.
~Enjoy.
-FAQ-
Q: Will this trip my Knox Counter?
A: No.
Q: Will this let me flash ROMs/Kernels and have a custom recovery?
A: No. The bootloader is still locked.
Q: Why does my device say "Custom" when booting up?
A: That just means Samsung's system checker sees the su/root. If you flash back to stock using Misterxtc's ODIN files here, then you will no longer be rooted or show "Custom." For now, until the bootloader is unlocked, deal with it if you happen to get caught by the checker.
Q: Does this work on the edge?
A: Not yet.
Q: I'm lost, confused, stuck, or getting errors that are hindering me from root access / SuperSU.
A: Post below, I can help or in the OP for the root method, here. Often your issues can be resolved just by restarting the root process from step one. On my 20th or so rewipe and root, I ran into some issues but just refollowed every step and was fine.
1 post, just in case.
This is rather exciting. I'm staring at my Note 4 which I like better than my s6, but it was never able to get root.
This may be the reason I was looking for to use my s6 over my Note4
Thanks for putting this guide together. Hopefully it should help those new to rooting. I'd add a link to the video as well.
Anyone else having trouble updating binary through chainfires su?
oconnell84 said:
Thanks for putting this guide together. Hopefully it should help those new to rooting. I'd add a link to the video as well.
Click to expand...
Click to collapse
Sure thing! Can you post it? On my phone atm so it's harder to dig.
jparasita said:
Anyone else having trouble updating binary through chainfires su?
Click to expand...
Click to collapse
Unroot through the settings in chainfire's SuperSU and reroot if you're having fatal issues that are preventing root/superuser. What errors are you specifically getting with updating the binaries?
At step 10, when I type "su" I get this error:
[email protected]:/ $ su
su
[-] Connection to ui timed out
[email protected]:/ $
StrumerJohn said:
Unroot through the settings in chainfire's SuperSU and reroot if you're having fatal issues that are preventing root/superuser. What errors are you specifically getting with updating the binaries?
Click to expand...
Click to collapse
Works find just wont let me update binaries and just curious if its just me
ascallop said:
At step 10, when I type "su" I get this error:
[email protected]:/ $ su
su
[-] Connection to ui timed out
[email protected]:/ $
Click to expand...
Click to collapse
Open up Kinguser, and then grab a rootchecker app off of the playstore. See if you're properly rooted, if not retry the pingpongroot app.
jparasita said:
Works find just wont let me update binaries and just curious if its just me
Click to expand...
Click to collapse
If you have the time, I'd redo the ADB steps later. Not a big deal since your root access works, but it's nice to keep SU binaries up to date.
This is what I get when trying to install su and binaries. Please help me
I think you're missing a step in number 12. I tried your guide and got an error message so I went to the original post below, then I got it all working right.
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
gti2756 said:
I think you're missing a step in number 12. I tried your guide and got an error message so I went to the original post below, then I got it all working right.
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
Click to expand...
Click to collapse
Whoops! I accidentally cut off the beginning of a line! Thanks a lot..
THADDIUS25 said:
This is what I get when trying to install su and binaries. Please help me
Click to expand...
Click to collapse
jparasita said:
Anyone else having trouble updating binary through chainfires su?
Click to expand...
Click to collapse
ascallop said:
At step 10, when I type "su" I get this error:
[email protected]:/ $ su
su
[-] Connection to ui timed out
[email protected]:/ $
Click to expand...
Click to collapse
Anyone having issues, go ahead and re-do the adb steps. My apologies.
In other news, I'll start working on a cleaned up stock ROM for you guys. Might take awhile due to school and work, but it'll be next on my list (no custom recovery, but FF flash. See Misterxtc's post here.)
I just rooted my phone and things are working great! I have two questions:
1.) Can anyone with more experience than me let me know if we can now install the Stock Samsung Browser as a system app (the stock browser has fingerprint reader as password which is awesome!) Please see the post here: http://forum.xda-developers.com/gal...xy-s6-apps-t3041330/post59644234#post59644234
2.) Can we modify the build prop or anything to allow us to tether for free without use of FoxFi? I know FoxFi works, but it makes me have a passkey on my phone which I hate. I also tried to install the FoxFi certificate as a system certificate and it still required me to have a passcode for some reason.
Just looking for some guidance! Thank you!
Works awesome! Thanks!!!
StrumerJohn said:
If you have the time, I'd redo the ADB steps later. Not a big deal since your root access works, but it's nice to keep SU binaries up to date.
Click to expand...
Click to collapse
Think it was cause you missed a command tryed again worked flawless cannot wait to see youre work
Is this (the superuser part) possible to do with a mac? I downloaded and extracted the ADB folder but cant figure out how to open a command prompt from the folder. (I already rooted but now trying to switch to SU)
What and where can I find the reactivation lock?

Mount system as rw on Android 10 with Magisk 20.4

I am using Magisk 20.4 and trying to mount /system on a Google Pixel running Android 10.
I have tried using:
Code:
adb shell su -c mount -o rw,remount /system
that gives: me
mount: '/system' not in /proc/mounts
Click to expand...
Click to collapse
The following also do not work:
Code:
adb shell su -c mount -o rw,remount /
'/dev/root' is read-only
Click to expand...
Click to collapse
Code:
adb shell su -c mount -o rw,remount /sbin/.magisk/mirror/system_root
'/sbin/.magisk/block/system_root' is read-only
Click to expand...
Click to collapse
I was also curious whether stuff in /sbin/.magisk/rootdir/system/ can actually override stuff in /system/ but that doesn't seem to be the case..
Has anyone managed to mount /system on Android 10? Is this issue specific to Google Pixel?
Cheers,
Paschalis
Its due to EXT4 dedup filesystem (it's not writable).
This was pointed out by magisk developer john wu, more info: https://mobile.twitter.com/topjohnwu/status/1170404631865778177
So it's impossible? Even with TWRP?
Turns out I don't need to mount /system.
I wanted this so I could ship my modified version of libart.so, libart-compiler.so and dex2oat (which are in APEX), as well some other external compiler libraries and tools.
So I've written some magisk modules, and it works really well. Even for the runtime apex. I'm impressed!
The only reason someone might need to mount /system is if he/she uses an app/tool that needs it.
The only way to make changes to the /system partition is to make a Magisk module that mounts the files you modified instead of the original ones.
Paschalis said:
Turns out I don't need to mount /system.
I wanted this so I could ship my modified version of libart.so, libart-compiler.so and dex2oat (which are in APEX), as well some other external compiler libraries and tools.
So I've written some magisk modules, and it works really well. Even for the runtime apex. I'm impressed!
The only reason someone might need to mount /system is if he/she uses an app/tool that needs it.
Click to expand...
Click to collapse
Well I need to mount because of Link2sd. Is there any way to do it?
jcruzcruz35 said:
Well I need to mount because of Link2sd. Is there any way to do it?
Click to expand...
Click to collapse
No, on Android 10 the /system partition is locked at read only, the only way to make modifications to the /system partition is to make a Magisk module.
JJcoder said:
No, on Android 10 the /system partition is locked at read only, the only way to make modifications to the /system partition is to make a Magisk module.
Click to expand...
Click to collapse
Sht, it has to be especially make it for each smartphone? Or you think there gonna be eventually a Module for everyone?
jcruzcruz35 said:
Sht, it has to be especially make it for each smartphone? Or you think there gonna be eventually a Module for everyone?
Click to expand...
Click to collapse
I'm sure eventually there will either be a universal Module, Or a way to resize the partition and change the file system to make it writable.
JJcoder said:
...Or a way to resize the partition and change the file system to make it writable.
Click to expand...
Click to collapse
Resized works, but how to change the file system to make it writable?
vagyula said:
Resized works, but how to change the file system to make it writable?
Click to expand...
Click to collapse
How did you resize it?
Code:
$ su
# mount --remount / -w
ONLY makes effert to terminal, which means other apps like Solid Explorer, Root Explorer etc are still r/o. Some roms(Pixel Experience tested, including stock) are not working.
hardplastic said:
Code:
$ su
# mount --remount / -w
Only works in terminal
Click to expand...
Click to collapse
It doesn't work on Android 10, you will just get the error:
Code:
'/dev/root' is read only
JJcoder said:
It doesn't work on Android 10, you will just get the error:
Code:
mount: '/dev/root' not user user mountable in fstab
Click to expand...
Click to collapse
Reboot your device and try again, it works both two of my devices in Android 10
hardplastic said:
Reboot your device and try again, it works both two of my devices in Android 10
Click to expand...
Click to collapse
Nope, Same error bcuz it is locked at read only.
JJcoder said:
Nope, Same error bcuz it is locked at read only.
Click to expand...
Click to collapse
That's weird, have you checked your operation is in the terminal? It only makes /system rw to terminal, other apps still r/o .
hardplastic said:
That's weird, have you checked your operation is in the terminal? It only makes /system rw to terminal, other apps still r/o .
Click to expand...
Click to collapse
No, you can't just simply Type a command and have it mount as rw...
If you want to make modifications you have to make a Magisk Module which uses Magic Mount to mount the modified files over the original ones.
I have no idea how u got it to work, I would like to see proof..
JJcoder said:
No, you can't just simply Type a command and have it mount as rw...
If you want to make modifications you would have to make a Magisk Module which uses Magic Mount to mount the modified files over the original ones.
Click to expand...
Click to collapse
Then how do you explain that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hardplastic said:
Then how do you explain that?
Click to expand...
Click to collapse
Let me see that u are on stock Android 10
JJcoder said:
Let me see that u are on stock Android 10
Click to expand...
Click to collapse

Categories

Resources