Related
Hello,
I installed CM11 on my galaxy s gti9000. All went fine but I get some errors. I tried one nightly build and I constantly got this error: " Unfortunately media manager has stopped." Now with the latest build Download manager isn't working, neither does the gallery. I get a similar error. I can disable those apps but I'll not be able to download apps from google play store. I'm certain that I did something wrong as I'm a newbie in this stuff. Any help?
Hi,
from which version you have installed cm11 ??? Did you wiping cache and data-partition??? Please give us more infos, what you have done ...
Here is a installation-guide:
http://forum.xda-developers.com/showthread.php?t=2526478
paulik123 said:
Hello,
I installed CM11 on my galaxy s gti9000. All went fine but I get some errors. I tried one nightly build and I constantly got this error: " Unfortunately media manager has stopped." Now with the latest build Download manager isn't working, neither does the gallery. I get a similar error. I can disable those apps but I'll not be able to download apps from google play store. I'm certain that I did something wrong as I'm a newbie in this stuff. Any help?
Click to expand...
Click to collapse
I think it was from 2.3 as the tutorial said. It was like a month ago so I'm not sure... Is there anyway I can downgrade to a good version and then install CM11 again? If yes, what version do you recommend me?
freakymod2120 said:
Hi,
from which version you have installed cm11 ??? Did you wiping cache and data-partition??? Please give us more infos, what you have done ...
Here is a installation-guide:
http://forum.xda-developers.com/showthread.php?t=2526478
Click to expand...
Click to collapse
paulik123 said:
I think it was from 2.3 as the tutorial said. It was like a month ago so I'm not sure... Is there anyway I can downgrade to a good version and then install CM11 again? If yes, what version do you recommend me?
Click to expand...
Click to collapse
Actually, downgrade doesn't seem to be necessary in your case. I would on your place first try to install ROM again as "clean installation" and it should work well.
download latest CM11 nigtly ROM
download Gapps from the opening post
paste the files on the root folder of either internal or external SD card of your i9000
reboot to recovery mode
wipe data/factory reset
wipe cache
wipe dalvik cache (under "advanced")
install zip CM11
install Gapps
reboot
enjoy
Any news about your CM11-Installation??? Does it work now with clean-install-tutorial ???
paulik123 said:
I think it was from 2.3 as the tutorial said. It was like a month ago so I'm not sure... Is there anyway I can downgrade to a good version and then install CM11 again? If yes, what version do you recommend me?
Click to expand...
Click to collapse
Hello, sorry for late response. I did a clean install as suggested with the 29 december nightly rom and everything works great now. Before the install, I was getting another error, something with android.process.media has stopped working and I deleted every media file on my internal sdcard because I had lots it (few hundreds I think). I don't know which solution worked but everything works fine now. Thx for the support.
freakymod2120 said:
Any news about your CM11-Installation??? Does it work now with clean-install-tutorial ???
Click to expand...
Click to collapse
No problem, thanks and great to hear that your CM11 now works as desgined :good:
The media-process sometimes makes problems, you can clean data and a few time later it will start again searching for media files ...this should work ...
paulik123 said:
Hello, sorry for late response. I did a clean install as suggested with the 29 december nightly rom and everything works great now. Before the install, I was getting another error, something with android.process.media has stopped working and I deleted every media file on my internal sdcard because I had lots it (few hundreds I think). I don't know which solution worked but everything works fine now. Thx for the support.
Click to expand...
Click to collapse
There is a way to get Marshmallow on the HTC ONE Sprint M7, it's called VanirAOSP ROM. This is a great in most ways, and it's now my daily driver, but be very careful, I almost bricked my phone a few times in setting things up. Here are some tips from what I learned.
Installation instructions (learned from this video, other sources, and hard work):
1) Unlock bootloader.
2) Install custom recovery like TRWP. If you have an old version of TWRP, upgrade it using TRWP Manager or Flashify.
3) Download latest nightly ROM from http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/m7spr/.
4) Download gapps. Biker57 suggests gapps from http://www.emccann.net/dho/5-Gapps/ as it's supposed to cause fewer force closes. I believe 60arm-DHO-GAPPs.zip is the correct file name.
5) Download SuperSU. Biker57 likes SuperSU v2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125.
6) Copy all 3 downloads (in .zip format) to the phone (internal storage, like the TWRP folder)
7) Enter bootloader (volume down and power button), then select bootloader.
8) Backup the current ROM, just in case things go bad like they did for me.
9) From TWRP, enter advanced wipe and select system, data, cache, and dalvik cache. Do not select internal storage as you will lose your current backup and other zips if you do (there is an exception to this, as I did it, but I nearly bricked my phone). Now slide to wipe.
10) Go to install, and first select the ROM's zip. Then choose add more zips and select the gapps zip you downloaded. Next select SuperSU. Now slide to install.
11) Be patient during install.
12) Wipe dalvik cache.
13) Reboot to system (aka phone).
14) Enable Developer Options (if you want), by going to Settings->About and hitting Build Number many times until it's enabled.
Known issues and workarounds:
-Camera app force closes after taking a picture - the picture saves, so just reload Camera app. I've also had good luck using Z Camera then viewing the preview before hitting back to reenter the camera app.
-Stock dialer FCs randomly - Install another dialer app, like True Phone.
-Facebook and Facebook Messenger force closes - use mobile website, which actually isn't too bad, or try the instructions listed here.
-Flashlight turns off after 3 seconds - use the cameras flash instead.
Known issues with no good workarounds:
-FM Radio doesn't work.
-Bluetooth audio doesn't work for phone calls most of the time.
-Switching the battery mode causes the brightness to change randomly - don't ever switch away from balanced mode
Other stuff
-You can find more about the updates made to Vanir ROM here.
-It's risky to play around with the radio, but if you want to try it they are listed here.
-Intersted in supporting Varin, you can donate here.
Please let me know if I missed anything. And feel free to copy freely if it helps others.
***disclaimer - follow at your own risk. I'm not responsible for what might happen to your phone. This is only a cheat sheet, and it's for reference purposes only.***
First off, good tutorial. :good:
Vanir is a great ROM but this Sprint ROM still has a lot of bugs in it. I've used the first Vanir Marshmallow ROM to the most recent and a plethora of bugs have been squashed. But this ROM is still not DD ready, the camera , torch, gapps, browser and settings are broken. I am not saying this ROM is bad, just that its not fully ready yet. Depending on the dev, this rom should be DD ready in 2-3 weeks, they've been releasing more often now. Thank the developer if you know him but if you're the developer, thank you.
We should try to get the dev to see if they can put up a Vanir thread with change logs and the whole shebang.
I'm glad this thread was started and the OP was done well. I've been using this ROM for a while and thought I'd pass along my thoughts and what works for me.
This rom has become my daily driver after learning how to fix a couple of issues. After the latest update of 2/18 the biggest issues of not having a cellular/data connection has been corrected. The only issues that remain for me at least are the camera and Facebook issues. Although the camera does force close it does so for me at least after the picture is taken and saved so it's all good for me. The Facebook issues are corrected by deleting a file in both the Facebook and Messenger file.
The following method works for me without boot loops or any other issues and hopefully will work for you too. I flash these all at the same time loaded in the order listed and don't forget to make a backup before you start just in case.
1 - Flash the 2/18 nightly just like you would any rom http://www.emccann.net/nuclearmistak...ghtlies/m7spr/
2 - flash the gapps found here http://www.emccann.net/dho/5-Gapps/ and select the 60arm file near the bottom.
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125 There are new versions, but the 2.64 has continued to work for me.
4 - Reboot
As I said earlier this works for me and I've used this method with their roms successfully a number of times. Good Luck !!
Thank the developer if you know him but if you're the developer, thank you.
Click to expand...
Click to collapse
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
anotherfakeusername said:
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
Click to expand...
Click to collapse
If you need help with thread stuff I can help, we should start a new thread completely and give it more of a ROM thread look with known bugs, work a rounds and honest opinions on it.
biker57 said:
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I'm not the developer either... Just a happy ROM user
There have been some issues with certain SU not working correctly with 6.0. You can try that but I would advise you to try a proven SU version.
is Snapchat also broken
Sent from my HTC One using Tapatalk
SuperSU 2.65 through TWRP 3.0.0-0
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I didn't install it from the Play Store, I just flashed this version (2.65) through TWRP 3.0.0-0 and it's working as expected :good:
Hello,
Flashing SuperSU through recovery is a better way, atleast for Marshmallow ROMs now. I'm using latest beta version (SuperSU v2.67) without any issues. It can be found in official SuperSU thread here.
As of camera issues, you can use 3rd party camera apps like Camera FV-5, ProShot or etc. Of course they cost few bucks but worth it. Issue doesn't solve totally in this ROM but app doesn't force close, instead freezes for few sec and then works again.
This ROM is my DD and faced no major issues so far. What I'm mostly missing is fast charge feature in kernel otherwise normally it takes plenty of hours to fully charge.
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Thanks...
Best Regards
CRACING said:
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Click to expand...
Click to collapse
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
Their list of gapps is rather long......which one did you use and did you flash it with the rom
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Correct, they have to be flashed with the rom as I mentioned in post 3.
anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
As of OTG, I didn't tested it but usb connection from TWRP to pc for file transfor works fine.
Btw; You are right, ROM is indeed fast.
biker57 said:
Their list of gapps is rather long......which one did you use and did you flash it with the rom
Click to expand...
Click to collapse
Use 60arm-DHO-GAPPs.zip
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Even if you install supersu from playstore, it ask to reboots to recovery to install supersu. But before you accept to reboot, you'll have to enable root access to apps in developer options. Otherwise supersu cannot reboot or go into recovery.
Anyhow, instead of going through all these, I simply flash supersu zip from recovery.
CRACING said:
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
Click to expand...
Click to collapse
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
anotherfakeusername said:
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
Click to expand...
Click to collapse
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Click to expand...
Click to collapse
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
anotherfakeusername said:
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
Click to expand...
Click to collapse
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
CRACING said:
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
Click to expand...
Click to collapse
The problem isn't using Google calendar, the problem is syncing Google calendar. I tried waiting, rebooting, re-adding my account, and everything else, but that didn't help.
Only downgrading Google Play services worked, and then Google calendar synced right away.
Thanks for the suggestions. Hopefully as they update the ROM it'll get resolved more fully.
Im trying to get viper4android installed on stock kernel (t817t). Ive searched high and low. All attempts have failed. I have switched the kernel to permisive, flashed all the build prop mods.
Has anyone got it to work?
Sent from my SM-T817T using Tapatalk
llawen said:
Im trying to get viper4android installed on stock kernel (t817t). Ive searched high and low. All attempts have failed. I have switched the kernel to permisive, flashed all the build prop mods.
Has anyone got it to work?
Sent from my SM-T817T using Tapatalk
Click to expand...
Click to collapse
Did you gave it storage permission on Application Manager?
follow these instructions, i did and have it working on both my Tab S2 and S7 Edge
http://www.droidviews.com/enjoy-viper4android-on-galaxy-s6-and-s6-edge/
I flashed one of the v4.8 zips from this thread http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075 (I think it was the Beats Universal version near the bottom) and V4A works great. Dolby Atmos isn't working however, fc every time I open it. I think it's fixable but I haven't really messed with it because I don't listen to music on my S2 very often and I'm happy with just Viper.
Flash this
Same for me, I did a lot of things just with no luck. So I decided to make a factory reset, clean install the new MM update trough Odin, then install TWRP and flash SuperSu zip.
Then I found this THREAD made for the s7 and found this ZIP inside the replies, the flashed it and worked like a charm.
Instructions to install a working V4a (pay attention because it's extremely difficult):
1-> Hard factory reset. (just take the tab back to stock)
2->Update to MM with odin if u want (I don't know if it works on Lollipop)
4->Flash TWRP through Odin
5->Flash SuperSu through TWRP (this will root the tab)
6->Install Busybox from Google play
7->Flash this zip through TWRP.
5->Done
Not difficult, just joking.
Let me know if it worked for you. If you need more instructions about installing MM just go to my post if you want.
miguimercadob said:
Same for me, I did a lot of things just with no luck. So I decided to make a factory reset, clean install the new MM update trough Odin, then install TWRP and flash SuperSu zip.
Then I found this THREAD made for the s7 and found this ZIP inside the replies, the flashed it and worked like a charm.
Instructions to install a working V4a (pay attention because it's extremely difficult):
1-> Hard factory reset. (just take the tab back to stock)
2->Update to MM with odin if u want (I don't know if it works on Lollipop even )
4->Flash TWRP through Odin
5->Flash SuperSu through TWRP (this will root the tab)
6->Install Busybox from Google play
7->Flash this zip through odin.
5->Done
Not difficult, just joking.
Let me know if it worked for you. If you need more instructions about installing MM just go to my post if you want.
Click to expand...
Click to collapse
Works fine
Sent from my SM-T710 using XDA-Developers mobile app
miguimercadob said:
Same for me, I did a lot of things just with no luck. So I decided to make a factory reset, clean install the new MM update trough Odin, then install TWRP and flash SuperSu zip.
Then I found this THREAD made for the s7 and found this ZIP inside the replies, the flashed it and worked like a charm.
Instructions to install a working V4a (pay attention because it's extremely difficult):
1-> Hard factory reset. (just take the tab back to stock)
2->Update to MM with odin if u want (I don't know if it works on Lollipop even )
4->Flash TWRP through Odin
5->Flash SuperSu through TWRP (this will root the tab)
6->Install Busybox from Google play
7->Flash this zip through odin.
5->Done
Not difficult, just joking.
Let me know if it worked for you. If you need more instructions about installing MM just go to my post if you want.
Click to expand...
Click to collapse
Finally this worked for me on the first hit, after spending hours installing other v4a releases.. .
(not flashed the zip with odin.... Flashed it in TWRP)
Thanks!
miguimercadob said:
Same for me, I did a lot of things just with no luck. So I decided to make a factory reset, clean install the new MM update trough Odin, then install TWRP and flash SuperSu zip.
Then I found this THREAD made for the s7 and found this ZIP inside the replies, the flashed it and worked like a charm.
Instructions to install a working V4a (pay attention because it's extremely difficult):
1-> Hard factory reset. (just take the tab back to stock)
2->Update to MM with odin if u want (I don't know if it works on Lollipop)
4->Flash TWRP through Odin
5->Flash SuperSu through TWRP (this will root the tab)
6->Install Busybox from Google play
7->Flash this zip through TWRP.
5->Done
Not difficult, just joking.
Let me know if it worked for you. If you need more instructions about installing MM just go to my post if you want.
Click to expand...
Click to collapse
Thx so much! Worked perfectly. Although all i did was search for the file name on Google (cuz the owner of the file had it in his trash bin) and flash w twrp cuz my rom is still stock and I had already done everything else long ago.
If any future ppl need the file, here it is: http://d-h.st/YKOZ
And if that link turns up dead eventually, search this file name on Google, there should still be one out there somewhere
ViPER4Android_FX_A4_6.0.1_New
7.1.1 anyone ?
hello dudes!
the file from above worked perfectly on 6.0.1 for me
just updated to 7.1.1 and as expected this version doesn't work on 7.1.1
anyone out there who managed to get viper working on 7.1.1
ROM on SMT810
https://forum.xda-developers.com/tab-s2/development/rom-resurrection-remix-t3508176
Thanks !
SOLVED !
Viper installation zip
&
this Busybox works aswell, if you are not on x86
from original post
BTW : damn ugly UI
Source: https://forums.oneplus.net/threads/...s-starting-on-oneplus-3.454469/#post-15056543
Usual 48h to hit devices thing is probably in effect here swell but i'm sure the VPN trick will work for most if you're impatient or waiting for this fix for your SIM issue.
The changelog seems to have added just the SIM fix but for some reason the changelog on the phone says there's more Notification fixes but have to wait and see on that
Here are some of the highlights:
Fixed some notification issues
Addressed SIM recognition issue
Enabled sRGB mode in developer options
Improved RAM management
Improved GPS performance
Enhanced audio playback quality
Updated custom icon packs
Improved camera quality/functionality
Fixed some issues in Gallery
Implemented latest Google security patches
Fixed bugs in Clock/Music apps
Thanks to @Patschi_ for the links
OTA file
http://otafs1.coloros.com/patch/ama...010-011_patch_1607052050_0e5983ace5314161.zip
Edit: MIrror:
http://www43.zippyshare.com/v/9NUHWPJ3/file.html
Edit2:
Full ROM
http://otafs.coloros.com/patch/amaz...6_OTA_011_all_1607052050_0e5983ace5314161.zip[/QUOTE]
Full ROM Mirror (Soon)
deleted.
The direct link, if anyone is interested in:
OTA file
http://otafs1.coloros.com/patch/ama...010-011_patch_1607052050_0e5983ace5314161.zip
Edit: MIrror:
http://www43.zippyshare.com/v/9NUHWPJ3/file.html
Edit2:
Full ROM
http://otafs.coloros.com/patch/amaz...6_OTA_011_all_1607052050_0e5983ace5314161.zip
Edit3:
Mirrors for all updates and ROMs are available here:
http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
already installed 3.2.0. and its working very well
should i need to update again for 3.2.1
JumboMan said:
already installed 3.2.0. and its working very well
should i need to update again for 3.2.1
Click to expand...
Click to collapse
no notification issues?
Patschi_ said:
The direct link, if anyone is interested in: (OTA file)
http://otafs1.coloros.com/patch/ama...010-011_patch_1607052050_0e5983ace5314161.zip
Edit: MIrror:
http://www43.zippyshare.com/v/9NUHWPJ3/file.html
Click to expand...
Click to collapse
Thanks for this do you mind if I add them to the OP? not that people shouldn't see your post just might be easier i'll give credits swell.
JumboMan said:
already installed 3.2.0. and its working very well
should i need to update again for 3.2.1
Click to expand...
Click to collapse
Might swell the Changelog states there's Notification issue fixes as well but still waiting to see if that's true.
Roxas598 said:
Thanks for this do you mind if I add them to the OP? not that people shouldn't see your post just might be easier i'll give credits swell.
Click to expand...
Click to collapse
Feel free to add it to the OP
Downloading the Full ROM right now to provide a mirror... could take a while as the download servers are quite slow right now.
mirrors will be provided here aswell I think: http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
daClaus said:
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
Click to expand...
Click to collapse
Are you using the System Update option on the phone to install or the Zip file? either way normally any changes to the system will make OTA fail (like root and xposed)
daClaus said:
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
Click to expand...
Click to collapse
Actually no. You don't have to unroot but you need to flash stock boot.img . Better option always is to flash Full 3.2.0 ROM twice (sometimes first flash doesn't succeed) and then 3.2.0 -> 3.2.1 OTA immediately and then SuperSU and Xposed. Or wait for Full ROM mirror. Will take me some 20 minutes more. I am downloading it at the moment.
Yes, I tried to install the downloaded ota file via TWRP. Guess I have to download the whole 1.2 GB to get the 15MB update.
---------- Post added at 02:37 PM ---------- Previous post was at 02:33 PM ----------
Naman Bhalla said:
Better option always is to flash Full 3.2.0 ROM twice (sometimes first flash doesn't succeed) and then 3.2.0 -> 3.2.1 OTA immediately and then SuperSU and Xposed.
Click to expand...
Click to collapse
Thank's for the hint! Had the 3.2.0 file on my phone and did it this way.
Sledge2013 said:
no notification issues?
Click to expand...
Click to collapse
can you explained it in detail.which notification issues?
Sorry for the question, just to be clear:
I install the full ROM in twrp, install it again without rebooting and after that immediately SuperSU?
Do I have to wipe Cache/Dalvik?
After that I reboot and all the apps are still there?
Spotted this and just VPNd it my self.
Fingers crossed i get less drain over night
Der-Knuffi said:
Sorry for the question, just to be clear:
I install the full ROM in twrp, install it again without rebooting and after that immediately SuperSU?
Do I have to wipe Cache/Dalvik?
After that I reboot and all the apps are still there?
Click to expand...
Click to collapse
If you install the full 3.2.1 rom just install it once, then supersu and THEN wipe cache/dalvik. Your apps will be still there he just needs to optimize them at the start(might take 10 minutes).
If you want to use this "trick" to install 3.2.1 OTA over a 3.2.0 full rom, i have no clue. But i would rather install the full rom. I tried it with the OTA last time and it didn't worked.
eikaramba said:
If you install the full 3.2.1 rom just install it once, then supersu and THEN wipe cache/dalvik. Your apps will be still there he just needs to optimize them at the start(might take 10 minutes).
If you want to use this "trick" to install 3.2.1 OTA over a 3.2.0 full rom, i have no clue. But i would rather install the full rom. I tried it with the OTA last time and it didn't worked.
Click to expand...
Click to collapse
Ok, thanks. That's the way I used to do it since years, but I'm new to OnePlus 3, so ...
Der-Knuffi said:
Ok, thanks. That's the way I used to do it since years, but I'm new to OnePlus 3, so ...
Click to expand...
Click to collapse
me too. coming from nexus 5 some things definitely changed for us flashoholics
flashed over 3.2.0, no issues so far. supersu, xposed, adaway all is working fine.
daClaus said:
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
Click to expand...
Click to collapse
daclaus, you have to install the complete rom via twrp, after that you have to install root and xposed again. ota will not work with twrp.
Hi
In latest open beta with Magisk 15.3 , used debloater and made space in system , but on flashing anything no error is there but nothing shows in app drawer , same is happening with Magisk also . Managed to flash viper but the drivers are not getting installed showing io error while same works fine for others without manual driver installation, no idea what's wrong !!!!
Yikes. Sounds like something is glitched in there. Try wiping : system and cache ( only )and reloading the rom and then rebooting into recovery and then booting up in system.
.
If it's still glitched ( ugg ) then its wipe all ( less external data ) and factory reset and start over.
.
Um, did you make yourself a nandroid backup ?
AKHIL.cochin said:
but on flashing anything no error is there but nothing shows in app drawer.
Click to expand...
Click to collapse
What do you mean by this? Do you mean that you don't see any apps after flashing a Magisk module? Many modules don't install any apps and you either don't have to do anything to configure or run a terminal command. What modules are you talking about?
Managed to flash viper but the drivers are not getting installed showing io error while same works fine for others without manual driver installation, no idea what's wrong !!!!
Click to expand...
Click to collapse
That's a known issue with V4A on OxygenOS Oreo. Some don't experience it though, which is incredibly frustrating...
Also what version of twrp r u using
old_fart said:
Yikes. Sounds like something is glitched in there. Try wiping : system and cache ( only )and reloading the rom and then rebooting into recovery and then booting up in system.
.
If it's still glitched ( ugg ) then its wipe all ( less external data ) and factory reset and start over.
.
Um, did you make yourself a nandroid backup ?
Click to expand...
Click to collapse
did a clean flash and checked , its still there , no idea whats wrong ..
Bradl79 said:
Also what version of twrp r u using
Click to expand...
Click to collapse
twrp-3.2.1-0
Didgeridoohan said:
What do you mean by this? Do you mean that you don't see any apps after flashing a Magisk module? Many modules don't install any apps and you either don't have to do anything to configure or run a terminal command. What modules are you talking about?
That's a known issue with V4A on OxygenOS Oreo. Some don't experience it though, which is incredibly frustrating...
Click to expand...
Click to collapse
" not only magisk , have u read my post , on flashing arise magnum on twrp also gave no errors and i selected viper , dolby , dolby atmos , xperia music etc and all flashed fine but none was showing in there thats what i have mentioned i also tried many viper and dolby modules in magisk , nothing s working "
AKHIL.cochin said:
" not only magisk , have u read my post , on flashing arise magnum on twrp also gave no errors and i selected viper , dolby , dolby atmos , xperia music etc and all flashed fine but none was showing in there thats what i have mentioned i also tried many viper and dolby modules in magisk , nothing s working "
Click to expand...
Click to collapse
Yes, I did read your post, but it was lacking in detail so I needed to ask some clarifying questions. Unfortunately, your answer is also somewhat lacking in detail...
But, I'm guessing you're trying to install some audio mods. V4A isn't working properly on OOS Oreo for the OP3T. A few users have it running fine, but it seems like those are a minority.
There are not that many Dolby mods that work on Oreo yet, so you might have to look around a bit to find one that does. There'll most likely be some more readily available soon though.
Didgeridoohan said:
Yes, I did read your post, but it was lacking in detail so I needed to ask some clarifying questions. Unfortunately, your answer is also somewhat lacking in detail...
But, I'm guessing you're trying to install some audio mods. V4A isn't working properly on OOS Oreo for the OP3T. A few users have it running fine, but it seems like those are a minority.
There are not that many Dolby mods that work on Oreo yet, so you might have to look around a bit to find one that does. There'll most likely be some more readily available soon though.
Click to expand...
Click to collapse
THE FRUSTRATING THING S ITS WORKING FOR ALL THE OTHERS WITHOUT ANY ISSUES IN SAME ROM KERNEL COMBO
AKHIL.cochin said:
THE FRUSTRATING THING S ITS WORKING FOR ALL THE OTHERS WITHOUT ANY ISSUES IN SAME ROM KERNEL COMBO
Click to expand...
Click to collapse
Yes, it's frustrating, but there's no need to shout. And it does NOT work for everyone else. I haven't had an audio mod working properly on my OP3T since updating to OOS 5+...
It works for some, but not for others. You could try the OOS beta. It seems like some have better luck with that.
Either you try to help, if possible, or you change to a working ROM combo, or you wait until someone finds a fix.
I had a problem that some modules wouldn't activate (they install successfully, but after reboot I would still see "module will be updated at next reboot"). As I didn't have time and will to debug this, I reverted to OOS 4.5.1.