Related
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
I say ALMOST because you must have either used the manual (adb) method to upgrade to Nougat, or flashed the v30b_update.zip to use this. If you are on MM, this will more than likely brick your phone.
OK, so after testing, here is the complete Nougat zip. It is every partition from the v30b KDZ except boot, system, and recovery (obviously), so you keep TWRP. This has the modem, tz, and rpm partitions. If you flashed the other zips that I posted with the individual partitions, no worries, reflashing them does not hurt anything, and I am not going to make yet another zip. Some people may want to just flash the minimal needed to get to Nougat so they can restore MM TWRP backups if they need / feel like it.
You can dirty flash this on top of my v30b_update.zip, but you are better off doing a factory reset (full wipe). I could have included the wipe in the zip, but this way -- YOU can decide.
Also, you MUST have an H901. Not an H900, not an F600, not a BMW, or Audi, or Toyota. Again, if you have anything other than an H901, this will brick your phone.
This fixes the front facing camera issue with 4x3 5mp (it was the aboot partition that solved that FYI). Can't say what else it may have fixed that I didn't even know was broken. I also can't say what functionality may be LOST -- that is why I am posting this.
If you flash this, and suddenly something doesn't work that used to, please post in this thread. Same goes if something suddenly STARTS working.
Download here
SHA1: b1ac20a6eaccf2dfbd22c09886ddcd03ab638ec3
If you want to be able to revert to MM, then you need to make a FULL backup of your phone, and I don't mean with TWRP.
* adb reboot recovery
* adb shell
# this will give you a list of all the partitions
* ls /dev/block/bootdevice/by-name
* exit
# You then need to backup all the partitions
* adb pull /dev/block/bootdevice/by-name/<just go through them in order> <name of partiton>.img
# example
* adb pull /dev/block/bootdevice/by-name/aboot aboot.img
* adb pull /dev/block/bootdevice/by-name/modemst1 modemst1.img
# do this for EVERY partition
# you will need 64gigs of space on your PC to hold everything even if the phone is empty since dd stores zeros.
# Now, if you ever want to revert, you do the reverse, and just flash each one of these with dd and you will be right back to where you are.
-- Brian
reserved
reserved #2
Awesome!! full Naugat... so when is debloated version coming? I tried to debloat, but even removing non essential T-Mobile apps gives me bootlloop, or if you can tell me which apps are safe to remove will be a huge help ...
Thanks for you work man only active developer for H901, and I know you have allot on your plate but you are our only hope... Cheers!!
A full debloat is a very tedious process, so it is bottom of the barrel. If someone else doesn't jump in, I will eventually release one though.
-- Brian
Thanks again! Just installed. Tested the only thing I encountered on the update.zip and it is confirmed fixed with this.
Keep up the good work! :thumbup:
---------- Post added at 11:22 AM ---------- Previous post was at 11:19 AM ----------
zeexhan said:
Awesome!! full Naugat... so when is debloated version coming? I tried to debloat, but even removing non essential T-Mobile apps gives me bootlloop, or if you can tell me which apps are safe to remove will be a huge help ...
Thanks for you work man only active developer for H901, and I know you have allot on your plate but you are our only hope... Cheers!!
Click to expand...
Click to collapse
I've removed all the Tmobile apps that I don't want or need and I haven't gotten any bootloops.
Just have to remove that apps entire folder. Also removed some Google apps I didnt want.
so...this does not include the N modem then? and the first update.zip does? cause i thought i saw the first update.zip it say flashing modem..
Please disregard, thank you
Is these fix front camera
Sent from my LG-H818 using XDA-Developers Legacy app
sumitverma1 said:
Is these fix front camera
Sent from my LG-H818 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes this will fix the front facing camera bug that was mentioned in the update.zip thread.
I notice this seems to include a RPM partition. So do we need to flash your add-on.zip still for the nougat power management? It sounds like all we need now is update.zip and this along with SuperSU ? Awesome work btw. My battery life overnight after flashing this was 1 percent loss with WiFi and Bluetooth on. You should combine your update and this camera/misc fix zip together.
First post updated to answer that and some other questions.
-- Brian
I flashed this new add-on or full partition zip
cleared my Dalvik cache and my regular cache and well I didn't fell like re entering all my mods and settings so I didn't do the full wipe. noticed the new boot loader right away can pause boot now lol. I didn't have the camera bug but am wondering how this latest zip will do with my battery some one posted it helped there overnight only running 1% will post if I find more things it affected "can't hurt things" and I'm happy with the mods N 7.0 can run so I'm even deleting my MM 6.0 BACKUPS. No need to have that option anymore. I do wonder about kernels, the old sound mod, and https://forum.xda-developers.com/tm...-msm-8992-cpu-io-ram-interactive-gov-t3351478
Any plans to track down where the rollback counter is getting incremented and remove that part?
@famewolf anti-rollback version wasn't incremented even if you took the OTA or flashed the KDZ. It was version 2 on MM, and it is still version 2.
I have no idea why people are having a problem flashing back to v20L (it passes the rollback check in LG UP -- but then fails later in the flash). Makes no sense....
-- Brian
runningnak3d said:
@famewolf anti-rollback version wasn't incremented even if you took the OTA or flashed the KDZ. It was version 2 on MM, and it is still version 2.
I have no idea why people are having a problem flashing back to v20L (it passes the rollback check in LG UP -- but then fails later in the flash). Makes no sense....
-- Brian
Click to expand...
Click to collapse
Ok, I'll chalk it up to my friend trying to go back to MM without restoring all partitions then because you made it clear a normal restore wasn't gonna do it. I think they tried using flashfire. I'm not upgraded yet.
Will this fix the battery drain issue or is it the same as flashing the fix?
Could you make a fix for just the front facing camera for those who flashed the update.zip and don't want to re-reset and flash?
@k00lguy105 I dunno. Some people were getting better battery life, others worse. Try it -- you can always revert.
@xxcmb3k3xx It was the aboot partition that fixed the camera. The thing is, I don't know the consequences of flashing JUST the aboot without all the other boot loader partitions. I will make you a zip if you want to try it, but I can tell you now that aboot is not something you want to mess with without 100% certainty of the outcome. I was convinced that the 808 could always be recovered with the SD card, but aboot is the one part of the boot process that will turn your phone into an unrecoverable brick.
If you don't want to wipe, then don't -- it is safe to dirty flash this. I only recommend wiping because that way you are guaranteed to not have problems. At least wipe cache, and as I said above, if bad comes to worse you can always revert.
-- Brian
runningnak3d said:
@k00lguy105 I dunno. Some people were getting better battery life, others worse. Try it -- you can always revert.
@xxcmb3k3xx It was the aboot partition that fixed the camera. The thing is, I don't know the consequences of flashing JUST the aboot without all the other boot loader partitions. I will make you a zip if you want to try it, but I can tell you now that aboot is not something you want to mess with without 100% certainty of the outcome. I was convinced that the 808 could always be recovered with the SD card, but aboot is the one part of the boot process that will turn your phone into an unrecoverable brick.
If you don't want to wipe, then don't -- it is safe to dirty flash this. I only recommend wiping because that way you are guaranteed to not have problems. At least wipe cache, and as I said above, if bad comes to worse you can always revert.
-- Brian
Click to expand...
Click to collapse
I just dirty flashed and everything seems to be working fine, I'll update for battery later.
I have got the used z5c. It's stock rom with no unlock bootloader or rooted.
Because this phone is very old(3years) so the battery health is not so good. Maybe it is better performace if I flash it in custom rom?
vgran said:
I have got the used z5c. It's stock rom with no unlock bootloader or rooted.
Because this phone is very old(3years) so the battery health is not so good. Maybe it is better performace if I flash it in custom rom?
Click to expand...
Click to collapse
Maybe... it will be much better if you install a custom rom (Lineageos) without gapps!! The Play-Services need a lot of energy.
i raccomend Resurrection Remix + Undervolting + microg + minimum big cores online set to 0 using kernel adiutor
I use the stock ROM but debloated (systemlessly), with some apps and services (and a few receivers) disabled as well. I also use a couple of scripts and Kernel Adiutor to tweak governor and VM settings.
You don't necessarily have to use a custom ROM and lose Sony-specific features to get good battery life!
plusminus_ said:
I use the stock ROM but debloated (systemlessly), with some apps and services (and a few receivers) disabled as well. I also use a couple of scripts and Kernel Adiutor to tweak governor and VM settings.
You don't necessarily have to use a custom ROM and lose Sony-specific features to get good battery life!
Click to expand...
Click to collapse
hi, I think I like the sound of this - custom rom would mean forfeiting find my phone right?
could you explain in a little more detail what you mean by systemlessly debloating ? actually a guide to doing exactly what you did would be awesome what did you disable and which scripts did you use? does this involve rooting the phone? I'm not a total noob, have flashed custom roms before but usually get guidance from a friend.
any info appreciated! just got this phone second hand and it struggles to last 2 days on one charge.
Thanks,
D
PS - sad to see compact phones go, I find even the z5 compact to be slightly too big coming from a galaxy ace 3 , and I have huge hands. I just want to be able to use my phone with one hand, lying in bed holding it above my head without it falling out of my hand and hitting me in the face ! the square edges don't help, and the case doesn't grip well enough - what case are you using?
deckadance said:
hi, I think I like the sound of this - custom rom would mean forfeiting find my phone right?
could you explain in a little more detail what you mean by systemlessly debloating ? actually a guide to doing exactly what you did would be awesome what did you disable and which scripts did you use? does this involve rooting the phone? I'm not a total noob, have flashed custom roms before but usually get guidance from a friend.
any info appreciated! just got this phone second hand and it struggles to last 2 days on one charge.
Thanks,
D
PS - sad to see compact phones go, I find even the z5 compact to be slightly too big coming from a galaxy ace 3 , and I have huge hands. I just want to be able to use my phone with one hand, lying in bed holding it above my head without it falling out of my hand and hitting me in the face ! the square edges don't help, and the case doesn't grip well enough - what case are you using?
Click to expand...
Click to collapse
Hi,
You could definitely use Google's Find My Device with a custom ROM, but I think you would lose access to Sony's 'my Xperia' service.
Unlocking the bootloader
The process of unlocking your bootloader and rooting has *many* steps, but I used this guide - and it was smooth, but took a little while: https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388
Things have changed since then, so if you plan to root I think some of the final steps will be different.
Modified steps:
- I later used the TA PoC tool - this would replace steps 6 and 7. For this tool you would disable dm verity, Sony RIC and force encrypt, but not install recovery. TA PoC has instructions in the script, it's nice.
- *edit* Instead of using the TA PoC tool, a modified version of rootkernel, as in the original guide, can be used to replace steps 6 and 7. Rename the backed up file from step 1 to TA.img and copy it into the rootkernel folder, then run the script with these options:
Disable dm-verity? Y
Disable force-encrypt? Y
Disable Sony RIC? Y
Install TWRP recovery? N
Install superuser? N
Install DRM fix? N
Install munjeni's TA PoC? Y
Install busybox? N
- Skip step 9. (You can install Xposed through Magisk later)
- Flash a recovery separately. I use this one
Rooting
Once the bootloader is unlocked and you have a custom recovery, you can install Magisk which seems to be the main way to root devices these days (I love it). As well as root management, it allows you to make changes to the system partition without actually touching the partition ("systemlessly") by installing modules in the Magisk Manager. It can also run scripts on boot.
Installation instructions are here but basically flash the Magisk zip in recovery.
Debloating
There is one module called Terminal Debloater which hides system apps of your choosing from the phone, as if they were uninstalled. You choose from a text-based list in a terminal emulator. I don't think I can explain it well, but there is a video!
[Magisk] How to Uninstall System Apps using Magisk
With root (and an app such as Titanium Backup) you could just disable them all instead but using this module felt cleaner to me
I think the list of apps that you don't need (and thus can be debloated or disabled) will be specific to you, but there are Google apps like Hangouts, Chrome, Photos, the Google app, Google Print Recommendation Service that I hid, as well as many Sony apps (perhaps ironic since my whole point was about keeping Sony features ha) like Support, What's New, Movie Creator, Xperia Lounge. And lots of weird little things like GoogleAnalyticsProxy, AnonymousData, CrashMonitor, phone-usage, pip - my phone has been fine without them.
I've attached my list from Terminal Debloater (it can be imported but it might be helpful just to look at)
This is another nice module if you ever find your phone's temperature to be a problem: https://forum.xda-developers.com/crossdevice-dev/sony/z3-z4-z5-fsc-improve-performance-t3673785
I use a governor script which I attached here with an app called Kernel Adiutor - it lets you change lots of settings but I mainly use it just to make sure that script runs at the right time. Part of the script sets the minimum number of big cores online to 1 (0, as in the post above mine, didn't work for me!)
(My other main script disables a few Google Play Services... services that I don't want running, every reboot. I don't want to make you break anything so I won't go into more detail at this point!)
The bad news
2 days on a single charge sounds pretty good I don't know what improvements all of this could provide, maybe you'd get to 3 days? Maybe it's not even worth it haha. I like having root though.
P.S.
I genuinely don't know what phone I'll move to if (when?) this one dies. You're right about the edges, they definitely affect the ergonomics of the phone. I still remember the way my HTC One S fit in my hand so beautifully compared to this phone!
I use this Ringke case. It's a little thick but it's worked very well. I drop this thing all the time and it's still fine.
So many links, sorry. I hope some of this is useful.
+-
But wait, there's more!
Worked out how to list the packages I have disabled (instead of debloated). Mostly Sony apps again lol. Now that I think about it there's a fair amount of bloat...
plusminus_ said:
But wait, there's more!
Worked out how to list the packages I have disabled (instead of debloated). Mostly Sony apps again lol. Now that I think about it there's a fair amount of bloat...
Click to expand...
Click to collapse
what a comprehensive response, LEGEND !
I saw that case but decided against it because the microusb port cover is just annoying, you can't connect it with one hand comfortably so it's more trouble than benefit
I used to have a nice rubbery original nokia cover on my N8 but can't find that anymore, I really liked that it wouldn't slide out my pocket...
deckadance said:
what a comprehensive response, LEGEND !
I saw that case but decided against it because the microusb port cover is just annoying, you can't connect it with one hand comfortably so it's more trouble than benefit
I used to have a nice rubbery original nokia cover on my N8 but can't find that anymore, I really liked that it wouldn't slide out my pocket...
Click to expand...
Click to collapse
:good:
You could cut off the port cover but it's a pretty extreme solution.
This may be a nice alternative. I think a potential problem with TPU cases is that some are advertised as slim and they're possibly too thin to actually protect the phone when dropped...
plusminus_ said:
Hi,
..........
Modified steps:
- I later used the TA PoC tool - this would replace steps 6 and 7. For this tool you would disable dm verity, Sony RIC and force encrypt, but not install recovery. TA PoC has instructions in the script, it's nice.
- Skip step 9. (You can install Xposed through Magisk later)
- Flash a recovery separately. I use this one
Rooting
Once the bootloader is unlocked and you have a custom recovery, you can install Magisk which seems to be the main way to root devices these days (I love it). As well as root management, it allows you to make changes to the system partition without actually touching the partition ("systemlessly") by installing modules in the Magisk Manager. It can also run scripts on boot.
.................
+-
Click to expand...
Click to collapse
@plusminus
Thank you for your excellent instructions, but have a little problem...
Booted fine off the Ta Poc new_boot.img
Booted up good through initial setup.
Flashed TWRP - good.
Installed Magisk using TWRP - no errors.
Rebooted.
Bootloop.
I fastboot flashed the new_boot.img again and am up and running again but without Magisk.
I have googled how to install Magisk after Ta Poc but not found anything to be confident of trying.
Do you know this issue? Can you suggest other routes to install Magisk? Any ideas?
Edit: also tried installing Magisk into the boot image through the Manager method - bootloop.
Success! but not with TA Poc. I used RootKernel, installed Magisk via TWRP. Booted good. Magisk Manager shows Magisk is up. The shows goes on...
goon-heaven said:
Success! but not with TA Poc. I used RootKernel, installed Magisk via TWRP. Booted good. Magisk Manager shows Magisk is up. The shows goes on...
Click to expand...
Click to collapse
I just saw your posts, I'm sorry my info caused problems for you!
I searched the TA PoC thread to see if I could find anything relevant, and it seems other users have had problems with Magisk after using TA PoC. The solution, as you found, is actually to use RootKernel! This modified version of RK includes an option for TA PoC (instead of the DRM fix), so it's probably the best option for our phone.
Sorry for the inconvenience; I will also edit my post. :angel:
Thank you for your guidance. Good to have you around to help.
Never be sorry. I know the risks and unforeseen issues that happen.
Flashtooled ROM again for a clean start, and flashed the modified RK boot.img, flashed TWRP, magisk. Your revised instructions has worked good for me.
Thank you!
Is there a twrp image for this device? and if not do you think it would be possible for me to compile my own?
You could definitely try, as far as I've seen there isn't an image out yet for the gen2. I've got one on hand though, and I'd be willing to help test once you've got it built!
It's not the easiest of tasks because we only have a 32MB recovery partition and stock kernel only supports gzip for compression. :/ Sooooooo yeah... Not fun lol.
Follow-up to this. I did try to make TWRP for this device, display stayed blank.. I assume others have likely tried and hit the same roadblock and gave up . Finding a GSI with any sort of Gapps package that works on this device is stupidly hard.