Database Info

[Temp Fix] Prevent GL2SD and Folder Mount from rebooting

I will not take any responsibility if something bad happens to your phone, or if you have to reflash the stock rom. This method is only tested on my own Xperia M2 D2303 and works fine so far.
If you did use the Towel Root method to gain root access to your M2, you probably tried to install Folder Mount or GL2SD in order to move some of your games and apps to your SD card. Unfortunately they will keep rebooting your phone unless you stop the SONY Ric service. Here is a temporary workaround.
Root your device first and follow the Towel Root guide, including the Super SU installation!
Make sure that your SD card is FAT32 formatted and there is sufficient space left to actually move the app/game
First download and install busybox from the play store and make sure that the install path says /system/xbin
Then also install Script Manager from the play store and open the app.
Tap the three dots on the bottom right of your screen to open the menu and select "New Script"
Give it a convinient name, "ric" will do just fine
Select SM Editor from the list
Type in the following (the first line is already there)
Code:
#!/system/bin/sh
mount -o rw,remount /system
stop ric
busybox pkill -f /sbin/ric
Save the file and close it
Now find the newly created "ric" in the list and tap it.
Make sure you select the "SU" and "Boot" icons and that "is script" is selected. Tap the save button.
{
"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"
}
Reboot and try if it works.
There are couple of "rootfixes" here on XDA that will attempt to fix the problem, but since they are all written for different Xperia devices they won't work. Also, this is NOT the same "halfroot" problem as on other Xperia phones since you can freely remount /system in RW mode, change permissions or delete/edit files inside.
This small script will be usable for all rooted M2's with locked bootloaders, while others will get custom kernels with blocked RIC sooner or later.
Remember: When you are done playing, unmount the folder in GL2SD/FolderMount before connecting the USB cable or stuff may happen.
Let me know if it works for you.

Currently, I'm not playing any large file gaming but Many of friends from M2 group experiencing bootloop when trying to folder mount, I'll let them know for this temp fix and post it here how the outcome.
Sent from my D2305 using XDA Free mobile app

Thank you very much !!!!!
Works very well and now, I can move my obb folder !!!!
Great script

it does'nt work
If I write these commands on terminal it work but the script produce no result.

How to instal busybox if system is read only?
Thanks

init.d support xperia M2 lollipop

{
"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"
}
1.- Requirements:
- Root
- Android 5.1.1
- Unlocked & locker bootloader
- Busybox
2.- Download the file to leave on the following link: Download
3.- and decompressed on your xperia
4.- use applications that leave the pack and install the application and concenden busybox root and give permissions to install
5.- and install the application busybox checker to find out if in your xperia ah busybox installed correctly
6.- now you are going to edit the file located in the /system /etc/
Code:
init.qcom.post_boot.sh
7.- and add the following line in the file opened
Code:
/system/xbin/busybox run-parts /system/etc/init.d
8.- Now create a folder called init.d with the following permissions
9.- the file that I download above comes a place it in the folder init.d the following file permissions
10.- android variable path
Code:
PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
11.- Now just restart your phone and create script as needed to optimize what you want :fingers-crossed: :good:
Note: the script that were never worked before in my terminal with this method that I bring everything works correctly

If you install/flash Xperia M2 5.1.1 RIC disabler, it'll also do all of that for you, so I don't get the point of making another tutorial for it. ¯\_(ツ)_/¯

I did not know there was a tool but carries it another mobile so neither the case with your comments please edit it because it misreads thanks

If ric disable do that work, its useless you tutorial, and for others devices with qualcom they can use the zip on this thread easy and simple

at no time it was to disable ric init.d this is to support the device please read and do not mix topics other than the Xperia M2 thanks

