So I've seen a few threads asking a similar thing but since they're quite old, I'd like to ask again.
Quick info about my setup:
running stock ROM, MOB30H
system-less root
system-less Xposed
kernel: ElementalX
TWRP recovery
I was hoping I'll be able to install OTAs with less hassle thanks to up-to-date SuperSU and a special version of Xposed. I indeed have received an OTA today - a small update, I believe 9 MB. When I tried to install it though, TWRP booted up and nothing happened.
Does someone run a similar setup? Have you been able to install an OTA after flashing stock recovery (which I guess is what needs to be done to install OTAs)? Would I have to reflash SuperSU and/or Xposed?
Related
Hi,
I unlocked My bootloader successfully and installed twrp. Everythings fine so far.
Now I saw a thread mentioning a rollback to stock 6.0.0 is neccessary before installing cm13 because of the baseband. Do I still have to do that?
I also read about supersu. Do I have to install it before cm? In a rooted device? I thought supersu is for rooting the device?
And finally I thought cm13 is stable for My A9 but there are only nightly builds. Recommended for daily use?
Sry for all those noob questions, but I already read around for hours, without coming to a solution. Although flashing cm to My S5 Mini was alot easier.
I appreciate any help with that stuff.
?
Btw. I saw the supersu Thread and I found instructions on how to root the device.
The Instruction says I have to install supersu to root the device. In the supersu thread they say my device has to be rooted to install supersu.
Confusion is complete
On all devices I've had, never had to root (SuperSU) to install CyanogenMod. Just unlock bootloader and install twrp.
The SuperSU thread is wrong, I read the same thing when I had a nexus 5. I think it means just bootloader needs to be unlocked.
Only time I used SuperSU was if I was on stock rom. CM13 has root built in. Enable it in developer options.
As far as having to downgrade to 6.0, no idea if it's still needed. It's one of the reasons I'm still on stock. I don't like methods needed to downgrade.
thx
Thanks for your reply.
I installed CM13 nightly successfully on my A9.
No Rollback neccessary.
itsabrick said:
Thanks for your reply.
I installed CM13 nightly successfully on my A9.
No Rollback neccessary.
Click to expand...
Click to collapse
Really? Your phone had latest stock update and you installed cm13, and have no issues with it? No boot loops?
I've been using cm for some days. Some apps a crashing once a while, voice recording in whatsapp doesnt work without crashing the APP. AS far as I use My phone it is fine.
I booted the phone two times since I installed cm and no bootloops.
Bought it in germany.
Edit: Don't know it was the latest stock. I left the Version that was already installed on the phone. AS far as I remember it was 6.0.1
(Not sure if it is better to make a new thread or ask in the SuperSU thread...)
Hey all. I had previously been running the 7.1 OTA build with SuperSU installed. It seemed fine and I had done OTA updates with it installed with little issue. This was pre-2.78 SR3 builds of SuperSU, so I was using the boot-to-root. One day, I inexplicably noticed that root was gone. App too. I was very confused because to the best of my knowledge no OTA updates or security updates happened since I last rooted.
With that, I decided to sideload update to NMF26Q, which apparently was released about 12 hours earlier, and install TWRP since it was needed for newer SuperSU. TWRP installed fine and worked, but SuperSU did not seem to work. In fact, every time I attempted to flash SuperSU 2.78 SR5, I noticed it would remove the SuperSU app if it was installed via the Play Store. Finally, I noticed that it was installing in System mode.
I attempted to override this by running `echo "SYSTEMLESS=true" >> /data/.supersu`, but nothing I did worked. It did the same exact thing. Looking through the shell script, I'm entirely unsure how it is possible that my override did not work. I also reflashed the stock boot image to both slots and then reinstalled TWRP. This had no effect on installing SuperSU.
I try to do due diligence before turning to the internet for help, but I don't have any clue what's going on here. Maybe it is best if i reflash the entire stock ROM, but I'd love to avoid that if possible, as everything else seems to work great, and I have no idea why this in particular would be an issue.
Use alpha 2 of twrp and ask will be well
Yep, that worked great. Cheers.
http://forum.xda-developers.com/showpost.php?p=69626115&postcount=2
Spend whole day browsing XDA, still can't get the thing done.
Running stock Nougat 39.2.A.0.361 with unlocked bootloaders and TWRP 3.0.2.0. Downloaded SuperSU 2.79, booted into recovery and flashed SuperSU. No errors, just a success message. However, after rebooting the phone, no sign of SuperSU exists. Flashtool also indicates root access is denied.
When installing custom ROM with SuperSU integrated ( http://forum.xda-developers.com/xperia-xz/development/rom-romaur-v1-0-fast-stable-t3486874 ) root works perfectly. Once custom ROM is installed, SuperSu icon is displayed and root access is OK.
I read that this problem might be because of incompatible kernel? I installed custom kernel (which was attached to RomAur - Stock_Kernel_f8331_fw.327-DRM FIX) before installing custom ROM, but I guess that re-flashing stock ROM later (using Flashtool) restored original kernel as well? If so, what exactly do I need to do in order to have rooted stock Nougat? Just flash some custom kernel (which one exactly?) and try flashing SuperSU again? Really don't want to brick anything.
P.S. Current kernel - 3.18.31-perf-g6af3ae9
if you are on stock nougat,
flash androplus kernel v18 from here:
https://kernel.andro.plus/tone2.html
after that,
flash supersu 2.78.
Thanks, will try. Is there any reason why using SuperSU 2.78 is needed? I see the latest one is 2.79?
manxp85 said:
Is there any reason why using SuperSU 2.78 is needed?
Click to expand...
Click to collapse
No - mine is running fine on 2.79SR1
BTW:
With stock kernel DM_Verity is ON
That detects any modification (e.g. installing SuperSU) in the non-USERDATA partitions via comparing signed checksums and if there is any modification found refuses to boot the device.
Well, my device boots perfectly, but SuperSu doesn't appear in apps list. Anyhow, I'll try with new kernel.
P.S. At the moment, phone runs androplus kernel v18 and custom ROM (Aura v4). After I will flash stock Nougat (using FTF file via Flashtool), will I need to re-flash androplus kernel v18 again?
manxp85 said:
Well, my device boots perfectly, but SuperSu doesn't appear in apps list. Anyhow, I'll try with new kernel.
P.S. At the moment, phone runs androplus kernel v18 and custom ROM (Aura v4). After I will flash stock Nougat (using FTF file via Flashtool), will I need to re-flash androplus kernel v18 again?
Click to expand...
Click to collapse
Welcome to the quirks of RomAur
It lasted less than a day on my device. I find the claims a bit overblown (did not notice them) and there were minor quirks/annoyances.
It needs time I suppose. But without the SONY sources auras76 can't do magic.
On my SAMSUNG G S5 I am on ResurrectionRom. THAT is an improvement over stock for me with LOTS of stuff I use and appreciate.
My Xperia XZ runs on stock ROM with AndroPlus Kernel v18 now. Do not forget to flash the Recovery too.
I am not sure if the SuperSU app is within the zip-file (80% positive it is). If not install it via Appstore.
Replaced RomAur with stock - works so much better. For some reason, root access on RomAur was lost every time after device was encrypted. No such problem with stock ROM.
Have you installed official Xposed for Nougat?
Does it work fine on your MotoZ?
Any performance issues/lags?
Please add details on your ROM version, root method and if you have Magisk installed too or not...
Thank you.
I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.
lilloscar said:
I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.
Click to expand...
Click to collapse
Two things...
- Greenify needs to fix its compatibility with Nougat, it's a known bug
- It is *needed* to use new official Xposed apk v.3.1.2 to manage modules activation. I've seen that unofficial or old version aren't able to enable them properly...
Thanks I have just read that about greenify, the list of compatible modules with nougat is short at this time guess so
Sent from my XT1650 using Tapatalk
Mine doesn't boot with xposed installed.
Stock 7.1.1 with turboZ and magisk
I remember that installing magisk caused a bootloop on my stock 7.0
I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).
Hi my fried. How long time this reboot in minuts?
Thanks
Ano59 said:
I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).
Click to expand...
Click to collapse
josenilsantana said:
Hi my fried. How long time this reboot in minuts?
Thanks
Click to expand...
Click to collapse
It took maybe 15-20 minutes for the first reboot.
For me systemless Xposed install e worked properly too.
Ano59 said:
It took maybe 15-20 minutes for the first reboot.
Click to expand...
Click to collapse
Hey everyone,
I have a Nexus 5 that I haven't updated in a long time that I'd like to get the latest possible OS for. The only modifications I've made which I think might be important are:
Unlocked bootloader
Rooted using SuperSU (v2.8.2 currently)
Installed XPosed (installer v2.6.1, not sure what version of the framework but it should be the latest supported by 4.4.4) with a few modules
Installed App Ops and removed permissions from some apps
Installed StickMount
I don't believe I have any custom recovery installed (I'd used a script to root and install XPosed originally and I don't know if it made any other changes). I'm comfortable using adb if needed but I'm cool with tools like FlashFire too.
My end goal is to have an updated OS with root and XPosed. I assume I'll need Magisk for XPosed, but not sure about root.
How should I go about doing this? I'm cool with losing all of my data (I'll be making backups with Titanium Backup) though knowing ahead of time if that'll be the case would be nice. If it's possible to update without losing data and without affecting anything that'd be nice, but maybe a clean start would be good? The OTA guide on this forum is only for 5, not 6, and most online guides start with 5. I don't want to mess up obviously. xD
Any advice/steps would be appreciated! Thanks!
Aecyl said:
Hey everyone,
Click to expand...
Click to collapse
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
pavik62 said:
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
Click to expand...
Click to collapse
The link you gave doesn't have the latest 6.0.1 build and it also says that it requires a minimum bootloader (HHZ12h) that I don't have (I have HHZ11k). Would it be possible to use the latest build from Google? What do I do about the bootloader? And would using TWRP as the recovery prevent me from passing SafetyNet?
Thanks for replying!
Could I follow this guide with the latest factory image and then install Magisk, root, and XPosed? https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Roxasmaker said:
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Click to expand...
Click to collapse
Would I have to do anything to XPosed or supersu first? I'd like to update to 6.0.1, too. I've seen online that there are OTA updates for it too.
Nope. But you may have to reinstall root, which is very easy once you're updated. Just let the updates do their thing, and you'll be on your merry way! Hope I helped
I think what I'll do is flash stock 4.4.4 keeping user data and then use the OTAs to update to 6. That way I have a clean system install to use Magisk with without losing any user data. (If that doesn't work I'll just flash 6.0.1 for a clean install.)