where can i find the stock kernel for 5.1 - Nexus 5 Q&A, Help & Troubleshooting

In attempt to switch from franco to elementalx, I think I have to flash the stock kernel before i flash elementalx.

jjs0891 said:
In attempt to switch from franco to elementalx, I think I have to flash the stock kernel before i flash elementalx.
Click to expand...
Click to collapse
Nah. If you're feeling paranoid, maybe flash stock system image.

people wrote that the franco kernel alters the ramdisk or whatever whereas elementalx does not. They say it may "cause problems". I haven't found anyone to have actually tested this theory and i'm not really willing to try. I don't want to set up my entire phone and apps again.

jjs0891 said:
people wrote that the franco kernel alters the ramdisk or whatever whereas elementalx does not. They say it may "cause problems". I haven't found anyone to have actually tested this theory and i'm not really willing to try. I don't want to set up my entire phone and apps again.
Click to expand...
Click to collapse
Download the factory image. Extract it. Inside is a zip file, extract it too. There you'll find the boot.img. Flash it with fastboot
Sent from my Nexus 5 using XDA Free mobile app

Is boot.img.p the same thing? That's the closest thing to boot.img in the zip file

jjs0891 said:
Is boot.img.p the same thing? That's the closest thing to boot.img in the zip file
Click to expand...
Click to collapse
The factory images are found here: https://developers.google.com/android/nexus/images
The .p extension means it's a patch, usually found in OTA files, which you probably downloaded instead of a factory image.

jjs0891 said:
Is boot.img.p the same thing? That's the closest thing to boot.img in the zip file
Click to expand...
Click to collapse
Use 7zip to extract the factory images.

beekay201 said:
Use 7zip to extract the factory images.
Click to expand...
Click to collapse
What's wrong with WinRAR?

zagorteney said:
What's wrong with WinRAR?
Click to expand...
Click to collapse
Nothing is wrong with WinRAR, why do you ask?

Aerowinder said:
Nothing is wrong with WinRAR, why do you ask?
Click to expand...
Click to collapse
I'm just asking if there is any difference in extracting factory images. I'm doing this with WinRAR and now have problems executing system.img not just with 5.1, but with 5.0.1 either.

I realised that the nexus toolkit has the option to flash boot.img.
Thank you guys for the helping

jjs0891 said:
I realised that the nexus toolkit has the option to flash boot.img.
Thank you guys for the helping
Click to expand...
Click to collapse
What's nexus toolkit? That's some foreign object isn't it? fastboot flash boot boot.img and you're done.
Sent from my Nexus 5 using XDA Free mobile app

Related

How do I Inject TWRP into a non-TWRP using rom?

