Hi All!
First of all i would like to state i'm not a noob at all. I have tried clearing cache, dalvik, format system > full OOS zip > SuperSu > Reboot ? Xposed arm64 zip.
But for the life of me, i am not able to get it working. I'm using the alpha 4 app from original thread and it still shows xposed framework not installed. What step am i missing in TWRP during flashing the zip?
Again, i am using the xposed zip from the original thread for arm64 system.
I do it pretty much the same and had no problems so far. As TWRP I use the official: twrp-3.0.2-1-oneplus3
-flash full rom
-flash supersu (some beta-supersu-forced-systemless.zip file which is properly not the newest)
-flash xposed-v86-sdk23-arm64.zip
-wipe caches
-reboot
After the reboot I already get the update news from the market about supersu where I update to the lastest Version.
extrem101 said:
I do it pretty much the same and had no problems so far. As TWRP I use the official: twrp-3.0.2-1-oneplus3
-flash full rom
-flash supersu (some beta-supersu-forced-systemless.zip file which is properly not the newest)
-flash xposed-v86-sdk23-arm64.zip
-wipe caches
-reboot
After the reboot I already get the update news from the market about supersu where I update to the lastest Version.
Click to expand...
Click to collapse
I am using the same recovery and the exact same zip file but i have no idea what the issue is. Are you also on OOS?
Yes OOS 3.2.7
Strange that it doesn't work on some devices like this. Unfortunately I don't know what you can make different.
Did you try to explicitely mount system in TWRP before flashing xposed?
groshnack said:
Did you try to explicitely mount system in TWRP before flashing xposed?
Click to expand...
Click to collapse
I haven't done this. But i can try after work hours and let you know once done.
I only had problems once with Xposed not working after a dirty ROM update (and then flashing Xposed). Clean install fixed that and since then I had no issues, doing very similar procedure as described above - I'm not even rebooting in between:
- wipe system, cache, dalvik, sometimes data
- flash ROM (FreedomOS, but that's still OOS)
- flash SuperSU (latest)
- flash kernel
- flash Xposed
- reboot
And it works ?
Sent from my OnePlus 3 using Tapatalk
Related
I can't update my N7100 from previous Omnirom to latest CM11. I wiped my phone, installing latest CM11 zip and phone is stuck at N7100 logo and restart to recovery. When I install Omni zip everything is working fine. I'm tried TWRP and Philz recovery but no results. Please help
did you wipe /system, /cache, /data and dalvik? (full wipe).
atmos929 said:
did you wipe /system, /cache, /data and dalvik? (full wipe).
Click to expand...
Click to collapse
Yes of course but I think CM isn't extracting to /system because when I leave recovery it shows there's no root and asks if I want to install it.
emlo16 said:
Yes of course but I think CM isn't extracting to /system because when I leave recovery it shows there's no root and asks if I want to install it.
Click to expand...
Click to collapse
Recoveries tend to do that... they do not detect superuser from any CM based ROM and offer you to install supersu after a ROM install and rebooting system.
I you do full wipes and you have tested latest Philz and TWRP recoveries... I can only suggest you to double check that the CM11 ROM is the correct one for your N7100.
It is strange that you encounter issues with CM based ROMs... these usually install without problems... I've encountered problems booting TW based ROMs, but not these. Sorry I can't be or more help. Good luck .
EDIT:: wait a second... according to your screenshot, you did a full wipe after installing the CM ROM... you are deleting your ROM that you just installed . The steps are:
1.- full wipe
2.- install ROM
3.- Install GAPPS
4.- wipe Dalvik <-- (some devs recommend this step, others don't... doesn't hurt to do it anyway)
Hi, is is possible after rooting to replace TWRP with the stock recovery, stay rooted and enjoy OTA updates.
Rooting is out of question, but besides the fact that 3.2.0 is still not available from the Oneplus website and it is hard to judge which unofficial source is trustworthy, I would prefer not to have to reroot and install xposed each time I flash a full image.
I am also interested in this.
Is this possible without wipe?
I guess root and xposed should be reinstalled even after OTA:
ErzlordCaron said:
Hi, is is possible after rooting to replace TWRP with the stock recovery, stay rooted and enjoy OTA updates.
Rooting is out of question, but besides the fact that 3.2.0 is still not available from the Oneplus website and it is hard to judge which unofficial source is trustworthy, I would prefer not to have to reroot and install xposed each time I flash a full image.
Click to expand...
Click to collapse
Download complete ROM from here: https://www.androidfilehost.com/?fid=24591020540823780
1. Booted into TWRP wiped Cache & Dalvik
2. Flashed Full ROM 3.2.0
3. Wiped Cache & Dalvik
4. Flashed systemless SU and systemless Xposed v85.7
5. Wiped Cache & Dalvik
6. Reboot
You will not lose data and be updated at the same time.
nidhish91 said:
Download complete ROM from here: https://www.androidfilehost.com/?fid=24591020540823780
1. Booted into TWRP wiped Cache & Dalvik
2. Flashed Full ROM 3.2.0
3. Wiped Cache & Dalvik
4. Flashed systemless SU and systemless Xposed v85.7
5. Wiped Cache & Dalvik
6. Reboot
You will not lose data and be updated at the same time.
Click to expand...
Click to collapse
Thanks, but I know how to do that - aside from the fact that I would like to get my ROM from Oneplus or at least a dedicated XDA-dev thread, instead of some link in some forum. The question was if I can flash the original recovery to be able to receive OTA updates.
I've been trying to flash xposed on latest rooted stock rom in the latest twrp but it doesn't seem to stick. When flashing the file there's no error message and it does mount the system for read/write, but when the phone restarts it doesn't register xposed. I've tried flashing v84 and v86. I've flashed xposed many times before but never encountered this issue. What could be the reason for this?
Same thing happened to me yesterday. Are you clearing your caches before and after flashing? I had to do a fresh install of the latest ROM, clear caches, Root, clear caches, Boot into recovery, flash xposed, clear caches. Then it installed I'm on 3.2.2 with v86 ARM-64.
Thanks for the reply! It didn't work unfortunately. Still doesn't stick. Never experienced that before.. very odd
slonn said:
Thanks for the reply! It didn't work unfortunately. Still doesn't stick. Never experienced that before.. very odd
Click to expand...
Click to collapse
Having the same issue here on stock OOS. I've flashed xposed a bunch of times without issue. Now it just doesn't stick for some reason.
did u use the arm64 version also have u tried systemless root, i have more success with that than the other xposed
Same problem here :/
if anyone found a fix, please help
Had the same issue, solved it by :
EDIT: make sure to have a pc with adb/fastboot close to you, for me the clean flash also flashed stock recovery. You could also possibly (haven't tried that) flash twrp itself right after flashing the full zip
Wipe system/cache/dalvik
Flash ONLY full zip - Reboot
Flash ONLY Supersu - reboot
Flash xposed - reboot - should work
No clearing caches after the very first wipe! Installed EX Kernel after xposed, too.
Hope this helps
I got it sorted by flashing the latest version of FreedomOS. Xposed works fine on that one
Back after a long time.
My OP3
- Freedom OS 2.10.4 [Android 7.1.1]
- BluSpark Recovery v40
On my OP3 I've always been on Freedom OS . Mostly due to
- Being close to stock,
- Debloated
- rooted for ad blocker, cerberus and titanium
However off the late facing lot of issue with network. Frequent drops on VoLTE and 4G networks on both sims. VoLTE sim will often disconnect and I will end with "Dial-> Immediate Call Ended" issue.
=> What would you recommend to use as daily driver ?
Would appreciate if you should add links. Any additional info regarding prerequisites (recovery, firmware etc) will be helpful.
You can try:
1-OxygenOS 5.0.3 with RenderZenith or Derp kernel.(Do not go for open beta OxygenOS builds, they are abandoned.)
2-Paranoid Android 7.3.1(Nougat but it won't upset you)
3-If camera, VoWiFi and OTA updates are not important, OmniDragon.
Everyone's expectations are different. These are just mine experiences.
You should update your TWRP before flashing, i guess it is outdated; PA and OxygenOS contains their own firmware but for OmniDragon you can use Open Beta 39/OxygenOS 5.0.3 firmwares.
qhsusb_bulk said:
You can try:
1-OxygenOS 5.0.3 with RenderZenith or Derp kernel.(Do not go for open beta OxygenOS builds, they are abandoned.)
2-Paranoid Android 7.3.1(Nougat but it won't upset you)
3-If camera, VoWiFi and OTA updates are not important, OmniDragon.
Everyone's expectations are different. These are just mine experiences.
You should update your TWRP before flashing, i guess it is outdated; PA and OxygenOS contains their own firmware but for OmniDragon you can use Open Beta 39/OxygenOS 5.0.3 firmwares.
Click to expand...
Click to collapse
Thanks. Will check OxygenOS 5.0.3
Any reason why you did not suggest LineageOS?
Also will I be able to keep custom recovery and root with OxygenOS 5.0.3
hyperorb said:
Thanks. Will check OxygenOS 5.0.3
Any reason why you did not suggest LineageOS?
Also will I be able to keep custom recovery and root with OxygenOS 5.0.3
Click to expand...
Click to collapse
According to my experiences, unfortunately LineageOS 15.1 is not a daily driver on SD820 phones. Used it on Mi5 and OP3, both of them suffered with lag, overheating, shuttering, deep sleep not working sometimes (lost apx.%30 battery per night), bad camera quality. It is good rom, but this issues must be solved.
You can keep root and TWRP on OOS. Process:
1-Flash TWRP and boot it.
2-Make the wipes(dalvik/data/cache/system are must, if you want full wipe of userdata you can select internal storage too.
3-Install OxygenOS zip, custom kernel zip(optional) and latest Magisk beta zip(16.7 today).
Reboot and profit.
qhsusb_bulk said:
According to my experiences, unfortunately LineageOS 15.1 is not a daily driver on SD820 phones. Used it on Mi5 and OP3, both of them suffered with lag, overheating, shuttering, deep sleep not working sometimes (lost apx.%30 battery per night), bad camera quality. It is good rom, but this issues must be solved.
You can keep root and TWRP on OOS. Process:
1-Flash TWRP and boot it.
2-Make the wipes(dalvik/data/cache/system are must, if you want full wipe of userdata you can select internal storage too.
3-Install OxygenOS zip, custom kernel zip(optional) and latest Magisk beta zip(16.7 today).
Reboot and profit.
Click to expand...
Click to collapse
Thank you for helping with my queries.
So it's just like flashing a custom rom. Also If I wipe internal storage then the ROM zip file will also get wiped. Wonder how do I copy it then?
Last set of queries before I flash this coming weekend
- Whch TWRP ? Latest blu_spark should do ? (I remember blu_spark had specific TWRP for OP3_OP3T
- I remember reading about recovery getting overwritten when flashing OxygenOS.. Will it happen with full rom zip
- Any precautions you would like to suggest ?
hyperorb said:
Thank you for helping with my queries.
So it's just like flashing a custom rom. Also If I wipe internal storage then the ROM zip file will also get wiped. Wonder how do I copy it then?
Last set of queries before I flash this coming weekend
- Whch TWRP ? Latest blu_spark should do ? (I remember blu_spark had specific TWRP for OP3_OP3T
- I remember reading about recovery getting overwritten when flashing OxygenOS.. Will it happen with full rom zip
- Any precautions you would like to suggest ?
Click to expand...
Click to collapse
Yes, if you wipe internal storage, the rom will be wiped. But you can just copy it from your pc while you are in twrp.
Latest Blu_spark twrp works fine for me. Will work for you too.
If recovery is overwritten, you can just flash twrp again via fastboot. It won't be overwritten then.
I think there was a way that after you can avoid having to fastboot by just installing twrp again right after you have flashed oos rom and then reboot. But I am not quite sure if it works. Maybe someone else with experience can elaborate. Anyways, the fastboot method will definitely work.
@hyperorb , If you flash Magisk right after OOS, your recovery won't be replaced by Oxygen one.
For recovery, you can use Official TWRP or OmniDragon TWRP.
many thanks @qhsusb_bulk @Harsh862
will try wit latest blu_spark first but will also keep others handy. Will not refresh internal storage for now. Maybe once I get a bit comfortable with this part. Will revert once I update.
OP3 OOS 5.0.3
Attaching link in case someone else need
Easy breezy.
Thanks to @qhsusb_bulk @Harsh862 Upgraded to OOS 5.0.3
1) Backups ( whatsapp, titanium, nandroid)
2) Remove all security - pin , fingerprint
3) Reboot to recovery
4) Upgrade TWRP to 8.6.1 blu_stark
5) Reboot to recovery
6) Full wipe except internal storage
7) Flash OOS
8) Wipe dalvik / cache
-------
9) Flash Magisk 16 (1600). I'm not sure what happened but it froze at a point with some message about /Vendor . Screen went black which white LED on.
10) Waited for 30 sec
11) Manual reboot to recovery
12) Wipe dalvik / cache
13) Flash Magisk 15.6.3
14) Wipe dalvik / cache
15) Reboot to recovery
------
16) All Ok
17) Reboot to System
I've been on nitrogenos for half a year. Maybe your could give a try
hyperorb said:
Easy breezy.
Thanks to @[email protected] Upgraded to OOS 5.0.3
1) Backups ( whatsapp, titanium, nandroid)
2) Remove all security - pin , fingerprint
3) Reboot to recovery
4) Upgrade TWRP to 8.6.1 blu_stark
5) Reboot to recovery
6) Full wipe except internal storage
7) Flash OOS
8) Wipe dalvik / cache
-------
9) Flash Magisk 16 (1600). I'm not sure what happened but it froze at a point with some message about /Vendor . Screen went black which white LED on.
10) Waited for 30 sec
11) Manual reboot to recovery
12) Wipe dalvik / cache
13) Flash Magisk 15.6.3
14) Wipe dalvik / cache
15) Reboot to recovery
------
16) All Ok
17) Reboot to System
Click to expand...
Click to collapse
Is this offical Rom?
Yes. I downloaded from OnePlus forums
hyperorb said:
Easy breezy.
Thanks to @qhsusb_bulk @Harsh862 Upgraded to OOS 5.0.3
1) Backups ( whatsapp, titanium, nandroid)
2) Remove all security - pin , fingerprint
3) Reboot to recovery
4) Upgrade TWRP to 8.6.1 blu_stark
5) Reboot to recovery
6) Full wipe except internal storage
7) Flash OOS
8) Wipe dalvik / cache
-------
9) Flash Magisk 16 (1600). I'm not sure what happened but it froze at a point with some message about /Vendor . Screen went black which white LED on.
10) Waited for 30 sec
11) Manual reboot to recovery
12) Wipe dalvik / cache
13) Flash Magisk 15.6.3
14) Wipe dalvik / cache
15) Reboot to recovery
------
16) All Ok
17) Reboot to System
Click to expand...
Click to collapse
Step 9 happens to me everytime I flash OOS/OB. I simply wait for the white led to come on, press the Power button for 8+ seconds and phone switches off. Restart in recovery mode and flash Magisk. This time it will install.
Hi all,
I've installed the AOSP 9.0 GSI A rom and aroma gapps; everything is working great. A new release of the AOSP rom (v115) has been released today.
I initially thought that the update procedure would be to flash the new .img file via TWRP but I found that all of my aroma-installed gapps disappeared after booting.
What's the correct procedure to update my GSI install whilst maintaining my chosen gapps?
I was thinking of flashing the new .img and then flashing the exact same gapps that I installed previously, will the 'reinstalled' gapps maintain their data in this case?
Thank you!
I don't use aroma gapps, I use magic gapps magisk module (with open gapps micro package) but I update whatever gsi I'm using each month when new patch drops and I always just wipe cache, delvik cache, flash new updated system.img, flash magic gapps magisk module, flash no encrypt zip, flash magisk root zip, reboot and my data is all saved and everything is fine.
I'd try the same thing if I were using aroma gapps, just dirty flash like a regular rom dirty install. Pretty sure it would work for you. Just make a backup and if not you can always restore.
flash713 said:
I don't use aroma gapps, I use magic gapps magisk module (with open gapps micro package) but I update whatever gsi I'm using each month when new patch drops and I always just wipe cache, delvik cache, flash new updated system.img, flash magic gapps magisk module, flash no encrypt zip, flash magisk root zip, reboot and my data is all saved and everything is fine.
I'd try the same thing if I were using aroma gapps, just dirty flash like a regular rom dirty install. Pretty sure it would work for you. Just make a backup and if not you can always restore.
Click to expand...
Click to collapse
Thanks for the advice from awhile ago, following this procedure worked for me!.
For anyone else in the same situation, here's what I did:
1) Boot into TWRP
2) Flash latest GSI img
3) Resize system file system (necessary on my device otherwise gapps will not install)
- Wipe -> Advanced -> select system -> resize file system
4) Flash aroma gapps zip
- It remembered my choices from the previous install
5) Flash uncryptable.zip
6) Flash magisk zip
7) reboot