Can't install Xposed Framework - OnePlus 3 Questions & Answers

Hey everyone.
I can't install the Xposed framework. The error messages are in the the screenshots you'll see attached.
(EDIT: I can't post outside links since i am a new user, also i am by this Time unable to upload screenshots.. i'm working on it.)
de(DOT)tinypic(DOT)com/r/2cx89yd/9
de(DOT)tinypic(DOT)com/r/14ufkvo/9
I am currently using an OnePlus 3 with oxygenOS 3.26 flashed via twrp.
Before I was using 3.24 where everything was working fine. Then I switched to sultanxda's CyanogenMod. Since the Home Button was not working correctly, I decided to go back to the just released Oxygen. Everytime I was clean installing it.
From there on I am unable to use Xposed. I flashed it many times, used different twrp versions and also the arm64 v85 instead of v86. Nothing really wants to work.
I thought, i am may not able to flash anything because the System is set to Read-Only, but flashing SuperUser.zip has worked without any problems.
I'll appreciate your help.

Can you confirm that Supersu is working? And did you flash a systemless or 'normal' version of Supersu?

P0ttiBoo said:
Hey everyone.
I can't install the Xposed framework. The error messages are in the the screenshots you'll see attached.
(EDIT: I can't post outside links since i am a new user, also i am by this Time unable to upload screenshots.. i'm working on it.)
de(DOT)tinypic(DOT)com/r/2cx89yd/9
de(DOT)tinypic(DOT)com/r/14ufkvo/9
I am currently using an OnePlus 3 with oxygenOS 3.26 flashed via twrp.
Before I was using 3.24 where everything was working fine. Then I switched to sultanxda's CyanogenMod. Since the Home Button was not working correctly, I decided to go back to the just released Oxygen. Everytime I was clean installing it.
From there on I am unable to use Xposed. I flashed it many times, used different twrp versions and also the arm64 v85 instead of v86. Nothing really wants to work.
I thought, i am may not able to flash anything because the System is set to Read-Only, but flashing SuperUser.zip has worked without any problems.
I'll appreciate your help.
Click to expand...
Click to collapse
Dont set system to read only
Try to flash official xposed v86
Or v86.2 systemless by topjohnwu
Also you need supersu 2.76++ to make it work

Related

Uninstall Root on Cm13?

