Had stock rom 5.0.2, rooted, xposed framework installed, twrp.
I used the xposed framework uninstaller zip, full unroot from supersu, flashed stock recovery.
When I try to install the update I get the triangle exclamation thing, the following text:
Installing update...
Warning: No file_contextsL50QCT.01.102.010
Package expects build fingerprint of htc/sprint_wwe/m7wls:5.0.2/LRX22G/499067.6:user/release-keys or htc/sprint_wwe/m7wls:5.0.2/LRX22G/499067.7:user/release-keys: this device has htc/sprint_wwe/m7wls:4.1.2/JZO54K/166937.10:user/release-keys.
Installation aborted.
Thanks for any help!
EDIT: solved, see second post
Joshlul said:
Had stock rom 5.0.2, rooted, xposed framework installed, twrp.
I used the xposed framework uninstaller zip, full unroot from supersu, flashed stock recovery.
When I try to install the update I get the triangle exclamation thing, the following text:
Installing update...
Warning: No file_contextsL50QCT.01.102.010
Package expects build fingerprint of htc/sprint_wwe/m7wls:5.0.2/LRX22G/499067.6:user/release-keys or htc/sprint_wwe/m7wls:5.0.2/LRX22G/499067.7:user/release-keys: this device has htc/sprint_wwe/m7wls:4.1.2/JZO54K/166937.10:user/release-keys.
Installation aborted.
Thanks for any help!
Click to expand...
Click to collapse
I fixed it myself, I had flashed the recovery from the HTC one stock recovery thread but it was outdated, I extracted the recovery from this ZIP in this thread and everything went smoothly. I am s-off.
Easily flashed TWRP, then Xposed Framework and SuperSU zips after installing new OTA update, everything quite functional. Very pleased.
Related
Hey everyone
I've been using the XT1053 Retail US Stock Lollipop Flashable ZIP without issue for quite a while, but decided to update to the modded version 2. So I flashed it, xposed, and supersu again. Booted up, everything was okay. But then it said I needed to update my supersu binary and that I didn't have root, so I went to reboot into recovery and flash supersu once more.
However, now I can't access TWRP and it merely says "no command"
Should I just try installing TWRP again or is there a way to see if it's still installed? It's weird that this happened after flashing a rom
edit: reflashed twrp recovery img, back to normal. Can't explain what caused this though
Hi, everyone:
I'm newbie of xPosed framware. My device is Nexus6 with 6.0.1 android installed. According the guide line of installing the xPosed framework, I flashed the TWRP recovery. Now my device works well with xPosed framework. But one issue is that after I receiving the Android system update, and pressing install, then my Nexus6 ran the system update and rebooted. But after my device rebooting, it still showed that I need to install the same Android system update patch. So it means the installation failed. I assume is it because of flashing TWRP recovery? Am I assumption correct?
Based on my assumption, I wonder can I roll back to the Android default recovery image? According this, can my device normally install the system update, or even the future OTA?
Thanks!
newcarcrazy said:
Hi, everyone:
I'm newbie of xPosed framware. My device is Nexus6 with 6.0.1 android installed. According the guide line of installing the xPosed framework, I flashed the TWRP recovery. Now my device works well with xPosed framework. But one issue is that after I receiving the Android system update, and pressing install, then my Nexus6 ran the system update and rebooted. But after my device rebooting, it still showed that I need to install the same Android system update patch. So it means the installation failed. I assume is it because of flashing TWRP recovery? Am I assumption correct?
Based on my assumption, I wonder can I roll back to the Android default recovery image? According this, can my device normally install the system update, or even the future OTA?
Thanks!
Click to expand...
Click to collapse
In order for OTA to work, you have to be completely stock unrooted.
Sent from my SPH-A120
Since you have a Nexus device, you can skip the OTA and just install the factory image from https://developers.google.com/android/nexus/images#shamu. However, you may want to flash the partitions individually instead of using the script so you don't have to redo TWRP and such.
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!
Hi folks,
i hope i im the right Forum as it seams more a xposed as supersu problem.
I have a Moto X Style rooted with System-less SuperSU 2.78 and Xposed "xposed-v86.1-sdk23" by romracer, Stock ROM 6.0.
Just got a notification that there is a security update available, proceeded but won´t flash. Stops with Error Code 7.
I thought OTA would work with system-less.
Tried also with disable Xposed. Same result. By the way when the phone reboots for flashing it goes into The Recover TWRP 3.0.2 GUI. Anyway i saw the error when switching to the log view.
Any idea whats wrong or i miss?
May i have to restore custom recovery, and if so can i flash the stock recovery with the existing TWRP or do i have to go ADB?
Thanks
Thomas
You have to flash stock recovery image (and probably also boot image) for OTA to work.
Simply use fastboot to flash those. Leave system intact.
Thanks, will do so.
Hey folks
Just reloaded stock rom. Everything fresh. (Android 6)
Latest Magisk version not working when flashed in TWRP. Renamed APK to ZIP like I always do and get this error "
Updater process ended with error 1
Tried extracting the boot.img and flashing it to boot option on the flash image section of TWRP. Yes that flashed ok but i sitll get the same Magisk install error.
Any ideas?