Database Info

Stuck in Bootloop after pushing framework-res

I accidentally pushed the wrong framework-res.apk file in adb and now im stuck in a bootloop
I have stock recovery and am rooted
I can enter download mode but I don't want to lose all my data.
What can I do?

If you didn't make a nandroid backup... You will have to re-flash your rom over again
Edited:
Just noticed your on stock... Yikes. Looks like you'll have to Odin that thing. When pushing apks. Set the permissions to rw-r-r before rebooting
And definitely watch what your pushing

Annex1 said:
If you didn't make a nandroid backup... You will have to re-flash your rom over again
Edited:
Just noticed your on stock... Yikes. Looks like you'll have to Odin that thing. When pushing apks. Set the permissions to rw-r-r before rebooting
And definitely watch what your pushing
Click to expand...
Click to collapse
I'd prefer people use the heimdall oneclick (check 'Projects' out my sig).
Odin always makes things complicated, and it's closed source.
Heimdall is open source, documented, and actively maintained.
Just a suggestion

Or try using Heimdal One-Click to flash a custom kernel only. Then find a kernel you can flash in CWM that has TWRP. Then you can copy over your original framework-res.apk in the TWRP file manager and see if it will boot.
None of that will mess with your files except framework-res.

It's been a long time since I've been on stock recovery but does ADB pick up the phone when its in recovery?

hechoen said:
It's been a long time since I've been on stock recovery but does ADB pick up the phone when its in recovery?
Click to expand...
Click to collapse
It does on the blastoff kernel in eollies oneclick

bhundven said:
It does on the blastoff kernel in eollies oneclick
Click to expand...
Click to collapse
I know it does with custom recoveries but if he can get it picked up in the stock recovery he can just push the original .apk back. Easy. If it picks it up.

hechoen said:
I know it does with custom recoveries but if he can get it picked up in the stock recovery he can just push the original .apk back. Easy. If it picks it up.
Click to expand...
Click to collapse
what does it matter? Push the apk with custom recovery. I don't know of anything you can flash with stock recovery.

bhundven said:
what does it matter? Push the apk with custom recovery. I don't know of anything you can flash with stock recovery.
Click to expand...
Click to collapse
F. I'm off topic.
You're rooted on stock recovery. Install root explorer, over write the framework-res.apk, reboot.

Thank you so much guys.
I was able to flash a custom kernal with Heimdall and I pushed the right framework-res and now everythings back to normal
I'm truly grateful for all your speedy and helpful replies.

I would advise you to flash a simple zip (take any simple mod or gapps) valid for your Android version and edit its updater script to just flash the system folder. Then add the zip a system folder with framework folder and put your right framework-res.apk,
This way you just flash, fix permissions and good to go... no Heimdall, kernel or any other change, and you're back in business.
Another even simpler way is to use our device's Aroma File Manager and simply copy the right file and fix permissions...

Flashing a Kernel via Recovery vs ADB

I was curious as to any difference between flashing a Kernel via ADB using a boot.img or flashing it as a .zip via recovery. Is there a benefit of one over the other. I've always done it via ADB, but I recently tried via a zip file through TWRP but didn't notice any difference, but wasn't sure if I was just being oblivious or not lol
I heard someone mention that when flashing it via ADB you don't get the Modules that come with the Kernel. Which I don't know if that was BS or not, cause as I stated, after trying it both ways, I didn't notice any features taken away i.e. flashed bricked kernel via ADB and then restored stock kernel and then flashed bricked via TWRP, and I was able to activate DT2W/S2W regardless of the method of flashing, as well as OC capabilities, Fast Charge, etc etc.
Just been curious about this for awhile, and there doesn't seem to be much discussion about it, so was unable to find an answer. Dev's always seem to give you the option to download a boot.img or .zip file, and wasn't sure if htat was just due to giving peopel the choice of preferred flashing method, or because of inherit benefits between the two.

Its simply 2 different options of installation. The final result is the same: a boot.img gets extracted and written onto the appropriate partition of your device.
When you use fastboot to flash the img. the executable on your computer does this directly.
When you use a recovery to flash the zip (which also contains the boot.img), the edify script within the zip gives instructions to the recovery on how and where to write the image to.
There isnt really any advantage to doing one over the other.

Silicon Knight said:
I was curious as to any difference between flashing a Kernel via ADB using a boot.img or flashing it as a .zip via recovery. Is there a benefit of one over the other. I've always done it via ADB, but I recently tried via a zip file through TWRP but didn't notice any difference, but wasn't sure if I was just being oblivious or not lol
I heard someone mention that when flashing it via ADB you don't get the Modules that come with the Kernel. Which I don't know if that was BS or not, cause as I stated, after trying it both ways, I didn't notice any features taken away i.e. flashed bricked kernel via ADB and then restored stock kernel and then flashed bricked via TWRP, and I was able to activate DT2W/S2W regardless of the method of flashing, as well as OC capabilities, Fast Charge, etc etc.
Just been curious about this for awhile, and there doesn't seem to be much discussion about it, so was unable to find an answer. Dev's always seem to give you the option to download a boot.img or .zip file, and wasn't sure if htat was just due to giving peopel the choice of preferred flashing method, or because of inherit benefits between the two.
Click to expand...
Click to collapse
Fastboot is the tool to which you are referring to, not ADB. You use fastboot to flash image files to partitions directly through the bootloader. That being said, there's no difference which method you use, the end result is the same. Using fastboot requires an unlocked bootloader, flashing through the recovery does not. When you flash a zip through the recovery, the proper destination partition is automatically overwritten whereas when you flash an image in fastboot, you have to specify the proper partition. That's the only real difference.

