Database Develop

Help with Pure Nexus Project would be greatly appreciated

I am new to my Nexus 6 and new to flashing custom roms. I have read the thread all morning long and still don't feel comfortable with what information I have obtained. I'm currently running marshmallow 6.0 rooted with supersu 2.52. How can I flash the latest pure Nexus project 6.0.1 correctly? I do have TWRP recovery installed and I'm running on build number MRA58R

Make a backup in TWRP, wipe your system partition, Flash the ROM zip and the GAPPS zip, reboot, profit. If anything fails you can roll back to your backup and try again.

Real simple. Download the latest built as well as the latest google apps (gapps)
Reboot to TWRP
Do a backup, so you have a restore point if something happens
Go to wipe->advanced wipe and choose both caches, system and data. DO NOT wipe internal storage
Go to install, choose the ROM and gapps and install them
Reboot
You will now be on the latest. You will have to set your phone up again, and all your text messages, home screen, act will be gone but all your stuff on your sdcard (internal storage) will be untouched.
You can also get real ambitious and make backups with something like titanium backup of all your apps and data and restore it after booting PN, but try to not back up system apps or system data (it should be an option... I dont know, I never use tibu). The main thing you lose without backing up is texts, I usually just deal with it/redownload apps/set up home screen again.
On future updates, unless there are major changes and its indicated by a majority of people in the PN thread, just dirty flash.
That is, backup, wipe caches, install new ROM version( I wouldn't reflash gapps ) this will leave all your apps, settings, ect... But should only be done when flashing the same or a very similar ROM. If you dirty flash and experience problems, go back and clean flash as I first instructed.

So I should not worry about flashing the new 32r radio?

shouldnt this have been one of the first things to learn BEFORE you ever rooted your phone? yea, nice job jumping in before learning your way around. i bet you even used a toolkit to root your device..

Everyone's got to start somewhere. And no toolkit here but thanks for your input! And thank you for the helpful responses.

roy.garlington said:
Everyone's got to start somewhere. And no toolkit here but thanks for your input! And thank you for the helpful responses.
Click to expand...
Click to collapse
no tool kit? ok, your -1 on not learning before rooting has a +1 right by it, for rooting the proper way. you just might earn some respect

Hey there simbo, what do you say about flashing the radio?

Sure. Or don't.
Whatever.
The radio is pretty separate from android. Its basically drivers to tell you phone how to use hardware.
FI has certain requirements for activation that may check what radio you have, but outside of that run what ever works good for you., its not going to for sure be any specific one. Newer may often be better but its not uncommon that an older one may work a little better.
Different apps can help you monitor (I dunno which ones... But I know its a thing ), you can also go into about phone -> status -> sim status and check signal strength where lower dBm is better(well a lower numeric value... Its technically a negative number, so higher is better i.e. -113 is worse then -104). This will vary slightly minute to minute and place to place so just taking a glance once won't really settle it for you
I just use it for a day or two, pay attention to how my signal is (just kinda how often did I have decent # of bars, nothing scientific), and check battery stats clicking on cell standby and looking at % of time with out signal.

roy.garlington said:
Hey there simbo, what do you say about flashing the radio?
Click to expand...
Click to collapse
youre choice. you can try any of the radios, from previous android versions, on any android version. they arent specific. im using the 27R radio. whichever one works best for you, thats whats important

roy.garlington said:
I am new to my Nexus 6 and new to flashing custom roms. I have read the thread all morning long and still don't feel comfortable with what information I have obtained. I'm currently running marshmallow 6.0 rooted with supersu 2.52. How can I flash the latest pure Nexus project 6.0.1 correctly? I do have TWRP recovery installed and I'm running on build number MRA58R
Click to expand...
Click to collapse
Well, it's all very easy if you read a little. Still i will give you one extra tip in case you start flashing all kinds of roms: You unlocked your bootloader. Before doing that you enabled "OEM unlocking" in 'Developer options'. Leave that enabled (this setting is 'sticky'. even when you wipe the device)!!!!. Leaving OEM unlocking enabled will disable "Device Protection" that causes sometimes a 72 hours lock-out from your Google account.

Nexus 6 running 7.1.1 stock but slowing to a crawl... advice?

Hi
So I'm no tech genius but I have a little bit of familiarity with Nexus Root Toolkit and my Nexus 6 is unlocked.
I have factory reset from the OS and started again but the phone is still way slower than it used to be. On top of that I've never had the nerve to try mucking about with alternative kernels and trying to get rid of the encryption.
But now I feel like I have no option. I want to do whatever I can to keep the phone usable for another year or maybe more and it seems like getting rid of encryption will likely help quite a bit!
Any advice on how to go about this as a a newbie with limited tech knowledge?
Cheers
R

ralphaverbuch said:
Hi
So I'm no tech genius but I have a little bit of familiarity with Nexus Root Toolkit and my Nexus 6 is unlocked.
I have factory reset from the OS and started again but the phone is still way slower than it used to be. On top of that I've never had the nerve to try mucking about with alternative kernels and trying to get rid of the encryption.
But now I feel like I have no option. I want to do whatever I can to keep the phone usable for another year or maybe more and it seems like getting rid of encryption will likely help quite a bit!
Any advice on how to go about this as a a newbie with limited tech knowledge?
Cheers
R
Click to expand...
Click to collapse
Quick update.
I found this video "How to Disable Forced Encryption on Rooted Nexus 6!" on Youtube which did a walk-through of using Nexus Root Toolkit to flash the Boot kernel with an img file that unencrypts the Nexus 6.
Problem was my Nexus 6's build is not listed. It's Android 7.1.1 N6F27M
I did a manual search and found a few boot.img files specifically for this build on Android File Host by a developer called bmasephol
Anyway, I downloaded the file from androidfilehost and then manually used the boot.img flash option to select and flash to my phone. It did appear to work but on re-booting the phone stull says it's encrypted under SECURITY.
Any suggestions on how I can either...
a. Get Nexus Root Toolkit to recognise my build or
b. Manually flash the right boot.img file to the phone so that it unencrypts my device?
Thanks for any advice.
P.S. I did think about picking a different boot.img for one of the other recent builds using 7.1.1 listed in Nexus Root Toolkit but I decided that might be adding fuel to the fire. Last thing I want to do is brick my phone!
R

ralphaverbuch said:
...Nexus Root Toolkit and my Nexus 6 is unlocked.
I have factory reset from the OS and trying to get rid of the encryption.
Click to expand...
Click to collapse
NRT installs also TWRP-recovery.
You may wipe the data partition and flash (with TWRP-recovery) a ROM with supersu included.
SuperSu patches the stock kernel. No forced encryption.
https://forum.xda-developers.com/showthread.php?p=74018955

NLBeev said:
NRT installs also TWRP-recovery.
You may wipe the data partition and flash (with TWRP-recovery) a ROM with supersu included.
SuperSu patches the stock kernel. No forced encryption.
https://forum.xda-developers.com/showthread.php?p=74018955
Click to expand...
Click to collapse
Thanks for the tip.
As a bit of a newbie can you just walk me through what I have to do with the file?
I have downloaded it to my Windows PC and have the Nexus 6 plugged in to the laptop with NRT. I have also already got TWRP on the recp]overy partitio. Then....? Not sure how/what I do at that point to get the ROM onto the phone and how do I wipe the data partition?
Apologies for the ignorance. At the limit of my knowledge/skills.

ralphaverbuch said:
Thanks for the tip.
As a bit of a newbie can you just walk me through what I have to do with the file?
I have downloaded it to my Windows PC and have the Nexus 6 plugged in to the laptop with NRT. I have also already got TWRP on the recp]overy partitio. Then....? Not sure how/what I do at that point to get the ROM onto the phone and how do I wipe the data partition?
Apologies for the ignorance. At the limit of my knowledge/skills.
Click to expand...
Click to collapse
Think I worked it out....

