updates and root - Wildfire General

folks, i have updated my wildfire to 1.25.x.x.x in system updates.
than i rooted my phone and checked for updates again and it found 1.37.x.x.x
So when i run that update, it reboots phone - shows unpacking icon with android and than shows triangle with exclamation which is Clockwork recovery.
Any idea what i should do to update it?
should i unroot it? or is there another way around it?
it shows Signature verification failed, thats why it won't install update.
thanks
Shucks, found solution

Related

[Q] Few Questions

Running ota ics
Wanted to install acer recovery from market, but *****ed about no root. Is this normal...? Do I need root to run acer recovery..?
Ran blackthunders ics 7.1 with the defult checks to get root
But still have no super user or busybox installed even though it is checked
Ran the unroot and it goes through the motions but does not change anything.
No says system updater has stoped. So I cleared data of system updater, still says system updater has stopped.
Also stuck at obtaining ip (reset) no fix.
Did I do it wrong, One click and I was screwed.
Also cmd box comes up adb server out of data.
Any ideas
Got fixed. Seems the 7.1 has no error checking when it roots and does it's thing, so with or without a connection it will run like its working whether or not its connected. And if you got a good connection and it drops during the rooting you won't know till you have a messed up tab.

4.1.2 update fails

My wife's nexus 7 won't update to 4.1.2. I wasn't paying attention to it, just noticed today she is still on 4.1.1. I keep going to update after stopping and clearing the Google services framework and I keep getting the red triangle. The error says assert failed... no app is listed, but it does say tegra 3 in the long error message.
More info:
Bone stock, never been rooted.
I have wiped cache.
I do NOT want to do a factory reset as she has stuff everywhere.
I am guessing I will have to load the update from the Google servers, but even then it might fail.
Of course I have done a Google search and got nothing useful other than to root and load a Rom. This is not mine and I am frequently gone, don't want to root it or anything as I am rarely home to fix any issues.
Could you please share the exact error here? It will be much easier to find a solution to the problem once we see what the error is.
Sent from my Nexus 4
Here is the messages during the update:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
Assert failed: apply_patch_check("Emmc:/dev/ block/ platform/sdhci-tegra.3/by-name/lnx:5007360:089ca623419a5766da5b95b17352cffcbf1c610:5013504:c48f8e86c73fb2c2ba1794f5ec98e27c9e206ed5")
Installation aborted.
That error means that the update was attempting to patch the kernel and failed. That is very strange if the device has not been modded at all.
Has the bootloader been unlocked?
Sent from my Nexus 4
Ya positive its never been unlocked. And I know it is still locked as one of the screens I went into last night showed this.
After sleeping on it, I got to thinking I can probably just call Google for tech support. This is actually a legit issue I didn't cause by playing with it! For once. Lol
Okay, I called Google and they just told me to do what I did, which of course wasn't helpful. They said to do a factory reset, which didn't work. I tried to do the following update to 4.1.2, and that had the same error:
http://www.youtube.com/watch?v=PwlXQoAzrBE
I am still on 4.1.1 build JRO03S. I am trying to do this without root but clearly I can sideload files with adb. I read someone else had the same problem but the display was changed from 213. My bootloader is locked and everything, so no root, not sure how mine could have been changed.
Anyone know how to manually update to 4.1.2 without root? (other than the instrucitons above, I see there is more than one version of 4.1.1, so maybe I used the wrong update file when I manually tried).
Please help!!!
Thanks
Use wugs toolkit to unlock boot loader, then reflash your nexus with the update you want. Once that finishes simply relock the boot loader. I had your same problem. Just make sure to use wugs to backup as boot loader unlocks wipe the device.
Sent from my Nexus 7 using Tapatalk HD

[Q] Get rid of "Custom" boot after MK3 update?