I want to use the system less root so I can play Pokémon Go. Is there a way to remove root or do I have to be running a stock rom? I'm using the latest nightly of the regular Cyanogen Cm13.
Thanks
Isn't root enabled via settings? Maybe turn it off in the settings or reflash and don't enable root?
I tried that but the system is still seen as rooted
Sent from my SGH-T999 using XDA-Developers mobile app
Shack70 said:
I want to use the system less root so I can play Pokémon Go. Is there a way to remove root or do I have to be running a stock rom? I'm using the latest nightly of the regular Cyanogen Cm13.
Thanks
Click to expand...
Click to collapse
in superSU app , under settings is a clickable box for "full unroot". tried that?
"err on the side of kindness"
mrrocketdog said:
in superSU app , under settings is a clickable box for "full unroot". tried that?
"err on the side of kindness"
Click to expand...
Click to collapse
I can't get the supersu app to work. It wants to update and fails update. Updating through twrp creates a boot loop. Good idea though, thanks.
Sent from my SGH-T999 using XDA-Developers mobile app
Shack70 said:
I can't get the supersu app to work. It wants to update and fails update. Updating through twrp creates a boot loop. Good idea though, thanks.
Sent from my SGH-T999 using XDA-Developers mobile app
Click to expand...
Click to collapse
hmmmmm well just for something to try , how about reflasing superSU then see if it will open. idk. just something to try
"err on the side of kindness"
CM13 has it's own baked-in implementation of ClockWorkMod's SuperUser, not SuperSU. You can install SuperSU, but it will conflict. You'll first need to delete /system/bin/su and /system/xbin/su, then you can "try" installing SuperSU, SUHide, etc..
1. install the latest version of TWRP for your device
2. boot into recovery and install SuperSU v2.78 SR1
-reboot system. open SuperSU and setup as normal
3. boot into recovery and install SUHide v0.54
-reboot system. open an app that require root to make sure your root is functioning
-try Pokemon Go. It should work fine
Do you need some sort of GPS spoof? You'll need Systemless XPosed and a good module
4. boot into recovery and install Xposed v86.2 - Universal Systemless (make sure you select 86.2 - you DO NOT need Magisk)
reboot system.
5. install Material Design Xposed Installer APK
-run XPosed Installer. it should show you are using 86.2 systemless
-click top left button and select download. search for a module called "Snorlax" and install the most recent version.
-this will hide your mock locations setting as well as show IV's, movesets, etc. of any Pokemon you encounter. it's all client side so no worries about bans!
-reboot system
-Test Pokemon Go. You should have no problems!
6. Need a GPS spoofing app? I use Fake GPS (well worth the $2.99). It allows you to pin favorite locations (I bounce quickly between spots where I can hit multiple lured PokeStops at once), and has settings to randomly move within a radius at whatever intervals and speed. They also have a GPS Joystick and Routes app that I have not yet tested since they don't offer a trial or free version. I'll update on that if they do offer a trial.
I have fresh installed CM13 on a Nexus 5, following the instructions above for systemless root + xposed. Pokemon Go v39.1 works without issue while spoofing GPS.
**UPDATE 10/7/2016 ** - edited to use updated suhide v0.54
FuNKSioN said:
CM13 has it's own baked-in implementation of ClockWorkMod's SuperUser, not SuperSU. You can install SuperSU, but it will conflict. You'll first need to delete /system/bin/su and /system/xbin/su, then you can "try" installing SuperSU, SUHide, etc..
1. install the latest version of TWRP for your device
2. boot into recovery and install SuperSU v2.78 SR1
-reboot system. open SuperSU and setup as normal
3. boot into recovery and install suhide v0.53
-reboot system. open an app that require root to make sure your root is functioning
-try Pokemon Go. It should work fine
Do you need some sort of GPS spoof? You'll need Systemless XPosed and a good module
4. boot into recovery and install Xposed v86.2 - Universal Systemless (make sure you select 86.2 - you DO NOT need Magisk)
reboot system.
5. install Material Design Xposed Installer APK
-run XPosed Installer. it should show you are using 86.2 systemless
-click top left button and select download. search for a module called "Snorlax" and install the most recent version.
-this will spoof your mock locations setting as well as show IV's, movesets, etc. of any Pokemon you encounter. it's all client side so no worries about bans!
-reboot system
Test Pokemon Go. You should have no problems!
***UPDATE***
I have just fresh installed CM13 on a Nexus 5, following the instructions above for systemless root + xposed. Pokemon Go v39.1 works without issue while spoofing GPS.
Click to expand...
Click to collapse
I deleted all the support files but Pokémon ends telling it's unable to log me in. Many users are reporting this error. It might just be my phone, the s3 is kinda old.
Shack70 said:
I deleted all the support files but Pokémon ends telling it's unable to log me in. Many users are reporting this error. It might just be my phone, the s3 is kinda old.
Click to expand...
Click to collapse
Hmm.. For ****s and giggles, I'll pull out an old S3 and give it a go. Will report back soon.
FuNKSioN said:
Hmm.. For ****s and giggles, I'll pull out an old S3 and give it a go. Will report back soon.
Click to expand...
Click to collapse
Wow! Thanks I appreciate it.
Shack70 said:
Wow! Thanks I appreciate it.
Click to expand...
Click to collapse
Sorry took so long. This phone is slow as ballz! Everything appears to be working correctly though. I have Pokemon Go 39.1 installed (had to use apkmirror to install since it wouldn't let me from the Play Store on the S3), and am using Snorlax module to hide mock locations. I'm also using Fake Gps to spoof location.
I'd say it should work for you as well. What modules are you using? If you don't care about anything on your phone, wipe everything from recovery. Then under advanced, adb sideload CM13 and GApps Nano from opengapps.org (ARM/6.0/nano). Restart system and follow all the steps from there after you have the initial phone setup done.
FuNKSioN said:
Sorry took so long. This phone is slow as ballz! Everything appears to be working correctly though. I have Pokemon Go 39.1 installed (had to use apkmirror to install since it wouldn't let me from the Play Store on the S3), and am using Snorlax module to hide mock locations. I'm also using Fake Gps to spoof location.
I'd say it should work for you as well. What modules are you using? If you don't care about anything on your phone, wipe everything from recovery. Then under advanced, adb sideload CM13 and GApps Nano from opengapps.org (ARM/6.0/nano). Restart system and follow all the steps from there after you have the initial phone setup done.
Click to expand...
Click to collapse
Thanks for your help. I updated yo the newest nightly build, did a full factory reset and deleted the 2 su files. After rebooting i re-downloaded the newest version of Pokémon and installed it. Game is working fine.
I don't use root much so I'll see how it goes without root and if I need root i can put the su files back(I made copies and put them in Dropbox) or try superSU/hideSU.
I know the s3 is slow but I'm putting off an upgrade until i have to upgrade. Until i upgrade I won't really realize how slow my phone is
Sent from my SGH-T999 using XDA-Developers mobile app
Going forward, I don't think the CM baked-in SuperUser is going to cut it. At least not the version in CM13. The specific versions of SuperSU + suhide I linked seem to pass all current checks though. So if you want root, go ahead and use them.
FuNKSioN said:
Going forward, I don't think the CM baked-in SuperUser is going to cut it. At least not the version in CM13. The specific versions of SuperSU + suhide I linked seem to pass all current checks though. So if you want root, go ahead and use them.
Click to expand...
Click to collapse
Yeah i get this is a temporary solution. Thanks for all your help. You've really gone above and beyond
Sent from my SGH-T999 using XDA-Developers mobile app
no problem man!
Thanks!
FuNKSioN said:
no problem man!
Click to expand...
Click to collapse
just wanted to chime in and say my own SGH-T999 is now running PG again, thanks to you FuNKSioN - so, thank you sir!!! wasted a LOT of time trying other solutions (mainly Magisk) with no luck, so i was pretty damned happy when your steps worked. first time i forgot to rename/delete the two su files, second time i did it immediately after flashing CM13 & GApps using ADB and then everything was fine. you rock!!! :victory:
and also, yeah - until Shack70 and i get a new phone, we have no idea what "slow as ballz" is! i will say, the S3 may be relatively slow but i have two backup batteries that take up very little space and are very easy to swap in and out.
romehu2 said:
just wanted to chime in and say my own SGH-T999 is now running PG again, thanks to you FuNKSioN - so, thank you sir!!! wasted a LOT of time trying other solutions (mainly Magisk) with no luck, so i was pretty damned happy when your steps worked. first time i forgot to rename/delete the two su files, second time i did it immediately after flashing CM13 & GApps using ADB and then everything was fine. you rock!!! :victory:
and also, yeah - until Shack70 and i get a new phone, we have no idea what "slow as ballz" is! i will say, the S3 may be relatively slow but i have two backup batteries that take up very little space and are very easy to swap in and out.
Click to expand...
Click to collapse
Glad to help. I was in the same boat: so much info in all directions and none of it seemed to work. I keep up with ChainFire's G+ account. He had a few posts linked directly back to XDA. Those few posts had everything needed. I just put it in simple steps. All thanks to him really
Sigh
And now SafetyNet is failing and PoGo won't log me in. Is this really worth it?
romehu2 said:
And now SafetyNet is failing and PoGo won't log me in. Is this really worth it?
Click to expand...
Click to collapse
reflashed CM13 + GApps, used ADB to rename system/xbin/su & system/bin/su to /su-off, and SafetyNet is happy (and thus, so is PoGo). but now, of course, phone isn't rooted.
---------- Post added at 05:18 AM ---------- Previous post was at 05:05 AM ----------
on the plus side, CM13 comes with File Manager which allowed me, without root, to install the v39.1 PoGo apk that I downloaded last week.
Sit back and wait for an SU update... It's only been a hot minute.

Can't boot any AOSP rom, stuck on 1+ screen, CB still boots

hello,
(with "this rom" i mean >sultan cm13<. I edited the title, before that it "was can't but sultan cm13", but now i know it doesnt boots any aosp roms)
a few days ago i used this rom as secondary with multirom (primary was freedom 1.10). now today, i wanted to use this rom as my dailydriver rom. i made the normal procedure, making a backup, then wiping the partitions (system, data, cache, dalvik) and after it flashing the rom. on the first try, i did it like i usually do, first the rom, then the gapps and then xposed. then i rebooted, and it was stuck on the 1+ logo screen about 10 mins. then i reflashed it, but just the cm.zip. then i still got stuck.
i tried it with the unofficial and the official twrp recovery. now i did a nandroid restore to the freedomos rom, and it boots normal.
please help me, i really want to use sultans cm13, i really like it!
i don't know why it doesn't work, i mean as a secondary it booted flawless..
btw i'm on the 3.2.7 firmware
(problem exists on all 6.0 aosp roms i tried. Please read further posts)
Did you follow the flashing instructions to the letter? If you did, you would have seen that the CM13 requires a one time flash of the OOS 3.2.6 firmware (linked in the thread).
Yeah sure but it did work with the 3.2.7 firmware on multirom, so i thought i dont have to do this. Well i will try this, and give you feedback then
Thanks
ReNeH99 said:
Yeah sure but it did work with the 3.2.7 firmware on multirom, so i thought i dont have to do this. Well i will try this, and give you feedback then
Thanks
Click to expand...
Click to collapse
BTW, which xposed version did you flash? If it was v86.x then that's the most likely culprit (since the latest patch, v87 works, v86.x causes bootloop).
i just flashed the 3.2.6 firmware, still does not work.
yes i used the v87 xposed, also the second try i only installed the cm.zip, without xposed and gapps, etc.
ReNeH99 said:
i just flashed the 3.2.6 firmware, still does not work.
yes i used the v87 xposed, also the second try i only installed the cm.zip, without xposed and gapps, etc.
Click to expand...
Click to collapse
Hmm... strange... TWRP doesn't give any errors either?
Hw4ng3r said:
Hmm... strange... TWRP doesn't give any errors either?
Click to expand...
Click to collapse
nope no errors, all the folders and build.prop, etc is in the /system folder too..
i also redownloaded the rom, md5 hash is right and it doesn't help either
May be a silly question but did you uninstall multirom?
Hw4ng3r said:
May be a silly question but did you uninstall multirom?
Click to expand...
Click to collapse
yep
i gonna try to flash RR 5.7.4, to see what happens then
edit: what i forgot to say, i also reinstalled multirom and the multirom recovery for another try. in the multirom menu the touch doesn't work then, and when the primary rom (cm13 sultan) boots after 5 secs, i just get a black screen, the phone isnt of, just a black screen, i have to press all 3 buttons for a reboot then.
edit2: RR also does not boot
edit3: lol i just reinstalled multirom and it boots as secondary rom. then i copied it to the primary slot, and *bling* it doesn't boot again... i dont get this...
Ok i tried it with multiple AOSP roms and it simply doesn't work. Strange thing is, they work as a secondary rom when i have multirom installed.
Does anybody have a solution for this maybe? I hope someone who knows about this problem can help me i don't want oos anymore i need aosp

[ROM] [B207] Simply Google M2 8.0 **Update 1/15/17**

Here is my stock based B207 rom, Simply Google. This is great for those of you who have a hard time getting the Google Apps to work and want some extra mods and features. You must have an unlocked bootloader and TWRP installed. This rom is tested on the M2-803L. Flashing it on other versions (801L, 802L) should work but you're flashing it at your own risk. All Google Apps you can download from the Play Store have been removed from the rom. I also heavily debloated it and removed a lot of Huawei apps. Please don't ask me to add anything in as I want to keep this rom slim. Open up Tablet Manager, hit the settings icon and uncheck Smart Tune-up if Permissions Manager force closes when you open it. Please hit the Thanks button if you like the ROM.
Features & Mods:
-AdAway
-Cust Mods
-Dark M2 Theme
-Deodexed
-GBoard
-Google Play Store, Google Contacts Sync
-Heavily Debloated
-Insecure boot.img
-Marshmallow Boot Animation
-Nova Launcher
-Region Mods
-SuperSU Preinstalled
Instructions:
1. OTA or Dload to B2xx first before flashing. The ROM will not boot if you're still on anything lower than B2xx
2. Download ROM and put it on the phone's internal storage or SDCard
3. Boot into TWRP recovery.
4. Performing a factory reset using TWRP is recommended.
5. Flash the ROM
6. Reboot System
7. Profit!
Bugs:
-You tell me
Simply Google B207:
https://www.androidfilehost.com/?fid=817550096634797575
​
Many thanks! What a nice surprise. This seems to be the first custom rom for the m8.
Appears that it is for the 802l. Would it also work for the 801l?
At the moment I have 5.1 reverted to stock. BL unlocked.
Demianis said:
Many thanks! What a nice surprise. This seems to be the first custom rom for the m8.
Appears that it is for the 802l. Would it also work for the 801l?
At the moment I have 5.1 reverted to stock. BL unlocked.
Click to expand...
Click to collapse
It should work on both versions provided you update to stock B2xx first. After someone updates to B2xx on their 802L I need them to send me two things.
1) Their cust folder so I can integrate it into the rom.
2) Their system/emui folder. There should be a folder called oversea in there which I need to integrate into the rom.
Sorry, I don't have the b215 yet. There was no update to 6.0 till now and i can't find even a newer version for the 801l then the one attached.
Demianis said:
Sorry, I don't have the b215 yet. There was no update to 6.0 till now and i can't find even a newer version for the 801l then the one attached.
Click to expand...
Click to collapse
The B215 update posted in one of these threads is for the 801L because when I flashed it I had no cellular data option at all.
Just tried to install the b019. But again it's a incompatible version. I guess it's because it's for the m2 803l.
Anyway, thanks for your help. I'll have to wait until until the official update hits my tab.
I tried with hisuite, but i have already the latest version available.
Hi. Thanks for the rom. I have 802l - b006 with unlock bootloader. Can I use your rom without updating to b219? I dont have any ota update that I can installl
Thanks
Sent from my HUAWEI M2-802L using XDA-Developers mobile app
budif said:
Hi. Thanks for the rom. I have 802l - b006 with unlock bootloader. Can I use your rom without updating to b219? I dont have any ota update that I can installl
Thanks
Sent from my HUAWEI M2-802L using XDA-Developers mobile app
Click to expand...
Click to collapse
No, things like wifi won't work unless you upgrade to B211 first. Hold off on flashing until I sort out the root issue. Systemless root causes freezes. I'm working on porting the kernel from the X2 so I can use regular root which will fix the freezing issues.
New build up. Fixed root causes freezing in apps.
Do you know where to get the b011? The b006 is the latest rom that I can find for my m2.
Sent from my HUAWEI M2-802L using XDA-Developers mobile app
budif said:
Do you know where to get the b011? The b006 is the latest rom that I can find for my m2.
Sent from my HUAWEI M2-802L using XDA-Developers mobile app
Click to expand...
Click to collapse
You're gonna have to wait until you get the OTA to B215. Then you can flash this rom.
Installed this last night after updating to B207 from the other thread. Works perfectly, thanks!!
how can i remove 3g above my signal? my data is turned off and it still shows
New update. Fixed Multi-Screen not working. Rebased the rom to the International B207 version. Deodexed and added more mods.
ajsmsg78 said:
New update. Fixed Multi-Screen not working. Rebased the rom to the International B207 version. Deodexed and added more mods.
Click to expand...
Click to collapse
Currently I'm using your rom with xposed included.
Is the update also for this version available?
Lots of thanks for your work!
Demianis said:
Currently I'm using your rom with xposed included.
Is the update also for this version available?
Lots of thanks for your work!
Click to expand...
Click to collapse
I didn't integrate xposed this time because I figured if someone wanted it they can install it separately. You can grab it here:
https://drive.google.com/folderview?id=0B5I_q70mNuR4OWRaejdUdE1fcjA
ajsmsg78 said:
I didn't integrate xposed this time because I figured if someone wanted it they can install it separately. You can grab it here:
https://drive.google.com/folderview?id=0B5I_q70mNuR4OWRaejdUdE1fcjA
Click to expand...
Click to collapse
Ok, many thanks for the links. I will uninstall xposed, then dirty flash and after the first boot install xposed again.
my 801w was detected during installation as 802l. Don't know if this is what's causing the trouble, but after installing via TWRP, coming from some b2xx official ROM, i'm stuck at the Huawei Bootscreen for about 10 minutes now. I know that the first start could take a lot of time, but this seems a bit unusual to me. I'll keep it watching for another 15-20 minutes and see if it boots up fine or is frozen in any way.
[Update] so it was stuck in a loop for sure. I tried flashing a clean b2xx from another thread, which booted fine, and dirty flashing your ROM over, but same behaviour. What actually DID work is flashing the boot.img from stock over your ROM, so keeping the other partitions from Simply Google Installation. At least it's booting up now, showing the proper Android Nougat loading screen. Let's see how it works out...
toxic_garden said:
my 801w was detected during installation as 802l. Don't know if this is what's causing the trouble, but after installing via TWRP, coming from some b2xx official ROM, i'm stuck at the Huawei Bootscreen for about 10 minutes now. I know that the first start could take a lot of time, but this seems a bit unusual to me. I'll keep it watching for another 15-20 minutes and see if it boots up fine or is frozen in any way.
[Update] so it was stuck in a loop for sure. I tried flashing a clean b2xx from another thread, which booted fine, and dirty flashing your ROM over, but same behaviour. What actually DID work is flashing the boot.img from stock over your ROM, so keeping the other partitions from Simply Google Installation. At least it's booting up now, showing the proper Android Nougat loading screen. Let's see how it works out...
Click to expand...
Click to collapse
I need the /cust folder from the 801w so I can add it to the rom so it shows up correctly.
ajsmsg78 said:
I need the /cust folder from the 801w so I can add it to the rom so it shows up correctly.
Click to expand...
Click to collapse
Hello
same for me, i have a W, and i'm stuck on logo menu.
I have backup my tablet in trwp before, can you send me your email ???
Thank you.
(PS: is it complicated to deoxed the huawei rom ?) Ty