ralphaverbuch said:
Think I worked it out....
Click to expand...
Click to collapse
Correction... I managed to install that zip file using TWRP after first wiping the data folder and it all works. But it's still telling me I'm encrypted?
Did I download the wrong one?
N6F27M-Lite-7.1.1-su282sr5.zip
Lite stock rom for the Nexus 6. Prerooted with SuperSU 282SR5 Updated October 2017.

To be unencrypted, after flashing a boot.img (also known as a kernel) that does not force encrypt, you must wipe the internal storage. THIS WILL DELETE ALL FILES, MUSIC, VIDEOS WHATEVER STORED ON THE "SD CARD" DO A BACKUP FIRST!
Of course, just wiping internal storage after a factory reset will probably fix the slow down without anything else needing to be done.
I run my phone encrypted
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
To be unencrypted, after flashing a boot.img (also known as a kernel) that does not force encrypt, you must wipe the internal storage. THIS WILL DELETE ALL FILES, MUSIC, VIDEOS WHATEVER STORED ON THE "SD CARD" DO A BACKUP FIRST!
Of course, just wiping internal storage after a factory reset will probably fix the slow down without anything else needing to be done.
I run my phone encrypted
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Ok so I think I put an unencrypted boot.img on the device already. So wiped the user data with a factory reset and restarted the phone to see if that did the trick...
... Except it bloody didn't!!!
Clearly I'm too thick.
What internal storage do I need to wipe?