I had a rooted S4 running stock ROM. Unfortunately, I STUPIDLY did the MK3 update without really thinking about it or researching it. As expected, it got rid of my root ability. Only after that did I find out that I couldn't reroot yet. So here's my question. I've used root explorer to see if the Superuser apk is still showing in the system/app directory, which it isn't. So I uninstalled the Superuser apk that was still showing in my applications list (do updates automatically move the apk to a non-system directory?) and restarted my phone. Unfortunately, the "Custom" logo is still showing on the boot screen. Does anyone know of a way to get rid of that? I'm sure root will be reestablished sometime in the future, but I'd hate to have something happen to my phone that required repair and me still have the "Custom" thing showing.
Any ideas would be greatly appreciated!
brickjr said:
I had a rooted S4 running stock ROM. Unfortunately, I STUPIDLY did the MK3 update without really thinking about it or researching it. As expected, it got rid of my root ability. Only after that did I find out that I couldn't reroot yet. So here's my question. I've used root explorer to see if the Superuser apk is still showing in the system/app directory, which it isn't. So I uninstalled the Superuser apk that was still showing in my applications list (do updates automatically move the apk to a non-system directory?) and restarted my phone. Unfortunately, the "Custom" logo is still showing on the boot screen. Does anyone know of a way to get rid of that? I'm sure root will be reestablished sometime in the future, but I'd hate to have something happen to my phone that required repair and me still have the "Custom" thinnon-sys
Any ideas would be greatly appreciated!
Click to expand...
Click to collapse
1. make sure you are using superSU and not superuser...
2. are you using geohot's lambda activeroot?
I have the custom icon on my boot screen sometimes,when it does my system settings show custom, and then sometimes it goes away and my systems settings show official.but I have never lost root, and my firmware updaters r renamed. I am curious. and if anybody can point me in the right direction A custom recoveryCWM preferrably, please do.

Nexus 4 OTA 5.1 Update error

I'm getting the OTA update to Android 5.1, it downloads, asks me to restart, then fails with an error screen and the robot lying on its back. The phone then reboots itself into the 5.0.1 firmware.
The phone is rooted, is anyone else getting the same issue. Are there any logs I can look at to find out why?
Thansk
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?
I used the excellent Wug Nexus Toolkit http://www.wugfresh.com/nrt/
Through there I unrooted. Then applied the new update.
rowdybeans said:
I'm getting the OTA update to Android 5.1, it downloads, asks me to restart, then fails with an error screen and the robot lying on its back. The phone then reboots itself into the 5.0.1 firmware.
The phone is rooted, is anyone else getting the same issue. Are there any logs I can look at to find out why?
Thansk[/Q
I tray everything but don't work, it tell me , cache file fail.
Click to expand...
Click to collapse
In my case, this did the trick: aaronhastings.me/updating-to-android-5-1-0-on-rooted-nexus-5
I hope it will help you, too.
Regards.

I think my fire tablet just updated on its own despite having the adb hide stuff done

Ive just rebooted my fire tablet after installing some minecraft mods, when I turnt it back on it came up with a promt saying it was installing the latest software or what ever it does when doing the ota, I knew this from upgrading to 5.0.1.
is it possible it was just doing what happens when normal android optimises apps on boot. is there a app to check the installed software version as im not near my pc to unhide and go in and check what firmware im on. I put this in general as it wasnt a question but just to inform that my tablet possibly had a update despite the proper steps taken to hide the ota and updates.
Saw Same Message But No Update (whew)!
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
dubliner52 said:
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
Click to expand...
Click to collapse
Have you tried unhiding to see the software version
Sent from my HTC One_M8 using Tapatalk
I didn't unhide it, but it says I'm still on 5.0.1. There was no update.
I saw the same thing but it didn't seem to update. I know the method i provided works for 5.0.0 to 5.0.1. Until there is a bump to 5.0.2 or whatever we don't know for sure if the "fix" works under 5.0.1.
Same thing happened to me but it was 3 days ago. I had been trying all day to install my adb drivers without success and switched off the device. When I restarted it immediately went into an update and I went into a panic that the new update would block the ability to access google play but immediately after the assumed "update" I successfully installed the adb drivers and google play without problem. I also checked the version and it still showed 5.0.1 so I wondered if my initial update on switching on the fire for the 1st time had somehow been unsuccessful and that had been what had been causing the inability to load the adb drivers although the tablet hadn't seemed to have any other problems and I had already downloaded and used several apps from Amazon.
I let it update upon first booting my Fire to 5.0.1. I was still successful in installing Google Playstore and hiding ads on lockscreen.
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik runtime files after rebooting when an apk is modified. nothing to do with an ota.
julianpaul said:
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik files after rebooting when an apk is modified. nothing to do with an ota.
Click to expand...
Click to collapse
That is my conclusion also.
I had this happen to me also. Considering amazon patched a root method I made sure to root and nuke any chance of a future OTA unless I wanted it too. That was a cheap move, Amazon.

Categories

Resources