I want to flash over to Slim ICS and try that out for a little bit but I want to continue using TWRP instead of CWM. I know I should be able to inject TWRP through the recovery bit I'm not sure how. Any help?
Sent from my Unicorn powered SGS4G
Juls317 said:
I want to flash over to Slim ICS and try that out for a little bit but I want to continue using TWRP instead of CWM. I know I should be able to inject TWRP through the recovery bit I'm not sure how. Any help?
Sent from my Unicorn powered SGS4G
Click to expand...
Click to collapse
To use the newest TWRP 2.2 you will need to pull the boot.img from aokp and make sure to pull the bcm4329.ko file to. Then using heimdall cmd flash the boot.img and then push the bcm4329.ko file.
The reason is because FB removed the inject TWRP toggle in the new versions.
eollie said:
To use the newest TWRP 2.2 you will need to pull the boot.img from aokp and make sure to pull the bcm4329.ko file to. Then using heimdall cmd flash the boot.img and then push the bcm4329.ko file.
The reason is because FB removed the inject TWRP toggle in the new versions.
Click to expand...
Click to collapse
Ah! Thanks! Where do I find the bcm4329.ko file?
Sent from my Unicorn powered SGS4G
Juls317 said:
Ah! Thanks! Where do I find the bcm4329.ko file?
Sent from my Unicorn powered SGS4G
Click to expand...
Click to collapse
/system/lib/modules
eollie said:
/system/lib/modules
Click to expand...
Click to collapse
Figured, thanks!
Sent from my Unicorn powered SGS4G
If you can't get it, I have a link to a CWM flash able zip that gives you twrp. Here's the link:
http://forum.xda-developers.com/showthread.php?t=1721489
brandonc0526 said:
If you can't get it, I have a link to a CWM flash able zip that gives you twrp. Here's the link:
http://forum.xda-developers.com/showthread.php?t=1721489
Click to expand...
Click to collapse
That is the older version of TWRP. It is a option, I just prefer the newest version it has the quirks ironed out.
I still haven't tested using the GB/CM7 twrp zip that you linked him to in ICS roms. I'll probably get around to making a twrp 2.2/ICS zip for you guys to stay on the safe side since it's easy to get the ramdisk image from an AOKP build. I just need to do it when I'm home.
brandonc0526 said:
If you can't get it, I have a link to a CWM flash able zip that gives you twrp. Here's the link:
http://forum.xda-developers.com/showthread.php?t=1721489
Click to expand...
Click to collapse
I knew that that existed but knowing it was for GB I wasn't gonna use it. Thanks though!
Sent from my Unicorn powered SGS4G
FBis251 said:
I still haven't tested using the GB/CM7 twrp zip that you linked him to in ICS roms. I'll probably get around to making a twrp 2.2/ICS zip for you guys to stay on the safe side since it's easy to get the ramdisk image from an AOKP build. I just need to do it when I'm home.
Click to expand...
Click to collapse
Actually that one works on all the ICS roms. I first tried it on CM9 then I realized it should work on all of them so I tried and it has not once failed on me. The only downside is that its a older twrp but still good.
eollie said:
To use the newest TWRP 2.2 you will need to pull the boot.img from aokp and make sure to pull the bcm4329.ko file to. Then using heimdall cmd flash the boot.img and then push the bcm4329.ko file.
The reason is because FB removed the inject TWRP toggle in the new versions.
Click to expand...
Click to collapse
how do i extract the boot.img?
Juls317 said:
how do i extract the boot.img?
Click to expand...
Click to collapse
Unzip the zip with winrar or whatever you use. Pull the boot.img over to your comp. Then flash it with heimdall.
Code:
heimdall flash --kernel boot.img
Or you could be reallllllllly nice to FB and ask him to make a CWM flashable of the new version of TWRP
hechoen said:
Unzip the zip with winrar or whatever you use. Pull the boot.img over to your comp. Then flash it with heimdall.
Code:
heimdall flash --kernel boot.img
Or you could be reallllllllly nice to FB and ask him to make a CWM flashable of the new version of TWRP
Click to expand...
Click to collapse
Haha, FB if you have time to do such a thing, I'm sure the community would appreciate it! But I'm ok with flashing through heimdall haha
Sent from my Unicorn powered SGS4G
Code:
unzip aokp_galaxys4gmtd_unofficial_milestone-6-03.zip boot.img
That will extract just the boot img, but it has to be don from cmd line. Then do what hecheon says.
eollie said:
Code:
unzip aokp_galaxys4gmtd_unofficial_milestone-6-03.zip boot.img
That will extract just the boot img, but it has to be don from cmd line. Then do what hecheon says.
Click to expand...
Click to collapse
No sh#t you can extract from a zip with heimdall! Thanks Still will most likely use winrar but good to know.
hechoen said:
No sh#t you can extract from a zip with heimdall! Thanks Still will most likely use winrar but good to know.
Click to expand...
Click to collapse
I dont think you can. Im using ubuntu so its the built in extractor.
eollie said:
I dont think you can. Im using ubuntu so its the built in extractor.
Click to expand...
Click to collapse
Damn you linux people. lol

Trying to update to 4.4.2 via TWRP Flash getting error

