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
I've got stock, odexed....am rooted. That's it. Got the update, trying to flash with TWRP and get "system/build.prop has unexpected contents" error. Can't install the update.
WHY????? It's killin' me!
Thanks.
velveteen71 said:
I've got stock, odexed....am rooted. That's it. Got the update, trying to flash with TWRP and get "system/build.prop has unexpected contents" error. Can't install the update.
WHY????? It's killin' me!
Thanks.
Click to expand...
Click to collapse
you apparently have a modified build.prop. You probably will have to re-flash system.img to apply the OTA.
or find what was changed in build.prop and revert the change.
If you installed ANY modifications (dalvik mod, camera mod, center clock, dpi changes, ANYTHING) than it will not flash.
Synyster06Gates said:
If you installed ANY modifications (dalvik mod, camera mod, center clock, dpi changes, ANYTHING) than it will not flash.
Click to expand...
Click to collapse
Hey guys, got (what I believe is) a similar issue.
the error message I'm getting when I try to flash the update (or sideload it) is "EMMC:/dev/block/platform/msm_sdcc.1/by-name/bootand a huge string of characters ending with the end quote that follows)" has unexpected contents.
I've flashed back to stock krt16m, bootloader is still unlocked with cwm recovery, and I still get this error. The only modifications I had made were flashing the bricked-kernel hammerhead and enabling doubletap to wake, also installed xposed framework with gravitybox and advanced power options.
I flashed the uninstall file for bricked-kernel hammerhead (which was a boot.img so assuming it was this and not xposed?) but I'm still unable to flash the update to 4.4.1
suggestions? is there a way to flash a new boot.img? I'm a relative beginner.. I'm unable to track down a link that has a stock boot.img, I'm not sure if this is part of the factory image but I'm assuming not if I'm still having this issue..
thank you for any input!
desucca said:
Hey guys, got (what I believe is) a similar issue.
the error message I'm getting when I try to flash the update (or sideload it) is "EMMC:/dev/block/platform/msm_sdcc.1/by-name/bootand a huge string of characters ending with the end quote that follows)" has unexpected contents.
I've flashed back to stock krt16m, bootloader is still unlocked with cwm recovery, and I still get this error. The only modifications I had made were flashing the bricked-kernel hammerhead and enabling doubletap to wake, also installed xposed framework with gravitybox and advanced power options.
I flashed the uninstall file for bricked-kernel hammerhead (which was a boot.img so assuming it was this and not xposed?) but I'm still unable to flash the update to 4.4.1
suggestions? is there a way to flash a new boot.img? I'm a relative beginner.. I'm unable to track down a link that has a stock boot.img, I'm not sure if this is part of the factory image but I'm assuming not if I'm still having this issue..
thank you for any input!
Click to expand...
Click to collapse
Is Bricked the only kernel you've used? Or did you try Franco as well? Francos modifies a few files that need to be fixed before you can flash the update - even if you flashed a stock boot.img.
If you haven't, try the stock boot.img from http://forum.xda-developers.com/showthread.php?t=2513701
Got the same message. Flash the stock 4.4 (not 4.4.1) boot.img from the factory zip.
Synyster06Gates said:
Is Bricked the only kernel you've used? Or did you try Franco as well? Francos modifies a few files that need to be fixed before you can flash the update - even if you flashed a stock boot.img.
If you haven't, try the stock boot.img from http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
yep, bricked was the only one I've tried so far. I'll try this and report back, thank you
*update* worked! thanks very much, it's updating right now.
desucca said:
yep, bricked was the only one I've tried so far. I'll try this and report back, thank you
Click to expand...
Click to collapse
I was the same as you. I had to flash stock boot.img and system.img for it to work. I only tried Bricked but went back to stock and at one point I tried Xposed. Guess one of them left a trace.
Sent from my Nexus 5 using xda app-developers app
david23c said:
you apparently have a modified build.prop. You probably will have to re-flash system.img to apply the OTA.
or find what was changed in build.prop and revert the change.
Click to expand...
Click to collapse
This. What did you modify in your build.prop? Revert to your backed up original build.prop (.bak), install a new stock build.prop, or flash system.img.
Nitemare3219 said:
Got the same message. Flash the stock 4.4 (not 4.4.1) boot.img from the factory zip.
Click to expand...
Click to collapse
you should flash boot.img and system.img to make sure you have a stock system partition.
david23c said:
you should flash boot.img and system.img to make sure you have a stock system partition.
Click to expand...
Click to collapse
i have the same problem, does flashing these files affect any of my data or configuration?
cannot update rooted nexus?
so in short can we say we just cannot update to 4.4.1 without reverting back to and losing all app data ?
Guys,
Please help me out here. I rooted my Nex5 because I could not stand the DPI (icons/text were ridiculously big)
Because an app I use a lot cannot function on a rooted phone, I unrooted my phone.
I guess this means the following: my bootloader is NOT stock (because I see the 'unlock' icon), I am NOT rooted and my OS is stock.
In the end I just want to get 4.4.1 the easiest way and of course still have my DPI still modified.
Thanks in advance!!!
gaurishmhatre said:
so in short can we say we just cannot update to 4.4.1 without reverting back to and losing all app data ?
Click to expand...
Click to collapse
Yes you can. I flashed the OTA in CWM after undoing the changes I'd made and it flashed fine without losing data
lowlow2 said:
Guys,
Please help me out here. I rooted my Nex5 because I could not stand the DPI (icons/text were ridiculously big)
Because an app I use a lot cannot function on a rooted phone, I unrooted my phone.
I guess this means the following: my bootloader is NOT stock (because I see the 'unlock' icon), I am NOT rooted and my OS is stock.
In the end I just want to get 4.4.1 the easiest way and of course still have my DPI still modified.
Thanks in advance!!!
Click to expand...
Click to collapse
You can't install the update. You need to revert all system settings to stock (including what ever changed your DPI) before you can update. After that, you can install it, re root and change your DPI;
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
chucky8 said:
i have the same problem, does flashing these files affect any of my data or configuration?
Click to expand...
Click to collapse
No, your data and configuration will be fine.
Synyster06Gates said:
You can't install the update. You need to revert all system settings to stock (including what ever changed your DPI) before you can update. After that, you can install it, re root and change your DPI;
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
No, your data and configuration will be fine.
Click to expand...
Click to collapse
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------
lowlow2 said:
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
Click to expand...
Click to collapse
One last question, can I just adjust (revert) the DPI setting ? Or will it detect I fuzzled with my build.prop and never work without replacing ? Thanks
lowlow2 said:
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------
One last question, can I just adjust (revert) the DPI setting ? Or will it detect I fuzzled with my build.prop and never work without replacing ? Thanks
Click to expand...
Click to collapse
You should be able to just edit it back to original configuration.
Synyster06Gates said:
You should be able to just edit it back to original configuration.
Click to expand...
Click to collapse
Tried this but unfortunately not working. I have the original system.img (+-600MB)
Can you tell me how I flash this with ADB (weirdly couldn't find it on xda via search!)
Thanks!
lowlow2 said:
Tried this but unfortunately not working. I have the original system.img (+-600MB)
Can you tell me how I flash this with ADB (weirdly couldn't find it on xda via search!)
Thanks!
Click to expand...
Click to collapse
Here ya go. Make sure the drivers are installed correctly. This guide has it all. You will only be flashing system.img, not the entire bat
http://forum.xda-developers.com/showthread.php?t=2513701
Synyster06Gates said:
Here ya go. Make sure the drivers are installed correctly. This guide has it all. You will only be flashing system.img, not the entire bat
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
thanks!!
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.
From what I understand it is just security fixes and no bug fixes? Is it worth flashing a new ROM for? I am on 4.4.3 right now and it is running pretty smooth.
jedinegotiator said:
From what I understand it is just security fixes and no bug fixes? Is it worth flashing a new ROM for? I am on 4.4.3 right now and it is running pretty smooth.
Click to expand...
Click to collapse
If you're on the stock ROM I don't see why you're even hesitant to simply flash the new factory images.
If you're on a custom ROM it'll get updated in a day or so, if not, then already.
Everything will run smooth regardless unless you mess up something really badly..
Sent from my Nexus 5
Lethargy said:
If you're on the stock ROM I don't see why you're even hesitant to simply flash the new factory images.
If you're on a custom ROM it'll get updated in a day or so, if not, then already.
Everything will run smooth regardless unless you mess up something really badly..
Sent from my Nexus 5
Click to expand...
Click to collapse
I'm on Kangakat but I don't like to dirty flash
jedinegotiator said:
I'm on Kangakat but I don't like to dirty flash
Click to expand...
Click to collapse
I dirty flash my new builds over my old almost daily and nothing bad has come out of it. The only reasons you would really need to clean flash is to start fresh, test out a new ROM, jump a whole android version (4.4.3 to 4.4.4 is minor.. I mean like Jellybean to KitKat), or if something isn't working properly.
Sent from my Nexus 5
Lethargy said:
I dirty flash my new builds over my old almost daily and nothing bad has come out of it. The only reasons you would really need to clean flash is to start fresh, test out a new ROM, jump a whole android version (4.4.3 to 4.4.4 is minor.. I mean like Jellybean to KitKat), or if something isn't working properly.
Sent from my Nexus 5
Click to expand...
Click to collapse
I am using xposed framework and gravity box. Will I have to reconfigure those if I dirty flash or will everything stay in tact?
jedinegotiator said:
I am using xposed framework and gravity box. Will I have to reconfigure those if I dirty flash or will everything stay in tact?
Click to expand...
Click to collapse
You'll just have to go into Xposed Installer and install the framework again, your stuff will stay.
Seeing as KangaKat is hardly a custom ROM and more of just a few minor mods on the stock ROM with Xposed thrown on top of it (lol).. I doubt you'll run into any issues.
As always, make a backup just in case.
Sent from my Nexus 5
jedinegotiator said:
From what I understand it is just security fixes and no bug fixes? Is it worth flashing a new ROM for? I am on 4.4.3 right now and it is running pretty smooth.
Click to expand...
Click to collapse
what kind of a question is this?
Ask yourself: Is security something that matters for you? If not well its not worth.
Creating a thread for this seams pointless.
Im still on 4.4.2 and with a stock rom but custom recovery and root, Is there a way to flash the 4.4.3 / 4.4.4 w/o wiping ? Can you guys link me to a guide or provide steps
EarlZ said:
Im still on 4.4.2 and with a stock rom but custom recovery and root, Is there a way to flash the 4.4.3 / 4.4.4 w/o wiping ? Can you guys link me to a guide or provide steps
Click to expand...
Click to collapse
You can extract the zip and flash the system, kernel, radio, and cache partitions separately using fastboot without overwriting your data partition.
BirchBarlow said:
You can extract the zip and flash the system, kernel, radio, and cache partitions separately using fastboot without overwriting your data partition.
Click to expand...
Click to collapse
How do I exactly flash those individually? I've used the guide in your signature before but thats to flash everything back to stock. Im not familiar with the commands to type, or maybe theres like a 4.4.4 with those mentioned that can be flashed via TWRP ?
EarlZ said:
How do I exactly flash those individually? I've used the guide in your signature before but thats to flash everything back to stock. Im not familiar with the commands to type, or maybe theres like a 4.4.4 with those mentioned that can be flashed via TWRP ?
Click to expand...
Click to collapse
This will do it for you.
http://forum.xda-developers.com/showthread.php?p=53532631
Or fastboot flash the system, cache, radio, and boot images
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
This will do it for you.
http://forum.xda-developers.com/showthread.php?p=53532631
Or fastboot flash the system, cache, radio, and boot images
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, Grabbing it now!
EarlZ said:
Thanks, Grabbing it now!
Click to expand...
Click to collapse
Or just grab the 4.4.4 zip and flash it in recovery, ie dirty flash.
Lokke9191 said:
Or just grab the 4.4.4 zip and flash it in recovery, ie dirty flash.
Click to expand...
Click to collapse
Wont that delete my data?
You won't lose any data, just flash the 4.4.4 zip in your custom recovery. Don't wipe cache or dalvik. The zip can be found here.
http://forum.xda-developers.com/google-nexus-5/development/rom-stock-4-4-3-ktu84m-odex-deodex-t2771010
Update without losing anything
http://nexus5.wonderhowto.com/how-t...ndroid-4-4-3-without-losing-any-data-0155334/
Sent from my Nexus 4 using XDA Free mobile app
Greetings!
So, the update 4.4.4. OTA was just avaible in my phone now and when it rebooted to install it, I received an error...AGAIN! I did some modifications to the system in the past, but then put the phone back to stock (using the tutorial here on xda) and flashed the 4.4.3. (from previsouly 4.4.2. - Nexus 5.
In this version (4.4.3.) the phone was completly stock except it had root (with cf-auto root) and with Xposed. I didn't do any modification to the system and when it was isntalling the new version, it did an error again, like I have done modifications to the system! I Already unchecked all the modules and unistalled the framework before updating to 4.4.4 OTA... Don't know why it isnt doing the workingOTA update..
Please help me! Thanks in advance!
how did you uninstall the framework?
Zepius said:
how did you uninstall the framework?
Click to expand...
Click to collapse
Went to Xposed Framework and clicked on Unistall framework, like I should..
ExoidX said:
Went to Xposed Framework and clicked on Unistall framework, like I should..
Click to expand...
Click to collapse
Save the hassle and flash the system and boot image from 4.4.4 in fastboot.
Sent from my Nexus 5 using XDA Free mobile app
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes and/or kernel, reboot into recovery, flash the OTA , boot to bootloader, connect to pc, fastboot flash recovery, reboot into recovery, flash supersu.
Rooted stock = reboot into recovery, flash the ROM.
No brainer really. Flashing an OTA if rooted is a fool's errand.
Sent from my Nexus 5 using Tapatalk
rootSU said:
No brainer really. Flashing an OTA if rooted is a fool's errand.
Click to expand...
Click to collapse
What's an OTA?
Lethargy said:
What's an OTA?
Click to expand...
Click to collapse
Unsure at this stage.
Sent from my Nexus 5 using Tapatalk
But if i'm completly stock and already unistalled Xposed, why I can't update OTA? I know how to flash the update, but would like to know why... Because if I receive an update installing error, maybe the system is with some files missing and I probably have to put back to stock all over again and then update no? (That's what i'm afraid off, because if I only need to flash the update no problem, but put all over to stock...)
ExoidX said:
But if i'm completly stock and already unistalled Xposed, why I can't update OTA? I know how to flash the update, but would like to know why... Because if I receive an update installing error, maybe the system is with some files missing and I probably have to put back to stock all over again and then update no? (That's what i'm afraid off, because if I only need to flash the update no problem, but put all over to stock...)
Click to expand...
Click to collapse
Who knows what all modules you installed and what changes those modules did to system? Just take our advice and flash the stock 4.4.4 rooted rom. Done within a few steps.
Why do you want to OTA update it?
- Sent from an IceCold Hammerhead!
vin4yak said:
Who knows what all modules you installed and what changes those modules did to system? Just take our advice and flash the stock 4.4.4 rooted rom. Done within a few steps.
Why do you want to OTA update it?
- Sent from an IceCold Hammerhead!
Click to expand...
Click to collapse
Exactly. We are not mind readers.. We do not have all the facts.. "Why?" Is not the right question. "How?" is the right question and that has already been answered.
Sent from my Nexus 5 using Tapatalk