linuxct said:
If you install/flash Xperia M2 5.1.1 RIC disabler, it'll also do all of that for you, so I don't get the point of making another tutorial for it. ¯\_(ツ)_/¯
Click to expand...
Click to collapse
kaiiori said:
I did not know there was a tool but carries it another mobile so neither the case with your comments please edit it because it misreads thanks
Click to expand...
Click to collapse
I don't think I should edit it. I'm just saying that this thread is pretty useless since, for the Xperia M2 (I think we're all talking about the same device, right?), to edit /system in LOLLIPOP and KK, you NEED to disable RIC, and to do that, you need to use that tool. That tool installs the init.d support, so, there's no need to do that all over again since the tool does it for you, either via command line, or via flashable zip, no need to touch the files by your own
I just wanted to clarify this because, I'm pretty sure some people that have flashed/installed the RIC Disabler had no idea they already had init.d, and they're going to follow this and screw something up... Just saying

Root samsung galaxy a sm t285

{
"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"
}
good afternoon
I root my Samsung tablet t285m
someone knows how i try and root with vroot and kingorot and nothing
I need root please help
I come to this forum because they are the master of the android
[IMG="TABLET SM T-285 TABLET A"]
[/IMG]

please see my PM (private message) maybe set you in some direction maybe not...also need help from you if possible advice/guidance
thanks

needed root file

gencom said:
needed root file
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/help/looking-to-direction-root-galaxy-tab-a6-t3390941
(T285M,....modified system image for debloat etc-tar.md5 fails on flash in odin-not sure if some signing is needed-have the system folder if anyone interested...took out some apps, added csc folder with some xmls for control on data on off auto for mms, added two fonts...nothing more than that)
also see page 14 here
http://forum.xda-developers.com/and...ng-tab-e-sm-sm-smnu-smp-t3302935/post66585078

I just got my T285 yesterday. Noticed that in Setting, App manager I can move some app to sdcard but after restart, the moved app disappear.
Sorry if I have mislead anyone.
Now I am also facing memory shortage with this 8G device.

I have lost all hope for root on the SM-T285. Why such a low profile device gets a locked down bootloader annoys me.
However I'm trying to customize its system.img, I'm stuck though as Heimdall fails at 3% upload everytime I try to use a repacked system.img file. Flashing the original image works fine though so it could just be in the way that I repackage the image. tune2fs shows some difference which I am still trying to sort out.
I'm willing to help if there are things that I can try.

jaritico said:
i found this on web, seems fake but, uses a beta root file of cf auto root webpage:
HOW TO ROOT GALAXY TAB A 7.0 (2016)
Note: This is a developing story. As far, we have found only one way to root your phone. But if someone invent more tricks of rooting in future, we will try to share with you.
You can install Chainfire’s SuperSU manually using a custom recovery such as TWRP (In this method we are showing how to install SuperSU.zip file with TWRP). If you are interested, check details below but take a backup of your device’s data first. This method should work with any variant of tab including SM-T280 (Wi-Fi only) and SM-T285 (4G/Wi-Fi)
Step One: Download Chainfire’s SuperSu.zip file.
Step Two: Copy the downloaded zip file to your device.
Step Three: Turn off your Samsung device and boot into recovery mode (boot device by pressing and holding down volume up, home, and power keys at the same time to enter in recovery mode).
Step Four: Take a backup, it is optional but important because if something happen bad in rooting, backup file will help you to restore previous state easily. So press ‘backup’ button, check all the boxes for backing up everything and then swipe to start the game.
Step Five: Once you have taken the backup file, press ‘install’ button, locate the SuperSu.zip file and confirm you want to install it.
Step Six: Reboot the device and your device is rooted.
Credits: http://lifeatsamsung.com/root-galaxy-tab-7-0-2016/
Click to expand...
Click to collapse
Yeah it's fake. To even be able to follow that, you need a custom recovery, but there is no way to install custom recovery right now with a locked bootloader.

Recent root problems on my L04 Marshmallow B820

I had the problem, I couldn't root my phone after the update from B521 to the latest B820 version.
I tried out SuperSu versions 2.65 till 2.74.
After rooting through TWRP, I always got bootloops and after unrooting the system starts normally.
As a last try, I looked into the install script and set the "SYSTEMLESS" var to "true".
Now I've got a rooted and starting phone.
So I think there must be a problem, at least for me, with automatically detecting a systemless installable Android version in SuperSu from chainfire at Honor 6, as I understand.
Did anyone else have that problem?
I added SYSTEMLESS=true in /META-INF/com/google/android/update-binary within SuperSu-v2.65.zip, just as described there, but it should defaults to true after proper detecting without this.
At my B521 system, I used SuperSu version 2.52, which worked there and wasn't booting at Marshmallow, too.

Install 2.62
{
"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"
}
Sent from my H60-L04 using Tapatalk

What Tools did you use? The multi tool doesn't have emui 4 on L04 yet

gammaanimal said:
What Tools did you use? The multi tool doesn't have emui 4 on L04 yet
Click to expand...
Click to collapse
Flash it using TWRP recovery...
Sent from my H60-L04 using Tapatalk

The Multi Tool says for TWRP L02 and L12, can I also install it on L04?

I've installed SuperSu 2.74 via fastboot/TWRP, but as I wrote, only with an modified updater-script, the system boots up. (for me, not sure why and maybe this can help others)

Machredsch said:
I've installed SuperSu 2.74 via fastboot/TWRP, but as I wrote, only with an modified updater-script, the system boots up. (for me, not sure why and maybe this can help others)
Click to expand...
Click to collapse
I think I have exactly the same issue, could you upload your modified supersu.zip for me or walk me through the modifications?
That'd be swell.

hagehagen said:
I think I have exactly the same issue, could you upload your modified supersu.zip for me or walk me through the modifications?
That'd be swell.
Click to expand...
Click to collapse
Have tested it today with latest stable SuperSu, which is v2.76-20160630161323.
-> open the archive with an archive-manager
-> go to /META-INF/com/google/android/ directory
-> edit update-binary with a text editor (your text editor should respect linux line breaks (LF), so if you're on windows, you have to make sure this, I think)
-> after the commented section(all lines with a # beginning), where you can read about possible system vars and beyond,
you have to set the SYSTEMLESS variable to true like in the following example of code:
Code:
...
# if needed. It must replace the input file and return a 0 exit code.
[COLOR="Red"]SYSTEMLESS=true[/COLOR]
OUTFD=$2
...
Line 2, you have to insert to achieve an systemless installation, which seems to be the only way for you and me to make it work.
Please make sure to pay attention to upper/lower case, because otherwise it will fail.
-> save the updated zip and install it via TWRP, e.g. via sideload
Hope, this was usefully.
Note: This is only usefull for Marshmallow as described in the file, because it will not work below.
If you leave TWRP afterwards, e.g. for reboot and it asks you for installing root, click on "Do not install".

FX file Explorer - How to make a file write accessible?

I'm Rooted and using Androids FX file Explorer, to try to add a ring tone to the ringtones system folder.
/system/media/audio/ringtones
Would someone explain how to make the file write accessable or direct me to a link to how to do this?
{
"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"
}
I searched but all I could find were links how to do it through a command promt, which is not what I'm looking for.
Android 13
galaxy A22 plus
Rooted with Majiks systemless-ly activated

20GT said:
I'm using Androids FX file Explorer, to try to add a ring tone to the ringtones system folder.
/system/media/audio/ringtones
Would someone explain how to make the file write accessable or direct me to a link to how to do this?
View attachment 5836745
I searched but all I could find were links how to do it through a command promt, which is not what I'm looking for.
Android 13
galaxy A22 plus
Click to expand...
Click to collapse
after android 8 (in preparation for project Treble), system partition is mounted during boot as read-only by default (as you can find out through the partition's mount flags). so there's 2 ways to achieve what you want:
you remove the shared_block feature from Super.img and mount system as R/W. There are tools to do this, but they're not tested on Samsung devices. Like this Tool.
you root your phone with Magisk and make a Magisk module to add your files systemless-ly. Here is the Developer Guide.
Of course, You would need an unlocked Bootloader. Here is the guide for Unlocking and Rooting. I also advise you to flash TWRP before experimenting with the Module you create. Good luck.

Slim K said:
after android 8 (in preparation for project Treble), system partition is mounted during boot as read-only by default (as you can find out through the partition's mount flags). so there's 2 ways to achieve what you want:
you remove the shared_block feature from Super.img and mount system as R/W. There are tools to do this, but they're not tested on Samsung devices. Like this Tool.
you root your phone with Magisk and make a Magisk module to add your files systemless-ly. Here is the Developer Guide.
Of course, You would need an unlocked Bootloader. Here is the guide for Unlocking and Rooting. I also advise you to flash TWRP before experimenting with the Module you create. Good luck.
Click to expand...
Click to collapse
Sorry I forgot to mention that I'm already Rooted with systemless-ly already activated.

Just tested Fx file explorer on my privious phone and it works correctly after mounting the folder.
I passed the root check. is there a diffent option/checkmark to allow Fx access to root or give Fx pemisions in majiks on android 13?