So this is really weird.....I flashed LineageOS, based on Android 8.1, to my phone a couple months ago. I made sure to include the BLOD (boot loop of death) patch, as well as the 4-core version of TWRP because i do suffer from the BLOD with Android versions 8.0 and above.
Not sure exactly when it happened, but it seems that my phone has now started using all 8 cores again. lol
I'm definitely not complaining, but i would like to figure out why this has happened, and hopefully help provide a long-term fix for other Nexus 6P users.
I've included screenshots of my active cores being used, as well as ROM info for the version of LineageOS I'm using.
Can any senior members help me investigate this further? Just let me know what other info I can provide.
Thanks,
Rob
Yes..try to investigate this buddy..I Am also suffering from BLOD...Thanks
I also have the blod and was able to get over a week with all my 8 cores running and then it got stuck in one again. I used ex kernel manager to check the cores and after running pixel experience 9.0 with all the patches for blod I decided hell let's go back to 6.0.1 so I did and just tried not flashing any patched twrps and went along like I normally would if I had no blod. Got in saw all my cores running and was fine for a week or so then right back into it. Definitely enjoy it but it could be risky for a long trip or time away from a PC in case it comes back.
Well, I'm still running LineageOS and the phone is still working on all 8 cores. I've kept up-to-date with the LineageOS updates, but I've been too scared to try flashing any other ROM or Kernel!
I'm still down to do some testing. I just need a dev that's interested to chime in. My java skills are....limited, to say the least.
On a side note....absolutely love LineageOS! Hats off to them for making such an awesome ROM.
Rob
Where did you get the OS?
What are the exact steps to install this OS?
Related
Hey guys,
I'm just looking for someone to point me in the right direction. Basically, my school has this web portal logon thing called Cloudpath (formerly xpressconnect) that requires you to log on to the portal's network in order to follow the instructions in your web browser for your specific OS. The problem arises with Android. It requires you to download an app, which does all the nitty gritty certificate installation and configuration for you. However, whenever I try this on a CUSTOM ROM (LOS-based and DU), I end up in a connecting loop. I never get connected to the secured network even though the certs appear to be installed correctly. I've tried using the app and doing it manually by downloading the certs myself. This only occurs on custom nougat roms, but works on stock MM (I haven't tried MM roms, because I want nougat).
As far as I know this problem only affects this phone after I install the rom and OpenGapps. Some of my peers have LOS and have gotten it to work, so I'm the only one, and the tech staff have no idea what to do. I don't have the log file on me, but if you need it, I can post it (they're pretty long, but seem to be detailed up until the connection part which just flops between CONNECTED and DISCONNECTED).
Is this a problem with the modem or the roms themselves? I was going to wait until the nougat kernel blobs got integrated to LOS, before trying again as I don't want to use the experimental build because it's a month old now. This problem has been around since at least January of this year. If there is a non-los based nougat rom, I would be glad to try that too. otherwise, I'm at a loss and I need some direction.
Any help is appreciated!
Seeings as how all of our Nougat ROMs are a mixed bag of partial MM and part Nougat still, and all custom ROM's for the MXPE use LoS's device tree, I am thinking this is a ROM issue, probably with some binary blob we don't have yet. The kernel source just released a few weeks ago, give it time and custom ROM's will get better (we think), and if the MXPE ever gets official Nougat, we will probably have better binary blobs too.
If it works on stock Marshmallow, it obviously isn't a radio thing, because your Nougat ROM's use the same radio firmware.
I don't have much else to say, but I would try a custom Marshmallow ROM and see if it works... if it fails as well, the problem is something in the LoS core device tree and it will need some developer's special attention (good luck with that, since we are considered to have a stable device tree it takes some work to get it changed), but if it works, chances are good that once custom Nougat ROMs get updated more it will likely work.
In a last ditch effort. I tried flashing the experimental build after posting this article, and it actually works! Now, this isn't the ideal situation given that there are some bugs (that I haven't run into yet) and that this build is a month old now. But for now, I'm satisfied. I just hope these blobs get integrated to official LOS soon.
Progress on that is here: https://review.lineageos.org/#/q/project:LineageOS/android_device_motorola_clark
If there are any roms out there that are considered stable and have these implemented now, I would appreciate it, otherwise, I think I'll be set for a little while. Thanks for your help!
NEED rom Recommendation Battery+Performance+Customization (if possible)
Doesn't matter if its oreo or pie based
Currently On Stock Oreo January Security patch
Performance is Not Good,Battery hardly survives
3hrs on screen Time
3 hours screen on time - battery needs replacement. Its just 10 bucks. Get a new battery for 10 bucks and swap it or get used to run everywhere around with a powerbank connected to your phone.
I got 2 days with fresh battery and latest stable LineageOS image clean installed (with ./flash-all.sh and TWRP)
@abdullahk6809
Alright, so i figured it would be easier to post via my computer rather than my phone.
TLDR : If you don't want to read all of this then stick with 8.1 roms for the best battery life and no issues. Cr droid and Resurrection Remix both posted their final 8.1 builds and both have run flawlessly for me. The same goes for AICP and AFAIK they are still merging up stream changes though minor with their weeklies.
As far as 9.0, we do not have official support, so it's still being worked on to get the best experience/no issues. AICP 9.0 has worked out the best for me with 9.0 then followed by Resurrection Remix.
There is a huge thing you need to be aware of if you're not already, that being our 9.0 roms currently use two different types of encryption. AOSIP, AICP, Resurrection Remix, CR Droid all use full disk encryption. (FDE) which is the same encryption we have always used. For that you just use the offical TWRP. All of the 9.0 stock roms currently are using file based encryption(FBE) and for that you need to use a specific TWRP that was made for it, and if you are currently on FDE (which you are) you need to format data after flashing the rom, meaning you will WIPE ALL OF YOUR INTERNAL. IF you decide to go back to an 8.1 rom, or try one that uses FDE, you will need to do the same process. Switch back to the offical TWRP, and format data after you flash the rom. If you go to FBE and stay on it, then you do NOT need to format data/switch twrp going one from FBE rom to another FBE rom, or updating the current rom.
So when choosing what to flash, you need to read the OP of each rom and know which encryption it uses, or it will not boot. Roms that run FBE AFAIK always have the twrp needed linked in the OP.
With 9.0, as i said, it is still a work in progress since we have lost official support. So if you read the threads some people are reporting issues with calls, Volte, issues with whatsapp etc.. So read the threads at least the last 15 or so pages to see if people are currently having issues. Like i said previously i could tell you to go flash x rom, because it works the best for me. But then you have issues because you use whatsapp and can't send voice messages or w/e and i don't use it. With people using the device for different reasons, you need to take time to see what works for you versus just a one word answer that will work for you.
A lot of people are having issues with 9.0 because of battery life, but I do not see a huge decrease in battery life, but i don't use battery killing apps like face book, whatsapp, or play games or anything. If you really are only getting 3 hours SOT you might want to see what is using your battery via better battery stats or gsam, because it's possible apps could be doing it, and no rom will change that. If you find out that no rouge apps are really killing your battery, as was just stated, depending on how old the device is, you might need a new battery. This phone is a good device but they used pretty ****ty components on it, thanks China. I myself have not had battery issues but i bought my device like three or four years ago, some devices are older.
Anyways, that's about all i can really offer for advice, i don't spend nearly as much time on this forum as i used to because i end up getting into confrontations with people that spread misinformaation, or refuse to follow simple courtesy that are not rules such as asking for eta's etc..
If you end up having any questions i might be able to answer, send me a PM. It might take me some time to respond as i don't use the app as much as i used to, but i'm always willing to answer even the dumbest question when asked via private message.
Lawlrus said:
@abdullahk6809
TLDR : If you don't want to read all of this then stick with 8.1 roms for the best battery life and no issues. Cr droid and Resurrection Remix both posted their final 8.1 builds and both have run flawlessly for me. The same goes for AICP and AFAIK they are still merging up stream changes though minor with their weeklies.
Click to expand...
Click to collapse
Hi Lawlrus, I'd just like to have a stable rom. Like you said 8.1 rom might be my best choice, but RR has stopped updating the 8.1 version so what I worry about is it's lacking security patches.
So would you suggest some roms that's stable and and getting updates as well ?
What I might need is :
1. dark theme 2. night light (blue light filter) 3. probably fling nav bar
Hello XDA.
Ive spent a few hours now reading OP8P forums, and got some rough idea of what I'm getting my self into.
I bought a OP8P, its coming to me within next 10 days. I bought it brand new from T-Mobile in Croatia (Europe).
This is my first time owning a Oneplus, my current phone is Galaxy S7, before that i had an S5... On these two i got some experience with custom roms, rooting, flashing, twrp.... But i didnt do anything to my phone in the last 2 years, its been stagnant... and the knowledge i gained... well, if you don't use it, you lose it..
It always seemed that oneplus had great support in XDA community, but from all these threads I read in past few hours, i gathered some confusing conclusions.
What i expected when i made the purchase is that I would be able to have a stock up-to-date OxygenOS, with root (magisk), twrp, xposed, banking apps working, youtube vanced, photochrome camera...
But..... seems like i would have to go through a lot of trouble achieveing all of these things, deciding between OOS 10 vs 11, if they're even achievable with some of the knowledge i kept from my samsung days...
So here are a few questions i would like answers for...
1. When i get the phone and start it for the first time, am I going to be running OOS 10 until i manually upgrade?
2. Do you suggest I stay on OOS10 or upgrade to OOS11?
3. If i upgrade to OOS11, can I have any of the stuff i mentioned that i expected?
4. I saw some user saying if I decide to root, i should not be using modified/patched boot.img... Why is that? (btw i don't recall ever doing this back in day, would love some info about it...)
5. Is TWRP possible, whats the new META?
4. Is there anything else i should know before doing anything, also I wouldn't mind if you would explain all this to me like im five years old
Thanks in advance!
I'm a op8pro owner, and I have Magisk (22.0), and root without twrp (no recovery yet suported for android 11 on this device). You have to patch boot.img with Magisk. Not a big head ache.
Photocrom camera not working on 11 as before on android 10, and I tried two existing methods (it works, but no "X-ray" feature).
Since android 11 is in its stable release, new devices should come with it, but not sure.
All apps mentioned, Root and non Root are working just fine,
Thanks for replying.
Could you possibly link the guide which I should follow, and save me from something outdated, since I might not be rooting my OOS11 from inactive slot on OOS10
Thanks again!
datnewnew said:
Thanks for replying.
Could you possibly link the guide which I should follow, and save me from something outdated, since I might not be rooting my OOS11 from inactive slot on OOS10
Thanks again!
Click to expand...
Click to collapse
Root OnePlus 8/8 Pro using Magisk & Install OTA Updates after Rooting
A guide on how to root the OnePlus 8/OnePlus 8 Pro using Magisk. Also learn how to install OTA updates on your rooted OnePlus 8 device.
www.thecustomdroid.com
Thanks, just read through it, really simple! thanks!
What do you think are the chances of hardware-based attestation being enabled on my phone? slim chance or?
Hello XDA community,
After months of struggling im in desperate need of your help.
What is my goal?
To compile our own kernel so we can mess around with Qualcomm's trustzone.
Where did it all start?
It all started a few months ago back in November 2021 when me and a friend read a blog about a Trustzone exploit in Qualcomm's MSM8974 processor. (link to the blog)
Big noobs as we where, we where getting hyped an bought ourselves a Samsung Galaxy Note 3 with a MSM8974 processor. After messing around with the device we learned more and more about android and the workings of the software. We first started to root the phone and play around with ADB. After that we found that we can use Frida aswell. But all of it didn't lead to the result we wanted. So we started to dig deeper in to the write-up of the blog. We soon came to the conclusion that we where not even close to doing the right thing.
What happend next?
After we came to the conclusion that ADB and Frida is not enough we understood we need to build our own kernel for this exploit to work. So we do what we always do and that was start googling and watch YouTube. By doing that we found 2 different kernels:
Lineage 18.1
SM-N9005_EUR_LL_Opensource
We where over the moon because inside the folders we found the the files that need to be replaced for the exploit to work. So we replaced the files and try to compile the kernel by using this YouTube tutorial. Everything seemed to go well, we made the
Code:
make msm8974_sec_defconfig
and we run
Code:
make menuconfig
so far so good. the last and final step should be to run
Code:
make
to compile the kernel. And that is where it went wrong an ran in to a error.
Then what?
Then we started to compare the original files with the modified files and we found out that it wasn't just a few modifications in the code but the code was different. So we did what we always do, go back to the source. So back at the blog we thought maybe its because they modified a Nexus 5 at android 4.4.4.
Now what?
Now im trying to find the source of a android 4.4.4 kernel of msm8974 so we can compare those files to the modified files. So if anyone has useful info or knows where to find a kernel for android 4.4.4 for a Samsung Galaxy Note 3 (SM-N9005).
TLDR;
Im looking for a source of android 4.4.4. for a Samsung Galaxy Note 3 (SM-N9005) (hlte)
Well, unfortunately today almost no one uses android 4.4.4. even that have the exact same device, I am using Android 11 on my phone.
I recommend not wasting your time on a kernel for Android 4.4.4. And if you really want to make a kernel for this device I need one for Android 10 and above.
Also I think making a kernel for AOSPs like LineageOS or HavocOS or crDroid ETC is much easier.
A.M.2.K.M said:
Well, unfortunately today almost no one uses android 4.4.4. even that have the exact same device, I am using Android 11 on my phone.
I recommend not wasting your time on a kernel for Android 4.4.4. And if you really want to make a kernel for this device I need one for Android 10 and above.
Also I think making a kernel for AOSPs like LineageOS or HavocOS or crDroid ETC is much easier.
Click to expand...
Click to collapse
Thanks for your response I will look in to it. not sure if it will be easier because the files that needed to be changed are:
arch/arm/mach-msm/scm.c
arch/arm/mach-msm/include/mach/scm.h
drivers/misc/qseecom.c
SwAgLaNdeR said:
Thanks for your response I will look in to it. not sure if it will be easier because the files that needed to be changed are:
arch/arm/mach-msm/scm.c
arch/arm/mach-msm/include/mach/scm.h
drivers/misc/qseecom.c
Click to expand...
Click to collapse
Well, I don't know much about kernels.
I said it's easier because I thought it's a pure and raw operating system. But now according to your post it turns out it's not easier.
Plus almost no developers left for this now very old model .
Forgive me if I post this in the wrong place, move it if necessary np.
Xda has been my go to for many many phones over the years. Many years. But recently I've grown a little deeper interest with the phone I currently own.
I need some clarity if anyone could please.
I've got a OnePlus 8 pro IN2025 on lineage 20 (whatever latest build in relation to the date on this post) and rooted with magisk 26.1.
Everything is running awesome. Even been able to remove a few Google system apps I despise.. this setup is reminiscent of a couple phones I've run on CM.. I thought those days were over.
So much appreciation to those keeping development alive. Much love.
To the point:
I'm trying to run as much of nethunter as possible without flashing it (and maybe I have the wrong idea so please correct me)
To my understanding, nethunter will require me downgrading to Android 12 with some other ROM - crdroid etc..
Flash twrp\ nethunter - then I have the nethunter ROM installed.
Problem is, I'm still a little attached to some Google stuff. I limit it, but there that is.
I've got the Kali app store installed and a few toys I can play with -
Question is, when I flash nethunter, is it like flashing any other ROM? Thats it. Or is there an equivalent to a "USB live version" that's temporary.. have I gone as far as I can without flashing?
I'm not interested in getting rid of lineage in favor of nethunter.
Thanks in advance. You guys are awesome!