adb reboot bootloader
fastboot oem unlock
fastboot flash boot <non forced encrypt boot.img> (suggest using Franco)
fastboot erase userdata
fastboot reboot
Please note; while you probably can do everything through a toolkit, it all happens in the background automatically, so when a problem develops, you don't know enough to resolve it. I don't use toolkits and don't support using them. Fastboot/ADB are not hard and Google had released them as stand alone tools making it easier.

Thanks for the tips. Not 100% confident I know what I'm doing but you never learn if you're not willing to give new things a go!
Cheers
R

I should have commented in the previous post, if your device bootloader is unlocked already, you don't need the "fastboot oem unlock" command.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

OK well I tried and sent it into a repeated bootloop between the google startup logo and TWRP... so whatever I did was plainly wrong! Trying to use NRT to at least get it back and running.... I'm clueless as to the steps I'm meant to take... Ho hum.

Does that mean you can not boot into TWRP?
If you can, do a factory reset, get to a known condition.
Then download Franco's kernel. Flash it in twrp. Reboot. Make sure everything works.
Boot to bootloader (fastboot). Connect to your computer. Type:
fastboot devices
It should come back with your device serial number. If it doesn't, there is a problem with your computer drivers.
Type the command:
fastboot format userdata
This will wipe everything on the "SD card". Reboot. You should now be unencrypted.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

nexus 6 8.1 oreo auto reboot issue

hi my device is nexus 6 running android oreo 8.1
i had tried two rom both 8.1
but they both have the same issue
the device reboots once every day
how to solve it?
thank you all

Tenzinjamyang said:
hi my device is nexus 6 running android oreo 8.1
i had tried two rom both 8.1
but they both have the same issue
the device reboots once every day
how to solve it?
thank you all
Click to expand...
Click to collapse
Let me know the rom names ?

ragulhm said:
Let me know the rom names ?
Click to expand...
Click to collapse
aosip and nitrogen

You might try ABC ROM or Beltz. Both are in the Android Builders Collective thread.
If you still have reboot problems with either of those ROMs, I would wonder if your battery has been replaced.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

before you do this, make sure you have found the oreo rom you want to use. Remember Oreo dont like crackflashing...
1 - Download the latest Google OTA image HERE https://dl.google.com/dl/android/aosp/shamu-ngi77b-factory-5cd75e2a.zip
2 - Use adb or wufresh tools to restore back to stock
3 - Once on stock, install TWRP and ROOT
4 - Reboot to TWRP and format everything, including storage
5 - Now Add the OREO ROM, Gapps, and Root zips to device storage
6 - Flash ROM, Gapps, and Root...NOW FORMAT data, cache, dalvik-cache, and storage (DONT WIPE SYSTEM)
7 - Reboot, PROFIT!!!

