Error in xposed - Lenovo Vibe P1 Guides, News, & Discussion

While I install xposed I get this error!
Even in recovery!
How I could fix it?

@keshow
I solved this problem only with magisk. My problem was related to twrp backup. When I restore, I can not write to the system.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

Fatih Firinci said:
@keshow
I solved this problem only with magisk. My problem was related to twrp backup. When I restore, I can not write to the system.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Click to expand...
Click to collapse
many thanks :good:

Related

[Q] TWRP restore problem

Hi i have silly problem with TWRP,
when i restore user data it works good, but if i want restoree system partition all works ok, but after reeboot phone always bootloop into recorvery, cant boot.
I must reflash via flashtools everything without user data to boot phone again (and install su etc via twrp)
Paweł
dromaczek said:
Hi i have silly problem with TWRP,
when i restore user data it works good, but if i want restoree system partition all works ok, but after reeboot phone always bootloop into recorvery, cant boot.
I must reflash via flashtools everything without user data to boot phone again (and install su etc via twrp)
Paweł
Click to expand...
Click to collapse
Just checking : do you wipe dalvik cache and cache partitions in TWRP?
Which TWRP do you use?
Nofan Tasi said:
Just checking : do you wipe dalvik cache and cache partitions in TWRP?
Which TWRP do you use?
Click to expand...
Click to collapse
I use TWRP from needrom jiaju s3 newest kitkat,
24.06.2015: Update Official ROM JIAYU S3 Version: S3S-20150623-142703
http://www.needrom.com/download/s3-lollipop-v5-1/
wipe dont solve problem
dromaczek said:
I use TWRP from needrom jiaju s3 newest kitkat,
24.06.2015: Update Official ROM JIAYU S3 Version: S3S-20150623-142703
http://www.needrom.com/download/s3-lollipop-v5-1/
wipe dont solve problem
Click to expand...
Click to collapse
I never tried LP yet but I guess one needs a LP TWRP for a LP ROM. Maybe someone else can help.
Problem solved, new TWRP version install and everything is ok
dromaczek said:
Problem solved, new TWRP version install and everything is ok
Click to expand...
Click to collapse
All right then! would you mind mentioning which new TWRP you installed?
Nofan Tasi said:
All right then! would you mind mentioning which new TWRP you installed?
Click to expand...
Click to collapse
https://onedrive.live.com/redir?resid=4E99B011246D904C!98350&authkey=!ACU2JTmbVHGDLrM&ithint=file,7z

Accidentally formatted /system partition. Busybox not working

I was facing an issue with a custom rom and tried to do data wipe with twrp.
But accidentally I selected /system partition also and wiped that. Not sure if this is the problem or not, but since then few apps are not working. Titanium backup is showing phone is not rooted (I tried the workaround of force sys/bin and it worked for a while). Busybox showing that phone is not rooted.
I am fed up with all these errors.
Please help me solve this. I am using SM-N900 (Exynos) Galaxy Note 3.
If you want root, flash supersu from twrp.
Akhyll said:
I was facing an issue with a custom rom and tried to do data wipe with twrp.
But accidentally I selected /system partition also and wiped that. Not sure if this is the problem or not, but since then few apps are not working. Titanium backup is showing phone is not rooted (I tried the workaround of force sys/bin and it worked for a while). Busybox showing that phone is not rooted.
I am fed up with all these errors.
Please help me solve this. I am using SM-N900 (Exynos) Galaxy Note 3.
Click to expand...
Click to collapse
Re-install "Root" and install "CWM Recovery" then flash busybox or download from Google Play
audit13 said:
If you want root, flash supersu from twrp.
Click to expand...
Click to collapse
dalisoft said:
Re-install "Root" and install "CWM Recovery" then flash busybox or download from Google Play
Click to expand...
Click to collapse
still didn't work

"can't mount system" (structure needs to be clean)

Hi everybody, since i restore my nandroid backup (to revert xxx rom to stock), it is impossible to mount system partition... and recovery twrp 3.1.1.1 say "can't mount system (structure needs to be clean..). How to solve this problem? Please i need help
edit: problem solved with an internal install of OOS... and after must reflash twrp and root
@brunsman6229 Could you tell me how exactly you solved the issue? Getting the same error and would like to know how to fix it!
brunsman6229 said:
edit: problem solved with an internal install of OOS... and after must reflash twrp and root
Click to expand...
Click to collapse
Hey, can you plss guide me through this. What is internal installation?
Will all of my data be wiped??
I fixed it by dirty flashing No limits rom. If you have a nandroid backup in hand, wipe everything except internal storage, dirty flash the rom then restore the nandroid backup.

Oneplus 5 shutting down after the OTA

Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Dr4In said:
Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Click to expand...
Click to collapse
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
strongst said:
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
Click to expand...
Click to collapse
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Dr4In said:
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Click to expand...
Click to collapse
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
strongst said:
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
Click to expand...
Click to collapse
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Dr4In said:
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Click to expand...
Click to collapse
If you mean your encrypted twrp of your internal storage = no.
I would start from scratch with decrypted.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I used this and solved the problem
I was facing to the same problem today, and the problem was the Magisk version! Same problem for Pixel 3/XL users...
The way you can fix it: Install v19.1 BETA (not the stable)! It should boot up!

[HELP] extracttarfork() process ended with error=255 - when i restore data via TWRP

Hi everyone, I have problems recovering data with TWRP - "extracttarfork() process ended with error=255"
How to fix it?
i worked on TWRP v3.3.1-4 Miui.gr version
I got the same problem... I did't find the solution. Can someone help ?
k1n9n0th1n9 said:
Hi everyone, I have problems recovering data with TWRP - "extracttarfork() process ended with error=255"
How to fix it?
i worked on TWRP v3.3.1-4 Miui.gr version
Click to expand...
Click to collapse
I had it too with many devices.
It really depends, some times, the TWRP can't access the partition it want to write. Other times, one file of the backup is corrupted (so it halt).
Try to change TWRP, mount the system partition and check. If it don't work.. i would say that you wont be able to fix with that backup in particular.
Try to make a new backup too, and restore from it to see if with the new backup, the problem persist.
Pupet_Master said:
I had it too with many devices.
It really depends, some times, the TWRP can't access the partition it want to write. Other times, one file of the backup is corrupted (so it halt).
Try to change TWRP, mount the system partition and check. If it don't work.. i would say that you wont be able to fix with that backup in particular.
Try to make a new backup too, and restore from it to see if with the new backup, the problem persist.
Click to expand...
Click to collapse
hi, I had this, try doing the partitions separate, I did data afterwards following a reboot.
Try OrangeFox-R10.0_8-Stable-davinci recovery.
flamedrops said:
Try OrangeFox-R10.0_8-Stable-davinci recovery.
Click to expand...
Click to collapse
Orange fox atm is the worse and most buggy recovery for K20
Pupet_Master said:
Orange fox atm is the worse and most buggy recovery for K20
Click to expand...
Click to collapse
even the latest one?
flamedrops said:
even the latest one?
Click to expand...
Click to collapse
Yeap, it is still in it's infancy, where other TWRPs solved some issues that even the latest OF still has
I have just made a new backup after restore from Titanium Backup, but after flash new firmware and test some new roms, some of apps were crushing after restore and must be installed and configured one again.

Categories

Resources