HELP: Issues updating rooted device to OOS 3.2.8

hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
backup all your data and install 3.2.8 with the official procedure
Sacob said:
backup all your data and install 3.2.8 with the official procedure
Click to expand...
Click to collapse
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
tropicanapure said:
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
Click to expand...
Click to collapse
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Sacob said:
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Click to expand...
Click to collapse
tropicanapure said:
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Click to expand...
Click to collapse
i got the impression that your phone wasn't booting xD
well, every time i flash those betas (9 and 10) TWRP asks me for a PIN that doesn't exists and to solve that i need wipe everything... so i wouldn't count on that
tropicanapure said:
hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
Click to expand...
Click to collapse
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
ptblad said:
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
Click to expand...
Click to collapse
tropicanapure said:
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
Click to expand...
Click to collapse
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
I wish I had, man. You went a number of steps ahead when your phone went past the boot animation
As a afterthought - try looking through your logs.
ptblad said:
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
Click to expand...
Click to collapse

Oxygen Updater, OOS 10.0.11, Rooted

Can I use the Oxygen Updater to go from OOS. 10.0.9 to 10.0.11? I'm rooted and have Magisk installed. When I went to the Updater it said it used TWRP, which I know still has issues on the 7T. Can I load TWRP 3.3.1-25 and use that? My goal is to move to the new release with out losing all my current installed applications (many!). Or do I have to do this all manually (a link would be nice is there already is a routine). Thanks.
davekaye said:
Can I use the Oxygen Updater to go from OOS. 10.0.9 to 10.0.11? I'm rooted and have Magisk installed. When I went to the Updater it said it used TWRP, which I know still has issues on the 7T. Can I load TWRP 3.3.1-25 and use that? My goal is to move to the new release with out losing all my current installed applications (many!). Or do I have to do this all manually (a link would be nice is there already is a routine). Thanks.
Click to expand...
Click to collapse
There is no working TWRP for the 7T yet. Just something in development. You'll have to do everything manually. Magisk has a guide on how to install an update and keep root. I haven't followed the guide yet myself but it is the method I will be using later tonight.
https://topjohnwu.github.io/Magisk/ota.html
Just make sure to disable/uninstall any magisk modules before you start. And probably any substratum overlays too just to be safe.
jsgraphicart said:
There is no working TWRP for the 7T yet. Just something in development. You'll have to do everything manually. Magisk has a guide on how to install an update and keep root. I haven't followed the guide yet myself but it is the method I will be using later tonight.
https://topjohnwu.github.io/Magisk/ota.html
Just make sure to disable/uninstall any magisk modules before you start. And probably any substratum overlays too just to be safe.
Click to expand...
Click to collapse
This guide works dude
manan001 said:
This guide works dude
Click to expand...
Click to collapse
Yeah, I just did it myself a little earlier. Easy and no issues
When I follow the steps at
When an OTA is available, first go to (Magisk Manager → Uninstall → Restore Images).
Click to expand...
Click to collapse
It says "Stock backup does not exist!" Is there a way I can create stock backups?
adobrakic said:
When I follow the steps at
It says "Stock backup does not exist!" Is there a way I can create stock backups?
Click to expand...
Click to collapse
I'm not an expert on this but as far as I know, it should have made the backup img file during the rooting process before patching the boot.img. If you don't have one then I don't know what happened to it. That step may not be 100% necessary though. I've read people saying you don't have to do that. I think it's mainly so you keep that stock img file backed up. Again, I don't know exactly but that's my understanding of it. I'm just giving you my thoughts on it
Stock backup does not exist
jsgraphicart said:
I'm not an expert on this but as far as I know, it should have made the backup img file during the rooting process before patching the boot.img. If you don't have one then I don't know what happened to it. That step may not be 100% necessary though. I've read people saying you don't have to do that. I think it's mainly so you keep that stock img file backed up. Again, I don't know exactly but that's my understanding of it. I'm just giving you my thoughts on it
Click to expand...
Click to collapse
I got this message -- Stock backup does not exist-- but proceed with the upgrade as per the instructions. Everything worked fine. Just waiting for the day when 7T TWRP will be available so I can use Oxygen Updater once again. Thanks for you comments.
davekaye said:
I got this message -- Stock backup does not exist-- but proceed with the upgrade as per the instructions. Everything worked fine. Just waiting for the day when 7T TWRP will be available so I can use Oxygen Updater once again. Thanks for you comments.
Click to expand...
Click to collapse
I also got this message when trying to uninstall magisk, so my question :
You proceeded with the upgrade - Was this from actual OS upgrade option in settings or from oxygen updater application?
If so, Im wondering if all you did was download the 10.0.11 full update & went to settings and applied it without doing anything in magisk.
Eg: you did not uninstall your modules and obviously did not uninstall magisk as it failed to do so cause there was no stock image.
At that point what did you do? You went to Re-install magisk (from where in magisk manager is the option?) and then selected "Install to inactive slot"
After that, you rebooted from magisk option to reboot and it took abit but rebooted all perfect?
Thanks
Upgrade rooted phone with OTA
JF-GINO said:
I also got this message when trying to uninstall magisk, so my question :
You proceeded with the upgrade - Was this from actual OS upgrade option in settings or from oxygen updater application?
If so, Im wondering if all you did was download the 10.0.11 full update & went to settings and applied it without doing anything in magisk.
Eg: you did not uninstall your modules and obviously did not uninstall magisk as it failed to do so cause there was no stock image.
At that point what did you do? You went to Re-install magisk (from where in magisk manager is the option?) and then selected "Install to inactive slot"
After that, you rebooted from magisk option to reboot and it took abit but rebooted all perfect?
Thanks
Click to expand...
Click to collapse
I downloaded the new OTA version (I think from the Updater app - if I remember it allowed you to download the OTA) to the root of my phone and then just followed the directions from the first reply to my post. I had the latest version of Magisk (Uninstaller, the app, and the Manager) installed in it's own folder in internal memory. After I got the message, just proceeded as if nothing was wrong and in the end, the upgrade worked fine. I didn't document every step, but the instructions worked.
https://topjohnwu.github.io/Magisk/ota.html
Did you uninstall all your modules first? Or leave them alone. I heard a few people didn't uninstall or deactivate there modules. I'm using xxx nolimits and don't want to have to redo everything, but I will if I have to.
Update :
A) I Downloaded 10.0.11 update from oxygen update app (zip on root)
Note - The only module I uninstalled was XXXNolimits and suggest you uninstall anything like this or any theming.
(I did leave busybox, systemless hosts, energized protection & a volume mod installed)
B) I manually updated from settings (Did NOT reboot)
C) I went to Magisk manager and installed Magisk in empty a/b slot as per instructions in link
D) I rebooted from Magisk
E) everything rebooted fine
F) I re-installed XXXNolimits - Rebooted
G) When rebooted, everything was exactly as it was before update and working fine!
So far so good. Phone was hot for awhile but cooled down after 10min and all is good.
Thanks everyone for your helpful posts
Does it pass SafetyNet check?
JF-GINO said:
Did you uninstall all your modules first? Or leave them alone. I heard a few people didn't uninstall or deactivate there modules. I'm using xxx nolimits and don't want to have to redo everything, but I will if I have to.
Update :
A) I Downloaded 10.0.11 update from oxygen update app (zip on root)
Note - The only module I uninstalled was XXXNolimits and suggest you uninstall anything like this or any theming.
(I did leave busybox, systemless hosts, energized protection & a volume mod installed)
B) I manually updated from settings (Did NOT reboot)
C) I went to Magisk manager and installed Magisk in empty a/b slot as per instructions in link
D) I rebooted from Magisk
E) everything rebooted fine
F) I re-installed XXXNolimits - Rebooted
G) When rebooted, everything was exactly as it was before update and working fine!
So far so good. Phone was hot for awhile but cooled down after 10min and all is good.
Thanks everyone for your helpful posts
Click to expand...
Click to collapse
Yep, safety net check pass.

Categories

Resources