I'm not the least bit sure the above is necessary. Without question you should be on the newest bootloader before going to oreo, but returning completely to stock, then rooting, which just gets overwritten by flashing a custom ROM seems excessive.
If you are that nervous about doing an upgrade, then I strongly recommend NOT using a toolkit. Toolkits are great, until something goes wrong and because you're automating the process you'll have no idea what went wrong. Particularly on N6, it is so easy to just use ADB/Fastboot. Those drivers have to be installed anyway for a toolkit to work so you're not gaining anything.
If you follow that advice, please make sure you back up EVERYTHING since the method is directing you to wipe your storage (user data). Of course, if you follow proper return to stock instructions, you'll wipe internal storage (user data) as a function of the -w fastboot switch.
IMHO, it's a mistake to link directly to a factory image release. Here is the factory image page, complete with instructions and checksums for the files. You should ALWAYS verify checksums before flashing a file. The file linked above is the last one listed (newest) in the shamu grouping.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

fkfmfz said:
before you do this, make sure you have found the oreo rom you want to use. Remember Oreo dont like crackflashing...
1 - Download the latest Google OTA image HERE https://dl.google.com/dl/android/aosp/shamu-ngi77b-factory-5cd75e2a.zip
2 - Use adb or wufresh tools to restore back to stock
3 - Once on stock, install TWRP and ROOT
4 - Reboot to TWRP and format everything, including storage
5 - Now Add the OREO ROM, Gapps, and Root zips to device storage
6 - Flash ROM, Gapps, and Root...NOW FORMAT data, cache, dalvik-cache, and storage (DONT WIPE SYSTEM)
7 - Reboot, PROFIT!!!
Click to expand...
Click to collapse
thank you but no work my nexus 6 still reboot (soft reboot) about every 24 hours

Tenzinjamyang said:
thank you but no work my nexus 6 still reboot (soft reboot) about every 24 hours
Click to expand...
Click to collapse
There are many reasons this could happen. An app, a theme, an old battery.
Look to get a log right after the reboot,
adb shell cat /proc/last_kmsg
adb logcat > crash.txt (look for a shutdown thread)
adb shell cat pstore/last_kmsg/serial logs
or if you are running a theme/substratum, remove it for now to see if the problem improves.
If you have mods like custom kernel, exposed, viper, remove them to see if the problem improves.
Delete bootloader logs by rebooting to bootloader, scroll through with volume buttons until reach bootloader log entry, long press power until the phone reboots and immediately fully charge. If the problem improves, it's likely due to the age of your battery.
Try booting to safe mode and see if the problem comes back. Safe mode will not only the minimum necessary for the device to run. It eliminates apps for the most part.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Oreo is far from stable. Samsung S8 had to cancel Oreo release due to rebooting as well

HueyT said:
Oreo is far from stable. Samsung S8 had to cancel Oreo release due to rebooting as well
Click to expand...
Click to collapse
I have never had a reboot on 8.1 ABC for shamu. Beltz is equally stable.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
I have never had a reboot on 8.1 ABC for shamu. Beltz is equally stable.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
do you know any good rom oreo 8.1 for oneplus one bacon? thank you.

Tenzinjamyang said:
do you know any good rom oreo 8.1 for oneplus one bacon? thank you.
Click to expand...
Click to collapse
No? This is a nexus 6 thread.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
I have never had a reboot on 8.1 ABC for shamu. Beltz is equally stable.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Do the random reboots occur when the device is charging? I had one this morning (running Beltz) while plugged in and fully charged, meaning the battery wasn't being used.

Strephon Alkhalikoi said:
Do the random reboots occur when the device is charging? I had one this morning (running Beltz) while plugged in and fully charged, meaning the battery wasn't being used.
Click to expand...
Click to collapse
I've not had reboots on either Beltz or ABC. Though I have been running ABC pretty much since it was built for shamu.
Back before I replaced my battery, especially towards the end, it would reboot when even when it was plugged in. At its worst, plugging-in would crash the phone.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
I've not had reboots on either Beltz or ABCBack
Click to expand...
Click to collapse
I've also a soft reboot once a day. Around 17h. N6 Beltz180314, unencrypted.
That reboot issue started when I installed substratum and black themed layers.
In the Beltz and ABC there's already a dark system theme. Imo this theme works well, but can cause a possible conflict with substratum.

