Related
http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
I think is a good idea to say which rom are we using and how xposed works on it. Its still an alpha, and there are many mods that dont work too. Users as @mrnickel have reported that the phone gets REALLY SLOW, and some issues like low memory.
INSTALL (at your own risk) INSTRUCTIONS:
-Make a nandroid backup
-Install apk from the thread link above
-Flash the framework zip from the same thread (updated version, bridge version 61 or up, if you flash 60 it wont work)
-Wipe dalvik cache and cache
-Reboot
Confirmed "working" on 100% stock rooted. [Thanks @jabskii. @Jhyrachy @thdervenis]
Confirmed "working" on TitanPrime ROM (now even better, the dev implemented full support for xposed)[Thanks @pantu99]
All credits to @rovo89
I tried it. Don't do it. I installed from the recovery and this happens:
1st- My cellphone is now broken. Whatsapp won't work.
2nd- My cellphone now tells that I have almost all storage full when it's not possible (see attached screenshots)
3rd- Xposed won't work
oscillat0r.lfo said:
I tried it. Don't do it. I installed from the recovery and this happens:
1st- My cellphone is now broken. Whatsapp won't work.
2nd- My cellphone now tells that I have almost all storage full when it's not possible (see attached screenshots)
3rd- Xposed won't work
Click to expand...
Click to collapse
What Rom?
Whatsapp works for me. But I have those other two bugs...dat storage and xposed doesnt work
Whatsapp started working with a reset. My system lost its date and time.
I set that up again and it's working.
The OS is titanrom with lollipop 5.0.2. The OS is working really really slow right now. It sucks because I installed it before going to vacation, not so wise move.
GUYS! DON'T INSTALL IT!
oscillat0r.lfo said:
Whatsapp started working with a reset. My system lost its date and time.
I set that up again and it's working.
The OS is titanrom with lollipop 5.0.2. The OS is working really really slow right now. It sucks because I installed it before going to vacation, not so wise move.
GUYS! DON'T INSTALL IT!
Click to expand...
Click to collapse
Keep calm, de dont know how doest it goles con Cm12 or 100% stock
I flashed it a first time:
errors with clock and disk space
Then i reflashed it again and wiped cache.
Now it works !
Jhyrachy said:
I flashed it a first time:
errors with clock and disk space
Then i reflashed it again and wiped cache.
Now it works !
Click to expand...
Click to collapse
Did you wipe dalvik too?
Humm, too late now. I will try tomorrow flashing the zip and then wiping cache and dalvik for the lulz
oscillat0r.lfo said:
Did you wipe dalvik too?
Click to expand...
Click to collapse
yes
I installed it and flashed then wiped dalvik and cache and it worked and said it installed. After boot xposed said it was installed but when I rebooted again it says xposed
Framework not installed is anyone else getting this?
Flashed in stock rom got storage bug
Flashed in cm12 no storage bug but module doesn't work and it's not a problem with module.
Just installed on XT1068, stock 5.02.
Wiped Dalvik/Cache
WORKING
Burned Toast
BlackList Pro
Native Freezer
YouTube AdAway
No Safe Volume Warning
XGEL Settings
App Settings
Network Speed Indicator
Ringer and Notification unlink
YouTube Background Playback
Exchange Bypass for Xposed
NOT WORKING
Complete Action Plus
DoubleTapToSleep
Recent Apps Cleaner
Play Store in App Info
XInstaller
APM+
Very happy with Xposed Lollipop so far!
I will continue testing modules. I am sure that pretty soon module developers will bring them up to date with Xposed Lollipop.
Jhyrachy said:
yes
Click to expand...
Click to collapse
100% stock 5.0.2?
laureano97 said:
100% stock 5.0.2?
Click to expand...
Click to collapse
100% Stock + Root
Clean install 5.0.2 with fastboot flash and root. I use TWRP.
I flashed first time, booted, refleshed and wiped cache (both) and then all worked
A lot of modules are still not compatible :/
Please and step-by-step how to install and how to copy files for 5.0.2 stock rom root
Thanks in advance
half269 said:
Please and step-by-step how to install and how to copy files for 5.0.2 stock rom root
Thanks in advance
Click to expand...
Click to collapse
1-Install a custom recovery
2-Make a nandroid backup from recovery (to sdcard1 is better, more free storage I think)
3-Install the apk from here http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
4-Flash the zip from the same thread
5-Wipe cache and dalvik
6-Reboot
In case of bootloop or something gets wrong, boot into recovery and restore the backup you did before flashing
I think its obvious, but all credits to @rovo89
Its working on my XT1068 titan prime ROM
I downloaded the apk and the zip
Installed the apk
And manually installed zip in twrp
After installing I wiped cache/dalvik cache and rebooted. Working flawlessly
This app CPU temp in status bar works but you cannot enter the app. It shows up on my status bar when I enable it on xposed installer .. Other than that this is awesome ! Thanks @laureano97
Sent from my XT1068/69 using XDA Free mobile app
If you guys are having issues like enough storage space or modules not working
1)Flash the zip into your recovery
2)Wipe Cache and Dalvik Cache
That will get rid of your "enough storage space" error
If some modules won't work its because it hasn't been updated for lollipop to work but some modules can work by changing SELinuxMode to permissive
To do that just search "SELinuxModeChanger" in appstore then once installed open it and change it to permissive then reboot your phone.
App Setting is working on my 5.0.2 Stock Lollipop but I tried Greenify and it wouldn't recognize if I installed greenify so it probably hasn't been updated to work in Lollipop and maybe some modules is also the same
OP updated
It seems like the zip rovo89 fisrt uploaded didnt work fine...An hour later he updated it. That was the problem when I flashed it first time. Bridge must be 60 or up
What is signed oos or something like that?
This happens to me every time I flash stock. I've been using a toolkit to restore TWRP.
Here is what I use:
https://forums.oneplus.net/threads/...very-drivers-bootloader-32-bit-64-bit.590277/
This one seems like it has more options for a toolkit:
https://forum.xda-developers.com/on...l-skipsoft-android-toolkit-oneplus-5-t3625419
Are you decrypted?
Flashe the ROM, flash TWRP and flash Magisk in one go (no reboots).
Only reboot after you've flashed all 3.
ckrummi said:
This happens to me every time I flash stock. I've been using a toolkit to restore TWRP.
Here is what I use:
https://forums.oneplus.net/threads/...very-drivers-bootloader-32-bit-64-bit.590277/
This one seems like it has more options for a toolkit:
https://forum.xda-developers.com/on...l-skipsoft-android-toolkit-oneplus-5-t3625419
Click to expand...
Click to collapse
What if I flash the "Signed flashable zips" on this thread via TWRP will it still delete the TWRP?
I normally flash Official Oxygen (full versions, no OTA updates) from TWRP and no issues at all...
flash rom, restart in recocery without restarting system, and flash magisk or superSU
that works for me.
nouse1981 said:
flash rom, restart in recocery without restarting system, and flash magisk or superSU
that works for me.
Click to expand...
Click to collapse
Not needed...
Flash Oxygen (full) from recovery
Go Mount, then umount /system
Flash Magisk
Flash your preferred kernel if any (I recommend Lighting)
Reboot system
bartito said:
Not needed...
Flash Oxygen (full) from recovery
Go Mount, then umount /system
Flash Magisk
Flash your preferred kernel if any (I recommend Lighting)
Reboot system
Click to expand...
Click to collapse
Is there a particular reason to unmount /system?
I did 2 updates without unmounting; it works fine.
Pwnycorn said:
Is there a particular reason to unmount /system?
I did 2 updates without unmounting; it works fine.
Click to expand...
Click to collapse
After flash the Oxygen ROM the /system remains mounted.
At least in my case, Magisk 14.0 installer fails to install if /system is mounted...
I like Lineage OS but the fact the second screen stays on even when locked drains battery even with a custom Kernal. I would love to be stock and rooted but since I DS the boot. I understand flashing stock will get rid of it(maybe I am wrong?). I just want a stock rom or a way to go to stock and stay rooted? is this possible or am I stuck with everyone else?
Yes. There seems to be too good Oreo ROMs out right now. Take a look in the ROMs kernels page
https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
https://forum.xda-developers.com/v20/development/alpha-omega-rom-oreo-vs995-h910-ls997-t3847510
kaluna00 said:
Yes. There seems to be too good Oreo ROMs out right now. Take a look in the ROMs kernels page
https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
https://forum.xda-developers.com/v20/development/alpha-omega-rom-oreo-vs995-h910-ls997-t3847510
Click to expand...
Click to collapse
Thank you, Is alpha Rom hard to install?
stevieshae said:
Thank you, Is alpha Rom hard to install?
Click to expand...
Click to collapse
No. Details should be in the OP
kaluna00 said:
No. Details should be in the OP
Click to expand...
Click to collapse
question, really quick... "partition backup procedure:
** This Is Required To Downgrade Back To Nougat 7.0 **
use a twrp flashable zip for your specific variant that is based on 7.0 nougat
or
download partition backup & restore" what does this mean haha?
stevieshae said:
question, really quick... "partition backup procedure:
** This Is Required To Downgrade Back To Nougat 7.0 **
use a twrp flashable zip for your specific variant that is based on 7.0 nougat
or
download partition backup & restore" what does this mean haha?
Click to expand...
Click to collapse
The first part just means to boot into TWRP recovery and use the backup function preferably with an SD card and then back that up somewhere else. Boot into TWRP, select Backup, make sure Boot, System, and Data are selected (They should be by default) select storage and choose where you want to save the recovery. Then Swipe to Backup, this can take a while.
Once you're done with backing up, should anything go wrong later, you can boot back into TWRP and select the backup using Restore, to go back to your original state at the time of backup.
jackson019 said:
The first part just means to boot into TWRP recovery and use the backup function preferably with an SD card and then back that up somewhere else. Boot into TWRP, select Backup, make sure Boot, System, and Data are selected (They should be by default) select storage and choose where you want to save the recovery. Then Swipe to Backup, this can take a while.
Once you're done with backing up, should anything go wrong later, you can boot back into TWRP and select the backup using Restore, to go back to your original state at the time of backup.
Click to expand...
Click to collapse
Thank you jackson for the fast response, have you tried the rom, and do you like it?
stevieshae said:
Thank you jackson for the fast response, have you tried the rom, and do you like it?
Click to expand...
Click to collapse
I'm currently using Alpha Omega v1.3.0 with my VS995 and it seems pretty good. Unless it's been updated though, the Oreo firmware is missing from v1.3.0. If you're on a ROM that isn't based on Oreo firmware, you need a ROM with Oreo firmware flashed first. I used AO 1.0.7, then clean installed 1.3.0 on top of it. I also had a weird bug with advanced calling getting disabled, but I fixed it and posted the solution in the main AO thread. I think it was a rare issue though on Verizons end. Finally, Magisk Manager was recently updated and no longer supports Magisk versions under v18.0. Since AO v1.3.0 comes with Magisk v17.1 you'll probably have to flash Magisk v18.1 (latest as of right now) to get that working properly.
jackson019 said:
I'm currently using Alpha Omega v1.3.0 with my VS995 and it seems pretty good. Unless it's been updated though, the Oreo firmware is missing from v1.3.0. If you're on a ROM that isn't based on Oreo firmware, you need a ROM with Oreo firmware flashed first. I used AO 1.0.7, then clean installed 1.3.0 on top of it. I also had a weird bug with advanced calling getting disabled, but I fixed it and posted the solution in the main AO thread. I think it was a rare issue though on Verizons end. Finally, Magisk Manager was recently updated and no longer supports Magisk versions under v18.0. Since AO v1.3.0 comes with Magisk v17.1 you'll probably have to flash Magisk v18.1 (latest as of right now) to get that working properly.
Click to expand...
Click to collapse
I cant lock with fingerprint. I came from lineage 7.1(android N) and I dont see anything on how to use fingerprint.... any ideas?
stevieshae said:
I cant lock with fingerprint. I came from lineage 7.1(android N) and I dont see anything on how to use fingerprint.... any ideas?
Click to expand...
Click to collapse
Are you on Alpha Omega now? If you went from a Nougat based ROM straight to Oreo, then you need to make sure the Oreo firmware gets flashed or the fingerprint will not work (There won't even be a fingerprint option in the menu). Clean Install AO 1.0.7 which contains Oreo firmware, then clean install AO 1.3.0 and you should be fine. Note that Magisk is out of date in the ROM and you should also flash Magisk v18.1 as well if you run into an issue with Magisk Manager.
jackson019 said:
Are you on Alpha Omega now? If you went from a Nougat based ROM straight to Oreo, then you need to make sure the Oreo firmware gets flashed or the fingerprint will not work (There won't even be a fingerprint option in the menu). Clean Install AO 1.0.7 which contains Oreo firmware, then clean install AO 1.3.0 and you should be fine. Note that Magisk is out of date in the ROM and you should also flash Magisk v18.1 as well if you run into an issue with Magisk Manager.
Click to expand...
Click to collapse
I cant get texting to work.. or calling? is that because I need to do the flash like you said?
stevieshae said:
I cant get texting to work.. or calling? is that because I need to do the flash like you said?
Click to expand...
Click to collapse
Sounds like you didn't install Alpha Omega 1.0.7 first. I had the same issue when the Oreo firmware didn't get installed coming from Nougat. If you clean install AO 1.0.7 in the install log you should see something about "Flashing prerequisite full firmware" at the beginning. Following the completion of that, you need to follow the same clean install process to flash AO 1.3.0 and you should be good.
jackson019 said:
Sounds like you didn't install Alpha Omega 1.0.7 first. I had the same issue when the Oreo firmware didn't get installed coming from Nougat. If you clean install AO 1.0.7 in the install log you should see something about "Flashing prerequisite full firmware" at the beginning. Following the completion of that, you need to follow the same clean install process to flash AO 1.3.0 and you should be good.
Click to expand...
Click to collapse
So flash AO 1.0.7 then 1.3 by formating data, the wipe dalvic, data, system, and cache. then install twrp and magisk. reboot into recovery. then install 1.3?
Also... Should I install dirty santa kernal?
stevieshae said:
So flash AO 1.0.7 then 1.3 by formating data, the wipe dalvic, data, system, and cache. then install twrp and magisk. reboot into recovery. then install 1.3?
Click to expand...
Click to collapse
First off, you should be rooted with TWRP 3.2.3-4 from here already installed. Then follow these steps:
Clean Install -> Format Data -> Advanced Wipe -> Cache, Dalvik, Data, System
Install 1.0.7 -> Choose the proper kernel for your root method
If you rooted via dirtysanta, choose the mk2000 santa kernel
Reboot to recovery, no need to go to setup
Clean Install 1.3.0 -> Format Data -> Advanced Wipe -> Cache, Dalvik, Data, System
Use the same kernel from above
Flash Magisk v18.1
Wipe Dalvik/Cache
Reboot to System
Download :
https://download.mokeedev.com/dragon.html
Installation:
1 - Boot into TWRP
2 - Wipe system, cache, dalvik and data partitions
3 - Sideload MK100.0-dragon-201912190517-NIGHTLY.zip
4 - Install Opengapps
5 - install Magisk.zip (Optional)
6 - Reboot into system
Thanks. Been meaning to try this.
Problem with getting magisk to install as "system-as-root"
I've tried the unmount/mount system partition
(Update) Also tried manually install of magisk/root/boot.img
And hints?
jamesthedisciple said:
Thanks. Been meaning to try this.
Problem with getting magisk to install as "system-as-root"
I've tried the unmount/mount system partition
(Update) Also tried manually install of magisk/root/boot.img
And hints?
Click to expand...
Click to collapse
Which version of TWRP are you using?
jamesthedisciple said:
Thanks. Been meaning to try this.
Problem with getting magisk to install as "system-as-root"
I've tried the unmount/mount system partition
(Update) Also tried manually install of magisk/root/boot.img
And hints?
Click to expand...
Click to collapse
Same problem here latest builds will not stay rooted using twrp-3.3.1-0
Also if you flash this Rom you should be aware it forces encryption, so not easy to move to another rom afterwards.
Twrp 3.3.1-0.
Root doesn't hold for Lineage 17 or asop10r9 either.
Not worried about encryption for the moment, tend to format data anyway until i can find a longtem "10".
When I have time I'll dive a little deeper. I have a twrp 3.3.1-2 to try out!
Root holds just fine on both below roms
[ROM][OFFICIAL][LineageOS][dragon] - [Lineage/17.0] -> 20191220
[ROM][UNOFFICIAL][PixelExperience][Ten/10.0][dragon] -> 2019/12/12]
I'm running PixelExperience and its solid everything's working good
Markeee said:
Root holds just fine on both below roms
[ROM][OFFICIAL][LineageOS][dragon] - [Lineage/17.0] -> 20191220
[ROM][UNOFFICIAL][PixelExperience][Ten/10.0][dragon] -> 2019/12/12]
I'm running PixelExperience and its solid everything's working good
Click to expand...
Click to collapse
That's good. Was that in twrp, unmount system, mount system, install magisk?
jamesthedisciple said:
That's good. Was that in twrp, unmount system, mount system, install magisk?
Click to expand...
Click to collapse
I didn't even bother with any of the unmount or mount options just formatted but I'm pretty sure just normal wipe will work also flashed PixelExperience then flashed latest Magisk-v20.1 in Twrp 3.3.1-0 no need to install OpenGApps its included in the PixelExperience Rom
Root works normally no issues
Markeee said:
I didn't even bother with any of the unmount or mount options just formatted but I'm pretty sure just normal wipe will work also flashed PixelExperience then flashed latest Magisk-v20.1 in Twrp 3.3.1-0 no need to install OpenGApps its included in the PixelExperience Rom
Root works normally no issues
Click to expand...
Click to collapse
That makes life easier!
Was that the same for the latest Lineage 17?
I'm running a google free pixel C!
jamesthedisciple said:
That makes life easier!
Was that the same for the latest Lineage 17?
I'm running a google free pixel C!
Click to expand...
Click to collapse
I haven't tried the very latest Lineage 17 build but was running the previous build before that and they were close but not quite as stable as PixelExperience Rom
There was no problems with root but the camera wasn't working.
I think i read its fixed in the latest build
Markeee said:
I haven't tried the very latest Lineage 17 build but was running the previous build before that and they were close but not quite as stable as PixelExperience Rom
There was no problems with root but the camera wasn't working.
I think i read its fixed in the latest build
Click to expand...
Click to collapse
Thanks. I now have LO17 latest build and root has held. Looking good.
The donate function is an error
The unique code is alway change when I change my Wifi. This problem make the tablet error. I cannot contract to the manager of Mokee because he uses Weibo
I used to have mokee on my moto x 2104 and this is the reason I will not use mokee without root. Here is a good explaination and a way to get round the problem of "mokee phone home". This works in mokee 9.
https://forum.xda-developers.com/moto-x-2014/general/opinion-x2-oreo-roms-fixes-roundup-t3809622
I have installed this ROM and everything works fine so far. The ads are okay since it is a free service. I can live with it. But one little suggestion for the developer: since this ROM is updated on a nightly basis, could you let us know the changes of each update? No details are necessary, just a couple words would be enough.
Thanks for keeping the development for Pixel C.
Problem with encryption
After installation I have the tablet with data encrypted and I can't use it!
How can I solve?
I use twrp 3.3.1-0
francoscala said:
After installation I have the tablet with data encrypted and I can't use it!
How can I solve?
I use twrp 3.3.1-0
Click to expand...
Click to collapse
Me too.
I use official version twrp-3.3.1-1-dragon.img
Grigori88 said:
Me too.
I use official version twrp-3.3.1-1-dragon.img
Click to expand...
Click to collapse
Do you have a problem with TWRP and decryption?
I been running this rom for a couple of months already theirs been a nightly update every single day rom is solid
The only issues I have is on reboots sometimes the rom gets hang at Google boot screen and the rom fails Safetynet Check ctsProfile in Magisk
Anyone alive in this thread I been running this rom since Dec updating it everyday but I can't seem to get today's 3/13/2020 build to boot past the Google screen any suggestions ?
Everytime no matter what I do after flashing a ROM it eventually stops my calling ability. It calls out but no one. Can hear me and I can't hear them.
What OOS are you using? How are you exactly installing roms, step by step..? What rom installing?? Must have more details to help...
After i see that info ill know more. Possible its a hardware issue but i lean more towards software.. Let me know those things and i can help more.
How I install on OnePlus 6t global (or converted)
Boot twrp v3.5.0
Flash OOS 10.3.7 from repo or updater app
Flash rom (with gapps)
Flash twrp installer zip
Flash finalize
Format data (wipes it ALL)
Reboot recovery
Flash magisk
Reboot system
*Select magisk icon in app drawer and allow update, itll usually auto reboot in 5 secs after it updates..
Without gapps rom install:
Boot twrp
Flash OOS 10.3.7
Flash rom (without gapps included)
Flash twrp installer
Flash finalize
Format data (wipes everything)
Reboot recovery
Flash gapps package
Flash magisk
Reboot system
*Select magisk icon in app drawer and allow update, itll usually auto reboot in 5 secs after it updates..
Use NanoDroid Micro G and Fdroid instead of Gapps on a rom that has sig spoofing and NO Gapps included:
1st part of micro G install:
Boot twrp
Flash OOS 10.3.7
Flash rom
Flash twrp installer zip
Flash finalize
Format data
Reboot recovery
Flash magisk 21.4
Reboot system
Select magisk icon in app drawer and allow update, itll usually auto reboot in 5 secs after it updates..
2nd part of Micro G rom install:
Boot twrp
Install micro g (stable) zip from Nanolx xda thread
Install Fdroid from Nanolx xda
Reboot system
Can also use twrp mauronofrio's 3.4.0-9-11. Those are newest twrp. I've flashed everything made for 6t and never an issue like this. Link to micro g and fdroid installer and more in my signiture.
(Edit)
Hey thanks for the responce, so here we go....
How I flash my roms
Flash OOS 10.3.7/twrp
Reboot recovery
Flash other side of a/b with OOS/twrp
Reboot recovery
Flash rom/twrp installer
Reboot recovery
Flash additional as in my migrate/magisk
Format data
Boot
The Roms I've tried are resurrection remix latest build & msm extended & one other I can't remember which tho. & with stock kernel. I've tried flashing other kernels it doesn't do anything or I'm trying the wrong ones.
Im not new to flashing been doing this for a while now, there's always bugs but there's also ways to fix the bugs. Something interesting is just one time calling it worked fine then the next call... back to no audio feedback. There are 2 other Roms that did the same thing. It happens completely random, like I'll be done modding my phone to my likings go a month or a week & all the sudden no audio. I doubt it's hardware cuz if I format data calls work again but yay all my customizing is gone. I've tried all the suggestions from other forums asking similar question like editing build.prop & a few other things I can't remember nothing's worked. I love this phone to death but it's not easy to keep it stable unless I wanted to go with linegen ROM but ever since they left cyanogen their customizations are lame. Anyways I hope this is enough details I imagine not just let me know thanks I appreciate your help.
I'm no noob but definitely not a master, i use micro g. It's something in the data partition so technically it should be fixable im just sick of re flashing every time it decides it's not a phone anymore just a mini computer that can't compute phone call audio
jessejamesd2i said:
I'm no noob but definitely not a master, i use micro g. It's something in the data partition so technically it should be fixable im just sick of re flashing every time it decides it's not a phone anymore just a mini computer that can't compute phone call audio
Click to expand...
Click to collapse
The only time i experienced similar on my 6t is when i used a sound mod, the zen 5 sound mod from asus phone ported.. It caused me to have this no sound issue but when i disable it via magisk it was fine and i had sound again.
Have you tried going back to OOS 10.3.7 only and see if sound is an issue?
If this is present on OOS i would think its a hardware issue.