Hi everyone,
I seem to have nothing but trouble when it comes to installing OTA updates for my Gear Live, and am wondering if anyone can help me.
It all started when the Android 5.1.1 update notification arrived on my Gear Live some time ago. I eagerly installed it, and expected it to install without any problems. Unfortunately, the update reached around 30%, before displaying the Android mascot with a red exclamation mark. I managed to restart the watch, and re-downloaded and installed the update. The same thing happened, except, it was stuck in a boot loop :crying:
I contacted Samsung Australia who took the watch in for repairs (it took them 4 weeks). I was pretty happy to see the watch working again, and running the 5.1.1 update.
Just yesterday, I received a notification that an update is ready to be installed. I swiped and hit install. The watch rebooted, and began the installation. Again, reaching 30% before failing and displaying the Android mascot with the red exclamation mark. I am yet again stuck in a boot loop. I managed to tap the Android mascot, which brought up the Android System Recovery. It said
"Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!"
I have cleared the cache, and have wiped the data through recovery. This seems to allow the watch to boot up, however, the process repeats itself when I try to update it again.
Does anyone know why the update would be failing, especially after it has already been repaired by Samsung, and how I can fix it myself (I don't really want to be without a watch again for 4 weeks)?
Thanks,
Tim
Did you try the live restore tool? (read the whole thread)
Brendo said:
Did you try the live restore tool? (read the whole thread)
Click to expand...
Click to collapse
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Verifying current system...
"/system/priv-app/ClockworkHomeGoogle/ClockworkHomeGoogle.apk" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
Click to expand...
Click to collapse
tims1710 said:
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Click to expand...
Click to collapse
Try a different usb cable? (ie official, not a cheap one)
My watch always took a few goes to get detected by adb
tims1710 said:
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Click to expand...
Click to collapse
I had that exact error yesterday when I was trying to install new OTA update. I flashed back to KMV78Y(from live restore tool v2) Don't use v3 it has corrupted file and breaks bluetooth.
Try to manually flash using fastboot. I wouldn't recommend trying to flash recovery partition from live restore tool since you can end up with a broken OTA and broken adb sideload. Also, don't try to flash TWRP into recovery partition. Loading it into ram memory is fine though.
Anyways, to manually flash using fastboot, you need to open console and go to directory of Gear live restore tool. Make sure your watch is in bootloader mode, not recovery. Type fastboot flash boot 78Yboot.img and then fastboot flash system 78Ysystem.img Do factory reset just in-case and upgrade your way up to latest firmware.
Related
So I did a "checkin" tonight to see if I could get a OTA and I got one! I am running a rooted phone with 2.2 on it and FRF50.
I clicked "restart and install" on my phone and it took me to a bootloader-type menu and it said failed.
Any ideas? Now the update doesn't show up anymore either...
download the full update and install that "insert link here"
I have the same problem... I downloaded the update, then I chose to install it and the update hanged to a screen with a android and an exclamation mark.
I have a rooted nexus 1 that runs 2.1-update1 (ERE27).
What do you mean by "download the full update"?
Can you post a link?
i'm having same issue.. its because we are rooted w/ custom recovery.
I don't think it's the boot loader...
At the screen with the android and the exclamation mark, I pressed the power and up buttons at the same time and I found these messages:
Code:
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/lib/modules/bcm4329.ko", [some really long string], [another really long string])
E:Error in /cache/signed-passion-FRF91-from-ERE27.e410116a.zip
(Status 7)
Installation aborted.
This is because I changed the wifi firmware to enable tethering.
I will try to restore the default bcm4329.ko and try again.
If anybody has anything to suggest, he is more than welcome
If you're running a custom recovery, you need the repackaged zip. Check the dev forum.
I don't know what a custom recovery is!
I have only rooted my phone without paying much attention (I was just typing some commands back then).
I restored my N1 to its original shipping state using this guide: (I can't post links, so just search in google for "Restore your Nexus One to its Original Shipping Image" and the first result is the one I used).
Then my nexus redownloaded the update, and it was applied successfully.
Perhaps it was an overkill to wipe everything to apply the update but it wasn't neccessary for me to keep everything I had in my phone!
Cheers!
So I just got a message for an OTA update and I tried to install it. During the installation, the phone aborted it and asked me if I wanted to reboot. What I didn't realize was that the system UI was deleted so that the new update could replace it. When I rebooted my phone it started up normally but then went into is a blue screen. I tried to reboot the system again in recovery mode but it won't go into it. Is there anyway I can fix this?
EDIT
I got into the recovery and tried to do a sideload to see if I could get a rom onto the phone but my phone won't connect to the computer. If anyone knows of something I could try, it would be much appreciated.
Hey everyone,
I'm having a problem after trying to flash CM12.1 on a i8190l.
The instructions I basically followed are the ones mentioned here: novafusion.pl/tutorials/installation-guide-golden/ and I used the rom Lollipop 5.0.2 (CyanogenMod 12.0) 20150428 stable with the Odin app to install it.
All went well up to the point 12. Click on Wipe, then use slider on the bottom to let process begin.
At this point I received a FAILED message with an error message saying below that /data couldn't be mounted. After that, I rebooted the phone, and it started loading the first android screen apparently. After a few minutes, Android threw up an error saying that it couldn't encrypt the data and had to reboot. After that reboot, the system won't stop going over a loop boot that flashes TeamWin over and over again.
I can still get to the download mode, what is the recommended step to take from here? Is it possible to recover the OS? Do I have to worry about the battery running out, or does it charge up while on download mode/other mode?
Thanks for your help
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
i2ectcf said:
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
Click to expand...
Click to collapse
did you wiped data, cache, dalvik?
snapdesign said:
did you wiped data, cache, dalvik?
Click to expand...
Click to collapse
Hi! I'm not sure how to wipe data, cache or dalvik, because when I upgraded to Nougat this apparently removed TWRP.
Also I'm wondering if trying to use srktool to reinstall TWRP for 6.0 might have corrupted my 7.0 phone?
Is there any way to wipe data, cache, and/or dalvik now? Or are there other things I could try to unbrick?
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow. Here's an outline:
1. Google "Huawei Bricked phone repair guide with DC Phoenix", go to the first result and look at the instructions (I can't post URLs yet).
I used Method 1. But note! The newer versions of DC Phoenix are missing a feature that the instructions make clear you have to use. To get the original version used in their guide, you have to download the latest version of DC Phoenix, open it on your PC, then click "Enter Support Area" which logs you in to a download section. Find "DC Unlocker Softwares", "DC_Phoenix", then download DC_Phoenix_v14.rar and run that instead. Whether it's Method 1 or 2 make sure you complete it - i.e. the fastboot flash step AND a step they call "flashing in upgrade mode."
(Also note that for DC Phoenix you want to feed it the oldest version of firmware available for your phone, in my case b152. This is because themes and icons won't be fixed until it receives the next version of firmware as an update.)
2. Once I did the fastboot and upgrade flash, I did a system reset from the Settings app trying to get themes and current icons again. (This didn't work but doesn't do any harm or might have helped somehow further down the line).
3. I used hajuuk's Firmware Updater and HiSuite to upgrade to the next version of firmware available (in my case b168).
3. All fine and your phone is back to stock - icons look nice again and local themes are back. To get the original icons layout, go to Recents, hold down on the Trash Icon, show system apps, and Clear Data for Huawei Home.
i2ectcf said:
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow.
Click to expand...
Click to collapse
Thanks for sharing! You saved me!
I'm having problem with I-8190 (s3 mini) that used to run Resurrection remix (android 5.1). I followed these instructions: https://forum.xda-developers.com/showthread.php?t=2429169 to install stock android
but the stock android did not work, it didn't have wifi available so it's stuck on 'google login' stuff and phone also spams "com.google.process.gapps" error.
That happened with few different stock android images. Then I decided to try install RR 5.1 (with odin) again, it phone remains in bootloop doing the 'optimizing application x/xx' part.
Then I re-installed twrp and tried flashing RR5.1 but install gives error, "Error executing updater binary in zip '/extern" (line break, dunno how it continues)
Could someone give some pointers on how to make phone run some operating system again..?
seegge said:
phone remains in bootloop doing the 'optimizing application x/xx' part.
Click to expand...
Click to collapse
That's not a bootloop, it's optimizing every app in the ROM. Do it again, then go watch TV until it's time to go to sleep and see if it's finished. (If not, plug in the charger and go to sleep and it should be finished by morning.)