Database Develop

Bootloop after flashing Xposed Framework

Hi, I'm pretty sure I flashed the correct Xposed, but then it started to bootloop and I had the option to "Download and recovery",
So now I'm downloading.
Any other solution?

Boot to recovery and flash Xposed uninstaller. If you try to install Xposed again make sure you choose correct version. You need "xposed-v85.1-sdk23-arm64-custom-build-by-wanam-20160530".

yiftach said:
Hi, I'm pretty sure I flashed the correct Xposed, but then it started to bootloop and I had the option to "Download and recovery",
So now I'm downloading.
Any other solution?
Click to expand...
Click to collapse
I bought this phone yesterday. I could never start using a device unless I unlock bootloader, root and install xposed. I managed to unlock bootloader, flashed TWRP and also flashed systemless SuperSu (2.74-2). Also, I installed systemless xposed (i have shared link below). Phone took sometime and making me to think it is stuck in bootloader. I switched off and start in TWRP. Wiped art/dalvik and cache. Restarted normally. Everything worked fine.
Someone suggested here how to install official xposed (http://newesc.com/es/instalar-xposed-huawei-p9/).
But I installed systemless xposed (see here: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268) which works fine without the need of any changes in /system/emui/base/prop/local.pro with this line "ro.config.hwtheme=1" as mentioned in the link I shared above.

Thank you guys!

Bootloop after supersu binary update

Pretty much as in the title. I believe it was on the dualrecovery root for 5.1.1 and the latest supersu binary update just dropped it into a bootloop. What do I do now?

Same issue here... Don't know what to do!

Welp factory reset in both recoveries didn't do anything.

Seems that manually flashing the 2.81 supersu zip worked for me.

Yep I posted a workaround in the superSU thread a couple of days ago. Flashing the zip version from TWRP works and fixes the bootloop.

i have the same issue and i am not know with this flash stuff
what should i do can some one explain to me

same problem anyone plz post the step to fix this

s2nabil said:
same problem anyone plz post the step to fix this
Click to expand...
Click to collapse
Boot into TWRP recovery and install SuperSu 2.79 zip from ChainFire or his latest v2.82 linked below that supposedly fixes the issue with bootloop on Xperia devices.
https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Thread discussing the problems and solutions.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1019

The last SuperSU 2.82 from 28.05.2017 working fine ... at last

Rebel2k said:
Same issue here... Don't know what to do!
Click to expand...
Click to collapse
Same problem but my computer wont recognise my phone & will only charge my phone I bought a new cable aswell still will only charge, Someone if any idea please help be appreciated.

Did you try to start in recovery with your phone, run the TWRP file manager and plug your phone? Don't you get access to the phone file system?

EQ2000 said:
Boot into TWRP recovery and install SuperSu 2.79 zip from ChainFire or his latest v2.82 linked below that supposedly fixes the issue with bootloop on Xperia devices.
https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Thread discussing the problems and solutions.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1019
Click to expand...
Click to collapse
https://download.chainfire.eu/1113/S...0528234214.zip
v2.82 updated work fine for me, thank u

EQ2000 said:
Boot into TWRP recovery and install SuperSu 2.79 zip from ChainFire or his latest v2.82 linked below that supposedly fixes the issue with bootloop on Xperia devices.
https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Thread discussing the problems and solutions.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1019
Click to expand...
Click to collapse
I was able to solve the boot loop problem with your advice but now the SuperSU icon is disappeared
Any idea how to bring it back?

so I had the exact same problem......supersu asked for an update and that caused a boot loop on my Z1c
I reflashed supersu using recovery,
First v2.82 << that did NOT fix the boot loop
Then v2.79 << this fixed the boot loop.
However, I left the phone to charge for a few minutes and supersu auto updated. Now it says it is v2.82 inside the supersu app. The app still keeps nagging about an update.......which I am not installing, fearing it will cause the boot loop again

Fix
Try to flash supersu.zip in twrp it's works on me

I also as many other users here have updated the library of super Su (got the
notification). And after the installation and rebooting got into the booting loop.
I have wiped cache and dalvick cashe with TWRP but it didn't help. I installed the
2.82 Update-SuperSu via TWRP. And after the long time of apps optimization I was
able to boot into the Android (Lollipop 5.1). However, I found the root was lost.
The RootChecker saying: "Root access is not properly installed on this device".
So, basically my question is how to restore the root and keep the bootloader locked
(important!)
Here I see several scenarios:
1. Restore using TWRP backup.
Should I wipe cache, dalvik cache and data before and after the restore?
2. install Update_SuperSU 2.79 or 2.76 (originally I have version 2.76)
Should I wipe cache, dalvik cache and data before and after the installation?
3. Flash with pre-rooted ROM.
Should I wipe cache, dalvik cache and data before and after the installation?
4. Start from zero, i.e to follow the procedure I have rooted the phone at time
I've purchased it. Namely:
4.1 Downgrade to KitKat
4.2 Root with FlashTool.
4.3 Flash prerooted Lollipop rom with TWRP
4.4 Flash with customized Lollipop rom
Xperia Z3c (compact)
Lollipop 5.1.1
I would appreciate for your suggestions.

TWRP gets replaced by stock recovery

So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks

Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?

Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).

gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867

pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.

pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.

gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.

Magisk bootloop from xposed

I have LLD-L31(C432) and a while ago I went through the process of unlocking bootloader and flashing magisk. I did this without custom recovery as it caused problems but it worked and I had magisk and root fully working. However, I think I tried to install a version of xposed that was incompatible with my os (EMUI 9). This caused bootloop every time I tried to boot into recovery(system with magisk).
I can still use the device but some apps can still see xposed and won't work. I can try to boot into the system with magisk but it loops - maybe because of xposed.
I have seen that you can flash xposed uninstaller, will this wipe data and will it work? Or is there a way to remove it and get magisk back without loss of data.
Alternatively (if this option results in a more stable magisk installation),could I flash twrp to recovery and then flash magisk to my system boot to have magisk permanently? and will this method wipe data?
Edit: I flashed twrp to recovery but when I boot to it, it just loads fastboot with reason bootloader 1 any help?
Thanks

MI 9 in bootloop

Hi!
I have pushed my MI 9 into bootloop and need help to get it back working.
The bootloader is unlocked, Magisk and TWRP are installed. I tried to install the latest Universal SafetyNet Fix, but instead of installing it inside Magisk I have "installed" the ZIP with TWRP and wiped the delvik cache. Now the phone is in bootloop.
In the Universal SafetyNet Fix- threat I got the hint to reinstall the stock boot.img, but I am unsure how to do this and which file to use.
Can I just use one of the boot.img linked in this threat, e.g., the one in 10.2.24.0?
[Root images] Boot 10.2.24.0 & 10.2.9.0 & 10.2.26.0
Version 10.2.26.0 Version 10.2.24.0 ------------ > Stock/Root Version 10.2.9.0
forum.xda-developers.com
and install it with fastboot, i.e., "Fastboot flash boot.img" ?
Or is there another solution to my problem, e.g., uninstall the safetynet-fix-v1.1.0.zip ?

Well, I gave it a try, but it doesn't work. Now the phone doesn't even show the MIUI logo anymore. Fortunately, I had made a backup with TWRP before I tried this, and I could reflash the old boot.img with
fastboot flash boot boot.emmc.win
Now at least the MIUI logo appears again, but my original problem is still there, the phone still doesn't boot completely, but resets and goes into twrp.

Problem solved by deleting the safetynet-fix folder. Thanks to Durete for this tip!
How to Uninstall Magisk Modules Using TWRP Recovery
Removing the Magisk module manually causes bootloop. You can easily uninstall Magisk modules using TWRP recovery without resetting your device.
www.droidviews.com
Durete said:
The easy way....
How to Uninstall Magisk Modules Using TWRP Recovery | DroidViews
Click to expand...
Click to collapse