I'm new to rooting and android in general. I'm currently running 4.4 rooted with stock I believe. Says ponury kernal in my settings.
I'm trying to flash the update for 4.4.2 via the TWRP install. I get a failed error: error executing updater binary in zip.
I've made sure my zip is the 4.4 to 4.4.2 but still no luck. Any ideas what I can do? Do I need to wipe something before I can put it on there?
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
tom1807 said:
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
Click to expand...
Click to collapse
The error was : error executing updater binary in zip. I will look into getting back to stock.
matthewordie said:
The error was : error executing updater binary in zip. I will look into getting back to stock.
Click to expand...
Click to collapse
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
jd1639 said:
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
Click to expand...
Click to collapse
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
matthewordie said:
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
Click to expand...
Click to collapse
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
jd1639 said:
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
Click to expand...
Click to collapse
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
Flashing the system image won't wipe anything
http://forum.xda-developers.com/showthread.php?p=14
Sent from my Nexus 5 using Tapatalk
Zepius said:
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
Click to expand...
Click to collapse
Well I really don't know the exact steps involved in "flashing the image". That's what I'm asking.
jd1639 said:
Flashing the system image won't wipe anything
Click to expand...
Click to collapse
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
matthewordie said:
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
Click to expand...
Click to collapse
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
jd1639 said:
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
Click to expand...
Click to collapse
Ah, I was close I actually did method 1. Yeah I did leave it unlocked since i'm going to root again right away. Thanks

[Q] how to reflesh stock kernel?