NLBeev said:
I've also a soft reboot once a day. Around 17h. N6 Beltz180314, unencrypted.
That reboot issue started when I installed substratum and black themed layers.
In the Beltz and ABC there's already a dark system theme. Imo this theme works well, but can cause a possible conflict with substratum.
Click to expand...
Click to collapse
I'm still on the "never had a reboot" side [emoji6]
I also use substratum and leave the dark system theme enabled...no reboots. I stand by my opinion that most shamu users with reboot problems need to look at their battery, esp. when it's hours into use.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
I'm still on the "never had a reboot" side [emoji6]
I also use substratum and leave the dark system theme enabled...no reboots. I stand by my opinion that most shamu users with reboot problems need to look at their battery....
Click to expand...
Click to collapse
Because my 'once a day reboot' happens in the afternoon I will check the battery charge % when it happens.
But it's a soft reboot; same as when substratum.
I keep an eye on the battery and also on substratum.

I get the once a day reboots also on Oreo ROMs, I would agree with the battery being old theory, but how do you explain no reboots when I go back to PN?

EAK128 said:
I get the once a day reboots also on Oreo ROMs, I would agree with the battery being old theory, but how do you explain no reboots when I go back to PN?
Click to expand...
Click to collapse
Kernel settings maybe? If possible, run the problematic ROM while on charger and see if it reboots.
@NLBeev, I agree that a soft reboot sounds more like theme, or maybe app. I can tell you that I've been running ABC Oreo for N6 since its release. I've been dirty flashing (deleting substratum theme first) each time until last week when I clean flashed.
I don't know if it's possible for you to stay tethered to a PC, but catching a logcat through ADB would probably help. You can store a larger file that way.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
....I don't know if it's possible for you to stay tethered to a PC, but catching a logcat through ADB would probably help.
Click to expand...
Click to collapse
Use my N6 daily
I am suspecting 3 things: battery, substratum and the powersave option of Ex kernel.
It's now evening here and no soft reboot yet.

Need Help

Ok guys I have a weird one. The other day I decided to switch roms. Before I flashed I followed the instructions and did a full wipe from TWRP.. So after wiping I went to install from OTG and I get error 7 or " this rom is for a shamu device". Now before I had decided to change roms I was running a an aosp rom that I found here in this fourm. I had magisk installed and had the Sony modual installed to trick the play store into thinking my N6 was a Sony device so I could install some of thier proteietary apps...I figured a full wipe would have removed that... That it didn't makes me think something in the build prop was changed and No I don't have a back up. I'm super smart about stuff like that.. .anyways now no matter what rom I try to install I get that message...is there a way to flash build prop or is there a different solution or am I Fu**ed ??
Thanks in advance

tombaldwin6 said:
... " this rom is for a shamu device". Now before I had decided to change roms I was running a an aosp rom that I found here in this fourm. trick the play store into thinking my N6 was a Sony device so I could install some of thier proteietary apps
Click to expand...
Click to collapse
You could try to change the updater-script.
Extract it from the zip and remove the line with the device check.

Mount system in twrp then userr adb to pull build.prop, edit it and then ADB push to return it.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

I wish I could mount system. However I did a full wipe and there is no system to mount. . Thanks for the reply though. I believe I'm going to try the the other idea where it's suggested that I change the updater script. I mean if I did a full wipe that makes sense set there is no system to mount, right? Thank you to both of you for getting back to me. I do appreciate it

Just doing the default wipe in twrp doesn't wipe system. In the wipe section, you should go into advanced (I think that's right) and check the partitions you want to wipe.
If you did a full wipe, then any chances you made should not have persisted. If you really did already wipe the system and data partitions, it's unlikely your previous modifications are the cause of the error. Double check that you have the right ROM downloaded - though the error makes it sound right.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

CPU 100% frequency.

