Database Develop

[Q] AT&T Kitkat Update "Install interrupted"

Hey,
So I was going to update my Phone to 4.4 KitKat.. This is a AT&T Phone. I've tried to update the phone twice through the check for updates section on the phone and both time it failed with this error message.
The phone was previously rooted and then the rooting was broken by an AT&T update so although I still get the Custom message when the phone boots up it's not rooted currently.. Do I have to roll this phone back to a unrooted version of the Firmware before I can do the update? If so can someone point me in a direction for instructions on doing that?
Thanks

Yes, from what I understand you have to go back to stock, or flash a leak.

Bricked, Unbricked, how to update?

So I was on 4.4.2 before and rooted and wanted to update and followed an old guide which led me to an old link to the toolkit. The result was downgrading to 4.2.2, OTAing, and then bricking. It took me awhile but somehow I flashed the 4.2.2 again and managed to unbrick myself. Now that I can access my phone again how do I update to the newest 4.4.4 without bricking again? I'm a bit afraid of doing anything at this point. Is it possible to just flash a custom rom to avoid it (I'm on developer edition)? Is it safe to RSDlite to 4.4.4 using the right carrier?

edit:
nevermind... I turned the phone off to check the status of the bootloader and saw it was unlocked, did a normal power up. For some reason it said android is updating even though I didn't do any updates and it randomly turned off and now it's completely dead .

Same problem
nvertigo said:
edit:
nevermind... I turned the phone off to check the status of the bootloader and saw it was unlocked, did a normal power up. For some reason it said android is updating even though I didn't do any updates and it randomly turned off and now it's completely dead .
Click to expand...
Click to collapse
My girlfriends phone has the same issue. It received an OTA update on Friday and kept havin problems running programs and rebooting. This morning it was off and when it booted, it couldn't get past the "unlocked bootloader" warning. I could get to the recovery menu but could not run TwRP because it froze at the splash.
I have tried installing a new recovery via faastboot but after it "installs" , it still appears to be the old recovery.

If you can boot the phone to FastbootAP/Bootloader, check the bootloader version on your phone, and get the corresponding SBF version or NEWER.
Example:
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
xx.xx = 4.4 <-- I forgot the bootloader version.
30.B4 = 4.4.2
30.B7 = 4.4.4
using an OLDER version SBF will fail at GPT.BIN and Motoboot.img, or will brick your phone!!!
Flash the SBF by following option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Doing this (flashing the latest SBF for your phone/bootloader) should bring everything on your phone back in line, making it safe to take future OTA's

What to do to avoid brick my Nexus 6 if I'm rooted already?

Good Morning all,
When I first time received my Nexus 6, unlocked the bootloader and Rooted with the app for windows Nexus Root Toolkit by Wugfresh, I did not change it to any custom recovery, I left it on stock the rom and I did not install any custom recovery as well., everything is on stock, I just I rooted it.
I've read a lot of things about partitions, downgrades, even OEM Locks and OEM Unlock Bootloaders and people have bricked many devices that I'm afraid to brick it, I'm confused know what steps to follow in order to properly update from lollipop 5.01 to 5.1
I'm on Android 5.01 and received the OTA to update to 5.1, but afraid to press the button in my nexus 6 where it says System Update Available
Should I continue to update with the OTA that I received even if I'm rooted? or should I do it manually with the Nexus Root Toolkit?
What do I need exactly to check / verify before I try to update my device and not brick it?
Please advise

rayosx said:
Good Morning all,
When I first time received my Nexus 6, unlocked the bootloader and Rooted with the app for windows Nexus Root Toolkit by Wugfresh, I did not change it to any custom recovery, I left it on stock the rom and I did not install any custom recovery as well., everything is on stock, I just I rooted it.
I've read a lot of things about partitions, downgrades, even OEM Locks and OEM Unlock Bootloaders and people have bricked many devices that I'm afraid to brick it, I'm confused know what steps to follow in order to properly update from lollipop 5.01 to 5.1
I'm on Android 5.01 and received the OTA to update to 5.1, but afraid to press the button in my nexus 6 where it says System Update Available
Should I continue to update with the OTA that I received even if I'm rooted? or should I do it manually with the Nexus Root Toolkit?
What do I need exactly to check / verify before I try to update my device and not brick it?
Please advise
Click to expand...
Click to collapse
Do not re-lock the bootloader, do not try to downgrade the bootloader. Do not Flash CM12 from the 3/13/2015(not available to download anyways). You should be ok.
If you have stock recovery, sounds like you can flash the OTA...but that is up to you.
Can you describer your system. You said it is STOCK rooted. Did you unlock bootloader? Never flashed anything before?

idtheftvictim said:
Do not re-lock the bootloader, do not try to downgrade the bootloader. Do not Flash CM12 from the 3/13/2015(not available to download anyways). You should be ok.
If you have stock recovery, sounds like you can flash the OTA...but that is up to you.
Can you describer your system. You said it is STOCK rooted. Did you unlock bootloader? Never flashed anything before?
Click to expand...
Click to collapse
Thanks on helping me out,
I'm attaching two shots so you can see all what I have, I have never flashed a custom ROM, just rooted using the wugfresh app for windows,
Also I have in developer options usb debug on and unlocked oem with a check mark.
Again, if you check everything above, I'm on 5.01 and I don't know if just pressing OTA system update button to update from the phone shall brick my phone whether I am rooted, or do I have to be with no root to proceed from there?
Please advice
Sent from my Nexus 6 using XDA Free mobile app

