Error updating from 4.3 to 4.4 - Nexus 4 Q&A, Help & Troubleshooting

I'm having difficulties updating from 4.3 to 4.4.
So, bear with me as I am a noob at this stuff, but when I got my Nexus, I rooted and flashed LTE onto the phone. I did not install TWRP, I just did a temporary custom recovery. Now, when I receive the OTA update, it stops around 25% of the way through, with an Error! and the red yield sign and the Android laying on its side.
I reset my phone, however, that didn't do anything. I think I have to undo the LTE before 4.4 can install. Maybe.
Could anyone offer suggestions/help me with this?
Thanks in advance.

To make the OTA update work you have to be unrooted running stock kernel and stock recovery. Otherwise you will get an error when updating OTA. First backup all your files to a computer.
- Download 4.4 custom ROM and flash it via recovery. Make sure to flash the latest boot loader and kernel.
OR
- Download stock 4.4 image file; unzip and run the flash all file. This will wipe everything in your phone and install stock 4.4.
OR
- Download N4 toolkit and flash 4.4 via that.
Sent from my Nexus 4 using Tapatalk

Related

[Q] Failed Custom Recovery Update w/ Dandroid 4.4

Phone: Samsung Galaxy S4 ATT I337UCUAMDL
Model Number in settings on 4.4 ROM = GT-I9505G
As the title says, I installed dandroid's newest 4.4 ROM from WICKED v5 4.2.2 and lost root. So I attempted to update my CWM Recovery from Odus 1x to the newest using Odin which failed do to write protected I suppose all though others says that doesnt effect their installs.
Where I'm at:
Cannot boot into recovery, says booting recovery the just reboots and enters Dandroid's ROM w/o root.
I'm now lost and have been reading the forums for hours. Currently downloading STOCK Samsung firmware for my device I337UCUAMDL_I337ATTAMDL_ATT.zip
CASUAL failed.
What do I need to do to get back to WORKING custom recovery w/ rooted dandriod 4.4 kitkat rom. Should I use Odin and flash stock rom then motochopper to root and try to reinstall working CWM recovery?
Please advise best course of action. My phone had been working properly with every ROM I tried before update to 4.4 ROM and attempted CWM recovery update (thinking that would fix my root issue). Thanks all!
If you have a nandroid, and I hope you do, just restore that in your custom recovery. If you don't, then you're going to have to return to stock with odin
Tried motochopper on the phone as it sits and it fails as well.
I have a stock backup but the problem is I no longer have access to any recovery. Guess I'm just gonna have to flash the stock firmware with Odin when its finished downloading and start over.
Just finished Odin flash back to samsung factory firmware. Phone stuck at att world logo on bootup, still can't access recovery. Any ideas?
GSXRspike said:
Just finished Odin flash back to samsung factory firmware. Phone stuck at att world logo on bootup, still can't access recovery. Any ideas?
Click to expand...
Click to collapse
If you flashed Odin successfully you can get into recovery.
Finally got into recovery it rebooted 3 times but just holding the req. buttons finally got me in.
Back on factory firmware and rooted w/ cwm recovery all back in place properly worrking.
I would like to use the Dandroid 4.4 ROM with this device. When I install am I going to lose root again and if so, how I do I get it back on this device since the model in the settings is going to change from I337 to I9505G after installing this ROM?
Figured it all out last night, re-flashed Dandroid's latest ROM which still caused me to loose root, then flashed SuperSU 1.51 instead of 1.80 and regained root. All is right in the world now.
GSXRspike said:
Figured it all out last night, re-flashed Dandroid's latest ROM which still caused me to loose root, then flashed SuperSU 1.51 instead of 1.80 and regained root. All is right in the world now.
Click to expand...
Click to collapse
Hey, if you dont mind me asking where did you get the 1.51 zip to flash? I'm having a similar issues with same ROM where i lost root but have recovery access.
Thanks
Update: Found the file. Flashed it. Root is back. Have you let market update it automatically? If so did you lose root afterwords?

Nexus 7 4.4.2 update