Ok so i flashed francos kernel trough FKU updater app and i want to go back to stock just to compare the battery life and some stuff again and to decide what to use.
How can i flash stock kernel back, do i flash all factory images or is there .zip file to flash trough recovery, or there is another way to do this? thanks for your replays.
Hi,
Stock kernel here (recovery zip file): http://forum.xda-developers.com/showthread.php?p=47269605.
You can also take a look here to fastboot the boot.img (kernel): http://forum.xda-developers.com/showthread.php?t=2513701.
Alexandar92zr said:
Ok so i flashed francos kernel trough FKU updater app and i want to go back to stock just to compare the battery life and some stuff again and to decide what to use.
How can i flash stock kernel back, do i flash all factory images or is there .zip file to flash trough recovery, or there is another way to do this? thanks for your replays.
Click to expand...
Click to collapse
boot.img is the kernel. If you have the factory images you can just fastboot flash that,
Hammer_Of_The_Gods said:
Hi,
Stock kernel here (recovery zip file): http://forum.xda-developers.com/showthread.php?p=47269605.
You can also take a look here to fastboot the boot.img (kernel): http://forum.xda-developers.com/showthread.php?t=2513701.
Click to expand...
Click to collapse
ok so i just download the zip and flash trough twrp right?
rootSU said:
boot.img is the kernel. If you have the factory images you can just fastboot flash that,
Click to expand...
Click to collapse
oh ok did not know that im quite new to this, but now i know thanks for information.
Alexandar92zr said:
ok so i just download the zip and flash trough twrp right?
Click to expand...
Click to collapse
That's right, download the right zip (4.4 or 4.4.1/4.4.2) put it "in your sdcard", reboot in recovery, flash and reboot, that's all
Hammer_Of_The_Gods said:
That's right, download the right zip (4.4 or 4.4.1/4.4.2) put it "in your sdcard", reboot in recovery, flash and reboot, that's all
Click to expand...
Click to collapse
thanks man i clicked on that thanks button
Alexandar92zr said:
thanks man i clicked on that thanks button
Click to expand...
Click to collapse
No worries, thanks
Last thing since you came from Franco kernel (the following procedure is specific):
The Gingerbread Man said:
Return to stock romz
Franco's kernel changes these system files below, so to change them back you can remove the .bak extension, or fastboot system.IMG and boot.IMG from a Google factory image which is probably easier and faster.
1 - Rename /system/lib/hw/power.msm8974.so.bak to /system/lib/hw/power.msm8974.so
2 - Rename /system/bin/thermal-engine-hh-bak to /system/bin/thermal-engine-hh
3 - Reboot to the boot loader and flash stock Kernel by downloading the Nexus images and then fastboot flash boot boot.img
...
Click to expand...
Click to collapse
So before flashing the stock kernel in recovery do the step 1 and 2 (even after if you forgot, it should be good).
Alexandar92zr said:
thanks man i clicked on that thanks button
Click to expand...
Click to collapse
May i suggest you start reading up before you get into serious rouble. Read the first 4 threads in the General section.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Hammer_Of_The_Gods said:
No worries, thanks
Last thing since you came from Franco kernel (the following procedure is specific):
So before flashing the stock kernel in recovery do the step 1 and 2 (even after if you forgot, it should be good).
Click to expand...
Click to collapse
ok lets see if i understood right.
im comeing from the stock rom just with francos kernel and now to go back to the stock i need to do step 1 and 2, how do i rename that files i connect my phone to pc or i need to download some file menager that can see that files? and about step 3 do i need to flash boot.img via fast boot or i can do it trough twrp as well?
sorry about the many questions but i do not want do do something wrong
Alexandar92zr said:
ok lets see if i understood right.
im comeing from the stock rom just with francos kernel and now to go back to the stock i need to do step 1 and 2, how do i rename that files i connect my phone to pc or i need to download some file menager that can see that files? and about step 3 do i need to flash boot.img via fast boot or i can do it trough twrp as well?
sorry about the many questions but i do not wont do do something wrong
Click to expand...
Click to collapse
With a file explorer, directly from your phone, (Root Explorer, Es File Explorer, etc...) follow the path to the files in point 1 and 2, rename the files and save. Then reboot in recovery and flash the stock kernel if you want to flash it via recovery (equal to step 3).
If you are not used with this kind of stuff (modify system files by yourself), flash the system.img and boot.img by following the link I provided above (http://forum.xda-developers.com/showthread.php?t=2513701).
Hammer_Of_The_Gods said:
With a file explorer, directly from your phone, (Root Explorer, Es File Explorer, etc...) follow the path to the files in point 1 and 2, rename the files and save. Then reboot in recovery and flash the stock kernel if you want to flash it via recovery (equal to step 3).
If you are not used with this kind of stuff (modify system files by yourself), flash the system.img and boot.img by following the link I provided above (http://forum.xda-developers.com/showthread.php?t=2513701).
Click to expand...
Click to collapse
i founded the files that i need to rename via es file explorer and now i understand it all and im not confused anymore about how to get stock kernel back.
im not used to this stuff yet because i rooted my phone yesterday and im quite new to this because last device i rooted and flashed lots of custom roms and stuff is to HD2 so i know the basic stuff but not much
and one of the topic question. why does my colors look a little diferent when i flashed the francos kernel? i know that there is something about color profiles etc. but i do not know where to start and look into that
Alexandar92zr said:
i founded the files that i need to rename via es file explorer and now i understand it all and im not confused anymore about how to get stock kernel back.
im not used to this stuff yet because i rooted my phone yesterday and im quite new to this because last device i rooted and flashed lots of custom roms and stuff is to HD2 so i know the basic stuff but not much
and one of the topic question. why does my colors look a little diferent when i flashed the francos kernel? i know that there is something about color profiles etc. but i do not know where to start and look into that
Click to expand...
Click to collapse
Okay, so all is fine to go back to stock, take your time and read all closely
About the colors, take a look here: http://forum.xda-developers.com/showpost.php?p=49561443 (links for profiles are down, for example: http://192.227.135.147/N5_ColorProfiles/Latest_Profiles/ from vomer).
Hammer_Of_The_Gods said:
Okay, so all is fine to go back to stock, take your time and read all closely
About the colors, take a look here: http://forum.xda-developers.com/showpost.php?p=49561443 (links for profiles are down, for example: http://192.227.135.147/N5_ColorProfiles/Latest_Profiles/ from vomer).
Click to expand...
Click to collapse
thanks i will look into this.
I made a stock kernel backup on Franco app and used it to restore back to stock kernel after using Franco was this process ok
Sent from my Nexus 5 using xda app-developers app

[Q] reverting from custom kernel to stock?

sorry if this doesn't quite belong here but I was curious to go back just to stock kernel, not completely stock itself. Could anyone link me to a good step by step for me to do this? Do i use adbfastboot the boot.img only? Im just a a little confused..
Sorry I am still new and learning. Thanks for any help!
Download the relevant kernel to your device from here.
Reboot to recovery
Install the zip you just downloaded
This stuff tends to be a lot simpler than you'd expect, tbh.
dallas220 said:
sorry if this doesn't quite belong here but I was curious to go back just to stock kernel, not completely stock itself. Could anyone link me to a good step by step for me to do this? Do i use adbfastboot the boot.img only? Im just a a little confused..
Sorry I am still new and learning. Thanks for any help!
Click to expand...
Click to collapse
Download the factory images from Google : https://developers.google.com/android/nexus/images#hammerheadkot49h
Extract the boot.img and flash it via fastboot.. (fastboot flash boot boot.img)
Make sure your on stock rom before you flash it..
Sent from my Nexus 5 using Tapatalk
dallas220 said:
sorry if this doesn't quite belong here but I was curious to go back just to stock kernel, not completely stock itself. Could anyone link me to a good step by step for me to do this? Do i use adbfastboot the boot.img only? Im just a a little confused..
Sorry I am still new and learning. Thanks for any help!
Click to expand...
Click to collapse
Fastboot, you flash with fastboot and yes the kernel image is boot.img. You should probably also reflash your ROM (system.img if you're on the stock ROM) as many custom kernels also modify the system partition.
BirchBarlow said:
Fastboot, you flash with fastboot and yes the kernel image is boot.img. You should probably also reflash your ROM (system.img if you're on the stock ROM) as many custom kernels also modify the system partition.
Click to expand...
Click to collapse
Thanks for all the replies guys!
I am indeed on stock rom. To flash the system.img is pretty much the same as the boot.img yes?
dallas220 said:
Thanks for all the replies guys!
I am indeed on stock rom. To flash the system.img is pretty much the same as the boot.img yes?
Click to expand...
Click to collapse
Hi,
Same way: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Hammer_Of_The_Gods said:
Hi,
Same way: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Click to expand...
Click to collapse
Thank you brother
And just to add to my noobness.. Returning to stock kernel and or rom doesn't wipe any files on the phone correct? Ie picture data etc....?
dallas220 said:
Thank you brother
And just to add to my noobness.. Returning to stock kernel and or rom doesn't wipe any files on the phone correct? Ie picture data etc....?
Click to expand...
Click to collapse
As long as you don't flash the userdata.img, you are fine!
If you are using the flashall script then remove the -w flag and you're good to go!
Sent from my Nexus 5 using Tapatalk
vin4yak said:
As long as you don't flash the userdata.img, you are fine!
If you are using the flashall script then remove the -w flag and you're good to go!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I plan on flashing sys and boot!
And so sorry but what do you mean the flashall srcipt?
Would that be basically flashing everything to stock?
Sorry for such dumb questions
dallas220 said:
I plan on flashing sys and boot!
And so sorry but what do you mean the flashall srcipt?
Would that be basically flashing everything to stock?
Click to expand...
Click to collapse
So no worries since you don't flash all (you use the "Method2" from the link I posted above), about the "flash-all.sh" file, when you open the factory image file, you have this script, more info here about the "-w" to delete: http://forum.xda-developers.com/showpost.php?p=51949577&postcount=4.
Hammer_Of_The_Gods said:
So no worries since you don't flash all (you use the "Method2" from the link I posted above), about the "flash-all.sh" file, when you open the factory image file, you have this script, more info here about the "-w" to delete: http://forum.xda-developers.com/showpost.php?p=51949577&postcount=4.
Click to expand...
Click to collapse
thanks for you help my brother. Just another question.. If I have a nandroidbackup on the computer that I made before I installed my custom kernel, could you somehow use that to get back to the stock kernel? Is that something...or I am just asking the most ridiculous questions?
It seems the more I read, the less I am confident with adb, flashing, backups etc.... :S
dallas220 said:
thanks for you help my brother. Just another question.. If I have a nandroidbackup on the computer that I made before I installed my custom kernel, could you somehow use that to get back to the stock kernel? Is that something...or I am just asking the most ridiculous questions?
It seems the more I read, the less I am confident with adb, flashing, backups etc.... :S
Click to expand...
Click to collapse
If want the stock kernel download the factory images from google and flash the boot.img via fastboot. That's the easiest way.
If you still want to use nandroid backup then copy the nandroid backup to the correct location... Head over to Philz Touch recovery and use the custom restore option by which you can select only the "boot" and "system" partition. But I haven't tried doing it so can't say whether it will work or not. However, technically it should work. I have no idea how to do this using TWRP though as I haven't used it much.

[Q] /system/bin/thermal-engine-hh has unexpected contents

I'm trying to flash the OTA update to 4.4.3, but during the system file check I'm getting an error that says that /system/bin/thermal-engine-hh has unexpected contents. I'm running stock rooted with franco kernel, but I flashed back to the stock 4.4.2 kernel before trying this. The only other thing I have installed non-stock is busybox.
Does anyone know what messes with that file and how to revert the changes?
vaindil said:
I'm trying to flash the OTA update to 4.4.3, but during the system file check I'm getting an error that says that /system/bin/thermal-engine-hh has unexpected contents. I'm running stock rooted with franco kernel, but I flashed back to the stock 4.4.2 kernel before trying this. The only other thing I have installed non-stock is busybox.
Does anyone know what messes with that file and how to revert the changes?
Click to expand...
Click to collapse
you CAN NOT install an ota when you are not fully stock. you will receive an ota, but it will always error out. you have to be completely stock to update via ota. by completely stock i mean completely, not even a build.prop edit. busybox is not stock.
simms22 said:
you CAN NOT install an ota when you are not fully stock. you will receive an ota, but it will always error out. you have to be completely stock to update via ota. by completely stock i mean completely, not even a build.prop edit. busybox is not stock.
Click to expand...
Click to collapse
I just uninstalled busybox and tried again, but I'm unfortunately getting the same error. I know that custom recovery and root are safe for flashing an OTA update, and they're the only two remaining non-stock things I have on the device.
Flashed stock boot.img again and this time also included stock system.img, then the OTA update flashed properly.
vaindil said:
Flashed stock boot.img again and this time also included stock system.img, then the OTA update flashed properly.
Click to expand...
Click to collapse
Haha ha. Crazy. If you were going to Flash a stock system.img, why not flash the 4.4.3 one?
Sent from my Nexus 5 using Tapatalk
Rename the files after uninstalling Franco kernel
Refer to here: plus.google.com/wm/1/+EzioTroito86/posts/LxN2SqqCpa4
You need to rename two files in the /system partition after removing Franco kernel. I renamed the files, and update my Nexus 5 to 4.4.3 successfully.
vaindil said:
I'm trying to flash the OTA update to 4.4.3, but during the system file check I'm getting an error that says that /system/bin/thermal-engine-hh has unexpected contents. I'm running stock rooted with franco kernel, but I flashed back to the stock 4.4.2 kernel before trying this. The only other thing I have installed non-stock is busybox.
Does anyone know what messes with that file and how to revert the changes?
Click to expand...
Click to collapse
harrysummer said:
Refer to here: plus.google.com/wm/1/+EzioTroito86/posts/LxN2SqqCpa4
You need to rename two files in the /system partition after removing Franco kernel. I renamed the files, and update my Nexus 5 to 4.4.3 successfully.
Click to expand...
Click to collapse
Thanks a lot for this suggestion.
I removed xposed, SU and franco kernel but was stuck at this issue.
Renaming the files did it.
Thanks once again.
No need to remove SU
You are doing almost the same thing as I did. I was using supersu. And, I found that SU do not bother the update, because it do not modify any files in the system. However, the update will remove the su binary automatically...
nirmit14 said:
Thanks a lot for this suggestion.
I removed xposed, SU and franco kernel but was stuck at this issue.
Renaming the files did it.
Thanks once again.
Click to expand...
Click to collapse
harrysummer said:
Refer to here: plus.google.com/wm/1/+EzioTroito86/posts/LxN2SqqCpa4
You need to rename two files in the /system partition after removing Franco kernel. I renamed the files, and update my Nexus 5 to 4.4.3 successfully.
Click to expand...
Click to collapse
Thanks! That solved it for me
Sorry for the thread revival, but I'm in the same boat. I am using Linaro kernel however, which is a Franco spinoff if I remember correctly. Would the above mentioned page with fix of filenames for Franco, fix my issue as well?
Mysticodex said:
Sorry for the thread revival, but I'm in the same boat. I am using Linaro kernel however, which is a Franco spinoff if I remember correctly. Would the above mentioned page with fix of filenames for Franco, fix my issue as well?
Click to expand...
Click to collapse
Things have changed. You must be fully stock now, including recovery. As before, stock kernel etc. You're best just flashing the updated system.img and boot.img, or one of the rom.zip
I have a thread about this in my signature.
rootSU said:
Things have changed. You must be fully stock now, including recovery. As before, stock kernel etc. You're best just flashing the updated system.img and boot.img, or one of the rom.zip
I have a thread about this in my signature.
Click to expand...
Click to collapse
I've flashed in stock system.img, and stock boot.img. Just finished re-doing it via NExus Toolkit. The latest error I am getting is the thermal engine system error. This led me to think I need to rename the files, as per the instructions about Franco, as people were saying even AFTER putting on stock system.img, these files remained?
Mysticodex said:
I've flashed in stock system.img, and stock boot.img. Just finished re-doing it via NExus Toolkit. The latest error I am getting is the thermal engine system error. This led me to think I need to rename the files, as per the instructions about Franco, as people were saying even AFTER putting on stock system.img, these files remained?
Click to expand...
Click to collapse
1) please done use toolkits. Its simple enough to do manually
2) these files exist in stock anyway
3) if you're flashing stock system image, why not just flash the latest then it won't matter?
rootSU said:
1) please done use toolkits. Its simple enough to do manually
2) these files exist in stock anyway
3) if you're flashing stock system image, why not just flash the latest then it won't matter?
Click to expand...
Click to collapse
I flashed system.img, and boot.img. I did not install 5.0 completely. I am just trying to repair my main system/recovery/boot files to work with the normal OTA.
Mysticodex said:
I flashed system.img, and boot.img. I did not install 5.0 completely. I am just trying to repair my main system/recovery/boot files to work with the normal OTA.
Click to expand...
Click to collapse
Sorry, no idea what you're talking about now or what the problem is.
rootSU said:
Sorry, no idea what you're talking about now or what the problem is.
Click to expand...
Click to collapse
nirmit14 says he had to rename two files, most importantly thermal-engine-hh.bak, however Is am not quite sure how to get access to these files, so I ask for advice on that.
Thanks.
Mysticodex said:
nirmit14 says he had to rename two files, most importantly thermal-engine-hh.bak, however Is am not quite sure how to get access to these files, so I ask for advice on that.
Thanks.
Click to expand...
Click to collapse
If you flash the kernel, it renames existing STOCK thermal-engine-hh to thermal-engine-hh.bak then creates new thermal-engine-hh. OTA Will not work with new thermal-engine-hh so you must delete that and rename STOCK thermal-engine-hh.bak Back to thermal-engine-hh
HOWEVER, if you flashed system.img like you said, then you only have STOCK thermal-engine-hh (because it is in system.img) and have NO thermal-engine-hh.bak at all.
So the answer to your question is irrelevant as you don't need to.
As for now you rename system files, options are
- root explorer
- adb shell
- file manager in recovery
But just flash 5.0 system.img and boot.img and be done with it.
I had originally manually flashed system.img and boot.img, and the file is there there.
I have sinced pulled the file onto my PC, renamed it, and pushed it back on. I will try the OTA again.
Mysticodex said:
I had originally manually flashed system.img and boot.img, and the file is there there.
I have sinced pulled the file onto my PC, renamed it, and pushed it back on. I will try the OTA again.
Click to expand...
Click to collapse
The. Bak file was still there? Assume you didn't wipe system when you flashed it then
rootSU said:
The. Bak file was still there? Assume you didn't wipe system when you flashed it then
Click to expand...
Click to collapse
Correct, everything was left on, I simply flashed the img files from the factory image. I assumed it would just overwrite it system.img.
Flashing recovery.img removed TWRM, so I thought the others would do the same.
Edit: Reflashed system.img using Nexus toolkit, and now the OTA took. I had confirmed that this flashing did remove the thermal file entirely. Still not sure what modified it, but I'm guessing it's Linaro kernel.

Categories

Resources