Related
How I can go about overclockin Cyanogenmod kernel nightly build. I have the source code downloaded to my linux box. Is it safe to change down to 128 mhz at what is safe maximum. I see that the settings are contained in kernel source is there anything specific for EVO.
Go get SetCPU. Don't go down to 128MHz (your phone will screw up, trust me), and anything over 1130MHz, you're asking for trouble. Some phones can go to 1152MHz, some can go to 1190, and some can go to 1200. The only thing you can do is try.
Looking at change log the latest one shows that they went back to stock speed
Nope. You can still OC to 1113MHz, they just removed some of the less-happy frequencies and underclocked the boot from 998MHz.
http://github.com/CyanogenMod/cm-kernel/commit/b0deae80410e5766471a6b2f12a34b92c9b38e76
Is there a lag fix except voodoo and RyanZA?
RyanZA is taking up 1GB of the RAM and the interface is not as smooth.
Voodoo is problematic - once you update recovery flash, you get a garbled screen for a split second on phone restart.
Is there a fix that is better then these two?
gil80 said:
Is there a lag fix except voodoo and RyanZA?
RyanZA is taking up 1GB of the RAM and the interface is not as smooth.
Voodoo is problematic - once you update recovery flash, you get a garbled screen for a split second on phone restart.
Is there a fix that is better then these two?
Click to expand...
Click to collapse
There is indeed.....
http://forum.xda-developers.com/showthread.php?t=814228
it says there that's it's alpha 0.2??? Is there anything stable? I have JHJP8 froyo 2.2.
You could flash another kernel, one including CWM and sztupy's Universal Lagfix.
Look here : SpeedMod Froyo 341MB RAM
The safest choice regarding versions : Ver I1.2: HZ=250
After flashing (through ODIN - Read carefully Hardcore's instructions) and reboot.
Then shutdown your phone, reboot in recovery mode (CWM), go to ULF and choose No-RFS a=ext-4.
Again, read a lot before, make backups (I use TitaniumBackup Pro) and you will end with a really fast phone.
Is it compatible with froyo and Orange ROM? ([KERNEL] SpeedMod Froyo 341MB RAM) and what is boot animation?
gil80 said:
Is it compatible with froyo and Orange ROM? ([KERNEL] SpeedMod Froyo 341MB RAM) and what is boot animation?
Click to expand...
Click to collapse
Yes, it will work !
Make sure you've backed up the /efs folder, just in case...
BootAnimation is replacement boot/shutdown animation (The shining "S" while booting)
But for your first kernel flash, please use the one I gave you previously.
If flashing went well, then you may willing to test another version ;-)
And to say again, and again, and again ..... backup ! backup ! backup !
Just done this... WOW!!!!
Thanks for the clear instructions - a lot of the threads make this seem very difficult when it doesn't need to be.
I did backup efs though.
I started by installing the 3 Button recovery and then CF-Root to get happy with the concept of flashing before doing any serious damage.
Forget anything you read about lagfixes being poor with Froyo, my SGS is flying!!! Very, very pleased..
D.
dangrayorg said:
Just done this... WOW!!!!
Thanks for the clear instructions - a lot of the threads make this seem very difficult when it doesn't need to be.
I did backup efs though.
I started by installing the 3 Button recovery and then CF-Root to get happy with the concept of flashing before doing any serious damage.
Forget anything you read about lagfixes being poor with Froyo, my SGS is flying!!! Very, very pleased..
D.
Click to expand...
Click to collapse
Please explain the steps you took
You already know how to flash but COMPLETE steps below for anyone new who is just starting out.
I'm using Linux and Heimdall. You can get Heimdall for windows if you wish, I assume steps and commands are the same (you'll need to disable Kies in windows, I don't know how)
Make sure you have lots of space on your internal SD card (I had 3.5Gb and no problems).
Make sure the phone is fully charged.
Enable debug mode under Wireless and network -> USB settings
Windows? Ensure KIES is disabled.
Plug USB cable into laptop
Download the 3-button boot to allow you to place the phone into 'download' mode
(for downloading kernels and other goodies to the phone) and 'recovery' mode (to allow you to select configurable options in custom kernels'
Search the forums.
http://forum.xda-developers.com/showthread.php?t=788108
http://forum.xda-developers.com/showthread.php?t=822756
http://forum.xda-developers.com/showthread.php?t=785201
Step 1, three button recovery. The files you're looking for are:
'GT-I9000_P-SBL_RCVDL_FIX_ODIN.7z'
and you need a pit, which is some kind of bootloader
's1_odin_20100512.rar' (search forums)
Now, extract the 7z file and un-tar the Aries_P-SBL.tar.md5 archive file it contains.
Unrar the s1_odin_20100512.rar archive.
Download the android SDK from google and install it. The adb tool that comes with it is the easiest way to put the phone into 'download' mode.
Put the phone into download mode and use heimdall to send the 3-button boot files:
'adb reboot download'
wait for a few seconds until the screen shows Download mode
'heimdall flash --pit s1_odin_20100512.pit --boot boot.bin --secondary Sbl.bin'
Wait for reboot.
Shutdown and check that you can enter all the download modes by pressing volumedown + home + power to enter download mode (cycle power when it comes up) and volumedown + home + power to enter recovery mode.
Reboot phone.
Install the CF-root kernel to allow you to gain root and backup efs.
I have JPO but CF-Root-JPM-v1.2-Busybox-1.17.1.zip worked just fine.
Extract and untar CF-Root-JPM-v1.2-Busybox-1.17.1.zip to get a kernel image called zImage.
again put the phone in download mode:
'adb reboot download'
wait for a few seconds until the screen shows Download mode
'heimdall flash --kernel zImage --pit s1_odin_20100512.pit'
Wait for reboot.
You now have a kernel with root access. This was a practice flash before the more complex speedmod kernel and gives you a chance to backup /efs
Again, use adb. Get a root shell on the phone and backup your efs
'adb shell'
$ <- this is the shell promot
$ su
# <- this is the superuser prompt
# cp -a /efs /sdcard/efs
#
# exit
adb pull /sdcard/efs
Extract the speedmod-kernel-i1_2-250hz-r2.zip file linked to above and again untar it. You will have another Linux kernel also called zImage. Don't get it mixed up with CF-Root.
again put the phone in download mode:
'adb reboot download'
wait for a few seconds until the screen shows Download mode
'heimdall flash --kernel zImage --pit s1_odin_20100512.pit'
Wait for reboot.
Once fully booted into the new kernel shutdown and restart in recovery mode.
Use the volume key to go up and down. Go to 'advanced ULK features' -> 'Lagfix options'->'Use No-RFS advanced a=e4'
Go Back
Go to 'Tweak options' and select all four tweeks inside (these alter some Kernel parameters).
Go Back
Go Back
Reboot System Now
After a mini-boot you'll get a warning about config files not matching. This is the system preparing to reformat the phone to ext4. Select the first option "Yes, with backup and restore"
Let the system backup your phone to the SD card
Let the system reformat your device
Let the system restore your phone
System reboots. Lagfix is installed
Profit.....
D
"You already know how to flash but COMPLETE steps below for anyone new who is just starting out."
No, I don't really know. I don't understand that part and when I did it last time it messed my phone. So I don't understand most of what you've explained. I'm kinda dumb when it gets too technical. I appreciate the effort and the long post. It must have taken quite some time.
I thought it would be easy to understand and comply but not for me. I need a guide for dumber
madfix said:
Yes, it will work !
Make sure you've backed up the /efs folder, just in case...
BootAnimation is replacement boot/shutdown animation (The shining "S" while booting)
But for your first kernel flash, please use the one I gave you previously.
If flashing went well, then you may willing to test another version ;-)
And to say again, and again, and again ..... backup ! backup ! backup !
Click to expand...
Click to collapse
I've used once my backup pro and it sucks since it messed up all my contacts and made an error with google process. I also used ROM Manager to no avail for restoring my ROM - I got an MD5 mismatch error.
By luck, I got the original Orange ROM backup to flash with Odin.
Of course I didn't o all the flashing since I really find it difficult to understand. I have no idea what is the right flow of things. what comes first and so on, I've read all the posts here and I simply can't find a 1 2 3 steps. It's mostly techincal with lots of links and sub links which confuses me as to what should I choose first.
Please can someone write a simple 1 2 3 step of how to fix the lag and add 341MB? With no links on to of links to confuse everything. I really need it simple.. I'm a moron, what can I say.
gil80 said:
"You already know how to flash but COMPLETE steps below for anyone new who is just starting out."
No, I don't really know. I don't understand that part and when I did it last time it messed my phone. So I don't understand most of what you've explained. I'm kinda dumb when it gets too technical. I appreciate the effort and the long post. It must have taken quite some time.
I thought it would be easy to understand and comply but not for me. I need a guide for dumber
Click to expand...
Click to collapse
Reading is THE key: http://forum.xda-developers.com/showthread.php?t=723596
I've read it all. I dont get it. What should I do to fix the lag issue?
I have PDA: JHJP8
PHONE: JHJP5
Which file(s) should I download?
madfix said:
You could flash another kernel, one including CWM and sztupy's Universal Lagfix.
Look here : SpeedMod Froyo 341MB RAM
The safest choice regarding versions : Ver I1.2: HZ=250
After flashing (through ODIN - Read carefully Hardcore's instructions) and reboot.
Then shutdown your phone, reboot in recovery mode (CWM), go to ULF and choose No-RFS a=ext-4.
Again, read a lot before, make backups (I use TitaniumBackup Pro) and you will end with a really fast phone.
Click to expand...
Click to collapse
According to: http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-speedmod-kernel-faq.html
I shouldn't use No-RFS a=ext-4.
Moreover, how can I find out my phone HZ?
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Click to expand...
Click to collapse
Well that i a good start. Good to see some reading before the jump in feet first.
corruptsmurf said:
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
Click to expand...
Click to collapse
That's why we're here.
corruptsmurf said:
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
Click to expand...
Click to collapse
Edited: added Later
ADB is a commander center/protocol (if you will) that allows you to control your phone via a PC/Mac/Linux. You can push files which would be taking the file and "pushing" to the phone. Or "pulling" files from the phone and putting them on the computer. It's simply as it states, pushing and pulling the files.
To see what a Kernel is read This.
A ROM is the phones physical Operating system. Similar to what Window, Mac or Linux world be.
corruptsmurf said:
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Click to expand...
Click to collapse
Before you can flash Clockwork Mod you need to root your phone and turn s=off. For one of the methods, - before you can start you need to set up the ADB (Android Debug Bridge). See my signature for the quickest and most painless way to get that set up. You will also need VISIONary.apk. A quick Google Search will find it for you. Link
corruptsmurf said:
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
If you want a 2.3 based ROM you will need to flash Recovery image 3.0.0.6, link can be found in my signature, and hit up the development section to read reviews on different ROMs. I personally like the plain AOSP look so that leave Cyanogen(mod). But i know TeamRoyal has put together some newer ROMs that i haven't tampered with yet.
I do everything on my phone through CWM (clockworkmod) or terminal emulator, so there's no need for a PC, unless to download the files and transfer them to my SDcard, as I don't understand adb. Anyways, I'm gonna explain this very short and sweet cuz I was once in your shoes, and remember how much I had to read to understand something That could've been explained so simply.
Think of it this way. You're building the software version of a car. Now, if the whole car is the ROM, then the engine is what would be the kernel. And flashing would then be another word for installing , Now, a toyota with a ferrari engine, would be a custom ROM. While a toyota with a ferrari engine and BMW insignias all over it would then be a custom themed ROM.
**Remember, you can never install a car on something, but you can always install something in a car**
Ex. You can never flash a ROM on a kernel, but you can always flash a kernel on a ROM.
Anyways, first off, you will need CWM recovery to flash. Get it from the market. In the app itself, flash (this is the "flash" in the app) recovery 3.0.0.6. This will flash (this flash is not in the app) anything; any ROM, any kernel, etc. as long as its a FLASHABLE ZIP.
To boot into the recovery (the place you do flashing), hold both volume down and power buttons down as you either turn on or restart your phone. The screen you see is the bootloader. Choose recovery using the volume buttons, and use the power button to select it.
Going to flash a new ROM? Do a factory reset (in recovery), wipe cache (in recovery), and wipe delvik cache (this is in advance in recovery). Then install zip. Its pretty straight forward from there.
Going to flash an updated ROM, skip factory reset (as this deletes all data on your phone) and do the rest.
After you've flashed the ROM, you can now flash the kernel.
Note that, kernels are ROM specific. Read what kinds of ROM's the kernel is for before you flash it.
There, easy as pie, yeah? Hope that helped.
I recommend cyanogenmod 7 (Gingerbread based ROM) with faux's kernel (Gingerbread based kernel)
Sent from my HTC Glacier using XDA App
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
Neidlinger's got your back.
1. Glad you're reading before doing. What a welcome change of pace!
2. Flashing is the process of installing new software. We "flash" it to the phone's memory.
3. ADB is using a computer to control the phone via command-prompt from DOS. Push is a command which sends a file from your computer to your phone. Do a search, there are lots of good guides on ADB. TrueBlueDrew made one just recently that I highly recommend.
Here's Drew's thread. Don't forget to hit his thanks button! - http://forum.xda-developers.com/showthread.php?t=928370
4. Start with Clockwork Recovery and a nandroid backup. That's good practice. CWR2 is compatible with Froyo (2.2) ROMs. CWR3 is compatible with Gingerbread (2.3) ROMs. CWR 3.0.0.6 is compatible with BOTH. Very convenient.
5. I say start with CM7. It's extremely stable, even though it's still in development. A ROM is a complete OS replacement for the phone. ROMs contain kernels, which control the most basic hardware, such as processor. If you flash a custom kernel on your stock ROM, you can overclock it more. You can also flash custom kernels on top of custom ROMs for different battery life, clock speed, etc.
To be honest I don't even bother with custom kernels since this phone is so damn fast out of the box I really don't see the point.
QUICK TIPS FOR CM7 - On your first boot, let it sit for 5-10 mins before setting up. There are background processes running and interrupting can harm stability. BEFORE you sign into google for the first time, after it's finished sitting, reboot. This will clear out any wifi glitches and give you smooth sailing.
Have fun!
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Uchennadi said:
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
This is pretty much spot on. The developers have included kernels that they feel make the OS preform at it's peak. and most of them will allow for overclocking. However on some of them you may need to use a program called "setCPU" to adjust the frequencies. Cyanogen(mod) will have this built into the ROM natively. However most of the veterans will not promote running your phone in an over clocked status 100% of the time. most of us leave the phone at 1Ghz or slower. There are physical reasons, ie the constant expansion and contract of the chip isn't good for the mother board.
If i were you i'd stick with the Stock Kernel and leave it running as it. That way the developer can adjust their ROM, if you use an 3rd party kernel they aren't familiar with the coding so it's not going to act correct.
I'm not putting down what the kernel coders do, they do an awesome job. but for a n3wb i'd leave well enough alone.
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.
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