Related
I've been seeing constant complaints around the OnePlus 3's development section of the forums regarding an unusual high CPU usage and massive battery drain on different ROMs. These reports are posted in the custom kernels thread.
flar2's ElementalX kernel thread (now locked unlocked):
[link removed]
eng.stk's blu_spark kernel thread:
[link removed]
The reports mostly state that "(insert kernel name) gives high CPU usage, battery drain, etc." flar2 and eng.stk both say it's not the kernel, yet every custom ROM seems to have issues with this strange "bug". Even stranger, it only affects some users.
So what gives?
To preface, I'll be as verbose as I can about my experience with this: I had this exact issue with the CPU nearly maxing out and massive battery drains on LOS/AOSP-based ROMs. I clean-flashed Resurrection Remix, DU, Citrus, and CypherOS, and I even tried flar2's EX kernel, blu*spark, and stock kernel that ships with the ROMs; every one of them had this problem. On average, I use my phone daily, but not really heavily (I don't play games, but I either web browse, Youtube, or calling/text), so I found it odd that my phone's battery drops from 100% to 72% every time I get up in the morning and down to 15% after only 2 hours of using my phone. I thought this was strange since I never had this problem before. I checked my phone's battery stats (Settings -> Battery) and didn't find anything strange. I blamed CM/LOS and switched to AOSP, same issue. From there was a full day and half of switching ROMs, swearing, and confusion. What I should've done from the start was check the logcat because the solution was literally written all over the logcat.
Something related to the modem was silently crashing in the background.
It would restart again and again, crashing every 5-10 seconds or so. It would comment something about com.phone.android - I forgot to save a screenshot of the message
but nevertheless this error was 5-6 lines long and was scattered all over the logcat. Again, silent crash: no (processes) has stopped, unfortunately, (processes) has stopped, etc). This would explain why my device never entered deep sleep and sky-rocketed the CPU frequency.
To conclude, I firmly believe the high battery drain and CPU usage is actually caused by Oxygen OS's 4.0.x firmware, NOT THE KERNEL. When I switched to 3.2.8 firmware or 3.5.5CE my issue was completely fixed - 10 hours of SOT and very good performance using the EX kernel +AKT combo. I think the reason why some people have this problem and others don't is because they're on different firmwares. Through testing, 4.0.x has these problems whereas 3.5.5CE and 3.2.8 does not.
I want to note that I did not test stock Oxygen OS. The firmware downgrade solution may also not work for you - hence why the thread's title name is "a potential fix". Some users on FreedomOS, Experience, or other custom Oxygen-based ROMs have reported two approaches to fix battery and CPU usage:
The modem/phone errors on firmware 4.0.x could be limited to custom AOSP/LOS ROMs. Using an older firmware may cause Oxygen OS Nougat to not boot anymore, so backup everything and make sure you have a restore point before trying my fix.
TL;DR: This is NOT a kernel issue. Don't blame flar2, eng.stk, or anyone but OnePlus. I believe this is a bug in OnePlus' Nougat firmware. Until OnePlus fix this, I urge everyone to flash either 3.2.8 or 3.5.5 firmware and see if the High CPU usage and battery drains are gone on custom AOSP/LOS ROMs. You can try downgrading firmware on Oxygen OS - but please backup and make a restore point if the ROM does not boot (I did not test stock Oxygen OS). If you're on Oxygen OS, I suggest you try using phhh's root and changing SELinux Policy to permissive first (though SELinux should be enforced) before downgrading firmwares. OnePlus needs to fix their unstable firmwares (and release Camera blobs, etc)!
STEPS:
0. If you're on Oxygen OS, try phhh root and changing SELinux policy to permissive first. If that doesn't work, or if you're not on Oxygen OS, go to the next step.
1. Go to jamal's firmware/modem collection: (link removed)
2. Click the Android 6.x button.
3. Click link to download Firmware + Modem zip 3.2.8 OR 3.5.5CE (I recommend 3.2.8).
4. Flash in TWRP recovery (any recovery version works).
5. Reboot and enjoy better battery life and no high CPU usage
5a. If you set a lockscreen with PIN, chances are that you won't be able to get pass the lockscreen; in that case, reboot back to TWRP recovery, mount /system, use the built-in filemanager to navigate to /data/system, and delete the 5 gatekeeper/lockscreen files.
5b. If your ROM kernel panics after flashing firmwares (screen suddenly goes black, reboots), delete the init.d folder.
UPDATE:
I've been doing some testing with the OOS 4.0.x firmware and I think I found out the issue!
I kept getting the same battery drain on LOS/AOSP-based ROMs. Reading the thread, it seems hardly anybody has this issue on newer firmwares. At first, I thought it was an F2FS issue. I started from scratch by wiping everything (including the internal storage), changed the /data partition to ext4, and upgrading TWRP. When I booted the ROM afterwards and let my phone sit for a few hours, I still had that strange error with the CPU behaving abnormally and battery drain. So I took to the logcat and started searching.
The error that generated heat and battery drain from OOS 4.0.x's firmware is the following:
Code:
Sending non-protected broadcast com.android.imsconnection.DISCONNECTED from system 2019: com.android.phone
com.android.phone? That's familiar....remember how I said in the OP it was a modem issue? But just above the error has this message:
Code:
ImsSenderRxr : Response data: [12, 13, -1, ...
That's Enhanced 4G LTE Mode! All I needed to do was flip the switch OFF and viola! All errors gone, CPU stable and minimal battery drain. Oxygen OS does not error out like this, so I'm certain this "issue" is exclusive to just LOS/AOSP.
Looking at the OP I realize how silly this thread is. I could've just attached the logcat into the Q/A thread and asked for help, done deal. My apologies everyone. If you downgraded the firmware to try this "fix", upgrade back!
For people running Oxygen/Freedom/Experience OS: if you have drain, this fix still applies to you:
Use phh's superuser instead of SuperSU
Using the command:
Code:
su
setenforce 0
or using init.d scripts to change SELinux's policy to permissive
If /data is F2FS, try changing it to EXT4
I'm open to discussion - did this solution work for you? Anyone try this on Oxygen OS? Or perhaps you have a different solution? Comment below, or use the poll! That will help me when I create future OP threads
Instead of complaining appreciate the efforts of eng.stk and flar2. Some are spoonfeed they don't want to search. Thank you for posting this!
madsponge26 said:
Instead of complaining appreciate the efforts of eng.stk and flar2.
Click to expand...
Click to collapse
To the contrary. I really appreciate their work for the OnePlus 3. They're extremely talented developers that I definitely look up to. I just blame OnePlus for the bugs
madsponge26 said:
Some are spoonfeed they don't want to search.
Click to expand...
Click to collapse
I completely agree with this, and it's sad, really. I remember when new XDA members were collaborating with developers and innovating (sorry, Apple). Now it seems like too many members are treating XDA like a technical support site.
madsponge26 said:
Thank you for posting this!
Click to expand...
Click to collapse
You're welcome
I've had this issue as well. I went from Experience Rom to Stock 4.0.2 since when I used Xceed the CPU load didn't go below 60%. But this is not a kernal issue.
I have flashed the 3.2.8 firmware+modem over OB11 and did not experience any bootloops. We'll see how battery fares.
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
peshellas said:
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
Click to expand...
Click to collapse
Well I tried this fix and it doesn't seem to work.. I'm currently on Oos 4.0.2 rooted and bluspark r32 kernel and I still have the hand warmer.. Heat is just reeks from all parts of phone :/
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
sarus_b said:
Well I tried this fix and it doesn't seem to work.. I'm currently on Oos 4.0.2 rooted and bluspark r32 kernel and I still have the hand warmer.. Heat is just reeks from all parts of phone :/
Click to expand...
Click to collapse
When you send the su command did it ask you, and you gave root permissions? Also if you use ARISE you must go to titanium backup and freeze an app called something like arkansysaudio, my spelling might be little off. I clean flashed Experience 10.1 then bluespark r32, then magisk and then phh root for magisk(latest) all was perfect but there was heat etc, after the nevax1 solution that was also gone. Phone is now perfect and passes safetynet security (snapchap, pay, etc)
Edit: In order to use magisk and phh root, you must completely remove supersu(it has an option in the app). So best way should be
0.flash the twrp 3.0.4
1.Flash rom
2.Flash bluspark r32
3.Reboot
4.Extract stock boot.img feom the rom you flash(open it via file Manager, its the first file you see)
5.Go to SuperSU app settings and completely remove it, and say no when it asks to restore boot.img
6.reboot to recovery
7.select install and change to image install, choose the boot.img you extracted and flash it in boot partition when it asks.
8. Flash kernel
9. Flash latest magisk(10.2 at the moment)
10. Flash latest "phh for magisk"
11.reboot
12. Install phh app from play store
13.open magisk and it should ask for root via phh Interface and then show you that magisk a d root are functional (you can test safetynet security on there too with one button)
14. Open terminal and run "su"( it will ask permission), and after that run "setenforce 0"
15. Profit, all should be perfect and you can enjoy it even safetynet free
Optional: download AKT PROFILES 1.2 app(not zip) and install. Run it give it root, and restart it. After that run it choose ballanced or battery saving profile of your choice for even greater battery and smoothness.
peshellas said:
When you send the su command did it ask you, and you gave root permissions? Also if you use ARISE you must go to titanium backup and freeze an app called something like arkansysaudio, my spelling might be little off. I clean flashed Experience 10.1 then bluespark r32, then magisk and then pph for magisk(latest) all was perfect but there was heat etc, after the nevax1 solution that was also gone. Phone is now perfect and passes safetynet security (snapchap, pay, etc)
Click to expand...
Click to collapse
Yes there was a prompt, obviously I won't be using kernel without being rooted..
Anyway I don't use any mods you mentioned yet the problem is still there... It has just decreased now.. Now it depends on my phones mood when to start heating up..
Same here, after the workaround I can't feel that much the heat but the drain is clearly there. Android System was taking 45% of the drain. Using FreedomOS with blu_spark kernel and no mods except Adaway.
peshellas said:
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
Click to expand...
Click to collapse
Yup, I have that in the OP.
lxxs said:
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
Click to expand...
Click to collapse
Like I wrote in the OP, I do not recommend changing the SELinux policy. I also mentioned in the OP that I did not test Oxygen OS, reason being that OOS 4.x seems like a rushed product (so I put no time investing to flash OOS). Since I haven't flashed OOS, I wrote on the bottom of the OP if anyone has modem errors popping up in the logcat. My "fix" is to simply downgrade to a stable firmware (3.2.8 preferably).
Looking at the comments so far, I think Oxygen OS may not be affected by the modem bug. I'll wait and see what people write in the comments and will edit the OP if necessary. Maybe try flashing the firmware, then clean flash the ROM?
EDIT: I just edited the OP so the phhh root workaround is more visible!
lxxs said:
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
Click to expand...
Click to collapse
Yes he doesn't recommend it for safety reasons, but it is far worse to run the phone in a max cores overheating state, it will at some point damage the motherboard and other components. So either this for now or downgrade to another version. Also people with stock op rom have it too, not all though, same with custom roms guys, not all face the issue. And im also suspecting it cam be related yo the kernels not managing selinux properly, but again, some people with custom kernels said ot worked out of the box.
---------- Post added at 10:54 AM ---------- Previous post was at 10:52 AM ----------
sarus_b said:
Yes there was a prompt, obviously I won't be using kernel without being rooted..
Anyway I don't use any mods you mentioned yet the problem is still there... It has just decreased now.. Now it depends on my phones mood when to start heating up..
Click to expand...
Click to collapse
Try all steps, they are not mods, its alternative root. I just did all those as mentioned exactly and problem is gone, I spent hours to come down to this. :fingers-crossed:
After writing:
su
setenroce 0
shall i get any feedback message? or just a new line to write a command?
Hello OP, thanks for getting this point out. I never liked blaming on things which we use for free , plus the devs put a lot of effort.
I have few questions. I'm kind of novice.
I'm on Experience ROM v9.6 with SuperSu 2.78 and modified twrp.
Can I flash the 3.5CE modem over it? I'm kind of scared with Op3.
I don't have anything beside it.
Thanks
AvivEliyahu said:
After writing:
su
setenroce 0
shall i get any feedback message? or just a new line to write a command?
Click to expand...
Click to collapse
There won't be any feedback, but if you go into Settings and to About Phone, then scroll to the bottom, you'll see that SELinux policy changed from "enforcing" to "permissive".
shubhaemk said:
I'm on Experience ROM v9.6 with SuperSu 2.78 and modified twrp.
Can I flash the 3.5CE modem over it? I'm kind of scared with Op3.
Click to expand...
Click to collapse
Try using phh root and changing SELinux first before downgrading the firmware. Don't worry about hard-bricking your OnePlus 3 - I've done bad things like flashing a OnePlus 3t version of custom ROMs (not unified) and I got out of it
Instead of updating old firmware and all, try the following to fix the issue permanently. Will persist across reboots as well -
Extract ElementalX / blu_spark kernel zip
append the following to cmdline parms
Code:
androidboot.selinux=permissive
Repackage and flash from TWRP
File is present at following location in the either zips -
ElementalX - boot/cmdline.sh
blu_spark - kernel/blu_spark_tweaks.sh
Before
Code:
androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237
After
Code:
androidboot.hardware=qcom user_debug=31 androidboot.selinux=permissive msm_rtb.filter=0x237
Its possible swith this with seLinuxModeChanger
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
Hey @kentexcitebot.
U really saved up many ppl's life with this...
After applying Ur fix my overnight drain is 1-2%, unlike b4 when it was >15%.
It really works , I really appreciate Your work.
Currently my device running Freedom Os 2.2, no kernal, only magisk+phh super su.
and battery is awesome .
Thanks,
Cheers!!!!!!!!!!!!!!!!!
I am using RR build 20170116 and firmware 4.0.2. Never had this problem. It occasionally does not go to deep sleep after screen off. Clear data of Google Play service or reboot always fix the problem.
How can I explain it if there's a problem with firmware 4.0.x?
Hello all.,,
I checked and read many thread slowly and steadily ,but couldn't find a good solution to root this phone 3T.
I just bought this Beautiful Device runing so smooth but with Hands tied too hard unable to run many apps and many ads and Bloatwares..
Thought to Root this device ,but all are mostly either Oxygen 3 or Marshmallow or 7.0. Version of ANdroid..and DW Error,is also a major concern to look out..
So Please help me to root this device running O2 4.1.1 (I literally dont want to change the stock,as of now) and Android 7.1.1 ,some simple steps...
Thanks and Regards
Awaiting for replies!!
I'm about to get this phone so I've been doing a lot of research myself. It looks like you can follow the steps in this thread and you can flash supersu through TWRP once you've unlocked the bootloader.
Unlock bootloader.
Flash TWRP.
Flash your preferred root zip in TWRP (SuperSU or Magisk are two good choices, I prefer Magisk).
That's about it...
i too tried the above method,,But I got struck with Logo of TWRP and got enabled only after 6 Hours.. But to my fate,,i'm still running on Stock recovery.. Not on TWRP !!
Use the latest official TWRP (currently 3.1.0-1). Works just fine.
i can relate to your question.
however, i discovered how to root the 3t and flash the usual zips files the finally the freedom rom, on my own.
it was a thrill.
i advise you to just take the blue pill.
I installed Blusparks Version of TWRP ,,but still no use,,SuperSU or Magisk both says My phone is not rooted!!!!
I want to live the Stock ROM and just to root the device,,But the steps are not futile for me!
What I would do if i was you.
Unlock bootloader
Flash TWRP
Flash latest Magisk 13.2 zip
Hey,
Is this method still valid for rooting the 3T?
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Yes, that is still valid, more or less. Might be a more current version of blue_spark's TWRP (official TWRP is on 3.1.1.2) although the link only says 3.1.1-x, so I don't know what that means. But probably won't make a huge difference.
Can't see what version Magisk is linked (my office network is blocking the link). If you choose Magisk, flash latest version 13.3, especially if you want to hide root (from Snapchat, banking apps, etc.). Older versions of Magisk will fail to hide, due to recent changes Google made to SafetyNet.
And what if we want to flash this beta to a brand new device?
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_12/
Should we first unlock the device, then install the TWRP recovery, then flash this beta rom and then root?
I've always used SuperSu on my previous devices. I just got my OP3T about a month ago. I was running SuperSu until I got the OOS 4.5 update 2 days ago. I did a full wipe and started from scratch. I decided to try Magisk. So far it's been awesome. Stock ROM.
I've been trying to search for an answer but haven't found a clear one.
I want to upgrade to a custom kernel. Franco to be exact. I want to be able to use DriveDroid, and I've read that this kernel enables the functionality it needs.
Will I lose AndroidPay and other non root features / break Magisk by flashing a new kernel? What do I need to do? Is there any prep, or can I just flash it and be good to go?
Just flash the kernel first and then the latest magisk zip and your good to go.
spotopolis said:
I've always used SuperSu on my previous devices. I just got my OP3T about a month ago. I was running SuperSu until I got the OOS 4.5 update 2 days ago. I did a full wipe and started from scratch. I decided to try Magisk. So far it's been awesome. Stock ROM.
I've been trying to search for an answer but haven't found a clear one.
I want to upgrade to a custom kernel. Franco to be exact. I want to be able to use DriveDroid, and I've read that this kernel enables the functionality it needs.
Will I lose AndroidPay and other non root features / break Magisk by flashing a new kernel? What do I need to do? Is there any prep, or can I just flash it and be good to go?
Click to expand...
Click to collapse
Android Pay should be affected by Magisk, not by the custom kernel.
And since you say that u had custom kernels before, you should already know that the installation of custom kernels doesn't affect the root.
Unleashed by ONEPLUS 3T rooted
Magisk hide will allow you to use Android Pay, it'll be in the settings.
Root will still work great too, I've used it for ages, never had an issues.
RASTAVIPER said:
Android Pay should be affected by Magisk, not by the custom kernel.
Click to expand...
Click to collapse
If the kernel is not prepared to hide boot flag, then it'll definitely affect SafetyNet.
OOS 5.0 (Oreo) seems to have a few hiccups, most notably lower battery life, and many are reverting back to OOS 4.5.1.
For those who've tried to downgrade to 4.5.1, can it be done without wiping internal storage? I'm trying to avoid this because I don't want to copy close to 100GB of files back to my phone as it's very time-consuming.
I use Titanium Backup so I'm not worried about app data too much. I'm currently rooted with Magisk and would like to go back to the same rooted setup on 4.5.1. I'm also on blu_spark/eng.stk's oreo-compatible TWRP right now.
rebelpixel said:
OOS 5.0 (Oreo) seems to have a few hiccups, most notably lower battery life, and many are reverting back to OOS 4.5.1.
For those who've tried to downgrade to 4.5.1, can it be done without wiping internal storage? I'm trying to avoid this because I don't want to copy close to 100GB of files back to my phone as it's very time-consuming.
I use Titanium Backup so I'm not worried about app data too much. I'm currently rooted with Magisk and would like to go back to the same rooted setup on 4.5.1. I'm also on blu_spark/eng.stk's oreo-compatible TWRP right now.
Click to expand...
Click to collapse
Unless you backup your 4.5.1 with the same twrp you are using right now, there might be a risk.
but you already have backup, right ? the worst thing is having to wait for those 100GB data to be copied back to your phone, rather than loosing everything.
I actually didn't bother doing a nandroid backup of my 4.5.1 partitions, all I did before upgrading to oreo was:
- titanium backup of all apps
- copy all of /sdcard to an external disk
I'm just considering what would be the shortest path to going back to 4.5.1.
What would be great though is if Oneplus releases the next version of stable Oreo that fixes the battery drain and the other issues that people have encountered.
I don't know why the peoples are complaining high battery drain in oxygen os 5.0. Peoples also complaint about VOLTE issues but I am using it without any issue. Perhaps they don't perform clean flash before ROM installation.
ersandeepkr said:
I don't know why the peoples are complaining high battery drain in oxygen os 5.0. Peoples also complaint about VOLTE issues but I am using it without any issue. Perhaps they don't perform clean flash before ROM installation.
Click to expand...
Click to collapse
Clean flashing would be a good option for tbose who have time. But the Oreo update was designed to be a seamless upgrade from OOS 4.x, especially for normal users who haven't even heard of the xda forums.
I don't think the same issues manifested for everyone, but considering the general response in Oneplus's forum, I think the OOS 5.0 problem has some issues.
Just to add, I can confirm better performance and battery life when I downgraded to 4.5.1.
rebelpixel said:
Clean flashing would be a good option for tbose who have time. But the Oreo update was designed to be a seamless upgrade from OOS 4.x, especially for normal users who haven't even heard of the xda forums.
I don't think the same issues manifested for everyone, but considering the general response in Oneplus's forum, I think the OOS 5.0 problem has some issues.
Just to add, I can confirm better performance and battery life when I downgraded to 4.5.1.
Click to expand...
Click to collapse
XDA forum is mainly for rooter.......
rebelpixel said:
Clean flashing would be a good option for tbose who have time. But the Oreo update was designed to be a seamless upgrade from OOS 4.x, especially for normal users who haven't even heard of the xda forums.
I don't think the same issues manifested for everyone, but considering the general response in Oneplus's forum, I think the OOS 5.0 problem has some issues.
Just to add, I can confirm better performance and battery life when I downgraded to 4.5.1.
Click to expand...
Click to collapse
Where exactly is it stated that Oreo is designed like this?
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
Where exactly is it stated that Oreo is designed like this?
Click to expand...
Click to collapse
Hey, the thread has been cleaned because of your trolling. Just stop it if you can't contribute anything useful to this topic.
After a long long wait its finally here. The oneplus 3T gets android pie. Install it and share your experience here
https://9to5google.com/2019/05/22/oneplus-3-android-pie/
I'm downloading using oxygen updater app
Anything to share? Any issues?
ptoner said:
Anything to share? Any issues?
Click to expand...
Click to collapse
Using this since past 2 days. I am completely stock with locked bootloader, unrooted and stock recovery.
No issues till now. Feels good to be back to stock oxygen OS for a change from all these custom roms.
affection788 said:
Using this since past 2 days. I am completely stock with locked bootloader, unrooted and stock recovery.
No issues till now. Feels good to be back to stock oxygen OS for a change from all these custom roms.
Click to expand...
Click to collapse
You installed it on a locked bootloader. So you factory reset the phone before updating. Or did you just flash and lose no data
Sent from my ONEPLUS A6003 using Tapatalk
ptoner said:
You installed it on a locked bootloader. So you factory reset the phone before updating. Or did you just flash and lose no data
Click to expand...
Click to collapse
I installed it on a unlocked bootloader. I was previously on Skydragon. Flashed stock OS in twrp. Lost all data in internal storage after reset.
Sounds good have been avoiding on my work phone for fear that it'll become unstable or slow. Seems thats not the issue
affection788 said:
I installed it on a unlocked bootloader. I was previously on Skydragon. Flashed stock OS in twrp. Lost all data in internal storage after reset.
Click to expand...
Click to collapse
I'm running rooted Skydragon OS with twrp and unlocked bootloader. Can I directly flash oos via twrp? Will there be any issues?
Does the stock recovery replace twrp after flashing oos?
Darkweb_182 said:
I'm running rooted Skydragon OS with twrp and unlocked bootloader. Can I directly flash oos via twrp? Will there be any issues?
Does the stock recovery replace twrp after flashing oos?
Click to expand...
Click to collapse
Yes you can flash it over twrp on skydragon and yes it will replace twrp with stock recovery. But keep in mind you will also have to format your internal storage completely because it will give a decryption failed error.
So after you flash stock and when the phone boots up it will ask you to format the internal storage so backup everything if you want to go this way.
affection788 said:
Yes you can flash it over twrp on skydragon and yes it will replace twrp with stock recovery. But keep in mind you will also have to format your internal storage completely because it will give a decryption failed error.
So after you flash stock and when the phone boots up it will ask you to format the internal storage so backup everything if you want to go this way.
Click to expand...
Click to collapse
Do you know if it will be the same if you are not encrypted, and want to stay not encrypted? Is there a way to do that without formatting (maybe using the patched firmware or theone3os)?
groshnack said:
Do you know if it will be the same if you are not encrypted, and want to stay not encrypted? Is there a way to do that without formatting (maybe using the patched firmware or theone3os)?
Click to expand...
Click to collapse
mine is decrypted and installed fine and is still decrypted,sorry wrong thread
Just installed it, the initial look seems good. The phone spent some time optimizing the apps but after that it seems smoother and much cooler looking.
Ok so if i still on android n 7.1.1 and rooted and magisk installed ohh and twrp is there too, is it going to be safe to install android pie oos 9.0.2 and to keep the root and magisk and the twrp without loosing my data?
If its safe pleas do till.
ml700 said:
Ok so if i still on android n 7.1.1 and rooted and magisk installed ohh and twrp is there too, is it going to be safe to install android pie oos 9.0.2 and to keep the root and magisk and the twrp without loosing my data?
If its safe pleas do till.
Click to expand...
Click to collapse
It is not. You will have to factory reset/format data for getting OOS Pie. That is going to delete your data, Magisk and in the process, you may have to reflash TWRP also.
I'm on open beta 39 OnePlus 3 with twrp bluspark.
So can I download the update or the full ROM? I'm a little confused as to where it is on the forums.
Then do I just flash it in twrp (wipe first I know but should I wipe data as well?) While flashing does it tell you to wipe, format or do I do that all myself?
What are the s steps?
I'm happy to wipe everything as I want to clean up my device anyway.
Thank you so much for the help.
affection788 said:
Yes you can flash it over twrp on skydragon and yes it will replace twrp with stock recovery. But keep in mind you will also have to format your internal storage completely because it will give a decryption failed error.
So after you flash stock and when the phone boots up it will ask you to format the internal storage so backup everything if you want to go this way.
Click to expand...
Click to collapse
How's the performance and battery on Oxygen OS 9. 0.2?
Can you root it?
Does Google camera work?
Darkweb_182 said:
How's the performance and battery on Oxygen OS 9. 0.2?
Can you root it?
Does Google camera work?
Click to expand...
Click to collapse
Performance is good and smooth. Good battery life as well. I haven't rooted it yet, wanna keep it stock for the time being but I am sure it can be rooted. Yes Gcam works. I am using one of the stable Arnova based Gcam.
affection788 said:
Performance is good and smooth. Good battery life as well. I haven't rooted it yet, wanna keep it stock for the time being but I am sure it can be rooted. Yes Gcam works. I am using one of the stable Arnova based Gcam.
Click to expand...
Click to collapse
I wasn't able to root Oxygen OS oreo firmware that's why I was asking
Darkweb_182 said:
How's the performance and battery on Oxygen OS 9. 0.2?
Can you root it?
Does Google camera work?
Click to expand...
Click to collapse
Battery life is not as good as Oreo OOS. I have disabled OnePlus's advanced battery optimizations, you should know.
Performance on stock kernel is mostly fine with stutters in phone app mainly. But i think that's phone app's fault. Performance with the custom kernel I am using right now is great and the ROM feels smooth.
Yes, I am running it rooted with a custom kernel.
I haven't used Google camera as I hardly use my phone's camera. Maybe once a week.
abhibnl said:
Battery life is not as good as Oreo OOS. I have disabled OnePlus's advanced battery optimizations, you should know.
Performance on stock kernel is mostly fine with stutters in phone app mainly. But i think that's phone app's fault. Performance with the custom kernel I am using right now is great and the ROM feels smooth.
Yes, I am running it rooted with a custom kernel.
I haven't used Google camera as I hardly use my phone's camera. Maybe once a week.
Click to expand...
Click to collapse
How did you root it?
Which custom kernel are you on?
Also does the bootloader get locked after flashing oos?
Darkweb_182 said:
How did you root it?
Which custom kernel are you on?
Also does the bootloader get locked after flashing oos?
Click to expand...
Click to collapse
Those are pretty basic questions actually. I assume you haven't rooted your phone in recent time?
I just flashed the magisk zip before first boot into system to keep twrp and one restart settled things and magisk is now working fine.
I am using mcd kernel build r27 but it has broken Hotspot functionality, which I don't care much about.
Why would the bootloader get locked after flashing OOS? You need to manually go into fastboot mode and manually enter some commands to lock/unlock bootloader. It can't be done via recovery afaik.