Hello,
I apologize in advance for my English.
I'm using nexus 6, stock 7.1.1 no root, no unlock bootloader ....
The problem is that my cpu2,3 is still running at 100% frequency.
I tried flash, factory reset ... nothing helps.
Before that, I had a root and I played with thermal config so that the kernels did not turn off at 40% of the battery.
I'm running now stock and the kernels behave like this ...
Please help, I'm quite desperate, my battery is gone, my phone is hot.
I discovered that this usually happens when the battery falls to about 35%, the two cores turn off, and when I charge the kernels are connected but the frequency is still 2649mhz.

Do you have an old battery?
You might try resetting the bootloader logs and see if that gives you any relief.
1) Power off your phone
2) Press and simultaneously hold the Power and Volume Down buttons putting the phone in fastboot mode
3) Use the Volume buttons and scroll through the menu until you see "Bootloader logs"
4) Press and hold the power key for 7+ seconds until the phone reboots normally
5) On boot, fully charge the battery
If you see some improvement as a result of those steps, consider replacing the battery.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Hello,
the battery is one month old.
This bug started after I tried different rom and kernels .... I tried also to change the BCL and wrote in a set of thermal engine.
Now, even after the flash stock rom these things happen, with a load of 0% and a frequency of 2649mhz.
I noticed that we just made stock 7.1.1 when I'm 5.1.1 so I'm going without a mistake.
I apologize for writing English through the translator

It's possible it's still the battery. But I'm not certain what the following means;
zip545 said:
I noticed that we just made stock 7.1.1 when I'm 5.1.1 so I'm going without a mistake.
Click to expand...
Click to collapse
Are you still on 5.1.1?
If that is right, then the thing to do is update to the last stock release. The easiest way to do that is probably using ADB sideload with a factory full OTA.
You can also fastboot flash the full factory image (confusing I know, but full factory and full OTA are different).
The instructions on each of those google sites are good. On the second one, where you would be fastboot flashing, the N6 is an older device so when 2 possible commands are suggested, use the one indicated as for older devices.
Also, instead of installing the full Android SDK, you could use Minimal ADB and Fastboot.
This thread should help.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

I tried this procedure about 5x ...
I do not know anymore so I'm writing to you where you have more experience ...
I was on 5.1.1 and flash ota update helped adb on 7.1.1 and so far everything goes well. I will check if the processor does not go all the way to 2649mhz.
As I say it all started by trying out rom, different kernels and editing a set of thermal engine .....
Is it possible that full factory image does not return all files ???
I have a screenshot but I can not send it here because I'm new.

If you did a full return to stock after trying the kernels you mention, all of those changes are gone.
When you flash a kernel, it's the same as the boot image. So when you sideload or fastboot flash the stock ROM, the boot image is returned to stock and your previous changes are gone.
I'm wondering if you had matched the kernels to the ROM version you were running. If you flashed a 7.x kernel on a 5.1.1 ROM, that might cause the trouble you had.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

I did some searching to refresh my memory. It's been a long while since 5.x [emoji6]
If all of your maxed cpu problems occurred while you were running 5.1.1, then I think it's likely a DNS bug that was around back then may have been the root cause of your problems.
If you still experience the cpu problems on 7.1, then it's not likely due to that bug.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

I probably wrote it wrong ....
I used android 7.1.1, no 5.1.1
I installed the lineage os14.1, I changed the thermal engine file so that two cores did not shut down at 40% of the battery.
I also installed the script to turn off the BLC which is here on the forum.
Then I installed the stock 7.1.1 and did the same, it did not work so I installed the Elementalx kernel.
Then I installed the factory image 7.1.1 and you noticed that the 2.3 core is ON 2649mhz! This was done even when the battery was 100%, 80% .....
Nothing helped, factroy reset, installing factory image ... just nothing
Then I installed stock 5.1.1 and everything worked out!
On stock 5.1.1 the processor was driving normally, then I factorydled again factory 7.1.1 and again the CPU kernels went nonstop to 2649mhz.
Now it seems that the processor is running normally, I am in the testing phase 7.1.1.