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
Related
SO i was running nook color version 1.1.0 and i used the autonooter to get clockwork installed. I then tried to use the monster rootpack to install phiremod but after it says install is complete i rebooted but now every time i reboot it goes directly to clockwork and i cant get it to boot up normally. is there anything i can do besides a restore to stock to install phiremod/cm7 or exit recovery? BTW i did remove the monster sd card so thats not the reason its booting that way....
When booted to CWR, use adb:
adb shell
Check that rom is mounted with:
mount
You should see /rom somewhere in the returned result.
If it's mounted, do:
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
If not:
mkdir /rom
mount /dev/block/mmcblk0p2 /rom
Then use previous command.
If that doesn't help, you can always flash my cwr remover .zip, found on my nook color restore to stock thread.
Sent from my HTC Desire using XDA App
thanks im going to try that right now.
So i am trying to run adb but it says device not found and i cant figure out how to get the device to mount
I had the same thing happen. In recovery, install the zip file in this post to remove recovery and keep it rooted. You will then be able to reboot normally.
http://forum.xda-developers.com/showthread.php?t=914690
I read that it does that with autonooter 3.0. What you need to do is reboot normally after flashing recovery (don't reboot into recovery immediately after flashing). Afterwards you can reboot into recovery.
Hello guys,
I had the same problem, but with Team Win Recovery
I tried to remove TWR folder in sdcard, wipe Cache, Dalvik cache and even factory reset.
I installed a new rom, and as last attempt i tried to wipe all system tree, but nothing happen.
I tried to fix following the list showed in this post, but I'm not able to mount "mmcblk0p2".
Any ideas? There is a TWR remover ?
Advance thank for helps.
krisslake said:
Hello guys,
I had the same problem, but with Team Win Recovery
I tried to remove TWR folder in sdcard, wipe Cache, Dalvik cache and even factory reset.
I installed a new rom, and as last attempt i tried to wipe all system tree, but nothing happen.
I tried to fix following the list showed in this post, but I'm not able to mount "mmcblk0p2".
Any ideas? There is a TWR remover ?
Advance thank for helps.
Click to expand...
Click to collapse
Not really sure what you are saying was your problem. But I have a lot of solutions to booting problems in my nook color tips thread linked in my signature. See items A8 and A12. And there is my partition repair thread.
Sent from my BNTV400 using Tapatalk
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.
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
Hi all, im here because i have some problem about install CyanogenMod of this tread:
http://forum.xda-developers.com/xpe.../rom-cyanogenmod-12-neo-s-homebuilds-t2984988
i hade a Xperia T, with 4.3 stock, with root, followed thsi http://forum.xda-developers.com/showthread.php?t=2798411=2333577
then i unlocked my botloader, following a italian guide by "Unlock SE xperia bootloaders", ask to Sony the hey for unclock, and all work fine.
Downloaded cm-12-20151108-NIGHTLY-mint with Gapps open_gapps-arm-5.1-pico-20160226, and pun in my microsd.
i have:
(1) Boot into TWRP recovery
(2) Do a factory reset and wipe system partition
(3) Flash latest ROM zip, but no Gapps (I'd do it later, first I wanted to see if it was loaded right to the Rom)
Reboot, configured cell phone, everything ok.
Then i try to follow step about resize partition, so i reboot phone, press "vol down", and my xperia boot into a "Cyanogen recovery", and not in the PhilZ Touch Recovery.
So I made some tests, and i have install TWRP by APK file, install ok, so i can go inside TWRP at the boot.
krasimiretov tell me to do that:
1. Install build from 08-01-2016(final)
2. You need to fastboot boot.img . There is no cyanogen recovery its TWRP. You must have done something wrong.
3. No towelroot is needed. After installing the build and flashing supersu from recovery phone is rooted.
4. You can do that with TWRP recovery no Philz needed.
so i have downloaded 08-01-2016(final), try to zip with TWRP but not able https://www.dropbox.com/s/n6do3ucbx8oju5a/2016-02-27 12.08.52.jpg?dl=0
i try to fastboot boot.img, by flashtool, istall it following this http://forum.xda-developers.com/showthread.php?t=1963961 but at the reboot xperia still "tunr off" afeter logo SONY, i should reboot (vol up+on for 10 sec, go to TWRP and reflash cm-12-20151108-NIGHTLY-mint for work again.
I am tempted to start all over from the beginning...but i shoud unlock again bootloaders, use unlocked bootloader, than i can, maybe, reflas ftf, right?
sorry if it's a little confused, but I do not know how to install the latest ROM, to be able to resize the partition
ok ..ok... i try again and now have work fine...
i just arrived to the Reboot, afetr install rom, gapps and update superSU, but screen is "stuck" at the recovery...is freeze there...i can reboot manually?
done!
redone the procedure,
I was wrong to flash the boot.img :angel:
So its working fine now ?
yep! work!!
but i have a little problem for resize...
13. Reboot
14. Enter the following terminal commands to fix storage permissions:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
say "su" not found:
/ # su
Sh: su: not found
Flash latest SuperSU from here: https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Did you flash that in TWRP ?
yea... anyway im trying again... (It has a bad sensitivity TWRP )
nothing... "SU" dont work, but T work without "problem" ... i just have some lag and some closing's applications...
and this error after rebooting:
https://www.dropbox.com/s/tb4p3oykwhwglof/unspecified.png?dl=0
i would like try the latest UNOFFICIAL by Neo ... where i can download it? its cm-12-20150405-UNOFFICIAL-mint ??
maybe better version 12
ok..i have try install cm-12-20150405-UNOFFICIAL-mint, replace boot.img with flashtool, twrp change version, like this https://upload.wikimedia.org/wikipedia/commons/f/fe/TWRP_2.7.0.0.png but when i try install the .zip, i received a error ... so i try to install the cm-12-20151108-NIGHTLY-mint, ok without error, but now ROM have loop on CM logo ...
nevermind... I was able to do everything alone ...
I do always panic
buti have always the messa
https://www.dropbox.com/s/tb4p3oykwhwglof/unspecified.png?dl=0ge
Its from the google apps. Why are you unstalling CM12 when there is more optimized and up to date CM12.1. And i write again. READ EVERYTHING IN OP CAREFULLY.
krasimiretov said:
Its from the google apps. Why are you unstalling CM12 when there is more optimized and up to date CM12.1. And i write again. READ EVERYTHING IN OP CAREFULLY.
Click to expand...
Click to collapse
i have unstalling the latest 12.1 (cm-12.1-20160108-UNOFFICIAL-mint.zip), and use Build CM12 UNOFFICIAL by Neo - 5/4/2015, because 12.1 was full of lag, and some app freeze and quite without message...
Now Xperia T is more fat without lag ...
Anyway i can install other 12.1 ... except the last one that is not working well ... what would you suggest me about, version 12.1?
Ok, i have try again with this version:
cm-12.1-20160108-UNOFFICIAL-mint
open_gapps-arm-5.1-pico-20160301
BETA-SuperSU-v2.68-20160228150503
Follow always the istruction:
Flash the boot.img from ROM zip via Flashtool (use Fastboot mode)
Boot into TWRP recovery
Do a factory reset and wipe system partition
Flash latest ROM zip (check "Downloads" section)
Flash suitable GApps for CM12.1 or CM12
Flash latest SuperSU from here: Link
Reboot
i have always the same message when boot the phone about SETTINGS
nosadello said:
i have always the same message when boot the phone about SETTINGS
Click to expand...
Click to collapse
We all have that message, that's bug about CM Theme, and It's nothing to worry about.
nosadello said:
yep! work!!
but i have a little problem for resize...
13. Reboot
14. Enter the following terminal commands to fix storage permissions:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
say "su" not found:
/ # su
Sh: su: not found
Click to expand...
Click to collapse
i should give this command on recovery or enable terminal on androd??
Hi,
I just installed Huawei P9 [ROM][6.0] fRomFuture - NewWorld V2 and the phone boots and works fine, but I cant update Su binary because of this error in TWRP ( I have unlocked bootloader and root):
failed to mount /data (Invalid argument)
Just clear the notification on each restart, don't try and update the SU Binary. It's a known issue
See the rom's thread
And re the TWRP issue, are you using the latest one from @paulobrien? 3.0.2.0 RC3?
colthekid said:
Just clear the notification on each restart, don't try and update the SU Binary. It's a known issue
See the rom's thread
And re the TWRP issue, are you using the latest one from @paulobrien? 3.0.2.0 RC3?
Click to expand...
Click to collapse
Thank you, nope I was using the one from SRK TOOL. Do you know how to install TWRP via Paul, its a img file (i'll have a hunt for his copy)
In twrp, go install, choose install image, choose file, select partition recovery and done
Other method with pc-fastboot command -> fastboot flash recovery blabla.img this method need root with stock rom. Custom roms already rooted so dont worry
Milamber said:
Thank you, nope I was using the one from SRK TOOL. Do you know how to install TWRP via Paul, its a img file (i'll have a hunt for his copy)
Click to expand...
Click to collapse
Don't know if the Tool is using the latest version. Paul's is here ... http://forum.xda-developers.com/p9/development/wip-twrp-support-t3372331 still has some issues backing up, but best we have at the mo.
you can either flash as @master' suggests or via adb
adb reboot-bootloader
fastboot flash recovery twrp-3.0.2-0-eva-modaco-rc3.img
fastboot reboot
edit: beaten to it! :highfive:
colthekid said:
Don't know if the Tool is using the latest version. Paul's is here ... http://forum.xda-developers.com/p9/development/wip-twrp-support-t3372331 still has some issues backing up, but best we have at the mo.
you can either flash as @master' suggests or via adb
adb reboot-bootloader
fastboot flash recovery twrp-3.0.2-0-eva-modaco-rc3.img
fastboot reboot
edit: beaten to it! :highfive:
Click to expand...
Click to collapse
Thanks to both of you from Australia!
Hi. when I try backup system ihad message : "createTarFork () process ended with error :255"
What`s wrong?
Last messages from log
I:addFile '/data/hw_init/system/emui' including root: 0
==> set selinux context: ubject_r:system_data_file:s0
I:addFile '/data/hw_init/system/emui/base' including root: 0
I:Error adding file '/data/hw_init/system/emui/base' to '/external_sd/TWRP/BACKUPS/MWS0216C19000719/2017-03-15--12-38-32//data.f2fs.win'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/MWS0216C19000719/2017-03-15--12-38-32/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup
Click to expand...
Click to collapse
ok. I changed SD card ,formated it in phone and did backup by TWRP-3.0.2-0-eva. Now I think all done good. Last question is what about this red alert at the end of log?
Unmounting main partitions...
Failed to unmount '/system' (Device or resource busy)
Click to expand...
Click to collapse