Excuse me, Fastboot is what I meant yes. My bad lol.
Thanks for the info, I figured as much. Im experienced with both methods and understand how they work. Just wasn't sure if there was a benefit over one or the other when it comes to flashing custom kernels. Thanks bro I appreciate the help. I will stick to flashing via fastboot then. I just prefer to do it that way.
I also use flashify sometimes as well. Seems to work pretty good.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Chromium_ said:
Its simply 2 different options of installation. The final result is the same: a boot.img gets extracted and written onto the appropriate partition of your device.
When you use fastboot to flash the img. the executable on your computer does this directly.
When you use a recovery to flash the zip (which also contains the boot.img), the edify script within the zip gives instructions to the recovery on how and where to write the image to.
There isnt really any advantage to doing one over the other.
Click to expand...
Click to collapse
i have a locked bootloader but i have root, can i "flash" throught root explorer overwriting boot.img file?
and reboot?

AXD96 said:
i have a locked bootloader but i have root, can i "flash" throught root explorer overwriting boot.img file?
and reboot?
Click to expand...
Click to collapse
Root explorer is not a flashing tool and no, it cannot modify the kernel
Sent from my Nexus 5 using Tapatalk

rootSU said:
Root explorer is not a flashing tool and no, it cannot modify the kernel
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
maybe a stupid question, but the kernel is all saved in boot.img?

AXD96 said:
maybe a stupid question, but the kernel is all saved in boot.img?
Click to expand...
Click to collapse
Yep Indeed. What you can browse is /sys, which are the "files" the kernel manipulates to do what it wants...
..but browsing here is of no benefit to changing a kernel
Sent from my Nexus 5 using Tapatalk

Unlock your device and just use the a custom recovery.
Sent from my Nexus 5 using Tapatalk

can we change kernel alone
i am using SENSONIC with stock kernel can i change kernel alone.
I want to change to franco kernel . Is it enough installing zip using recovery or i have to do fresh install of the ROM.........
Thanks in advance.

[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] Remove Custom Zips/Mods

I have LG Nexus 5 Phone rooted recently. With Custom Recovery I have installed some Zips (Called Mods). One of the Zips is Corrupt and my phone is not responding at all. I want to remove the Custom Zip/Mod only as I don't wan to wipe off whole system.
Is there any way to remove that particular Mod using TWRP Manager or any other way without loosing my data/stuff on my phone.

Restore the backup you made before flashing it
Sent from my Nexus 5 using XDA Premium 4 mobile app

pepdavies said:
Restore the backup you made before flashing it
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am not able to find any backup. I think I have not created it. Does this application creates backup automatically?
If in worst to worst case there is no backup, what are all other options I do have here.

Hi,
pepdavies said:
Restore the backup you made before flashing it
Click to expand...
Click to collapse
This, yes... but I doubt he made a backup if he ask how to "remove" the mods...
@anshumangoyal, maybe the there is an "undo" zip file, a revert to stock zip file? What mod have you flashed?
Dirty flash your rom, no wipe, and you won't lose anything...
And no automatic backup, you need to do it yourself in recovery, first thing to do when you flash some stuff.

pepdavies said:
Restore the backup you made before flashing it
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hammer_Of_The_Gods said:
Hi,
This, yes... but I doubt he made a backup if he ask how to "remove" the mods...
@anshumangoyal, maybe the there is an "undo" zip file, a revert to stock zip file? What mod have you flashed?
Dirty flash your rom, no wipe, and you won't lose anything...
And not, no automatic backup, you need to do it yourself in recovery, first thing to do when you flash some stuff.
Click to expand...
Click to collapse
But, how to do this dirty flash. I cannot see any such option in TWRP. Do i need to install some another tool etc??

anshumangoyal said:
But, how to do this dirty flash. I cannot see any such option in TWRP. Do i need to install some another tool etc??
Click to expand...
Click to collapse
Boot in recovery, go to your rom zip file, flash and reboot...
Without more relevant info I can only say that...
Stock rom? Custom rom? Link to the mod you flashed?

Hammer_Of_The_Gods said:
Boot in recovery, go to your rom zip file, flash and reboot...
Without more relevant info I can only say that...
Stock rom? Custom rom? Link to the mod you flashed?
Click to expand...
Click to collapse
It's Stock ROM I have Rooted to, I am not using ay custom ROM. So whare to download this Stock ROM. And also once this Stock ROM is flashed do I need to root the phone again.
I may be asking very silly questions, but this is what I was able to know in last 1-2 months and "still Learning"

