Database Develop

[Q&A] [LB] The definitive root Remount-Reboot fix!

Q&A for [LB] The definitive root Remount-Reboot fix!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

FolderMount
I flashed it, but after that I lost my root permission. After towelroot I have root permission again, but foldermount causes reboot again. How should I fix this issue?
towelrooted Xperia M - stock 4.3 build 15.4.A.1.9 - LB

Hi,
I have the Xperia Z1 compact with android 4.4.4 this work with device?

fenix2021 said:
Hi,
I have the Xperia Z1 compact with android 4.4.4 this work with device?
Click to expand...
Click to collapse
Try it yourself.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!

Remount reboot problem for Experia LT30p
I rooted my Experia LT30p phone and installed PhilZ Touch Recovery according to the instructions at http://forum.xda-developers.com/showthread.php?t=2798411. Afterwards
I followed the instructions at http://forum.xda-developers.com/xperia-z/orig-development/lb-definitive-root-remount-reboot-fix-t2317432 and installed the BusyBox app by Robert Nediyakalaparambil, opened this app and selected "install (requires root)" (I am assuming that that is ment with update your busybox). After installing Link2SD the phone keeps rebooting. Only if I remove the SD card, the phone boots properly.

Waiting for device, connect usb cable
Like @asbesto "I am stuck at Waiting for device, connect usb cable" even after follow those steps that he did it in this guide...
I'm using Xperia SP C5303, Android 4.3 12.1.A.1.205 rooted (SuperSU) and already installed BusyBox
Any ideas ?

I try to root my Xperia M C1905, entered in instal in remountreboot fix, and it didn't find my device there. I enabled USB debugging. Thanks in advance. Just says waiting for device, connect USB cable now...

hi friend
i upgraded my sony xperia z2 to 4.4.4 and rooted
i installed your fix as i did this in 4.2.2
but after a week my phone start to reboot automatically this means this fix dosen't work on this version
dude i just working on my phone for a week to make it working with folder mount ,for noob like me it's hard to installing rooms and root them and again and again (
i just want to thank you for what u did for us ,
but can you make fix working on this version ?

about link2sd bootloop
Does it fix the bootloop that occured to me while creating second partitions for link2sd?i tried every possible methods for that but everytime my phone went on bootloop which could be eliminated by removing the sd card.

Can anyone help me??
I have an xperia m... Rooted via towelroot...i want to play nfs most wanted...
I installed "Folder Mount"... Pasted the game data in sdcard/android/data... Copied the folder
name in internal/android/data... But when i try to mount them via folder mount...and click on the pin...my phone reboots...everytime it happens with my xperia m...can anyone help me
out??
I am dying to play nfs most wanted... Help anyone...??

In post #281, chemcup had a problem with errors due to read-only file system, e.g.:
cp: can't create '/system/bin/killric.sh': Read-only file system
I had the same problem with an Xperia LT30. This is a factory unlocked version direct from Sony (but my BL is still locked).
I ran across a ticket mentioning that doing an "su" first allows remounting. See the note by Blister Bee.
https://jira.cyanogenmod.org/browse/CYAN-5908
Anyway, went into adb, did the su remount, and then ran the script and it worked!

Root Vanished.
Everytime when I run the program and apply Remount Reboot Fix, it breaks my root. What to do, I have Sony Xperia M, running 4.3 android.

[[Solved]] [[Guide]]How to apply remountrebootfix on locked boot loader.
I have seen many peoples facing the problem of reboot even after the remountrebootfix so I m posting this idea.
I have applied this method on my Sony Xperia M, and got a full root access. You may also try it manually...
Warning- I will not be responsible for any damage caused to your phone, you are doing it at your own.
1. Download towelroot apk by Geohot...
2. Open it and click make it rain. Now you will get Half root access.
3. Now download remountrebootfix flashable zip and extract it somewhere you remember on your sd card.
4. First of all you need busybox for this, I think you would have already installed the latest version of it previously.
5. Now go to system/bin in your phone's root and if you find ctrlaltdel and killric.sh then delete them. And paste new ctrlaltdel and killric.sh from the extracted folder. Now reboot your phone.
6. After that download latest version of foldermount from play store, and try to mount any folder, if it fails then it will show a message to fix the rom, fix it and then again reboot. Now Foldermount will work perfectly.

make changes undone
Hi NUT,
i just wondered if you could implement a feature to make the fix undone. This could be useful if i want to use the OTA update again that seems to need RIC service to run for verifying system.
The reason i asked is because i tried to unroot via SuperSU option "completely unroot", i removed the manually done SD fix and tried to install the OTA. It fails half of the installation because i think the RIC service is not up and running and therefore it recognize a system change.
...would be really cool though. Thanks NUT for your hard work. I'll appreciate it!
best regards
Soul Inferno

