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.
Hi guys,
sadly I'm not able to boot into my new OP3T after installing a few xposed modules (gravitybox, youtube adaway and minminguard).
TWRP install and rooting was done without any issues. Then I installed xposed and the modules, rebooted and was stuck at the animated logo with the red and white balls.
After that I tried restoring my backup that I did after installing TWRP but that didn't worked out. Now I'm stuck at the android logo screen and slowly getting depressed
Haven't found any solution in the other threads. Does someone pls have an idea? :crying:
best regards,
gekkoo7
Which one of OS you installed in OP3T ? OOS 4.01 ? Or OOS 3.5.4 ?
gekkoo7 said:
Hi guys,
sadly I'm not able to boot into my new OP3T after installing a few xposed modules (gravitybox, youtube adaway and minminguard).
TWRP install and rooting was done without any issues. Then I installed xposed and the modules, rebooted and was stuck at the animated logo with the red and white balls.
After that I tried restoring my backup that I did after installing TWRP but that didn't worked out. Now I'm stuck at the android logo screen and slowly getting depressed
Haven't found any solution in the other threads. Does someone pls have an idea? :crying:
best regards,
gekkoo7
Click to expand...
Click to collapse
assuming you have given up on trying to save the data, just wipe and do a clean install. the full zips are here on XDA. I would recommend going with the Blu_Spark TWRP as it saves you from having to jump thru the hoops of the official TWRP. I installed in and 4.0.1 last night in like 3 minutes flat.
https://forum.xda-developers.com/oneplus-3t/development/kernel-t3516012/page28
Thank you for the reply!
Currently I'm struggeling to get any data on to the phone as my phone is not listed with adb devices, so I can not push anything.
Installed the latest fastboot and adb version from Google.
Kris Chen said:
Which one of OS you installed in OP3T ? OOS 4.01 ? Or OOS 3.5.4 ?
Click to expand...
Click to collapse
did no change, therefore the version out of the box - 3.5.4
I suggest installing the full 3.5.4 OTA zip. It can be transferred to internal storage with TWRP. When you are in the recovery go to mount, mount USB storage to transfer the needed file.
Sent from my iPhone using Tapatalk Pro
worked - thanks a lot
I have a rooted Vodafone smart tab 3G (alcatel_OneTouch_I215X-2MVDEU1) tablet with Android 4.4.2 kitkat installed on it. I'm trying to use some xposed modules on it. I have successfully managed to install xposed and it's framework and reboot it. But after i install one module, and then reboot it again, my phone stucks in a boot loop until i restore the factory version of my phone/wiping all the data using recovery mode. How can i successfully install modules without getting stuck in a boot loop? I really want to use xposed modules.
*How to get past boot loop
So... was tired of some miscellaneous issues with 4.5.0 (rooted w/ Magisk, TWRP recovery) and decided to finally jump to 5.0. Failed initially in TWRP (was using stock 3.1.xx), moved to the OOS internal upgrade option, and actually managed to boot into 5.0 (albeit stock recovery and no root) after that succeeded.
Powered off, connected to PC, fastboot flashed TWRP 3.1.1 blu spark, rebooted into recovery, reflashed blue spark img, flashed OnePlus3TOxygen_28_OTA_060_all_1711160447.zip (went fine AFAIK, "script succeeded, 1.0000"). Cleared Dalvik/cache, flashed SuperSU v2.82... and this is where things got weird. First, flashing SuperSU failed once at the point of compressing the ramdisk. rebooted into TWRP, tried again, and it finished without error messages. Wiped Dalvik/cache once more and rebooted. This time, I got a permanent boot where my OP3T appeared to freeze at the first OP logo on a black background and would go no further even after 10+ minutes. Swapped out my SuperSU zip with a download straight from their website, same frozen boot. Redownloaded OTA_060_all, same thing. Wiped dalvik/cache/system before each attempt, no luck.
Gave up, fastboot -w, reflashed TWRP blu spark, and now even just drying to flash the plain OTA_060 zip results in a "no OS installed" when I try to reboot. When I try to flash either Magisk v15 or SuperSU 2.82, TWRP freezes entirely in the first steps, crashes to a white notification icon, and requires a long power button hold to reboot. I am lost at this point. AFAIK, my OP3T is basically a blank, wiped slate, and I've never experienced full-on TWRP freezes while flashing before blu spark.
In the meantime, I've installed OTA_057 (4.5.1) instead, thankfully without a bootloop, but fully wiped any suggestions?
I've jumped from Nougat to Oreo too. These are my steps: while on nougat open the TWRP recovery (stock TWRP); MAKE A COMPLETE BACKUP; updated it to the latest version (3.2.1.0.- if you have it installed then there's no need for this step); complete wipe; install the OTA using USB OTG; boot to system; run the first setup; (now TWRP might got overwritten just reboot to recovery, if it reboots to TWRP great, move on, if not then reboot to system and install TWRP using ADB); reboot to TWRP recovery; flash Magisk 15 (or SuperSU, but I don't use it so I can't say if it works); flash kernel if you want; reboot to system; check if Magisk/SuperSU works and that's it. At this point I've made another complete backup just in case I skrew up something in the future. Hope I helped! Good luck!
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Tagtag123 said:
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Click to expand...
Click to collapse
Yep, I believe that's exactly the version I tried I eventually just gave up after doing the complete device wipe through fastboot commands, am now running 5.0 with no problems but have the stock recovery and am not rooted :/ Now I just need to make a backup and then I can mess around and try and find a root method that doesn't basically soft brick my phone...
Even I am running OOS 5.0
The way I rooted is:
Flashed oos 5.0 using TWRP (https://forum.xda-developers.com/devdb/project/dl/?id=27381&task=get)
Boot normally
Reboot to TWRP, flash TWRP using fastboot if you find stock recovery. Then boot to TWRP.
After you in the TWRP recovery, flash superSU 2.82 SR5
Then flash suhide (it helps you hide root from apps which are a bit finicky about root).
This works for me.
SuperSU v2.82-SR5 flashable ZIP:
http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
suhide v1.09 flashable ZIP:
http://download.chainfire.eu/1219/suhide/UPDATE-suhide-v1.09-20171001222116.zip
I just followed these steps coming from rooted 4.5.1 and worked perfectly.
https://forums.oneplus.net/threads/guide-how-to-install-oos-5-0-over-rooted-4-5-1.684519/
Unleashed by my rooted OP3T in 8.0
Today I updated my magisk installation from v17.3 to v18.0 using the Magisk Manager app, I rebooted my phone and I'm stuck on the phone logo.
I can get into TWRP, from there I tried to reinstall v17.3 and also uninstall v18.00 but for both cases I get "unable to open boot image" followed by a red "Error 1" in TWRP.
I have a OnePlus Two, running stock MM rom from OnePlus. Never had a problem with Magisk, any tips on how to fix it?
It's not a bootloop, I think boot image is broken.
Thanks for your help
I managed to fix this by downloading the stock rom and flashing the boot.img file inside using TWRP, reflashed Magisk 18.0 without problems.