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.
Related
Fixed.
RusherDude said:
If I am on 4.4 stock rooted, with a custom recovery, and stuff modified on /system.. what I do when the update to 4.1.1 comes?
If I don't do nothing, the update will download automatically (which I don't want at all...), then try to patch and fail (I guess it won't even start since it detects that it's not stock system and recovery to flash the update) and it may even loop downloading and failing by what I readed being a bug on some 4.3 roms on the Nexus 4?
So how I should act in the following situations? First make a nandroid then..
a) I wanna flash it asap: I get the ota zip asap its posted and flash it on CWM and hope it goes ok. I may **** up stuff and have to revert to the nandroid, or 1it can go ok and just lose root and the system changes, right?
b) I wanna stay on 4.4 until all the stuff is ported to 4.1.1: It will at some point download the ota (****) by itself and spam me continuously to install it, right? If I wanna stay on 4.4 until all the stuff I use its compatible with 4.1.1, what I got to do to evade the auto-downloading of the ota and the spam about the update?
I don't know.. any way to stop the auto-update from working or so? That would be great!
Thanks in advance.
Click to expand...
Click to collapse
Here is what I just did, and it worked perfectly.
1. Take note of all the mods you installed so you can install them afterwards.
2. Put phone in bootloader mode / fastboot
3. Grab the 4.4 stock image from Google. Extract system.img file from it and flash that through fastboot (without the -w command) (fastboot flash system system.img). Don't worry you won't lose anything if you omit -w. Apps and data are preserved, it just set the \system area back to stock
4. Copy the OTA udpate zip to your phone, flash with TWRP. Since everything is 'back to stock' it should flash fine.
I had to re-root with TWRP after flashing before I rebooted. Everything was good to go. Then reflash your mods.
sonicdeth said:
Here is what I just did, and it worked perfectly.
1. Take note of all the mods you installed so you can install them afterwards.
2. Put phone in bootloader mode / fastboot
3. Grab the 4.4 stock image from Google. Extract system.img file from it and flash that through fastboot (without the -w command) (fastboot flash system system.img). Don't worry you won't lose anything if you omit -w. Apps and data are preserved, it just set the \system area back to stock
4. Copy the OTA udpate zip to your phone, flash with TWRP. Since everything is 'back to stock' it should flash fine.
I had to re-root with TWRP after flashing before I rebooted. Everything was good to go. Then reflash your mods.
Click to expand...
Click to collapse
Ok, that covers the a) situation where I want to flash it asap, thanks! (also note everyone, you got to disable xposed and all mods before flashing the ota)
PS: You can just flash the stock kernel and undo all the system changes, no need to flash the entire 4.4 stock zip.
What about the b) situation?
RusherDude said:
Ok, that covers the a) situation where I want to flash it asap, thanks! (also note everyone, you got to disable xposed and all mods before flashing the ota)
PS: You can just flash the stock kernel and undo all the system changes, no need to flash the entire 4.4 stock zip.
What about the b) situation?
Click to expand...
Click to collapse
Don't know why you'd want to go all the way back to 4.1.1. That's from July '12.
mattjorgs said:
Don't know why you'd want to go all the way back to 4.1.1. That's from July '12.
Click to expand...
Click to collapse
Wut? in the b) situation I just wanna STAY on 4.1 until all the stuff is ported to 4.1.1 (if something needs porting).
RusherDude said:
Wut? in the b) situation I just wanna STAY on 4.1 until all the stuff is ported to 4.1.1 (if something needs porting).
Click to expand...
Click to collapse
You mean 4.4? And 4.4.1? Lol
Sent from my Nexus 5 using Tapatalk
How to update to 4.4.1
I am rooted/bootloader unlocked with TWRP v2.6.3.1. When I try to flash in recovery manually with ota zip, I get a Failed error with error "E: error executing updater binary in zip"
What are step to update for a device like mine??
Cheeze[iT] said:
You mean 4.4? And 4.4.1? Lol
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Omg yea, 4.4 lol, fail haha
Trying to do the 4.4.2 update but its says unexpected item in build prop every time I try to flash in recovery all I ever touched was LCD density and I flashed return to stock on 4way reboot and ad blocking hosts so I'm thinking I need an untouched build prop of someone is willing to help
Sent from my Nexus 5 using Tapatalk
+1
I also would be grateful if someone would upload 4.4.1 (KOT49E) stock build.prop...
i need this too.
Just fastboot flash the system image. Problem solved!
jd1639 said:
Just fastboot flash the system image. Problem solved!
Click to expand...
Click to collapse
4.4.1 isn't on AOSP yet, is it safe to flash 4.4 system.img on 4.4.1? Will it just revert me back to 4.4?
akhan47 said:
4.4.1 isn't on AOSP yet, is it safe to flash 4.4 system.img on 4.4.1? Will it just revert me back to 4.4?
Click to expand...
Click to collapse
Yes it's safe. Then sideload the 4.4 to 4.4.2 update zip
jd1639 said:
Yes it's safe. Then sideload the 4.4 to 4.4.2 update zip
Click to expand...
Click to collapse
Thanks you, will do this later today.
akhan47 said:
+1
I also would be grateful if someone would upload 4.4.1 (KOT49E) stock build.prop...
Click to expand...
Click to collapse
4.4.1 build.prop.
Remember to change permissions to rw-r-r
https://www.dropbox.com/s/7vp174py4fmmfip/build.prop
Sent from my Nexus 5 using XDA Premium 4 mobile app
jbielman said:
Trying to do the 4.4.2 update but its says unexpected item in build prop every time I try to flash in recovery all I ever touched was LCD density and I flashed return to stock on 4way reboot and ad blocking hosts so I'm thinking I need an untouched build prop of someone is willing to help
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hi,
Same problem for me but I need the KRT16M stock 4.4 /system/build.prop file to be able to apply the OTA update... and I don't want to reflash the stock system.img because I have added some ogg files and renamed some others to add custom ring bells and remove camera sounds... so basically (even if that's not that a pain in the ass to do it again) I would be pleased not to have to do that again.
Anyone ? (I'm googling like hell... only build.prop I found was the one here, from 4.4.1 :/)
hehe2 said:
Hi,
Same problem for me but I need the KRT16M stock 4.4 /system/build.prop file to be able to apply the OTA update... and I don't want to reflash the stock system.img because I have added some ogg files and renamed some others to add custom ring bells and remove camera sounds... so basically (even if that's not that a pain in the ass to do it again) I would be pleased not to have to do that again.
Anyone ? (I'm googling like hell... only build.prop I found was the one here, from 4.4.1 :/)
Click to expand...
Click to collapse
It's not going to work
jd1639 said:
It's not going to work
Click to expand...
Click to collapse
Well, I ended up by flashing the system.img, then sideloading the OTA, then flashing latest TWRP then installing latest Super SU and cleared cache/dalvik "et voilà", now I only got to put my custom ogg ringtones/notifications files in place and I'm good
Couldn't find that crappy build.prop anyway... but I adb pulled it (after having flashed the system.img) just to make a diff with my previously modified one (that I backuped).
Well, running 4.4.2 fine now, with no app to re-install, kinda "OTA" like... with the added mess up, but kept my root so...
You can always just download the stock ROM and pull the build.prop from there.
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
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.
I've got a Nexus 5 with Android 5.0. I've had it rooted and unlocked using SkipSoft Unified Android Toolkit. I recently got a notification for an OTA update for 5.0.1. When I tried to install it, it downloaded ok but upon restarting it dropped me into teamwin recovery menu with options for: Install, Wipe, Backup, Restore, Mount, Settings, Advanced, Reboot. Not knowing what to do I clicked on Reboot -> System which booted back into the phone. Nothing changed or got installed.
Does anyone know how I can apply the latest OTA update? Do I have to unroot first, apply and then re-root? Does the Toolkit have support for 5.0.1 rooting yet?
TIA
You must be 100% stock to update so yes, you need to fully unroot.
Though you should just fastboot flash the system.img and boot.img
Don't use toolkits. Do things manually. You can either flash SuperSU from recovery or use cf-auto root from a computer.
Its very easy, there is flashable 5.0 stock ROM, I dirty flashed, or you can do it like rootSU said via fastboot, root has been lost, then I flashed stock recovery via fastboot, there is thread for recoveries, then I upgraded via ota and flashed twrp via fastboot and flashed SuperSU to gain root and custom kernel.
My way is much quicker though as you flash 5.0.1 system and boot straight away. Nothing else.
rootSU said:
My way is much quicker though as you flash 5.0.1 system and boot straight away. Nothing else.
Click to expand...
Click to collapse
We will never understand why people even bother with OTAs regardless what we ever tell them
rootSU said:
You must be 100% stock to update so yes, you need to fully unroot.
Though you should just fastboot flash the system.img and boot.img
Don't use toolkits. Do things manually. You can either flash SuperSU from recovery or use cf-auto root from a computer.
Click to expand...
Click to collapse
Ok, I'm not 100% sure I understood everything you said. I've downloaded the 5.0.1 update from here: https://developers.google.com/android/nexus/images. Using 7zip, I noticed the system.img and boot.img is contained in the tgz file (along with several other files). Do I just extract just those two files? And then what do I do in Teamwin?
Will all my apps and data persist?
TIA
Techno79 said:
Ok, I'm not 100% sure I understood everything you said. I've downloaded the 5.0.1 update from here: https://developers.google.com/android/nexus/images. Using 7zip, I noticed the system.img and boot.img is contained in the tgz file (along with several other files). Do I just extract just those two files? And then what do I do in Teamwin?
Will all my apps and data persist?
TIA
Click to expand...
Click to collapse
Boot into bootloader
fastboot flash system system.img
fastboot flash boot boot.img
Boot into Lollipop
You didn't touch userdata.img so it doesn't touch the data partition, although a wipe is usually recommended anyways because it's a new version of Android.
Lethargy said:
Boot into bootloader
fastboot flash system system.img
fastboot flash boot boot.img
Boot into Lollipop
You didn't touch userdata.img so it doesn't touch the data partition, although a wipe is usually recommended anyways because it's a new version of Android.
Click to expand...
Click to collapse
Sweet, that worked a great. Thank you.