[Q] Unable to root device

Device: Sony Xperia Sp
Model Number: CS303
Android Version: 4.1.2
Problem: Unable to root device
Situation
1) Enabled USB Debugging from Settings> Developer Options
2) Enabled Unknown sources from Settings > Security
3) Downloaded DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit and extracted files
4) Ran "RUNME.bat"
5) Followed the instructions on the screen
6) Script seems to have finished executing successfully with "all done".
7) Device when rebooted, does not show signs of change.
Solution: ?

Hi,
I suggest you ask in the thread you got the toolkit from. Otherwise, I'll have your thread moved to your device section... Here,
> Sony Xperia SP > Xperia SP Q&A, Help & Troubleshooting
Good luck!

acquiredskills said:
Device: Sony Xperia Sp
Model Number: CS303
Android Version: 4.1.2
Problem: Unable to root device
Situation
1) Enabled USB Debugging from Settings> Developer Options
2) Enabled Unknown sources from Settings > Security
3) Downloaded DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit and extracted files
4) Ran "RUNME.bat"
5) Followed the instructions on the screen
6) Script seems to have finished executing successfully with "all done".
7) Device when rebooted, does not show signs of change.
Solution: ?
Click to expand...
Click to collapse
Go to this link for root .254 firmware http://forum.xda-developers.com/showthread.php?t=2405933 or http://forum.xda-developers.com/showthread.php?t=2440375 . Good luck :good:

Go to http://towelroot.com and click on the lambda icon to download the app towelroot. Ignore any warnings from chrome.
Install towelroot on your phone. Open it and tap on 'make it rain'. If the device does not not reboot then you have root. Reboot and check if you have root with root checker app.
Refer to this thread for more details http://http://forum.xda-developers.com/showthread.php?t=2783885

Prat92 said:
Go to http://towelroot.com and click on the lambda icon to download the app towelroot. Ignore any warnings from chrome.
Install towelroot on your phone. Open it and tap on 'make it rain'. If the device does not not reboot then you have root. Reboot and check if you have root with root checker app.
Refer to this thread for more details http://http://forum.xda-developers.com/showthread.php?t=2783885
Click to expand...
Click to collapse
Thank you for your reply!
After installing towelroot, rebooting and checking with a root checker app, I do indeed have root access.
Thank you, once again.

Can't even install XPosed (Flashfire Issue?)

