Hey guys, so I was running 3.2.8 firmware and modem (marshmallow) with latest AOKP stable (not nightly) nougat rom and things were working as they should...
Now the official 4.0 nougat oneplus oxygen rom comes out and I'd figure it's time for an update... So I do a clean install of oxygen 4.0, boot into system, and then flash twrp-3.0.2-1.28 recovery to flash aokp nougat rom.
After that I flash latest stable SuperSU 2.79, reboot and then boot back again to install Adaway systemless v2 zip
Problem is, my phone randomly un roots itself, busybox app would freeze (had to flash it through TWRP later) and Adaway won't merge hosts file.
I know it probably has to do with either latest root, the recovery, encryption/decryption, or firmware (or combination of some of these) from what I've read on the forums...
Can anybody tell me what is causing these problems and help me fix this?
I've tried installing twrp-3.0.2-0_blu_spark_v11 recovery, version 19 of bluspark's modified TWRP, and SuperSU 2.79 sr2 but I still can't get Adaway to work and system keeps unrooting...
Is it bc I have to keep the system read only in recovery? Update my partitions to f2fs? Do I need to encrypt/decrypt my device?
Related
So I was on rooted 3.2.6 with xposed installed and decided to upgrade to 3.2.8.
I dirty flashed the full ROM 3.2.8 onto my 3.2.6 (without flashing SU or xposed because I wanted to use Snapchat with snapprefs again so I i flashed 3.2.8 without root , logged into Snapchat etc. )
after that I flashed superuser and xposed and since then my phone doesnt boot.
I interrupted the first try because it took over 20 minutes then tried it again after clearing cache and dalvik but it still doesnt boot ( i see the two circles and red dot)
Hope someone can help me
PS: I didnt make a backup because it would be too large, on the other hand I have the full 3.2.8 on my internal storage as well as the latest superSU
solved it
If someone experiences the same problem you need the newest xposed version v87. Flash it normally and wipe cache/dalvik , thats it !
I had that, I fixed it by boot to twrp flash the xposed uninstaller zip to remove xposed, then the phone should boot normally, I then found a newer version of xposed (the November security patch in 3.2.8 doesn't like older versions) and flashed it via twrp again, all my modules were still there and didn't need setting up again either.
Hope that helps
J_The_Nerd said:
I had that, I fixed it by boot to twrp flash the xposed uninstaller zip to remove xposed, then the phone should boot normally, I then found a newer version of xposed (the November security patch in 3.2.8 doesn't like older versions) and flashed it via twrp again, all my modules were still there and didn't need setting up again either.
Hope that helps
Click to expand...
Click to collapse
thats exactly what I did and it works perfectly now. Thanks.
Im running stock ROM 7.1.1 with Latest ElementalX Kernel and latest Magisk + MagiskSU. Also Running latest TWRP 3.1
I haven't updated yet. so I have the march patch, and this recent patch im behind on my 5x. I thought maybe i could just accept the OTA and just reflash magisk and the elementalX kernel afterwards. Oh, and likely would have to do TWRP as well. But accepting the update clicking to restart and install just rebooted me into TWRP. Flashfire doesn't work yet either been waiting a month on that. I get that failure during "uncrypting" error.
I'm slightly new back on the modding scene, until recently have been out of it for years. I did recently make a mistake with an audio mode and had to download the full image and use fastboot to throw that back on my device. Anyway with 7.1.2 out i really do want to update so i need to do it manually, and hopefully without losing my data. (or having to restore it from a backup if possible anyway)
I'd read somewhere that you can download the full images and extract the updated images you need and flash them to your device then your respective addons root kernel ect.. There seems to be lots of way to go about it, but little clear on how to do this so that's what brings me here to this post. What's the best way to manually update (add security patches) if im running Magisk and magiskSU.
Thanks in Advance.
https://elementalx.org/how-to-install-android-monthly-security-updates/
After you flash the /system /boot /vendor (I would also do bootloader and radio), reboot into TWRP and install kernel & Magisk.
As the title says I am unable to boot after flashing Magisk (tried v16 and v15.3). It boots fine without magisk but of course no root and no custom recovery. Any help would be appreciated. Didn't have any problems on the previous stable build.
You need to first flash OOS 5.1 let it boot, then go to fastboot and flash twrp then go to twrp and flash magisk, only way to get root
hello, that's what I did and it worked well
this has happened here since 5.0.4
Try to use lastest blu-spark's TWRP, then flash 5.1 & Magisk without extra boot in the middle.
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
ToucanSam said:
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
Click to expand...
Click to collapse
It's not broken. The vendor error message is because it was recently updated to work better with Project treble, which uses a hidden partition for the vendor. You can simply ignore the error and it will work fine. Or if you flash a treble ROM, the error will then go away.
I just got the phone. Format it in recovery.
Flash latest blu spark twrp (v.8.73).
Flash the Oos ob06.
Reboot to system. Set the phone, instal apps from Play.
Reboot to Fastboot.
Reflash recovery.
Reboot to recovery.
Flash Magisk 15.3. Reboot to system. OK.
Updated Magisk with Magisk.
Hi, Can anyone help me. in my oneplus 5T after installing new rom it is working smooth but i can't upgrade to new updates. in recovery mode the files seems to be decrypted and cant find any folders where i copied the updation . instead new files are found and can't access and find any of the folders of my own. this happened after i input the security lock. i wiped the entire data and installed new roms still it seems so. somebody please help me to find a solution for this
Hello everyone,
I have the Xiaomi Redmi 5A.
Currently I am running Official Pixel Experience ROM (8.1.0, oreo) https://forum.xda-developers.com/xiaomi-redmi-5a/development/rom-pixel-experience-t3801702 on it. It so happens that when I try to flash SuperSU latest zip, the flashing goes fine but the device doesn't get rooted on checking in a root checker app and also no SuperSU app comes in the app drawer after flashing. I am not sure why this happens. But flashing magisk roots the device. Why not SuperSU?
In the Pixel Experience ROM thread they told to use vendor TWRP and not the Official TWRP but even on vendor TWRP I don't get root access after flashing SuperSU...
Previously I was using Unofficial Lineage OS (14.1, nougat) https://forum.xda-developers.com/xi.../unofficial-lineage-os-14-1-redmi-5a-t3773985 on my device. In Lineage OS when I flash SuperSU I get root access and also the SuperSU app comes in the app drawer. Why not in Pixel Experience?
Is the kernel responsible for this?
Is it something related to "mount"?
I come across this "mount" word in TWRP but I'm not sure what does this mean...
In TWRP while flashing SuperSU I saw "ramdisk restore failed, aborting". What does that mean?
Also is it related to SuperSU being a system-less root software and magisk being a system-based one?
Please help me... It's driving me nuts!:crying:
P.S. I know magisk is better but I want SuperSU, so don't suggest me to use magisk and forget SuperSU.:laugh:
Thanks.
Shakti Panda said:
Hello everyone,
I have the Xiaomi Redmi 5A.
Currently I am running Official Pixel Experience ROM (8.1.0, oreo) https://forum.xda-developers.com/xiaomi-redmi-5a/development/rom-pixel-experience-t3801702 on it. It so happens that when I try to flash SuperSU latest zip, the flashing goes fine but the device doesn't get rooted on checking in a root checker app and also no SuperSU app comes in the app drawer after flashing. I am not sure why this happens. But flashing magisk roots the device. Why not SuperSU?
In the Pixel Experience ROM thread they told to use vendor TWRP and not the Official TWRP but even on vendor TWRP I don't get root access after flashing SuperSU...
Previously I was using Unofficial Lineage OS (14.1, nougat) https://forum.xda-developers.com/xi.../unofficial-lineage-os-14-1-redmi-5a-t3773985 on my device. In Lineage OS when I flash SuperSU I get root access and also the SuperSU app comes in the app drawer. Why not in Pixel Experience?
Is the kernel responsible for this?
Is it something related to "mount"?
I come across this "mount" word in TWRP but I'm not sure what does this mean...
In TWRP while flashing SuperSU I saw "ramdisk restore failed, aborting". What does that mean?
Also is it related to SuperSU being a system-less root software and magisk being a system-based one?
Please help me... It's driving me nuts!:crying:
P.S. I know magisk is better but I want SuperSU, so don't suggest me to use magisk and forget SuperSU.:laugh:
Thanks.
Click to expand...
Click to collapse
Hello,
I don't know exactly what you are encountering but SuperSU should work on this ROM and run fine. I ran this ROM before and SuperSU works fine. I now switched to Magisk because I need ViPER4Android to work on Oreo.
Unless you are running a Treble based ROM, that is a different story. If you are running a Treble based ROM, please refer to this https://forum.xda-developers.com/showpost.php?p=76937637&postcount=24 thread to get root working.
CONTINUE TO READ IF YOU ARE NOT RUNNING A TREBLE BASED ROM,
I need to get some things straight. Android with version 6.0 (Marshmallow) and above (should) and (only) run systemless mode (including SuperSU). I came across a thread and read that root with Marshmallow and above would not work without patching bootloader and make system unmodified.
SuperSU and Magisk are almost the same. Magisk just offers extra module repository and SuperSU just offers root. SuperSU works both in system mode and systemless mode but Magisk only works in systemless mode.
This might help you:
- Do a clean flash (Wipe System, Data and Cache)
- Try using this latest version of SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (SuperSU v2.82 SR5 released by Chainfire himself)
- If it doesn't work then something might be wrong with the boot partition.
- If you really need root and SuperSU REALLY DOESN'T WORK, (spoiler) try Magisk...
Growtopia Jaw said:
Hello,
I don't know exactly what you are encountering but SuperSU should work on this ROM and run fine. I ran this ROM before and SuperSU works fine. I now switched to Magisk because I need ViPER4Android to work on Oreo.
Unless you are running a Treble based ROM, that is a different story. If you are running a Treble based ROM, please refer to this https://forum.xda-developers.com/showpost.php?p=76937637&postcount=24 thread to get root working.
CONTINUE TO READ IF YOU ARE NOT RUNNING A TREBLE BASED ROM,
I need to get some things straight. Android with version 6.0 (Marshmallow) and above (should) and (only) run systemless mode (including SuperSU). I came across a thread and read that root with Marshmallow and above would not work without patching bootloader and make system unmodified.
SuperSU and Magisk are almost the same. Magisk just offers extra module repository and SuperSU just offers root. SuperSU works both in system mode and systemless mode but Magisk only works in systemless mode.
This might help you:
- Do a clean flash (Wipe System, Data and Cache)
- Try using this latest version of SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (SuperSU v2.82 SR5 released by Chainfire himself)
- If it doesn't work then something might be wrong with the boot partition.
- If you really need root and SuperSU REALLY DOESN'T WORK, (spoiler) try Magisk...
Click to expand...
Click to collapse
Thanks man.
I'll try that for sure but later i.e., doing a clean flash and trying to flash SuperSU again...
I'll let you know once I've done that.
Thanks again man!!!:angel:
Shakti Panda said:
Thanks man.
I'll try that for sure but later i.e., doing a clean flash and trying to flash SuperSU again...
I'll let you know once I've done that.
Thanks again man!!!:angel:
Click to expand...
Click to collapse
Sure, no problem
[HELP] Get stuck in bootanimation &then only boot to TWRP after upgrade Magisk & TWRP
I have sucessfully rooted my phone but yesterday when i upgraded Magisk from 16.4 to 17.1 and then flashed lasted TWRP, my phone some how corrupted .
After that I tried to flash Factory Image and boot TWRP portable -> Flash ElementalX 2.05 -> Magisk 17.1 -> VerifiedBootSigner-v8 -> Reboot but my phone get stuck in bootanimation about 5 min and then reboot to recovery. Then it will always boot back to recovery when I reboot.
I have searched here but couldn't find any solution.
I tried to flash ElementalX and TWRP only and my phone booting normally. But anytime I flash Magisk it can't.
Please help me, I don't know what to do next, Thank you and sorry for my bad English. :crying:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Cozmikk said:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Click to expand...
Click to collapse
What version of TWRP did you use?