For the life of me I cant get 4.4.2 to install/boot on my nexus 7 2012 wifi
Wondering if there is a stock rooted zip out there so i can just flash it and be done with it.
Ive:
wiped
locked/unlocked bootloader
flashed the stock image (installs/boots but doesnt start) 'com.google.settings' fails at start.
flashed 4.4 image and tried to update via OTA (fails)
flash 4.4 and tried to sideload the update in stock recovery (failed, unexpected contents in system/google email)
flash 4.4 and tried to install update viz TWRP...failed
running out of ideas. My last hope is a 4,4,2 stock rooted rom i can just flash via twrp. but there doent seem to be one.
found one for my n10/n5, but not my n7 (2012 wifi)
any leads?

[Q] Deleted Stock Recovery?

Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
DeadlySin9 said:
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
Click to expand...
Click to collapse
The app is flashify
Sent from my Nexus 5 using XDA Free mobile app
Possible to restore stock recovery?
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
I would flash in Odin the stock mf3 tar file, but out will wipe the device. All his apps and data. If you can find the mf3 recovery image file you could try to flash that in flashify, if you're rooted
Edit, found this. I didn't download the file but I'm guessing it's a .img file. You could flash that in flashify or use the dd command
Sent from my Nexus 5 using XDA Free mobile app
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
In addition to the above post from jd, the CM installer will not work on our device as our bootloader is locked. There is no way to run any AOSP based ROM once your phone is on MF3 firmware or higher.
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
muniz_ri said:
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
Click to expand...
Click to collapse
Thanks to everyone for all the information, and thank you especially for sharing the link. I am staying with my parents short-term in a very rural area with awful internet and I was dreading downloading the 2+GB stock firmware file just to get recovery back. This is perfect. Thanks again!

SGS4 Stock Rooted. KitKat Update OTA failure (using triangle away.)

Ok, so last OTA worked. Here is what i did:
I used triangle away's feature to hide system modified warning
i downloaded the OTA update
I disabled the triangle away fix before installing OTA (like it says to do in triangle away)
Phone rebooted and installed the OTA in CWM
Done.
I tried this today to upgrade from 4.3 to whatever is being pushed by my carrier (kitkat)
this time, when i install the OTA, it reboots to CWM and CWM says "install untrusted zip?" I hit yes, it says install aborted. I hit no, it says same thing.
I have heard others mention this, and were told to restore a stock recovery. I have found instructions to do that here:
http://www.android.gs/how-to-install-stock-recovery-for-the-samsung-galaxy-s4-i9500-i9505/
But i dont have a i9500, i have the canadian model, the i337m
Can i still flash the stock recovery image from an i9500? or will i brick something.
also not understanding why i have to do any of this when it worked last time and nothing has changed....maybe because its jumping from 4.3 to 4.4 ... i dunno..
Any advice appreciated, id love to get this OTA. I just dont want roms anymore, only stock. but i want to stay up to date with my android version, and that is becoming tough for me.
thanks.
I'd flash the nb1 tar file in Odin. That'll return you to stock and you'll get the ota's
See this http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app

5.1 OTA upgrade error

I am on 5.0.1 rooted with stock ROM and stock kernel. I recently got 5.1 upgrade notification.
After downloading the data and restarting the phone, it started installing updates and after a while it showed "error" and stopped.
Now I m on 5.0.1 with no 5.1 upgrade notice.
What is wrong and what should I do for this?
Thank you.
Do I need to unroot? I am on stock kernel and ROM.
mike_24_11 said:
Do I need to unroot? I am on stock kernel and ROM.
Click to expand...
Click to collapse
Yes, you need to unroot before you can apply the OTA upgrade. Look for the Nexus Root Toolkit, and it should be able to clean up for you.
But prior I didn't need to unroot to upgrade anytime! To upgrade JB to KK or KK to LP, I didn't unroot before installation.
you need stock recovery to update via OTA
Yeah I was on pure stock. Stock ROM kernel and recovery.
Btw, I unrooted my phone with simply unroot and then OTA update went well.
So now I am on stock 5.1 unrooted.
Thank u all.
i have troubles as well. i unrooted, installed stock recovery (via n4 toolkit) and tryed to install. it takes longer then before but i stell get an error. SuperSU is gone in my app drawer.. any other help?
PS: i am on stock rom 5.0.1
i tryed to use sideload ADB update. it says: "/system/bin/app_process32" has unexpected contents. Error in sideload/package.zip. Status 7
any tipps?

Categories

Resources