This is an update to my original post which was using frameworks kernal which was not really overclocked.... this new boot.img uses ivans kernal which is capable of 710 MHZ
MAKE A NANDROID BACKUP FIRST !!!!!!!
I take no credit for Ivans Kernel or jamzelles Rom which are both great!!! Thanks for all your hard work guys!
THIS IS A UPDATE FROM THE ORIGINAL BOOT IMAGE I POSTED!! THIS ONE ACTUALLY WORKS.
I tried Sensable 3.0 but had a problem with the dialer like everyone else, This way I can keep my phone as is i.e. all home screens apps etc.
I have combined Ivans OC kernel with the Ramdisk for jamzelles sensable 2.0 rom to create a new boot.img. I have been succesful in flashing this new boot image to my existing sensable2.0 rom and have noticable speed increase.
Here is the boot image. It is in zip format.
Unzip the file to your androidsdk\tools folder
run the following from prompt
type "adb shell reboot bootloader"
once phone boots to hboot and says "fastboot usb"
type "fastboot flash boot boot.img"
hold down vol down to hboot mode
hold vol up to recovery
reboot phone
After reboot you can go into phone information / software information and verify the kernal says 2.6.29oc [email protected] #26
Download setcpu from
http://forum.xda-developers.com/showthread.php?t=505419 and install.
Here are the notes on using SetCPu
Overclocking info:
To use overclocking to work, you can buy SetCPU for $1 in the Android Market, or legally free from here. <- Yeah, click that
1)When starting SetCPU, Use Auto detect Freqs
2) Move to your desired speed.
3) Set up your profiles
Not sure if this can be done with the other roms or not I will post back my results as i test it with the roms.
This kernel does not appear to be overclocked. The ondemand seems to be turned off, hence the increase in performance and drop in battery life.
This was the kernel from frameworks evil eris....??? Is it not overclocked?? His rom states it is? I am running Set cpu in performance mode not on demand
Framework's EvilEris 2.0 has over clock implemented but it does not work. Both him, ivan and maybe a few other devs are still working on bringing official over clocking to the Eris. Be patient and they will come...
denonlake said:
This was the kernel from frameworks evil eris....??? Is it not overclocked?? His rom states it is? I am running Set cpu in performance mode not on demand
Click to expand...
Click to collapse
This kernel does not appear to be overclocked, from what I have seen and heard , it just locks the cpu at its highest possible rate. It can not clockdown during times of idleness.
Thanks Jcase I will wait for an actual overclock kernel then
I'm not saying its not faster, It jsut doesnt looked OC'd to me.
Hey all,
Earlier today i flash cm7 and the glitch 13.1 kernel, ive gotten to grips with all the changes now and now i am trying to overclock to 1.5 as is possible under glitch.
I got voltage control and after doing some reading decided to get the xtreme version.
The problems i am having now is the phone wont go past 1.3mhz... and if the screen is off too long the phone reboots its self... any ideas what i can do to overcome these?
Is glitch or cm7 holding me back at 1300? Or is it my handset...?
Cheers everyone
You have to experiment with the voltages(be careful!). If you can't get it runnig, well, then your devices' OC capabilities are limitated(1300Mhz is normal, some people even get up to 1800, others only 1100Mhz-there are big differences between every single device).
Hey dark_knight35,
Thanks for letting me know about device specific limitations, much like x86 overclocking in a way.
I will try and get my head round over and under volting and see if it will let me set a higher clock, but i am also going to try diffent kernels i think... know of any amazing or 'the best' oc'ing kernel(s)?
Cheers.
Also the phone randomly crashes and reboots... this is with or without voltage control oc'ed or stock, fault of the kernel or rom? Going to be trying differnt kernels anyway at some point...
mod2max said:
Also the phone randomly crashes and reboots... this is with or without voltage control oc'ed or stock, fault of the kernel or rom? Going to be trying differnt kernels anyway at some point...
Click to expand...
Click to collapse
Well, if phone crashes even without OC, you should do a clean reflash of ROM and kernel.
UPDATE
So this moning this I reflashed Glitch 13.1 as dark_knight35 said, and guess what? As of yet, it has not rebooted its self xD
I should have known something was amiss... because when I came from CF-Root with stock rom the Glitch kernel writing is all read with its own boot logo.
And in recovery at the top it now says "Glitch kernel - CWM-based Recovery v5.0.2.7" and full screen is red text instead of "CWM-based Recovery" with blue text.
So it's all good now and can OC to 1.7 if I wanted to.
Only thing I am missing if anyone know if the baseband as it currently says "Unknown" and you need the correct baseband or (modem) to do anything telecomms wise... so gunna head over to SamMobile in a min and try and hunt down the JV2 modem.
Does anyone know where I can get JV2 modem? Also how do you flash a modem in Odin? Just set it to PDA and start? ...wouldn't wanna do something wrong.
Cheers all.
ANOTHER UPDATE
Phone still reboots, but it's only when it's running off the battery because when it's charging it's fine.
I never had this problem yesterday morning before I learned how to flash etc etc so it's defo software/firmware related and not the handset's hardware.
I'm going to reflash CM7.1 then before even booting up I will reflash Glitch aswell.
If this doesn't stop it would I be right in saying that the modem (or lack of it) is making it crash when it sleeps or locks the screen?
Something about the modem causing unwanted behaviour I sorta of remember from one of TotallyDubedHD's videos but please no one hold me to that lol.
mod2max said:
ANOTHER UPDATE
Phone still reboots, but it's only when it's running off the battery because when it's charging it's fine.
I never had this problem yesterday morning before I learned how to flash etc etc so it's defo software/firmware related and not the handset's hardware.
I'm going to reflash CM7.1 then before even booting up I will reflash Glitch aswell.
If this doesn't stop it would I be right in saying that the modem (or lack of it) is making it crash when it sleeps or locks the screen?
Something about the modem causing unwanted behaviour I sorta of remember from one of TotallyDubedHD's videos but please no one hold me to that lol.
Click to expand...
Click to collapse
Dunno if the modem can cause reboots. If you want to flash one, look into silky's modem thread in dev section and choose one.
Gesendet von meinem GT-I9000 mit Tapatalk
http://forum.xda-developers.com/showpost.php?p=53605359&postcount=10351
I just incountered this today.
What does that mean?
Is it just V2.7.1? Are newer ones also heat protected? Why make them "non-heat protected" in the first place?
It says in the thread: "They do not run all cores online and maxed as TWRP does right now".
I am running 2.7.0 and my cores aren't running on max and not all of them work all the time. I checked with Antutu. So.. What does that mean?
Thanks.
-MaoR- said:
http://forum.xda-developers.com/showpost.php?p=53605359&postcount=10351
I just incountered this today.
What does that mean?
Is it just V2.7.1? Are newer ones also heat protected? Why make them "non-heat protected" in the first place?
It says in the thread: "They do not run all cores online and maxed as TWRP does right now".
I am running 2.7.0 and my cores aren't running on max and not all of them work all the time. I checked with Antutu. So.. What does that mean?
Thanks.
Click to expand...
Click to collapse
Your recovery uses a different kernel than your rom... There's no possible way you can run antutu in recovery.
The official builds just don't have the kernel setup right so they run full throttle
Sent from my LG-VS980 using XDA Free mobile app
Yoinx said:
Your recovery uses a different kernel than your rom... There's no possible way you can run antutu in recovery.
The official builds just don't have the kernel setup right so they run full throttle
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
So when is it running max? Only when I use the recovery itself?
BTW, I found this: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705.
All I need to do to intall it is simply flash it through recovery?
And the warning in the post means that flashing this recovery will change partition type AND will wipe everything?
-MaoR- said:
So when is it running max? Only when I use the recovery itself?
BTW, I found this: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705.
All I need to do to intall it is simply flash it through recovery?
And the warning in the post means that flashing this recovery will change partition type AND will wipe everything?
Click to expand...
Click to collapse
No no no no. You got it ALL wrong =).
Let me explain.
One basic thing you need to understand is that the recovery and the ROM do not interfere with each other. If they did, you wouldn't be able to recover your device if you messed something up ROM-wise.
SO: Your recovery has a "kernel" and your ROM has a kernel. You can't use the same kernel for both recovery and ROM, heck, in most cases you can't even change the recovery kernel unless you flash an entirely new recovery.
What you see in Antutu is your ROM kernel and how it behaves. So put that aside as it has practically no value when you are talking about the recovery.
To your question:
Why would you build a recovery without thermal protection in the first place?
The answer is pretty simple: On most devices nothing has ever happened running a recovery without thermal protection. Most actions in recovery take a maximum of 3-4 minutes and then you're out of there again. The second thing is that since you're operating with a really tiny bit of storage (for the kernel) it's hard to incorporate many codes. AFAIK the whole recovery thing can only take up about 16 MB of storage. That's not much at all!
But a few months back some G2 owners got permanent white/black lines on their screen. It was later proven that heat caused the issue and that it often occured in recovery when flashed. So dr87 made the custom 2.7.1.0 recovery with thermal protection which basically throttles the cpu when it reaches a specific temperature. That would limit the generated heat and save your device - but most recovery actions (like restoring/installing and so on) take a few more seconds to complete but it isn't noticable.
For the recoveries. You have linked to two threads: 2.7.1.0 by dr87 and 2.8.0.2 by blastagator.
I personally still use 2.7.1.0 by dr87 and I've had 0 issues till date. You install that by finding the proper recovery for your device and flash it in the recovery. It is that simple.
The 2.8.0.2 by blastagator also has thermal throttling but I have not used that. No, it will NOT wipe your data UNLESS you change your file system from EXT4 to F2FS. So you can safely flash that but if you choose to change the file system then your data will be wiped.
I hope this answers your questions.
vPro97 said:
No no no no. You got it ALL wrong =).
Let me explain.
One basic thing you need to understand is that the recovery and the ROM do not interfere with each other. If they did, you wouldn't be able to recover your device if you messed something up ROM-wise.
SO: Your recovery has a "kernel" and your ROM has a kernel. You can't use the same kernel for both recovery and ROM, heck, in most cases you can't even change the recovery kernel unless you flash an entirely new recovery.
What you see in Antutu is your ROM kernel and how it behaves. So put that aside as it has practically no value when you are talking about the recovery.
To your question:
Why would you build a recovery without thermal protection in the first place?
The answer is pretty simple: On most devices nothing has ever happened running a recovery without thermal protection. Most actions in recovery take a maximum of 3-4 minutes and then you're out of there again. The second thing is that since you're operating with a really tiny bit of storage (for the kernel) it's hard to incorporate many codes. AFAIK the whole recovery thing can only take up about 16 MB of storage. That's not much at all!
But a few months back some G2 owners got permanent white/black lines on their screen. It was later proven that heat caused the issue and that it often occured in recovery when flashed. So dr87 made the custom 2.7.1.0 recovery with thermal protection which basically throttles the cpu when it reaches a specific temperature. That would limit the generated heat and save your device - but most recovery actions (like restoring/installing and so on) take a few more seconds to complete but it isn't noticable.
For the recoveries. You have linked to two threads: 2.7.1.0 by dr87 and 2.8.0.2 by blastagator.
I personally still use 2.7.1.0 by dr87 and I've had 0 issues till date. You install that by finding the proper recovery for your device and flash it in the recovery. It is that simple.
The 2.8.0.2 by blastagator also has thermal throttling but I have not used that. No, it will NOT wipe your data UNLESS you change your file system from EXT4 to F2FS. So you can safely flash that but if you choose to change the file system then your data will be wiped.
I hope this answers your questions.
Click to expand...
Click to collapse
Thank you for the long comment. Appreciate the time it takes you to answer an Androfool like me
About the black\white lines u mentioned. Its a pretty weird thing.. I mean.. No way their device got so hot at recovery (hotter than when playing games or other heavy usage) that it messed up the screen.
I also heard about people who got screen damage for no apparent reason.
And if we are talking about the lines already, I recently heard that the LG has 2 panel types and that ROM\Kernel need to fit it. To avoid screen damage problems or something. That is pretty weird for me.
About recovery, shouldn't you use the latest available version? I mean.. I dont think they release new ones just cause.
And just because I got curious: What does changing file system gives me?
Thanks again.
-MaoR- said:
Thank you for the long comment. Appreciate the time it takes you to answer an Androfool like me
About the black\white lines u mentioned. Its a pretty weird thing.. I mean.. No way their device got so hot at recovery (hotter than when playing games or other heavy usage) that it messed up the screen.
I also heard about people who got screen damage for no apparent reason.
And if we are talking about the lines already, I recently heard that the LG has 2 panel types and that ROM\Kernel need to fit it. To avoid screen damage problems or something. That is pretty weird for me.
About recovery, shouldn't you use the latest available version? I mean.. I dont think they release new ones just cause.
And just because I got curious: What does changing file system gives me?
Thanks again.
Click to expand...
Click to collapse
Hello again, and no problem. I'd appreciate it if you took the time to hit the thanks button
Even though your device feels warm when playing games like Asphalt 8 it's nowhere near the temperatures the device can reach without throttling. On stock roms the CPU throttle kicks in at about 70 degrees which lowers the cpu frequency and saves the device from heat damage. In recovery, however, there is no such protection by default. Therefore the CPU can get extremely hot - around 90 degrees (without being sure, I think it can hit 95 degrees before shutting off, if it shuts off) and that's what damages the screen.
The white lines you are talking about are not persistent/permanent. They're just there due to incompatibilities between panel type and kernel type. So that's no damage to hardware, just software not working properly.
And yes, some people have gotten permanent lines on a completely stock device. Once again, I tend to think that heat is the problem because that's what many people reported. But surely, faulty hardware is to blame, too.
About the recovery, well, both yes and no. Some updates are crucial and necessary, while others bring new features like a new UI or something like that. When it comes to recovery, I like to play it safe and I use a version as long as it's working as it should but when a newer version is deemed stable I'll use that. So that's just me, but feel free to get the newest.
Changing file system has some benefits in terms of speed - I doubt it's noticable to the average user, but it should be faster when benchmarking etc. Read more about it here: http://forum.xda-developers.com/showthread.php?t=2697069
Keep in mind that changing file systems will WIPE everything, so don't do this unless you have a OTG micro SD reader.
Hi all.
Samsung Galaxy A3 (2016) SM-A310F phones have Exynos 7580 Octa core (8 cores , two clusters with 8 cores Cortex A53) cpu and can work on 1.6 Ghz. I'm find way for activate second cluster with other 4 cores and speed up for 1.6Ghz.
IT IS NECESSARY:
Activate Developer Mode then go to
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
To activate 8 cores and 1.6 Ghz we need first install root with
https://drive.google.com/file/d/0B95gNRt0IyAMSU1LTFVpY01zT3c/view?usp=sharing
Then install custom recovery (only for backup old boot.img) from this thread
http://forum.xda-developers.com/sam...ent/recovery-samsung-sm-a310f-fd-y-m-t3317339
and afrer flash my modified boot.img
Mod edit
Link removed
thats all.. Thank
You need to post a comparison with and without your kernel otherwise it proves nothing.
original kernel A3
Still only 4 cores running according to the last image.
Have you got one that shows all 8 cores in action?
man, exynos governor disable last 4 cpu when not needed high perfomance. But i'm try take snap.
P.S. I'm add snap - 8 cores active (while running geekbench 3)
thanks.. its work
Thanks a lot for this, seems to go to be true.
Is there any cons to perform this ? like Battery draining much more faster or unstability of the system ?
Any downfalls?
Thanks a lot for this.
One question though. Are there any downfalls? Even though we could always go back to stock, would be good to know if activating 4 additional cores that were previously inactive has any effect on the phone. Like why are they even inactive in the first place?
:good:
no discernible performance gain. cpu-z always show the last 4 cores as "stopped".
qwsdert4 said:
no discernible performance gain. cpu-z always show the last 4 cores as "stopped".
Click to expand...
Click to collapse
Have you tried loading the cpu's with something intensive?
ashyx said:
Have you tried loading the cpu's with something intensive?
Click to expand...
Click to collapse
I will try, since sliding the screen would not put any hard burden on the cpu.
I suspect that the custom kernel only unlock 1.6GHz and also reveals the true name of the CPU. However the other four cores are still locked by some means. It would be great if the other four cores are unlocked, since it is such a beautiful little handset
confirmed, working (by ticking all cores in Kernel Adiutor home page). God this phone is fast now! Thank you very much OP
Step-bg-step
Hey guys,
Thanks a lot for this but would it be possible for someone to write more detailed steps in unveiling the 8 cores?
Thanks
Can I enable OEM, root and install your boot(via odin) without custom recovery? Sorry if the question is stupid but I am new to this things.
This is my geekbench without and with installed this mod, to compare for you, guys- GOD, this phone is rly fast now! Proof:
OP please delete this post #16, I dubled it.
Aceseatleon said:
Can I enable OEM, root and install your boot(via odin) without custom recovery? Sorry if the question is stupid but I am new to this things.
Click to expand...
Click to collapse
yes.. you dont need the custom-recovery like TWRP or CWM... it's only necessary for backing up your device before you flash the new boot.img
Info
After flushing will it be like factory reset or all of my data will be in my phone?
Why did you mentioned that custom recovery is needed for backup (for what) or it is must to backup the phone i case something to go wrong?
Aceseatleon said:
After flushing will it be like factory reset or all of my data will be in my phone?
Why did you mentioned that custom recovery is needed for backup (for what) or it is must to backup the phone i case something to go wrong?
Click to expand...
Click to collapse
U need custom recovery for backup boot sector, just in case when something goes wrong with flashing that boot
What about the data. Reset or everything will stay intact.?
Read First: This method is relatively drastic, and will hurt device performance some. You should only use this as a last resort, if the more basic methods of fixing a soft brick didn't work (e.g, factory reset, flash stock firmware, etc.)​
*Update 7/30: On my 6P, I found that the original kernel with this mod was using pretty much 1.5 cores, instead of all 4. People with the 5X were also reporting this, so I modified the images to utilize all 4 cores better. It helps performance a lot (able to beat stock 6P in some Antutu marks now, and play intensive games), try it out if you haven't yet!
*Petition:
I made a petition for Google to officially release and sign modified boot.imgs, so that people with locked bootloaders can fix their devices too. Check it out here. (I apologize for dumbing it down so much, I wanted to make sure everyone could understand it)
*Changelog:
8/26 - EX kernel for Android O uploaded.
8/22 - Android O working, boot.img and source uploaded.
8/08, 2nd Change - Added boot.img for 48C firmware (August security patch).
8/08 - Updated EX kernel to version 4.1.2. This updated zip adds the CPU utilization patch to the init.elemntalx.rc, instead of removing the old init.angler.rc and copying the new init over. That should mean more compatibility with Roms/kernels that modify the init.angler.rc. I also modified the camera-daemon to use cpus 0-3 instead of 0-2, so hopefully this should make the a camera bit faster too.
8/07 - Added boot.img for 1 core, just to see if it would work for devices that didn't work with the 4 core image.
7/30, 2nd Change - Added universal EX zip, this zip should modify your kernel to use only 4 cores, and it should modify it to utilize all 4 cores. You can flash this over most ROMs and it should work. Also added a donation url, and this changelog.
7/30 - Updated this fix to greatly improve performance. Before this fix, the device was only using 1 core for foreground tasks, now it will use all 4 cores. Also revamped OP, and added Marshmallow images.
7/23- Created this fix, stock boot.img, twrp, and EX kernel added.
*What this fix does, and how to apply it:
The problem:
The problem with most of the devices in a BLOD, is that a hardware failure related to the BIG cluster has occurred. This fix remedies the problem by disabling the BIG cores. Unfortunately, this does mean that you will take a performance hit. However, I am continually working on ways to improve the device's performance.
The update: If anyone remembers device performance with the first fix, it was hurt a lot, however, after finding out that the device was only using 1 core for all foreground tasks, I modified the ramdisk to utilize all 4 cores more effectively, and it helps a lot.
Requirements: For this fix to work, you need:
A brain
A computer
A bootlooping 5X with an unlocked bootloader/OEM unlocking enabled
The modified files of your choice.
Fastboot on your computer (preferably installed system wide). If you do not know what this is, or do not have it, look at this post. Answer yes to all of the prompts to install it.
How to apply the fix:
Boot your phone into bootloader (hold power and volume down).
Connect your phone to the computer.
Go to the folder where you have the modified files, then hold shift and right click in a blank space, click on "open command prompt here" in the menu that pops up.
In the command prompt: type "fastboot flash boot [name of the file here]" and then press enter. If you're flashing TWRP, replace boot with recovery. (Linux users, make sure you're running as root)
Edit: with the new universal EX zip, you don't have to flash the modified boot.img now, you can just flash TWRP, and then flash the EX zip, and everything should work.
Boot up your phone, and hopefully it should work!
*If your phone is bootloader locked/OEM locked:
You can try to get your phone to boot long enough to enable OEM unlocking. Some users have reported success by freezing their phone for a bit, then booting it. Others have let their battery drain all the way, and then tried to boot their phone, but the most successful method seems to be heating up your phone (a lot).
If you do attempt any of these methods, make sure you have time and patience, as it will take a long time.
To enable OEM unlocking and unlock bootloader:
Go to settings.
Go to developer options, if you do not see that, go to "about phone", scroll to build number, and then tap it 7 times. You should now see developer options in settings.
Once you're in developer options, click on "OEM unlocking" and accept the prompt.
Now reboot your phone to bootloader, connect your phone to the computer, and type "fastboot flashing unlock" Your bootloader should now be unlocked.
*Downloads:
Boot.img from Android O DP6: Download | Mirror. This Image is the from the first official release of Android O, and is modified to use 4 cores. As a bonus, it also disables forced encryption. Thank you to @xls654 for figuring out how to get Android O to work.
Boot.img from stock 48C, 7.1.2 firmware (August security patch): Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people on the 6p say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
Boot.img from stock 47Z, 7.1.2 firmware: Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people on the 6p say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
TWRP version 3.1.1: Download | Mirror. This TWRP image is modified to use only 4 cores.
EX kernel version 5.03, for Android O: Download | Mirror. EX kernel for Android Oreo, modified to use 4 cores. You must flash it over the 4 core boot.img for it to work.
EX kernel version 4.12, universal zip: Download | Mirror. This zip is modified to use only 4 cores, and it will also apply the speed fix. Flash this in TWRP. I highly recommend you flash this, as it improves device performance notably, and disables forced encryption. This kernel should work with almost any other ROM, and it applies the core utilization mod from the first image, thanks to AnyKernel.
Boot.img modified to use only 1 Core. Some people were reporting that the 4 core images weren't working for them, someone suggested that I make a 1 core version to see if that helps at all. Here it is: Download | Mirror
For Marshmallow:
Boot.img from the latest 6.0.1 20K firmware: Download | Mirror. This boot.img is modified to use only 4 cores, and is modified to utilize those 4 cores more effectively. Untested as of now.
Ex kernel version 1.2.0 for Marshmallow: Download | Mirror. This is the latest EX kernel for marshmallow, it will keep the core utilization mod from the above image, and should work on almost any other ROM, thanks to any kernel. Untested as of now.
*Source Code:
Source for 4 core Android O DP6: Source.
*Tested custom ROMS/kernels
you should be able to use almost any ROM with a stock based kernel, just flash the EX zip over it.
If you have a custom ROM/kernel that worked for you, let me know and I'll put it up here.
*To improve performance slightly:
Flash a custom kernel. I will upload more kernels as people request more, so stay tuned.
Flash a custom ROM. Once again, I will upload more as people request more, so stay tuned.
Overclock the little cores. It can slightly help offset the lost performance, on my 6P, I have mine overclocked to 1632MHz, and it works perfectly for me. Edit: I actually recommend not overclocking. Many people have reported their Little cores failing, so I would go for longevity on this device, and keep it at stock clocks, or even underclock it. The speed difference you get from overclocking is negligible anyways.
Disable animations in developer options. Seriously, as soon as I found out about this tweak, I've used it on ever single device I've owned, it helps a ton.
*Credits:
@rchtk, His post here gave me the idea for how to modify the images.
@flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
@xls654, He found out how to get Android O working with 4 cores.
*FAQs:
What's the password for TWRP/Why is TWRP asking for a password? - In android 7.0, Google added forced encryption to the data partition. To get around this, click cancel when TWRP asks you for a password, and then factory reset the device. Then you can flash EX kernel/Magisk to disable forced encryption.
Why am I getting an error when I try to flash the images? - Your bootloader is probably not unlocked, try running the command "fastboot flashing unlock", If you get an error there too, then you will have to enable OEM unlocking before you can continue.
It's not working for me, how do I fix it? - My only advice for that is: "Flash the stock firmware for whatever version image you're trying to flash, then reflash the images again" If you're stuck on the boot animation, wait at least 20 minutes before you declare it's not working. If none of that works, chances are you have a different problem.
Does EX kernel have the new speed fix? - Yep, the EX kernel zip should apply the 4 core fix, and the speed fix. It should also work with almost any ROM, including stock.
I would like to help as many people as I can, however, I am much more likely to be able to easily help you/reply to your post if you clearly state your problem and the steps you attempted to fix it. I will be much less likely to reply to posts such as "omggg i flashed the image and my phone won't boot helppp" Please read through post first, I did not spend time typing up this OP for no one to read it. If I can see that you read through the OP and have attempted all the steps, then I will be much more willing to help you.
I set up donations on my profile, for those of you who want to donate. I have spent countless hours modifying, flashing, testing, and helping, don't get me wrong, I love doing this and helping y'all out, but donations really keep me motivated to keep going, and donations also will help me fund new equipment and devices that will help further my android development. Every single donation is appreciated Donate to me here!
If this guide helped you, please click thanks, it means a lot to me
Didn't work
I flashed the image and the bootloop is still there, thanks for the effort though. Anything else you'll need for the 5X to continue your research ?
Acelogic_ said:
I flashed the image and the bootloop is still there, thanks for the effort though. Anything else you'll need for the 5X to continue your research ?
Click to expand...
Click to collapse
dang :/ If you can get into twrp, pulling the "console-ramoops" would be helpful, but I don't think you can boot to twrp.
this actually fixes my phone, i do the same with elementalx kernel i disable the big cores as soon as my phone boots up so this img is really handy
TheIronLefty said:
this actually fixes my phone, i do the same with elementalx kernel i disable the big cores as soon as my phone boots up so this img is really handy
Click to expand...
Click to collapse
Awesome! Glad to hear it.
XCnathan32 said:
dang :/ If you can get into twrp, pulling the "console-ramoops" would be helpful, but I don't think you can boot to twrp.
Click to expand...
Click to collapse
Yeah Twrp is not working.
So I just flashed this over the May 2017 build and my phone boots and is working just fine, albeit a bit slowly.
I'll update to the latest build and reflash but for now you can say it works as intended. Thanks for the effort
Gonna try this
Sent from my EVA-L09 using Tapatalk
It's worked for me. Phone is slower, and taking picture with hdr+ is okey but processing is very slow. I turned off animation, is there anything else I can change so phone can perform faster ?
Any idea how long this should take? I managed to get into my 5x and enable debug mode / OEM unlocking
I ran the fastboot flash boot N2G47Z_4Cores.img command and its been stuck for about 5 minutes
This works, thanks. First time I've been able to boot my 5X in months.
Acelogic_ said:
I flashed the image and the bootloop is still there, thanks for the effort though. Anything else you'll need for the 5X to continue your research ?
Click to expand...
Click to collapse
I uploaded a custom TWRP image and EX kernel zip. Try flashing the modified TWRP, and then flashing the modified EX kernel, and see if that works.
after trying again I was able to get it to write successfully however the nexus 5x is still bootlooping, this is an original hardware revision nexus 5x if that helps
ragdoll96 said:
So I just flashed this over the May 2017 build and my phone boots and is working just fine, albeit a bit slowly.
I'll update to the latest build and reflash but for now you can say it works as intended. Thanks for the effort
Click to expand...
Click to collapse
X-calibar said:
It's worked for me. Phone is slower, and taking picture with hdr+ is okey but processing is very slow. I turned off animation, is there anything else I can change so phone can perform faster ?
Click to expand...
Click to collapse
I updated the OP with a modified EX kernel, and some tweaks to make your device faster, check it out to see if it helps your device.
stipo42 said:
Any idea how long this should take? I managed to get into my 5x and enable debug mode / OEM unlocking
I ran the fastboot flash boot N2G47Z_4Cores.img command and its been stuck for about 5 minutes
Click to expand...
Click to collapse
My first time took around 10 minutes to boot I think, if it takes over 20 minutes, reboot your device and reflash, and if that fails, update your firmware to the latest version.
stipo42 said:
after trying again I was able to get it to write successfully however the nexus 5x is still bootlooping, this is an original hardware revision nexus 5x if that helps
Click to expand...
Click to collapse
Are you upgrading from stock firmware or a custom rom? This boot.img is for the latest 7.1.2 build. Unless you have files that you can't afford to delete, I would recommend reflashing your stock firmware with the latest version.
flar2 said:
This works, thanks. First time I've been able to boot my 5X in months.
Click to expand...
Click to collapse
Awesome! I just want to say how much I love your kernel, it makes this fix much more viable.
update: I was able to install twrp and boot into that, but its asking for a password.... @XCnathan32 is there a specific password you set or should "default_password" work?
stipo42 said:
update: I was able to install twrp and boot into that, but its asking for a password.... @XCnathan32 is there a specific password you set or should "default_password" work?
Click to expand...
Click to collapse
default_password didn't work for me, I just clicked cancel when it asked for the encryption, and then I factory reset the device through TWRP. If you have important files you can't delete, you can try just flashing EX Kernel, as I don't think EX needs to access the /data partition.
Update 2 : Seems I was able to just cancel out of the password prompt. Flashed Elemental X and it looks like its booting!
Awesome job my friend, you fixed the (temporarily) unfixable. I'll play around with this for a few days and report back.
Thanks!
XCnathan32 said:
So I found a bootloop fix for the Nexus 6p here, and some users reported having the same problem with their Nexus 5X.
I do not own a Nexus 5X, but I made a modified boot.img the same way I made the modified 6P image. It simply disables the big cores, as that's what was preventing the 6P from booting.
Please report if this works/does not work for you, that way I can get a good sample size to determine how effective this is.
Disclaimer: I have not tested this, I uploaded this image so testers could flash it and report if it works or not. If your device breaks/spontaneously combusts after flashing this, you accepted that risk.
Edit: A few people have reported this working, so it should be safe.
N2G47Z_4Cores.img, this image is based on the latest 7.1.2 firmware for the Nexus 5X, modified by me to only use 4 cores. 4 reported working, 2 reported not working.
To flash it: you must have an unlocked bootloader and fastboot on your PC. Boot your device into bootloader, and then run the command fastboot flash boot N2G47Z_4Cores.img Hopefully, your device will now boot up.
TWRP3_1_1_5X.img, modified to use only 4 cores, will get working TWRP on your device. Not tested yet
To flash, navigate to the folder where it is downloaded, make sure you have fastboot installed, and then run this command: fastboot flash recovery TWRP3_1_1_5X.img.
EX4_10_5X.zip, Elemental X kernel V4.10 for android 7.1.2, modified to use only 4 cores, I highly recommend you flash this, as EX kernel is faster, and you can overclock to the little cluster to make up for some speed. Not tested yet.
To flash, copy the zip to your device, then flash it in the modified TWRP, just go through the AROMA installer as usual. Changing the BIG cpu frequency in the installer will not change anything, as the cores are disabled.
Additional notes:
Root worked on my 6p by flashing the regular SuperSu zip just as normal. None tested for 5X yet
To improve performance slightly:
Disable animations in developer options, it helps a lot.
Overclock little cores with EX kernel, I have mine set to 1632 MHz and everything is working fine so far.
Set CPU governor to performance (or some aggressive governor), with the BIG cores disabled, the battery is already much better, so using a better performance governor shouldn't be a problem for battery life.
Doing a fresh flash of the firmware/factory reset can help a lot too.
Fast custom roms can also help.
Roms that me/other users have found working with this fix:
Pure Nexus worked well for me on the 6p, insane battery life and very little lag. If you are going to flash a rom, be sure to flash the modified EX kernel over it.
If you find a rom that works with this fix, tell me, and I'll put it here.
Credits:
@rchtk, his post here gave me the idea for how to modify the images.
@flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
Feel free to ask me for help, If you have a favorite ROM/Kernel that you want to use, tell me and i'll modify it to use 4 cores.
Please click thanks if I helped you, it means a lot to me
Click to expand...
Click to collapse
Hey man I tried this method, and I can confirm that this works! Although it is slow, it's better than nothing I truly do appreciate your efforts. SCREW LG