Ok, it seems you don't want to post a link to the mod you flashed, or at least say the name, I asked 2 times and maybe we could do a revert zip file for you if we know what you have flashed (it depends of what kind of mod) then...
Take a look here to return to stock: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Or flash a stock rom via recovery? Maybe easier for you...
EDIT: stock roms, flashable zip file: http://forum.xda-developers.com/showpost.php?p=52732041&postcount=4 (two first links), see above to flash...

Hammer_Of_The_Gods said:
Ok, it seems you don't want to post a link to the mod you flashed, or at least say the name, I asked 2 times and maybe we could do a revert zip file for you if we know what you have flashed (it depends of what kind of mod) then...
Take a look here to return to stock: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Or flash a stock rom via recovery? Maybe easier for you...
EDIT: stock roms, flashable zip file: http://forum.xda-developers.com/showpost.php?p=52732041&postcount=4.
Click to expand...
Click to collapse
Oops I am sorry, I was not aware of terminology here. If I see in System Setting I have Build Number: KOT49H and Kernel Version: 3.4.0-gadb2201
Is this information you are looking for. I had unrooted latest android software, which I rooted using wugFresh tool kit software on windows 8.
Model: Nexus 5, LGD820, D821
Android 4.4.2 KOT49H
I hope this will help out.

Nope, it's not what I asked but...
I gave you a link to some full stock roms (rooted) to flash in recovery: http://forum.xda-developers.com/showpost.php?p=52732041&postcount=4 (use the first one for example).
Put it on your phone via computer, reboot in recovery go to the zip file you've just put, flash the zip file and reboot, the modified files from the mods you flashed will be replaced by the original stock files.
Use this link to "learn" how to use some commands (manually) and return to stock when you encounter a plroblem: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Here you need to flash the system.img (I guess, since I don't know what you flashed), or "all"...
Maybe harder for you since you used a Toolkit the first time but with time and reading...
If it seems even too hard for you, then in your Toolkit is there an option to return to stock, reflash the system.img?
When I ask you what mod you flashed, I mean it's a theme? A kernel? A sound mod? A camera mod? Because if we know what you flashed, maybe we can do a revert zip file for you by replacing the files by the stock ones in the zip).
What is the exact name of the zip file, the last you flashed and gives you problem?
Read all closely and take your time...

Hammer_Of_The_Gods said:
Nope, it's not what I asked but...
I gave you a link to some full stock roms (rooted) to flash in recovery: http://forum.xda-developers.com/showpost.php?p=52732041&postcount=4 (use the first one for example).
Put it on your phone via computer, reboot in recovery go to the zip file you've just put, flash the zip file and reboot, the modified files from the mods you flashed will be replaced by the original stock files.
Use this link to "learn" how to use some commands (manually) and return to stock when you encounter a plroblem: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Here you need to flash the system.img (I guess, since I don't know what you flashed), or "all"...
Maybe harder for you since you used a Toolkit the first time but with time and reading...
If it seems even too hard for you, then in your Toolkit is there an option to return to stock, reflash the system.img?
When I ask you what mod you flashed, I mean it's a theme? A kernel? A sound mod? A camera mod? Because if we know what you flashed, maybe we can do a revert zip file for you by replacing the files by the stock ones.
What is the exact name of the zip file, the last you flashed and gives you problem?
Read all closely and take your time...
Click to expand...
Click to collapse
Thanks,
Now I understood. These were two Zips I installed were: cargo_N5_RebootMenu_KOT49H_odex.zip and cargo_only_Batt___rechts_odex_N5.zip
These were 2 mods I had.

anshumangoyal said:
Thanks,
Now I understood. These were two Zips I installed were: cargo_N5_RebootMenu_KOT49H_odex.zip and cargo_only_Batt___rechts_odex_N5.zip
These were 2 mods I had.
Click to expand...
Click to collapse
Ok, good.
The first: http://forum.xda-developers.com/google-nexus-5/themes-apps/mod-advanced-4-reboot-menu-odex-t2521809, you have a revert zip file (just below the mod you flashed): Back to stock: cargo_N5_Back_to_stock_RebootMenu_KOT49H_odex.zip.
The second: http://forum.xda-developers.com/goo...ps/mod-center-clock-battery-mod-odex-t2526039, same thing you have a revert zip file in attachment: Back_to_Stock_odex_N5.zip.
Download them and flash them to restore the original files, you really need to read closely before flashing stuff

Hammer_Of_The_Gods said:
Ok, good.
The first: http://forum.xda-developers.com/google-nexus-5/themes-apps/mod-advanced-4-reboot-menu-odex-t2521809, you have a revert zip file (just below the mod you flashed): Back to stock: cargo_N5_Back_to_stock_RebootMenu_KOT49H_odex.zip.
The second: http://forum.xda-developers.com/goo...ps/mod-center-clock-battery-mod-odex-t2526039, same thing you have a revert zip file in attachment: Back_to_Stock_odex_N5.zip.
Download them and flash them to restore the original files, you really need to read closely before flashing stuff
Click to expand...
Click to collapse
This is Super Find. I am sorry, I was not aware of this. Next time I will check this for sure and make sure I also take a backup before doing these nasty things. Many thanks again for your help.

[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.