I seen this subject discussed but never really saw a answer, seems like everyone resorted to re installing firmware which I would like to avoid if I can.......
so, Ran into some trouble today trying to trying to do the 3e recovery mod today and had to reinstall stock firmware (using odin and gtg). Got root access and was up and running. I went to updates just to see if anything was there and a update started and completed. the phone rebooted and was on the white and red update screen for about 4 secs and the phone rebooted again. When it Got back to the home screen and got a message saying the update had failed. since then device management will not stop popping up. it stays in the task bar and if you use any process that needs it, the failed update screen pops up again and DM crashes and restarts itself. the message in the taskbar says "connecting to DM server" like its trying to get a update. how can I stop this without resetting the phone?
loulou704 said:
I seen this subject discussed but never really saw a answer, seems like everyone resorted to re installing firmware which I would like to avoid if I can.......
so, Ran into some trouble today trying to trying to do the 3e recovery mod today and had to reinstall stock firmware (using odin and gtg). Got root access and was up and running. I went to updates just to see if anything was there and a update started and completed. the phone rebooted and was on the white and red update screen for about 4 secs and the phone rebooted again. When it Got back to the home screen and got a message saying the update had failed. since then device management will not stop popping up. it stays in the task bar and if you use any process that needs it, the failed update screen pops up again and DM crashes and restarts itself. the message in the taskbar says "connecting to DM server" like its trying to get a update. how can I stop this without resetting the phone?
Click to expand...
Click to collapse
it shouldn't be a prob after you flash a new rom on it.
If it really bugs you, you can try freezing it or remove the update manager pak with TiBu
I'm having a problem updating my phone to 4.4.2. Command prompt recognizes my device, and I can get to side loading. The problem is when the update reaches 100% it says E: footer is wrong and E: signature verification failed. My phone is stock, locked, and non-rooted. The only thing I can think might have changed anything is the percent enabler app which I used but I returned the phone back and deleted that app.
Btw, I did not receive the 4.4.1 or 4.4.2 updates which is why I'm trying to update this way.
Hello fellow xda-ers,
I have a OnePlus One, but i cannot seem to update the phone.
What is the exact problem?
- there is a system update ready, so i download the update and it asks me to install and then it tries to reboot
- the phone shuts down and doesn't reboot, i have to manually turn the phone off which makes the update sequence stop.
- the phone tells me again theres a update, but it doesnt reboot after it shuts down.
- even just giving the phone the command to reboot, just shuts the phone off and the phone doesn't reboot.
What did i try?
- via oneplus toolkit (mac) i flashed it to stock default, but still the problem persists.
- i flashed a 5.1.1. firmware straight from cyanogen mod, but still the problem persists.
- i flashed a custom recovery (while unchecking the update cm recovery), but the problem still persists.
I don't know what to do... Anybody have advice? It would be much appreciated.
I am pretty aware of what to do and not to do, i have been flashing phones since the iPhone 3gs. But this is just odd.
I was having similar problem. Except mine was booting into the bootloader. From there I tried to manually install the update. It kept failing so I gave up. Then about a week later (today) I let it try to install and it seemed to be working, except when it finally booted back up, it had completely wiped my phone!!! Now I'm midway though reinstalling all my apps and it gives me the "There's an update available for you phone". So apparently it didn't even update in that process.
I've got the exact same problem here.
Hi Community ,
Today one of my friends bought me the Alcatel Onetouch Idol 3 the 4.7 version Single SIM 8GB, Contract-free from Germany. During the first boot he was instructed to install the new firmware updates, everything went fine "I guess" until the phone restarted, he told me that the recovery mode screen appeared, but frankly i think that he got this screen by accident maybe he was pressing the power key and the volume up key while the phone was restarting who knows, anyways he selected Reboot system now from the menu, and when the phone starts up, no notifications were found and nothing says that the system was updated successfully.
So after all of this he checked the system firmware version, And it was 5.0.2-010 05,and a message saying new updates are available appeared. He proceeded the installation of this update, And everything went fine this time and he system is now 5.0.2-010 07.
So is it normal or the android system will be corrupted, The fact that i have the 5.0.2-010 07, does it mean that all the previous updates are applied correctly to the system ?
How can i please remove all the firmware updates and remove any changes so i can reinstall the system updates properly ?
P.S: I'm an android noob don't be harsh to me please
Hello and welcome to the comunity.
If everything works as it should be, that means the update was succesfull. Sometimes OTA updates are a small files about 50MB which only fixes some bugs, and thats why you dont need to see "android is upgrading" in the boot and also sometimes the OTA reboots the phone to recovery to be able to flash system files correctly.
So when you have 010.07 that means the update was successfull. If you maybe encounter some problems, just do factory reset the phone (you will lost all installed apps, sms, call log, but no photos and music).
DallasCZ said:
Hello and welcome to the comunity.
If everything works as it should be, that means the update was succesfull. Sometimes OTA updates are a small files about 50MB which only fixes some bugs, and thats why you dont need to see "android is upgrading" in the boot and also sometimes the OTA reboots the phone to recovery to be able to flash system files correctly.
So when you have 010.07 that means the update was successfull. If you maybe encounter some problems, just do factory reset the phone (you will lost all installed apps, sms, call log, but no photos and music).
Click to expand...
Click to collapse
Thanks a lot for the reply, So when the OTA reboot to recovery, choosing reboot system now from the recovery menu was the right choice ?
i think when the OTA has to reboot to recovery then there you should see some instalation progress which should end with automatic reboot. But anyway, when all works as it should dont bother with it.
DallasCZ said:
i think when the OTA has to reboot to recovery then there you should see some instalation progress which should end with automatic reboot. But anyway, when all works as it should dont bother with it.
Click to expand...
Click to collapse
I saw the installation progress only in the second update, in the first update the phone rebooted into recovery mode in which there is a static menu that i don't really remember the choices.
but yeah, anyways thanks
i am on custom rom, so i don't know how exactly the updates work. I am waiting to next update to android 6.0, but it will come not before march as i have i formations (more likely in summer )
I might as well try here if anyone will see my post.
I'm screwed. Latest stock ROM, unrooted and locked bootloader. I have/had the Google App (beta) installed on my phone but for the past couple of days it was constantly crashing and my phone became sluggish so I decided to uninstall it today. I left the beta program and as provided with instructions there went to uninstall the beta version to install the non-beta one.
It stayed on "uninstalling" for about 10 minutes and I presumed it was just a Google Play glitch and decided to reboot my phone. Big mistake! After the first install it was optimizing apps (but only one, so it was probably the Google App but it never got out of the next step (starting system/app, I don't recall what it said exactly right now)). I decided, stupidly, to reboot the phone since it was stuck and now I'm stuck on a bootloop and the phone won't even go past the Android logo animation. I guess the uninstallation never completed somehow and the app got corrupted(?).
I'm lost and I don't know what my options are except trying a factory reset and/or even unlocking the bootloader and getting a custom recovery and potentially rooting the phone too. But I really don't want to lose my data!! I have no backups.
Is there ANY chance I could somehow manage to solve the problem? Is it possible to sideload an app with a locked bootloader and stock recovery? I'm trying to sideload the Google app back in case it got corrupted but it doesn't work. I get the following errors:
Code:
E: footer is wrong
E: signature verification failed
installation aborted
Haaalp!
EDIT: Even weirder. I just let it run the booting sequence again and it got beyond the lollipop logo animation and is now stuck on "Android is starting... Starting apps." message.