When I've tryied to unistall the xposed that was it appears
Restoring backup from /system/bin/app_process.orig': Permision denied
Cannot move /system/bin/app_process.orig to /system/bin/app_process
I don't know what I have to do. It's a i8200N
Related
This is the account of my foolishness and I advice everyone not to follow it.:::
1.installed Linux installer std and complete Linux installer from play store.
2.when the 2nd app failed to unmount and GUI crashed showing some errors with busybox, followed 3rd step.
3. found the embedded busybox from 1st app n directly placed it in /system /xbin
4. the original busybox is gone n everything is fine but got too many errors in reading root directory of phone. None of the file manager is showing me root.
5. I'm suspecting that it has done something wrong with my cwm recovery as well for which I can't take a chance of bricking my phone.
6. NOW I need kind advice of u ppl on how to confirm the presence of recovery.img or whatever it should be to recover my cwm backed up data.
boot into recovery, if recovery do not boot then pull battery and start the mobile it will start normally, download busybox installer from play store (the one from stephen)
install busybox through the app(busybox problem will be solved)
download tass recovery cwm.tar file and flash with odin you will get cwm recovery back
did it
I've already tried busybox installers. non of them worked cause the whole root directory is unreadable to any of my apps except diskusage n similar things those show memory occupied.
then you should flash firmware and root again
Superuser
maybe update superuser binary?
solved
chmod 777 path name n got busybox 1.12
You lost root access because there is no busybox. Reflash the ROM. Easy way out.
nothing lost at all just replaced.
as I've stated the command above u, it was just a busybox w/0 permissions. I was getting permission denied.
thanks to Gael péron for his Help.
hi all,
I was running my TX with advanced kernel v4, rooted:
http://forum.xda-developers.com/showthread.php?t=1922925
yesterday i installed Miui Security from here:
http://forum.xda-developers.com/showthread.php?t=1663222
Then the root is gone. I checked that /system/bin/su and /system/xbin/su are still there but they are inter-linking with symbolic link when i view them with root explorer.
fixes tried:
When i use ADB push trying to replace them, it said "too many symbolic links encountered"
I cannot remove both file as i cannot su in ADB shell.
I booted into CWM recovery but ADB is not enabled in CWM.
I reflashed the flashable zip in CWM to gain root access with no error message prompted, but after reboot into system the SU files are still the same
I reflashed the kernel with flashtools and fastboot, still no change applied to the phone.
Any idea?
finally got it fixed...
I rewrite the updater-script in the CWM flashable zip for root package to force remove both /system/bin/su and /system/xbin/su and rewrite them back.
Thanks for watching...
I've the same problem
Hi guys,
I've the same problem.
I've flashed my Xperia T with MIUI-3.11.22 rom.
I've activated the root permission on Security tab, but my phone doesn't give me the root access (I've tried to install adbd insecure and BusyBox but the result is "problem with root access".
Some ideas?
Thx
After folowing all the steps on this guide (http://forum.xda-developers.com/showthread.php?p=41997803#post41997803) to finnaly have .253 rooted, it seems I can't write to system. Every time I try to uninstall system app using titanium backup, the phone reboots. The selected app is uninstalled, but I have to do it one by one, cause it reboots always after unistalling. Same when trying to integrate dalvik cache files to the rom with Titanium Backup or to integrate an updated app to the room. When I open the File Manager, the phone instantly reboots too... Any idea about how can I fix it?
Thanks!
Rebooting Fixed!
If someone else is facing the same problem, I fixed rebooting issue while writing to system following this guide, thanks to the user [NUT]:
[XZDualRecovery][v2.3 RELEASE] cwm 6.0.3.2 & twrp 2.5.0.0 [locked bootloader]
CWM Usage warning: Root can be lost (almost worst case), a bootloop can be experienced (worst case) or a reboot upon remounting /system to be able to write to it (most cases, relatively harmless) when using CWM and before a reboot out of recovery answering the question 'ROM may flash recovery, fix it?' question is answered with 'yes'. This can be recovered from by opening a terminal app and typing the following commands:
Code:
su
/system/bin/stop ric
mount -o remount,rw /system
chmod 755 /system/etc/install-recovery.sh
Alternatively you can boot in to TWRP and go to the Advanced menu -> File manager and look for /system/etc/install-recovery.sh to set permissions 755 on it.
You need to reroot, as that is the issue.
From me to you.
hum...
It means... downgrade to.434, root again,... reflash .253?
.LEONARDO. said:
It means... downgrade to.434, root again,... reflash .253?
Click to expand...
Click to collapse
Whichever way you want, but this is a root related problem.
Xperia Z rebooting while writing to system FIXED
Rebooting Fixed!
If someone else is facing the same problem, I fixed rebooting issue while writing to system following this guide, thanks to the user [NUT]:
[XZDualRecovery][v2.3 RELEASE] cwm 6.0.3.2 & twrp 2.5.0.0 [locked bootloader]
CWM Usage warning: Root can be lost (almost worst case), a bootloop can be experienced (worst case) or a reboot upon remounting /system to be able to write to it (most cases, relatively harmless) when using CWM and before a reboot out of recovery answering the question 'ROM may flash recovery, fix it?' question is answered with 'yes'. This can be recovered from by opening a terminal app and typing the following commands:
Code:
su
/system/bin/stop ric
mount -o remount,rw /system
chmod 755 /system/etc/install-recovery.sh
Alternatively you can boot in to TWRP and go to the Advanced menu -> File manager and look for /system/etc/install-recovery.sh to set permissions 755 on it.
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
So today I woke up to my phone without magisk and all the apps I converted to system apps before. I presume somehow an OTA update happened while I was sleeping. I downloaded the latest Magisk (14.0) and reflashed it, got back root. I then proceed to attempt to convert apps back to system apps. That's when the problem surfaces. I try to move with 3 different system app movers. Two throw errors that /system cannot be mounted.
Link2SD error: 'mount:/dev/block/bootdevice/by-name/system'->'/system': Device or resource busy
/system/app mover error: Could not remount /system
I manage to manually move it with ES File Explorer in Root Mode. However, the app itself does not detect that it is now a system app despite setting the required permissions.
What gives? Do I need to wipe all data and restart?