So I got around to "rooting" my "LG G4" (H525) via that one click tool called Kingroot.
So far so fine.
Pretty much all applications that require root will will allow it...
Except for one:
FlashFire....
It keeps telling me that root access was not possible,
that I shall't install SuperSU.
[However SuperSU will error out right on the start telling me to `update the binary']
=> What binary ? Why update it (just got the newest SuperSU from the Playstore)?
Trying to flash said binary using any Flashify merly showed me the lovely "your device is bricked" bugdroid...
Any idead from someone with similar FlashFire / SuperSU problems ?
Thanks in advance:
-Rye-

Do you have a custom recovery/twrp?
Sent from my HTC One M9 using Tapatalk

Nope, all stock.
(Part of the reason why this confuses me so much... I changed nothing... except for Root)

KingRoot is intentionally designed to serve two purposes. The first is to give you root access through their app. The second, which they don't warn you about, is to prevent you from managing that root access any other way than through their app.
They have written their app specifically to force you to use their root manager and to prevent you from uninstalling it and installing any other SU app. They went so far as to specifically block installation of SuperSU because they're upset that it replaces their app (which is blatantly absurd and hypocritical). If that's acceptable to you, then certainly do it their way.
However, because they place such restriction on root access (which seems to be a self-contradictory philosophy) then it directly interferes with the installation of more powerful root apps like flashing utilities and Xposed itself.
At this point there are two options. Either you can find a utility that breaks their stranglehold on your device and follow the specific instructions to remove their app and install something that's not restrictive, or you can restore your device to pre-root condition and root it again yourself using the open, non-restrictive methods made available to the community. Each method may be about as complicated as the other.

Uninstall system app

Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc. At first I thought it was Floating Fake Location issue but soon I realize I can't even uninstall other Sony bloatware such as Socialife, Xperia Lounge etc.
Please enlighten me why I can't uninstall system app even tho I am rooted.
P/S: it may have something to do with my root (partial? as I didn't unlock my bootloader), as I can't even mount r/w using root explorer or any other app that can mount r/w on /system.

Steven90 said:
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc. At first I thought it was Floating Fake Location issue but soon I realize I can't even uninstall other Sony bloatware such as Socialife, Xperia Lounge etc.
Please enlighten me why I can't uninstall system app even tho I am rooted.
P/S: it may have something to do with my root (partial? as I didn't unlock my bootloader), as I can't even mount r/w using root explorer or any other app that can mount r/w on /system.
Click to expand...
Click to collapse
You also need to instal Supersu, which is an interface for granting root. Then you will be able to delete system apps.

optimumpro said:
You also need to instal Supersu, which is an interface for granting root. Then you will be able to delete system apps.
Click to expand...
Click to collapse
I am using Kingo SuperUser to grant the apps root permission. Had some trouble replacing Kingo SuperUser with Chainfire SuperUser but I figured Kingo should've done the trick as well. When I mount Kingo did prompt me for permission and I allowed it, somehow I think the root is incomplete ?

Steven90 said:
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc.
...
...
somehow I think the root is incomplete ?
Click to expand...
Click to collapse
Does your device have recovery installed? You can delete system apps through it: mount /system through XZ Dual Recovery's TWRP and delete the folder with the app's apk inside. You could also try flashing a SuperSU zip this way to fix root, but make sure you don't use the systemless version.
I suggest you next time don't use kingroot or any one-click root: though uncomplicated, they're notorious for being untrustful, leaking private IMEI information to unknown servers, and unreliable. Read THIS thread thoroughly, re-root using the method in the 2nd post, and upgrade to 5.1.1, or get a pre-rooted FTF through XperiFirm.

kentexcitebot said:
Does your device have recovery installed? You can delete system apps through it: mount /system through XZ Dual Recovery's TWRP and delete the folder with the app's apk inside. You could also try flashing a SuperSU zip this way to fix root, but make sure you don't use the systemless version.
I suggest you next time don't use kingroot or any one-click root: though uncomplicated, they're notorious for being untrustful, leaking private IMEI information to unknown servers, and unreliable. Read THIS thread thoroughly, re-root using the method in the 2nd post, and upgrade to 5.1.1, or get a pre-rooted FTF through XperiFirm.
Click to expand...
Click to collapse
No I haven't installed any custom recovery.
Cause I am already using 5.1.1 so I figured Kingo Root is the easiest way to go, didn't know it will cause so much trouble. So basically I need to unroot then root again using the "proper" method? I am already on 5.1.1 btw.

Steven90 said:
No I haven't installed any custom recovery.
Cause I am already using 5.1.1 so I figured Kingo Root is the easiest way to go, didn't know it will cause so much trouble. So basically I need to unroot then root again using the "proper" method? I am already on 5.1.1 btw.
Click to expand...
Click to collapse
The fact that you can't install Supersu and get root indicates that your phone is not fully rooted. I bet you wouldn't be able to install recovery either for the same reason...
Do the classic rooting, install TWRP and then flash any pre-rooted stock rom you want...

optimumpro said:
The fact that you can't install Supersu and get root indicates that your phone is not fully rooted. I bet you wouldn't be able to install recovery either for the same reason...
Do the classic rooting, install TWRP and then flash any pre-rooted stock rom you want...
Click to expand...
Click to collapse
I suspect I am not fully rooted as well. Can you point me a direction towards "classic" rooting my my Z1 5.1.1 ? Almost every post I went points me back to one-click-root solution.

I have the same problem, it's because we can't remount /system to rw ("operation not permitted"), so the update to SU isn't working as well, tried several different methods with terminal emulator but without any luck. Neither will total commander help in this situation. I'm begining to lose hope

Steven90 said:
I suspect I am not fully rooted as well. Can you point me a direction towards "classic" rooting my my Z1 5.1.1 ? Almost every post I went points me back to one-click-root solution.
Click to expand...
Click to collapse
Ulvgrim said:
I have the same problem, it's because we can't remount /system to rw ("operation not permitted"), so the update to SU isn't working as well, tried several different methods with terminal emulator but without any luck. Neither will total commander help in this situation. I'm begining to lose hope
Click to expand...
Click to collapse
Try this, it's almost a one-click tool
http://forum.xda-developers.com/showthread.php?t=2784900
Exploit maybe works with 5.1.1, but if not, downgrade your firmware to 5.0.2, use Easyroot to exploit, then upgrade back.
The "classic" root I was referring to requires downgrading from Sony's Lollipop/Kitkat FW to Jellybean due to Sony patching the exploits in the newer FW used for rooting. The steps are outdated now and is replaced by Easyroot. http://forum.xda-developers.com/showthread.php?t=2688933

SuperSU in CM13 and CM13 based ROMs

Is there any way to use SuperSU in CM13 or CM13 based roms such as Resurrection Remix? In particular on a Nexus 6P?
I ask because I have been using RR for quite some time now but until recently never really noticed the limitations of CM's privacy guard. SuperSU pro has always seemed like a better implementation of a Root management app to me when I've used it in the past on previous devices.
I had considered just disabling root access from the setting in developer options and then updating the binary from the SuperSU app via TWRP and hoping that SuperSU would take over root management after that but I have read that a few people have bricked/bootlooped their devices after doing that and I don't want to have to deal with fixing that.
Many thanks in advance for any help you can provide.

Squall88uk said:
Is there any way to use SuperSU in CM13 or CM13 based roms such as Resurrection Remix? In particular on a Nexus 6P?
I ask because I have been using RR for quite some time now but until recently never really noticed the limitations of CM's privacy guard. SuperSU pro has always seemed like a better implementation of a Root management app to me when I've used it in the past on previous devices.
I had considered just disabling root access from the setting in developer options and then updating the binary from the SuperSU app via TWRP and hoping that SuperSU would take over root management after that but I have read that a few people have bricked/bootlooped their devices after doing that and I don't want to have to deal with fixing that.
Many thanks in advance for any help you can provide.
Click to expand...
Click to collapse
After disabling the root option within the Developer Options, when you open SuperSU and go to the Settings, do you leave the option for "Respect CM root settings" unchecked?
With CM/LOS, when you disable the root option, in SuperSU, you need to keep the "Respect CM root settings" unchecked or SuperSU will default the root to Disabled.
Many individuals don't know that.
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

Ibuprophen said:
After disabling the root option within the Developer Options, when you open SuperSU and go to the Settings, do you leave the option for "Respect CM root settings" unchecked?
With CM/LOS, when you disable the root option, in SuperSU, you need to keep the "Respect CM root settings" unchecked or SuperSU will default the root to Disabled.
Many individuals don't know that.
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
Click to expand...
Click to collapse
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.
When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.
Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
Sent from my Nexus 6P using XDA Labs

Squall88uk said:
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.
When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.
Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I am in the same boat. I am using the the latest RR FROM which is awesome, but I'm not wanting to use magical. Have always used super SU and stick Mount for my next SD. Would like to know the process for disabling manual and cm/Los root mgmt. To use Super SU. I can't use stick Mount with root explorer without super SU. WHEN I try to update binary it fails and if I try to flash in recovery, I get stuck in boot loop and have to restore backup.

Having a similiar problem on Galaxy S2 with RR 5.8.2 - installed SeperSu and it fails to update its binary when I choose 'normal'. Tried Cwm/Twrp option on a stock rom once and the phone got softbricked. Converting SuperSu to system app doesn't help.
---------- Post added at 05:05 AM ---------- Previous post was at 04:48 AM ----------
Squall88uk said:
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.
When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.
Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
No such option appears in SuperSu after disabling root access in dev options here also.

There was a time a while ago that I had asked something similar to to one of the CyanogenMod Team Developers.
I was told that when the Superuser option (in the Developer Options) is set to disabled, that means that the CyanogenMod systems Superuser access is left open. When one of the other options are set, that means that the CyanogenMod system is set to manage Superuser access that is seen by the new access to the Manage Root Access option below it.
So in short, disabled means root access is left open and CyanogenMod doesn't manage it.
If you use another root management app, like SuperSU, and leave the Root Access on disabled, then SuperSU takes on managing Root Access.
I've never had a problem with SuperSU and always left the Root Access disabled.
I hope i had explained it okay...
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
***PLZ THANK ME WITH A THUMBS UP***

Ibuprophen said:
There was a time a while ago that I had asked something similar to to one of the CyanogenMod Team Developers.
I was told that when the Superuser option (in the Developer Options) is set to disabled, that means that the CyanogenMod systems Superuser access is left open. When one of the other options are set, that means that the CyanogenMod system is set to manage Superuser access that is seen by the new access to the Manage Root Access option below it.
So in short, disabled means root access is left open and CyanogenMod doesn't manage it.
If you use another root management app, like SuperSU, and leave the Root Access on disabled, then SuperSU takes on managing Root Access.
I've never had a problem with SuperSU and always left the Root Access disabled.
I hope i had explained it okay...
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
***PLZ THANK ME WITH A THUMBS UP***
Click to expand...
Click to collapse
Disabled Root access in developer options, rebooted phone and started Supersu, it tries ro update its binaries and fsils again. Then I look for the "respect CM root settings" option but don't see it.
Some people are having success flashing the Supersu.zip through TWRP but isn't there a risk of replacing the RR bundled recovery and ending in bootloop? Is it possible to flash TWRP zip from RR recovery without causing more issues?

kikot said:
Disabled Root access in developer options, rebooted phone and started Supersu, it tries ro update its binaries and fsils again. Then I look for the "respect CM root settings" option but don't see it.
Some people are having success flashing the Supersu.zip through TWRP but isn't there a risk of replacing the RR bundled recovery and ending in bootloop? Is it possible to flash TWRP zip from RR recovery without causing more issues?
Click to expand...
Click to collapse
I attached an image of where in SuperSU the setting is but, I leave it unchecked...
Try flashing the SuperSU zip since flashing it also installs the binaries too.