rayosx said:
Thanks on helping me out,
I'm attaching two shots so you can see all what I have, I have never flashed a custom ROM, just rooted using the wugfresh app for windows,
Also I have in developer options usb debug on and unlocked oem with a check mark.
Again, if you check everything above, I'm on 5.01 and I don't know if just pressing OTA system update button to update from the phone shall brick my phone whether I am rooted, or do I have to be with no root to proceed from there?
Please advice
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Looks like you should be fine to install the OTA with no worries.
Please note: I in NO WAY take responsibility for anything that happens to your phone though....sorry...have to put disclaimer

idtheftvictim said:
Looks like you should be fine to install the OTA with no worries.
Please note: I in NO WAY take responsibility for anything that happens to your phone though....sorry...have to put disclaimer
Click to expand...
Click to collapse
Lucky me that I did not press the button to do it through OTA, read below
Can I still take an OTA after I unlock and root?
Answer: On Lollipop, No. On KitKat, yes (sometimes) – if you haven’t made any other system level modifications.
With Lollipop, the OTA update process checks the entire system blob. That means if just one small thing is different about the system partition the OTA will fail. Since rooting itself (regardless of the method: manual/toolkit) installs Superuser as a system app and su binaries to the system partition it inherently breaks OTA’s.
So how should you update a rooted Lollipop device?
1. Wait for the official factory package from google to be released for the build you would like to update to.
2. Backup your apps + data, as a safe measure – in case you end up having to wipe data.
3. Use “Flash Stock + Unroot” and check “No-wipe mode” (to avoid a data wipe).
That’s it. Afterwards you can re-root.

[Q] Unlocked Bootloader running 5.01 - is it safe to upgrade OTA to 5.1?

Hi Noob question here, I don't want to root or flash my Nexus 6, I bought it from a guy 2nd hand and he had flashed various roms. He restored it to stock android before selling it to me - It has the unlocked padlock on boot - Unlocked Bootloader running 5.01 - is it safe to upgrade OTA to 5.1? Will there be any danger of bootloop?
What should I do?

@Darius,
Unlocked bootloader has no effect on installing OTA.
Yes, there's always a risk of bricking if you don't follow the directions precisely. There are several "how to" threads. Read, understand, and ask questions.

Whatever you do, relocking the bootloader is probably not the answer ?
Sent from my Google N6 on VZ

Darius said:
Hi Noob question here, I don't want to root or flash my Nexus 6, I bought it from a guy 2nd hand and he had flashed various roms. He restored it to stock android before selling it to me - It has the unlocked padlock on boot - Unlocked Bootloader running 5.01 - is it safe to upgrade OTA to 5.1? Will there be any danger of bootloop?
What should I do?
Click to expand...
Click to collapse
If the device is completely stock (including recovery), you should be able to take the OTA. Unless there is something wrong with your device hardware, I don't see any risk. It is just a regular OTA you get from google, direct to device, and you just apply it. Just make sure your phone has a full charge, and don't interrupt the update process.
As a precaution, you should back everything up - never say never
Oh, and to second what DebianDog wrote, don't lock your bootloader

Thanks for all the tips guys, applying update right now...

I have been trying to upgrade my Sprint Nexus6 for the last 3 days. the download goes well the install gets halfway through the blue line under the Android and then he lays down with an "Red Error"
boot loader unlocked and rooted running Stock 5.01. suggestions of the log files i should pull to help narrow this down?

myopic said:
I have been trying to upgrade my Sprint Nexus6 for the last 3 days. the download goes well the install gets halfway through the blue line under the Android and then he lays down with an "Red Error"
boot loader unlocked and rooted running Stock 5.01. suggestions of the log files i should pull to help narrow this down?
Click to expand...
Click to collapse
Nothing needed to narrow it down - you cant take the OTA if you rooted -> because rooting installs SU -> which changed your /system partition -> it no longer matches what the OTA looks at -> and it will fail, sorry.
Unroot it and you might try it again, or you would have to re-flash a stock image to be clean and then take it. The bootloader being unlocked is not the cause.

Return rooted VZW xt1060 4.4 back to stock

Hi,
I rooted my GF's Verizon Moto X on 4.4 like 2 years ago and can't remember how I did it. I feel like it had something to do w/ slapMyMoto or one of those toolkits.
With the announcement of Lollipop finally being released I wanted to return it to stock so It can be updated to 5.1.
Does anyone know how I should go about doing this? Is it as simple as just doing a standard update? through the software update in "about phone" or will that break it without reverting somethign first?
EDIT: when i click on update, it give me the following error "Unfortuantely, com.motorola.vzw.settings.extensions has stopped"
EDIT2: looks like that previous error was because i had some of the updater/OTA apps frozen. It now seems to present me w/ the option to update to 4.4.2. Decided to give it a shot and try to take the OTA. It rebooted and shows the android guy with "installing update" then eventually turned to a "error" android guy and rebooted, so no successful update.
THanks and sorry for the probably dumb question. I've been too spoiled w/ nexus'.

Download the stock firmware and flash it with Moto's fastboot executable, at least if the bootloader is unlocked you can do that. I'm not really sure if it will work with a locked bootloader, but I'd imaging that it wouldn't. I believe that there is a sticky here that even guides one through the process of returning to stock.

Thanks, i did eventually find some info and flashed the stock 4.4 image. After doing so, I was able to take the OTA to 4.4.2. However now that i'm on 4.4.2, it says my "software is up to date" when checking for the 4.4.4 OTA. Anybody have any tips on how to get it to go to 4.4.4?

to get 4.4.4 update
530farm said:
Thanks, i did eventually find some info and flashed the stock 4.4 image. After doing so, I was able to take the OTA to 4.4.2. However now that i'm on 4.4.2, it says my "software is up to date" when checking for the 4.4.4 OTA. Anybody have any tips on how to get it to go to 4.4.4?
Click to expand...
Click to collapse
it happened with mine too. I uninstalled motorola update service then got the official 4.4.4 OTA update. i hope that works for you too.