I am using OOS 3.5.4. My device is rooted. But I cannot make changes to system files, when I am trying to remove a file from 'init.d' folder it says resource busy. When I am trying to copy a file to the init.d folder it says it failed to copy. Same with other folders in system. How to explore root and write ?
ProudRed said:
I am using OOS 3.5.4. My device is rooted. But I cannot make changes to system files, when I am trying to remove a file from 'init.d' folder it says resource busy. When I am trying to copy a file to the init.d folder it says it failed to copy. Same with other folders in system. How to explore root and write ?
Click to expand...
Click to collapse
Have u rooted your phone with systemless meathod or normal usual method with su in system partition
if you use the normal method then mount ur system as read wite use Root explorer apps like ES file explorer, Root Explorer etc.
Press the thanks button if i helped u.
Azaruddin said:
Have u rooted your phone with systemless meathod or normal usual method with su in system partition
if you use the normal method then mount ur system as read wite use Root explorer apps like ES file explorer, Root Explorer etc.
Press the thanks button if i helped u.
Click to expand...
Click to collapse
Hi, mine is system less method. I have been using ES File explorer, after mounting when I am trying to delete any file it says resource busy.
One of the examples.
{
"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 ONEPLUS A3003 using Tapatalk
ProudRed said:
One of the examples. View attachment 4167740
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
ok. First Enable the root explorer option from the navigation drawer of the ES File Explorer the mount ur system read write mode and then try.
if that doesn't work boot into twrp and mount ur system as read write mode and then try :good:
Azaruddin said:
ok. First Enable the root explorer option from the navigation drawer of the ES File Explorer the mount ur system read write mode and then try.
if that doesn't work boot into twrp and mount ur system as read write mode and then try :good:
Click to expand...
Click to collapse
Root explorer is enabled. But rw is mounted only when I am doing it from twrp
ProudRed said:
Root explorer is enabled. But rw is mounted only when I am doing it from twrp
Click to expand...
Click to collapse
Since ur using Systemless root first boot into ur TWRP and mount us system as R/W and try. but if u modify ur system the u will trigger the dm-variety. if u want to modify ur system then go for usual normal root method. root ur device with superSU.
Azaruddin said:
Since ur using Systemless root first boot into ur TWRP and mount us system as R/W and try. but if u modify ur system the u will trigger the dm-variety. if u want to modify ur system then go for usual normal root method. root ur device with superSU.
Click to expand...
Click to collapse
Flashing super su from twrp ? Still its systemless root I guess. As it doesnt gets installed in the system.
Sent from my ONEPLUS A3003 using Tapatalk
ProudRed said:
Flashing super su from twrp ? Still its systemless root I guess. As it doesnt gets installed in the system.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
using SuperSU u cant root ur device in both the method either systemless or using system.
Are u using magisk? give some more info about ur scenario.
Azaruddin said:
using SuperSU u cant root ur device in both the method either systemless or using system.
Are u using magisk? give some more info about ur scenario.
Click to expand...
Click to collapse
Yes I am using magisk but rooted with super su. Magisk is the root manager. Previously when I rooted with super su, it didnt get installed into the system. I flashed from twrp
ProudRed said:
Yes I am using magisk but rooted with super su. Magisk is the root manager. Previously when I rooted with super su, it didnt get installed into the system. I flashed from twrp
Click to expand...
Click to collapse
Try the Magisk module "Magisk init.d | Universal init.d enabler!"
https://forum.xda-developers.com/apps/magisk/module-magisk-init-d-universal-init-d-t3579305
or
try the following commands from the twrp terminal:
su
mount -o rw,remount /system
mkdir /sdcard/init/
cp /system/etc/init.d /sdcard/init/
rm -r /system/etc/init.d/*
Azaruddin said:
Try the Magisk module "Magisk init.d | Universal init.d enabler!"
https://forum.xda-developers.com/apps/magisk/module-magisk-init-d-universal-init-d-t3579305
or
try the following commands from the twrp terminal:
su
mount -o rw,remount /system
mkdir /sdcard/init/
cp /system/etc/init.d /sdcard/init/
rm -r /system/etc/init.d/*
Click to expand...
Click to collapse
already using the init.d enabler. It does mount the init.d files. But I cannot make any changes to system files.
I trued using these commands in terminal app. When I entered this "mount -o rw,remount /system" got "invalid argument" error.
ProudRed said:
already using the init.d enabler. It does mount the init.d files. But I cannot make any changes to system files.
I trued using these commands in terminal app. When I entered this "mount -o rw,remount /system" got "invalid argument" error.
Click to expand...
Click to collapse
hmm k then no other go u have to root ur device with system based root then only u can modify the system partition.
Azaruddin said:
hmm k then no other go u have to root ur device with system based root then only u can modify the system partition.
Click to expand...
Click to collapse
How do I do that ? these days super su have become systemless. Any other alternative ?
ProudRed said:
How do I do that ? these days super su have become systemless. Any other alternative ?
Click to expand...
Click to collapse
First make an Nandroid back up and try these steps, so that if any thing goes wrong u can restore the backup (recommended).
Step 1: boot the device and full unroot in Supersu app.
Step 2: try to flash the stock boot.img if that fails flash the stock OOS (dirty flash is enough, no need of clean flash)
Step 3: boot into twrp >go to the terminal > and type: "echo SYSTEMLESS=false>>/data/.supersu"
Step 4: now flash supersu v2.71 or higher in twrp (if you read the logs, it should say something like "installing in system mode")
Then u will be installing su in system mode.
Smash the thanks button if i helped u
Azaruddin said:
First make an Nandroid back up and try these steps, so that if any thing goes wrong u can restore the backup (recommended).
Step 1: boot the device and full unroot in Supersu app.
Step 2: try to flash the stock boot.img if that fails flash the stock OOS (dirty flash is enough, no need of clean flash)
Step 3: boot into twrp >go to the terminal > and type: "echo SYSTEMLESS=false>>/data/.supersu"
Step 4: now flash supersu v2.71 or higher in twrp (if you read the logs, it should say something like "installing in system mode")
Then u will be installing su in system mode.
Smash the thanks button if i helped u
Click to expand...
Click to collapse
Thanks I will try it once back home. Btw how to flash the stock boot image ? Extract it from the zip ?
Sent from my ONEPLUS A3003 using Tapatalk
ProudRed said:
Thanks I will try it once back home. Btw how to flash the stock boot image ? Extract it from the zip ?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
hmm you can also do that or dirty flash the full rom zip of OOS 4.1.3.
Azaruddin said:
hmm you can also do that or dirty flash the full rom zip of OOS 4.1.3.
Click to expand...
Click to collapse
I am on 3.5.4. That will do right ?
Sent from my ONEPLUS A3003 using Tapatalk
ProudRed said:
I am on 3.5.4. That will do right ?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
hmm s you can flash 3.5.4 :good:
Azaruddin said:
hmm s you can flash 3.5.4 :good:
Click to expand...
Click to collapse
After the optimization of apps are done, the device gets into soft reboot mode and stuck at boot animation. (the brightness is very dimmed).
Related
Hi All,
Here is rooted 3.2.78 firmware for SDE enabled devices.
I did two versions:
- squashfs (like my previous build), in this one, system is read-only, you can't add/remove stock apps and edit system files. Files are compressed so it takes less storage space than ext4, it should be also slower than ext4.
- ext4, system is read/write and should be quicker. Be careful if you modify system files though.
Both have kernel/modules from 3.2.78.
To install it:
0) You must have SDE installed. If you didn't do it already, check there instructions on how to do it.
1) Extract zip file content
2) Copy android_3.2.78.squashfs (or android_3.2.78.ext4) to internal storage root. You can do it the usual way or with adb with this:
Code:
adb push android_3.2.78.squashfs /data/media
or
Code:
adb push android_3.2.78.ext4 /data/media
3) Reboot
4) On boot menu, select "Recovery system"
{
"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"
}
5) Select "developer edition menu"
6) Select "flash kernel and initramfs"
6) A drive should appear on your PC, copy zImage and initramfs.cpio.gz to it.
7) Select OK, the kernel should flash.
8) Select OK to reboot and maintain vol+ pressed. Boot menu should appear after reboot.
9) Select SDE in boot menu, you should be rooted and SuperUser functional.
The only change from stock: I enabled vibrator control panel option, it has been reported to work on some, it doesn't on mine.
I checked 3.2.78 stock firmware, it has an updated bootloader, it may be worth flashing stock firmware too to have everything synched.
Download rooted 3.2.78 on squashfs here.
Download rooted 3.2.78 on ext4 here.
Cheers,
LeTama
great thank you
gonna flash it as soon as its downloaded
btw do i have to do any special things to flash the ext4 ?
Ok...good job....!!!
I understand now why I did not have options rw in root-explorer....because I managed the Rom with squashfs and not with ext4.....
Now everything is ok....thanks again @letama...
No, nothing special for ext4, same thing as squashfs...
letama said:
No, nothing special for ext4, same thing as squashfs...
Click to expand...
Click to collapse
Are you saying that installing with ext4 partition I'll can't be mount RW in root_explorer ?
-because with squashfs I can't ....
surdu_petru said:
Are you saying that installing with ext4 partition I'll can't be mount RW in root_explorer ?
-because with squashfs I can't ....
Click to expand...
Click to collapse
no i think he answered my question from above
surdu_petru said:
Are you saying that installing with ext4 partition I'll can't be mount RW in root_explorer ?
-because with squashfs I can't ....
Click to expand...
Click to collapse
No, sorry, our posts crossed, I was effectively replying to djnilse. I'm trying to refrain my "quote mania", it was not a good idea this time
Ext4 is R/W, and permanently, no need to remount it in root explorer.
I would have preferred ext4 mounted first as r/o and allow the option to remount as r/w when needed, but this is not possible with the way Archos designed their rootfs.
Hi Letama,
Thanks for your build but I cant use your kernel with 3.2.78 kernel modules and when I extract kernel from 3.2.78, init kernel does not boot :/.
Thanks in advance
Thaolia
ok i flashed it everything worked fine
i have now a dualboot recovery menu with Android(non-root) and developer(root)
on developer the root is ok, also the system is r/w
thx letama for the rooted newest update
As a question to get out of the way early in the thread, I'm on your earlier rooted one, do I need to wipe?
Sent from my HTC Desire HD using xda premium
Tha0lia said:
Hi Letama,
Thanks for your build but I cant use your kernel with 3.2.78 kernel modules and when I extract kernel from 3.2.78, init kernel does not boot :/.
Thanks in advance
Thaolia
Click to expand...
Click to collapse
Archos kernel is using a new compression scheme for initrd, check my howto, the "find . | cpio ..." command. You need to rebuild your initrd.
Quinny899 said:
As a question to get out of the way early in the thread, I'm on your earlier rooted one, do I need to wipe?
Click to expand...
Click to collapse
I don't think so, Archos firmware update doesn't, so it shouldn't be necessary.
I had to wipe mine for another reason so I can't be sure though.
letama said:
Archos kernel is using a new compression scheme for initrd, check my howto, the "find . | cpio ..." command. You need to rebuild your initrd.
Click to expand...
Click to collapse
My extract kernel is of 5Mb (I use your howto for extract the 3.2.78 kernel). Init and recovery extract kernel doesn't boot with a lzop initramfs.cpio. Wheras with your kernel and modules, all works fine.
Sry but I certainly forget somethings.
Thanks in advance
Thaolia
Tha0lia,
5 MB is wrong:
- aos-unpack gives you 9_MMCF (5145304)
- dd strips header and gives you init_kernel which contains zImage+initrd (5145040)
- aos-kernel-unpack of init_kernel gives you kernel and initrd separated (unpacked-kernel, unpacked-cpio.gz), that I renamed to init-zImage afterwards.
This is the one you want, size should be 3993572.
Cheers,
LeTama
Noticed an issue in the first post:
adb cp should read
adb push
Sent from my ARCHOS 80G9 using xda premium
Quinny899 said:
Noticed an issue in the first post:
adb cp should read
adb push
Click to expand...
Click to collapse
Thanks! I shouldn't post when I'm in a hurry . First post fixed.
letama said:
Tha0lia,
5 MB is wrong:
- aos-unpack gives you 9_MMCF (5145304)
- dd strips header and gives you init_kernel which contains zImage+initrd (5145040)
- aos-kernel-unpack of init_kernel gives you kernel and initrd separated (unpacked-kernel, unpacked-cpio.gz), that I renamed to init-zImage afterwards.
This is the one you want, size should be 3993572.
Cheers,
LeTama
Click to expand...
Click to collapse
Sorry, your kernel and my extract kernel have same md5sum.
It's my fault but thanks for your help.
Have a nice day !
Thaolia
For the Buzz in FRANCE
http://www.jbmm.fr/?p=25015
(ps : je recherche des rédacteurs "techniques" pour jbmm - envoyez un MP)
Is it possible to get swap working in the build modifications?
When I use swapper for root from the market, reboot and type free, I get this:
It shows it as empty and unused. Any idea why? There's a swapfile on /sdcard, in fat, which is being activated by the app on boot. Could this be fixed? I'm using the latest rooted ext4 version btw
Sent from my ARCHOS 80G9 using xda premium
I got swap working!
You use swapper 2 and direct it to /mnt/sdcard, and rather than /sdcard. Turns out internal is ext and it needs fat
Sent from my ARCHOS 80G9 using xda premium
First ....THANKS @letama, and last but not least thanks to @tRAcE3k for .ext4 build.
Official Stock Firmware v3.2.79 => ROOT, Update : Su binary v3.0.3.2, Superuser v3.0.7 and busybox v1.19.3, Add : enables vibrator and adjust volume !
(There is no need to install busybox.apk or busybox installer.apk from market, busybox is already installed into /system/xbin/ - only for .ext4)
This ROM is only for SDE enable ( recovery) ....you can use it as a daily ROM...
These are the files you need :
- zImage => http://www.4shared.com/file/KXp8bLDa/zImage.html
- initramfs.cpio.gz => http://www.4shared.com/archive/6Y9sMqJ5/initramfscpio.html
- archos_3.2.79.squashfs => http://www.4shared.com/zip/-vo5gkRr/firmware_3279squashfs.html (...version without busybox and update!)
- archos_3.2.79.ext4 => http://www.4shared.com/zip/dmrcBtJM/3279_updat.html
How install this :
- connect device via USB cable
- adb push archos_3.2.79.squashfs data/media/ ........for read-only /system
- adb push archos_3.2.79.ext4 data/media/..............for read-write /system and other stuff
- reboot into recovery , Recovery System-> Developer Edition Menu -> Remove Kernel ( for boot only to SDE) -> I Understand -> Ok -> Developer Edition Menu -> Flash Kernel and Initramfs -> copy zImage and initramfs into new driver -> Ok ! that's all
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
hitman72 said:
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
Click to expand...
Click to collapse
No, you have to flash zImage and initramfs.cpio.gz in sde developer menu each time. First, filename changed and it's hardcoded in initramfs, second, Archos bugfixes are also in the kernel so new zImage is required.
Thanks surdu_petru for taking the relay!
letama said:
No, you have to flash zImage and initramfs.cpio.gz in sde developer menu each time. First, filename changed and it's hardcoded in initramfs, second, Archos bugfixes are also in the kernel so new zImage is required.
Thanks surdu_petru for taking the relay!
Click to expand...
Click to collapse
old firmware (3.2.77 etc) must be removed manually from device?
ext link is invalid "......". ciao ;-)
gegabit said:
old firmware (3.2.77 etc) must be removed manually from device?
Click to expand...
Click to collapse
When everything works, yes, you can remove the previous .ext4 from internal storage. That's the only thing you have to remove.
hitman72 said:
ext link is invalid "......". ciao ;-)
Click to expand...
Click to collapse
now its upload to share.
- archos_3.2.79.ext4 => /.......future upload ..... it's 512Mb ext4...........
Click to expand...
Click to collapse
Hi Folks.
Thought I'd do my bit. Here are some more sources to download the ext4 firmware.zip
http://www.multiupload.com/0OTX0D54XW
Thanks to surdu_petru for the original image and tRAcE3k for the repacking instructions in this post.
Thanks
Trev
hitman72 said:
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
Click to expand...
Click to collapse
[email protected] sure is right....on the ather hand, every new firmware ( ex. firmware_archos_it4.aos) has its own boot image ( boot.img = zImage + initramfs) -used to boot devices and has its own flash files / system files which are grouped in an archive ( contains - libraries, aplikations, and other stuff ) - used to run system android , and all these are closely linked ....I think you can now better understand how to use them, and why ......
hitman72 said:
ext link is invalid "......". ciao ;-)
Click to expand...
Click to collapse
Ok...Now is valid link : http://www.4shared.com/zip/bp7XjWzY/archos_3279ext4.html....
Good luck!
Downloaded the ext4 version and couldn't get it to work.
Only root through the ADB Shell functioned, anything else Superuser automatically got denied, even though in the Superuser app it was set to prompt.
Chmodded the su binary to 6755 and it started to work
droobey said:
Downloaded the ext4 version and couldn't get it to work.
Only root through the ADB Shell functioned, anything else Superuser automatically got denied, even though in the Superuser app it was set to prompt.
Chmodded the su binary to 6755 and it started to work
Click to expand...
Click to collapse
Ok! Now just upload new update .....
First off Thanks very much surdu_petru for the work!
Please excuse my novice ability here, but...
I'm not sure if I did everything correctly, but I don't have root anymore. (i did with 3.2.78)
I did the adb push of the archos_3.2.79 to /data/media
then did the flash of intramfs and zImage from the beginning of this post.
I rebooted into developer and Root Checker says i don't have Root anymore?
Do i need to chmod the SU binary now to fix? if so where is the SU binary located in the filesystem? (i'm not sure how i would execute that command, via adb?)
revere521 said:
First off Thanks very much surdu_petru for the work!
Please excuse my novice ability here, but...
I'm not sure if I did everything correctly, but I don't have root anymore. (i did with 3.2.78)
I did the adb push of the archos_3.2.79 to /data/media
then did the flash of intramfs and zImage from the beginning of this post.
I rebooted into developer and Root Checker says i don't have Root anymore?
Do i need to chmod the SU binary now to fix? if so where is the SU binary located in the filesystem? (i'm not sure how i would execute that command, via adb?)
Click to expand...
Click to collapse
OK! Try >adb shell chmod 6755 system/bin/su
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
revere521 said:
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
Click to expand...
Click to collapse
same problem here the chmod doesn't solve it.
Eacy root command runed gets a deny from superuser even when tel superuser to allow everything
revere521 said:
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
Click to expand...
Click to collapse
.....after install all....try to update Superuser into Market......
Update doesn't help :-(
surdu_petru said:
.....after install all....try to update Superuser into Market......
Click to expand...
Click to collapse
Update doesn't help :-(
tryed the update fix of superuser also
Update of the su binarie failde at md5sum check
basd82 said:
Update doesn't help :-(
tryed the update fix of superuser also
Update of the su binarie failde at md5sum check
Click to expand...
Click to collapse
OK I know.....just wait max 1 hour and I'll uploaded the new archos_3.2.79 files...with it everything works perfectly ( I have tested all , root_explorer, es file explorer, Root Check ....it's OK !!!!!).
basd82 said:
same problem here the chmod doesn't solve it.
Eacy root command runed gets a deny from superuser even when tel superuser to allow everything
Click to expand...
Click to collapse
ok! but now problem was solved.....just redownload the new firmware_3.2.79 files , unpack and enjoy*
Hi guys today I have rooted my xolo a500s IPS
using farmaroot but when I tried to mount system
r/w for pushing some apps and removing some on
system partition but it is not mounting because of
that i cant make changes on system please help
how can I mount system partition
TheRoHit18 said:
Hi guys today I have rooted my xolo a500s IPS
using farmaroot but when I tried to mount system
r/w for pushing some apps and removing some on
system partition but it is not mounting because of
that i cant make changes on system please help
how can I mount system partition
Click to expand...
Click to collapse
Can you mount in CWM? If yes, then try this workaround. Mount system and Flash Aroma File Manager. Now you have mounted System folder for pushing and deleting APKs. :thumbup:
Press thanks if helped. :thumbup: :thumbup: :thumbup:
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands
hnkotnis said:
Can you mount in CWM? If yes, then try this workaround. Mount system and Flash Aroma File Manager. Now you have mounted System folder for pushing and deleting APKs. :thumbup:
Press thanks if helped. :thumbup: :thumbup: :thumbup:
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands
Click to expand...
Click to collapse
I have not installed cwm yet
TheRoHit18 said:
I have not installed cwm yet
Click to expand...
Click to collapse
Which browser are you using ? And check again if your phone is rooted see if you have the SuperSU app.
I recommend you to use Root Browser.
PrimeNexes said:
Which browser are you using ? And check again if your phone is rooted see if you have the SuperSU app.
I recommend you to use Root Browser.
Click to expand...
Click to collapse
I used all apps like es file explorer , root browser, root explorer but system can't be mounted on rw I really what's the reason and my xolo is rooted
TheRoHit18 said:
I used all apps like es file explorer , root browser, root explorer but system can't be mounted on rw I really what's the reason and my xolo is rooted
Click to expand...
Click to collapse
Do you get a prompt form the SuperSU application for allowing the root access ? If you don't check the superSU settings you may have disabled the root access for any app.
PrimeNexes said:
Do you get a prompt form the SuperSU application for allowing the root access ? If you don't check the superSU settings you may have disabled the root access for any app.
Click to expand...
Click to collapse
yes I get prompt from supersu
I also tried installing busy box but it also not getting installed
TheRoHit18 said:
yes I get prompt from supersu
Click to expand...
Click to collapse
I recommend you to check the SuperSU setting as you problem does sound like root access is not available to the app.
Try installing terminal emulator and type "su" in the terminal and press enter if you get "[email protected]: / # " then the apps are getting the access.
then type "reboot" and if your phone reboots then the apps can interact with root file.Give it a try and post the result.
PrimeNexes said:
I recommend you to check the SuperSU setting as you problem does sound like root access is not available to the app.
Try installing terminal emulator and type "su" in the terminal and press enter if you get "[email protected]: / # " then the apps are getting the access.
then type "reboot" and if your phone reboots then the apps can interact with root file.Give it a try and post the result.
Click to expand...
Click to collapse
bro I tried this via adb the phone is rooted and I also tried mounting system via adb but it showing read only file system
TheRoHit18 said:
bro I tried this via adb the phone is rooted and I also tried mounting system via adb but it showing read only file system
Click to expand...
Click to collapse
Can you upload some pics like the settings page of superSU,the error you get while browsing the root files with Root Explorer ?
And tell me what thing you did for rooting.
PrimeNexes said:
Can you upload some pics like the settings page of superSU,the error you get while browsing the root files with Root Explorer ?
And tell me what thing you did for rooting.
Click to expand...
Click to collapse
here are the some ss...
TheRoHit18 said:
here are the some ss...
Click to expand...
Click to collapse
First of all upgrade the superSU or install the latest Frameroot from Here
And then try
PrimeNexes said:
First of all upgrade the superSU or install the latest Frameroot from Here
And then try
Click to expand...
Click to collapse
I have used it for rooting my xolo really m confused my phone is rooted but still I can't make changes in system also I tried installing busybox but failed to install
TheRoHit18 said:
I have used it for rooting my xolo really m confused my phone is rooted but still I can't make changes in system also I tried installing busybox but failed to install
Click to expand...
Click to collapse
I am not getting whats the problem so first you you install the CWM so that we can install a Custom ROM so if your files or Settings are messed up it will be cleared or just factory reset your phone or Super-wipe the phone.
PrimeNexes said:
I am not getting whats the problem so first you you install the CWM so that we can install a Custom ROM so if your files or Settings are messed up it will be cleared or just factory reset your phone or Super-wipe the phone.
Click to expand...
Click to collapse
I have installed cwm the problems is system is not mounting to r/w coz of that I can't remove or push apps to system
TheRoHit18 said:
I have installed cwm the problems is system is not mounting to r/w coz of that I can't remove or push apps to system
Click to expand...
Click to collapse
can you mount it in CWM ??? And did you installed a custom ROM ?
PrimeNexes said:
can you mount it in CWM ??? And did you installed a custom ROM ?
Click to expand...
Click to collapse
yes I can mount in cwm but when I flashed a s4 launcher successfully but nothing happend
TheRoHit18 said:
yes I can mount in cwm but when I flashed a s4 launcher successfully but nothing happend
Click to expand...
Click to collapse
Try to flash a Custom ROM for IPS I will try to make a zip that checks your R/W.But flash a CustomROM for a trial but first make a nandroid backup :good:
PrimeNexes said:
Try to flash a Custom ROM for IPS I will try to make a zip that checks your R/W.But flash a CustomROM for a trial but first make a nandroid backup :good:
Click to expand...
Click to collapse
can you pls suggest me a c ROM for my IPS
Hello there....
I have flashed latest 5.1 lollipop via flash tool...
Then i rooted via kingroot and changed with superSU...
Then i install the xzdualrecovery via installer...(i have check almost all versions..)
And i got recovery...
But the problem is when i try to flash xposed framework sdk22
It can't flash and says can't mount /system ...
Please anyone help with this problem....
Thanks
DastanShaikh said:
Hello there....
I have flashed latest 5.1 lollipop via flash tool...
Then i rooted via kingroot and changed with superSU...
Then i install the xzdualrecovery via installer...(i have check almost all versions..)
And i got recovery...
But the problem is when i try to flash xposed framework sdk22
It can't flash and says can't mount /system ...
Please anyone help with this problem....
Thanks
Click to expand...
Click to collapse
try mounting the system before you flash
ExCuTioN said:
try mounting the system before you flash
Click to expand...
Click to collapse
I tried mounting system... From recovery... But its also failed...
DastanShaikh said:
I tried mounting system... From recovery... But its also failed...
Click to expand...
Click to collapse
you werent able to mount the system or did the flash fail again?
ExCuTioN said:
you werent able to mount the system or did the flash fail again?
Click to expand...
Click to collapse
The problem is solved...
But i have to mount the system using terminal in recovery every time before flashing anything.... Even before making backup....
And one thing more...did u tried Lucky Patcher...??
Cuz when i enable module of lucky patcher..in xposed.....the phone goes in boot loop.......
Any help.??
DastanShaikh said:
The problem is solved...
But i have to mount the system using terminal in recovery every time before flashing anything.... Even before making backup....
And one thing more...did u tried Lucky Patcher...??
Cuz when i enable module of lucky patcher..in xposed.....the phone goes in boot loop.......
Any help.??
Click to expand...
Click to collapse
you could try Rashr https://www.google.gr/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwj4v8__3qTJAhVFWBQKHW_mBQMQFggfMAA&url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dde.mkrtchyan.recoverytools%26hl%3Del&usg=AFQjCNGu4pHxHY9Qtjx32JgaHSioXrepGA&sig2=QydTlDPGIzJT6A1Bu1QDeA with rashr you can install any recovery you want and you wont lose the previous one, it might fix your problem
PS: I dont think there is a fix with lucky patcher, you could try contacting the developer
ExCuTioN said:
you could try Rashr https://www.google.gr/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwj4v8__3qTJAhVFWBQKHW_mBQMQFggfMAA&url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dde.mkrtchyan.recoverytools%26hl%3Del&usg=AFQjCNGu4pHxHY9Qtjx32JgaHSioXrepGA&sig2=QydTlDPGIzJT6A1Bu1QDeA with rashr you can install any recovery you want and you wont lose the previous one, it might fix your problem
PS: I dont think there is a fix with lucky patcher, you could try contacting the developer
Click to expand...
Click to collapse
Ok..
DastanShaikh said:
The problem is solved...
But i have to mount the system using terminal in recovery every time before flashing anything.... Even before making backup....
And one thing more...did u tried Lucky Patcher...??
Cuz when i enable module of lucky patcher..in xposed.....the phone goes in boot loop.......
Any help.??
Click to expand...
Click to collapse
Can you tell me how you did to mount thee system in terminal? I tried "mount -o rw,remount /system" but it doesn't work, it shows an error message.
Ash.VIII said:
Can you tell me how you did to mount thee system in terminal? I tried "mount -o rw,remount /system" but it doesn't work, it shows an error message.
Click to expand...
Click to collapse
Open terminal in twrp folder...
Then run following commands-
mount -o ro /system
mount -o rw,remount /system
Maybe you got error.... But when u try to flash anything.. It definitely works.. Hope this helps
Worked like a charm, thank you very much
Dear community,
I installed xposed using the following adk: XposedInstaller_3.0_alpha4.apk then flash, from recovery, the framework for my Oukitel K6000 Pro (Android 6.0): xposed-v86-sdk23-arm64.zip
All worked fine until I have to restore a backup from recovery (backup taken before I flash the framework).
Now, Xposed cannot see the framework, so I tried to uninstall it using xposed-uninstaller-20150831-arm64.zip always from recovery. The uninstallation seems goes ok, so I reboot the device, enter again into recovery to flash again the xposed-v86-sdk23-arm64.zip
Unfortunately I got an error during install process:
chown: /system/bin/dex2oat.orig.gz read only file system
or
cp: can't create '/system/xposed.prop' File esists
And the installation stop there.
Could someone help me to reinstall the framework and come back to working status?
Thank you
Lucas
Lord Spectre said:
Dear community,
I installed xposed using the following adk: XposedInstaller_3.0_alpha4.apk then flash, from recovery, the framework for my Oukitel K6000 Pro (Android 6.0): xposed-v86-sdk23-arm64.zip
All worked fine until I have to restore a backup from recovery (backup taken before I flash the framework).
Now, Xposed cannot see the framework, so I tried to uninstall it using xposed-uninstaller-20150831-arm64.zip always from recovery. The uninstallation seems goes ok, so I reboot the device, enter again into recovery to flash again the xposed-v86-sdk23-arm64.zip
Unfortunately I got an error during install process:
chown: /system/bin/dex2oat.orig.gz read only file system
or
cp: can't create '/system/xposed.prop' File esists
And the installation stop there.
Could someone help me to reinstall the framework and come back to working status?
Thank you
Lucas
Click to expand...
Click to collapse
Try clearing art/dalvik and cache then reboot directly back into recovery and flash Xposed again
Sent from my SCH-R220
Thank you for reply mattzeller, unfortunately, after cleaning art/dalvik and cache and reboot directly into recovery to install sdk I got the same error:
chown: /system/bin/dex2oat.orig.gz read only file system
Lord Spectre said:
Thank you for reply mattzeller, unfortunately, after cleaning art/dalvik and cache and reboot directly into recovery to install sdk I got the same error:
chown: /system/bin/dex2oat.orig.gz read only file system
Click to expand...
Click to collapse
Try mounting system as read/write in recovery before flashing
Sent from my SCH-R220
mattzeller said:
Try mounting system as read/write in recovery before flashing
Click to expand...
Click to collapse
I believe you mean from terminal, could you please share the command to do that? Thx!
However I see from recovery log, during uninstall/install processes:
Mounting /system and /vendor read-write
So, packages already tried to mount system... Maybe fails, I don't know!!!
Lord Spectre said:
I believe you mean from terminal, could you please share the command to do that? Thx!
However I see from recovery log, during uninstall/install processes:
Mounting /system and /vendor read-write
So, packages already tried to mount system... Maybe fails, I don't know!!!
Click to expand...
Click to collapse
In recovery open terminal :
mount -o rw,remount /system
Then try to flash Xposed
Sent from my SCH-R220
DAMN!DAMN!DAMN! This is what I done on terminal:
# mount -o rw,remount /system
Try to flash xposed-v86-sdk23-arm64.zip
Got: cp: can't create '/system/xposed.prop' File esists
Then from terminal:
# rm /system/xposed.prop
rm: can't remove '/system/xposed.prop': Read-only file system
At this point I don't know how can I proceed. Maybe flashing stock rom, then install framework from recovery, and then restore backup
Just to inform that I solved reflashing stock rom, recovery TWRP and SuperSU... Then flash again the Xposed SDK. Unfortunately I cannot use the TWRP backup, and I had to configure my phone from scratch.
Lord Spectre said:
Just to inform that I solved reflashing stock rom, recovery TWRP and SuperSU... Then flash again the Xposed SDK. Unfortunately I cannot use the TWRP backup, and I had to configure my phone from scratch.
Click to expand...
Click to collapse
Sounds like something in your backup got screwed up I would suggest deleting that back up once everything is set up and redoing it
Sent from my SCH-R220