to be clear, all i need to do is get the the update.zip to switch to gen1
is this correct?
does the bootloader need to be unlocked?
....your thoughts?
-------------
update 1: the downgrade to gen 1 worked fine, as i type this message the ICS update is downloading/installing, i'll keep you up to date
update 2: three updates later i'm running version: 4.0.3....wooohoooo
nobody answered me but i found out you do not need to unlock the bootloader
Sorry I missed this post. Thanks for the updates.
Related
Checking the forum for the pass 2 days but can't really get satisfaction answer:
I have just unlock my bootloader but not yet rooted.
I would prefer to have the standard ROM instead of the customer ROM at this moment, question below:
a) If I do not rooted my phone, do I able to update through OTA as normal? (my ROM still on 1.28 and wish to wait for the 1.29 to solve the SD card missing issue). Do I need to relock it back first?
b) If I decided to rooted my phone, can I still get the full update (including Radio.....?) Do I must use the RUU file to do the update.
Sorry if above question seems stupid as I'm totally new to Android system.
Phonix
I updated to JB yesterday with the OTA on T-mobile. I am rooted and used OTA root keeper to restore root. I went to change my build.prop file to change the display density. What I didn't do was use the new build.prop from JB. So I softbricked my phone. I restored to UVALH2 and was going to get the OTA's to go back to JB. When I click on "Software Update" it says I am up to date. I noticed that my baseband is still JB's.
The question here is, does software update go off of what is listed for the Baseband or the Build Number?
Solved
Haven't made too many posts where I need to update afterwards. I decided to reflash UVLH2 modem. Once back in phone I went to about device and tried to do the SW update. It prompted me for download.
So, from what I can tell here, OTA are based upon your radio version, to answer my own question. Good day!
Glad you got it figured out. All of that is covered in the Official Jelly Bean thread.
This one is closed. If anyone uses search (ya right jk) and this thread comes up, just go to the above thread.
Hello Guys
another question,i have E980 AT&T but if i returned to stock JB can i update to KK from the phone Software Update OTA? kindly dont answer if you are not sure
Still waiting...
I can't believe that there isn't anyone can answer this inquiry....
People aren't answering because you can find the answer by doing the search, consider these type of questions are discussed a year ago. Yes, you're safe to install through the OTA update as long you're not rooted while you're updating. If you're rooted while doing the OTA update, you will most likely end up with the bootloop.
hawkwind212 said:
People aren't answering because you can find the answer by doing the search, consider these type of questions are discussed a year ago. Yes, you're safe to install through the OTA update as long you're not rooted while you're updating. If you're rooted while doing the OTA update, you will most likely end up with the bootloop.
Click to expand...
Click to collapse
first of all thanks for your reply, second thing, i know that im safe to do an upgrade through OTA and i know that for sure i dont have to be rooted, and my question is IF i went back to 4.1.2 (JB) can i upgrade officially OTA to KK 4.4.2 if i entered the (software update menu)?
I didn't say to be rooted, I meant it's unsafe to do an ota update if you were rooted. If you flashed the stock jb ROM, and wanted to update to stock kk using the ota, you're safe to do so as long you don't root before your update. Is that what you're asking?
Thanks again for responding, but in my question at the begining i didn't mention the root issue, and i know that u cant update ota if u r rooted, and what im.asking for is when i return to JB 4.1.2 and i want to have the official KK can i updated ota?
My E980 performed this update OTA some time ago. I purchased my E980 when it was ~1 year old from AT&T so it was $50. I suggest you check the AT&T support site to see fi you can update it via them if you step down to 4.1.2. The issue is that the update may no longer be pushed to your phone and you may be required to perform the update manually.
Hi!
I have a question:
If I'll just unlock the bootloader (no root or recovery), will I be able to install OTA updates?
If yes, can I root it and still install OTA's?
I'm ok with having to reroot, but can I install OTA's while I have a custom recovery and root?
Thank you!
EDIT:
Thanks to ollie_o I found a solution, see below for details
I was wondering the same - I've had one small OTA update when I first turned the phone on, but nothing since I unlocked the bootloader - has there been a December security update yet?
Can anyone confirm what the most recent OS version / security update is?
Mine's running the LMY48B build (Oct 7) with the November security update (2015-11-01)
Found out the solution!
benjymous said:
I was wondering the same - I've had one small OTA update when I first turned the phone on, but nothing since I unlocked the bootloader - has there been a December security update yet?
Can anyone confirm what the most recent OS version / security update is?
Mine's running the LMY48B build (Oct 7) with the November security update (2015-11-01)
Click to expand...
Click to collapse
Thanks to olli_o, I was able to find the answer:
You can't update with root, I don't know about unlocked bootloader, but you can install updates manually even if you are rooted. You just need to re-install the root after each update
Link to guide: http://forum.xda-developers.com/wileyfox-swift/general/rom-wileyfox-swift-t3267037
:good: Thank you olli_o :good:
Can someone help me downgrading from AW 2.0 to 1.5??
I tried to flash old Bootloader with no success. Also update from recovery over adb push wasn't successful.
Maybe someone can help me? I don't like AW 2 at all.
Yes. Use the non-preview image here: https://www.androidfilehost.com/?fid=745425885120748838
I think I've tried this too. But I can try again.
Are these steps right?
Flash developer preview of AW 2.0
Flash AW 1.5
Flashing AW 1.5 over actual AW 2.0 is not possible. Bootloader can't be flashed.
maierbosch said:
I think I've tried this too. But I can try again.
Are these steps right?
Flash developer preview of AW 2.0
Flash AW 1.5
Flashing AW 1.5 over actual AW 2.0 is not possible. Bootloader can't be flashed.
Click to expand...
Click to collapse
Why would you flash both in succession? Use adb to flash 1.5 AFAIK.
maierbosch said:
I think I've tried this too. But I can try again.
Are these steps right?
Flash developer preview of AW 2.0
Flash AW 1.5
Flashing AW 1.5 over actual AW 2.0 is not possible. Bootloader can't be flashed.
Click to expand...
Click to collapse
The other images should still flash. It should still work even if the bootloader won't downgrade.
I've tried to flash via adb version 1.5. Stucks on flashing Bootloader.
Error message is wrong Bootloader or when I flash only old Bootloader it stucks on writing but finished message won't be shown. Sorry for my bad English!
I've also tried to flash only system.img from 1.5. But then the watch won't boot. Only shows Huawei logo.
1. Make sure your bootloader is unlocked, obviously. If your bootloader is locked, it will not allow a downgrade. Look for "unlocked: yes" when your watch is in fastboot mode.
2. ADB is not involved in this process and not capable of flashing anything, so I'm not sure what you mean by "flashing via ADB." The only thing you could maybe use ADB for is rebooting into fastboot mode (adb reboot-bootloader). You need to be in this mode to flash anything.
3. Flashing only system won't work because you're trying to use 1.5 with the 2.0 kernel still installed. Flash as many of the 1.5 images as possible. System.img and boot.img at the bare minimum.
Also, I'm in the process of making a flashable zip to downgrade 2.0 back to 1.5. Part of this process involves me downgrading my watch using the Google factory image that I linked to. It worked just fine, bootloader and all.
I have rolled back to M6E69F - (sturgeon-m6e69f-factory-e659286a.tgz) When I try to update with the Jan 2017 security patch OTA it says Error: Expects build fingerprint M9E41Y or M9E42C Release keys. This device is running M6E69F. How do I apply the Jan 2017 update? Android wear 1.5.0.3594574
Vapor85 said:
I have rolled back to M6E69F - (sturgeon-m6e69f-factory-e659286a.tgz) When I try to update with the Jan 2017 security patch OTA it says Error: Expects build fingerprint M9E41Y or M9E42C Release keys. This device is running M6E69F. How do I apply the Jan 2017 update? Android wear 1.5.0.3594574
Click to expand...
Click to collapse
OTAs only work on the firmware that they were designed for. There were a total of 3 updates that were released between M6E69F and the 2.0 rollout. You need to find those OTAs and install them in sequence. I found the OTAs that you need last night because I'm working on a flashable zip that will give everyone M9E42C with OTAs disabled. I'll upload those OTAs and post them here in a few hours.
EDIT: Here is a zip containing the 3 OTAs: https://www.androidfilehost.com/?fid=745425885120732730
1. Extract update1, update2 and update3.zip.
2. Install update1 via adb sideload in recovery.
3. Reboot normally and allow the watch to complete the "android is upgrading" process.
4. Repeat this process with update2 and update3.
Hello.
For me it was a success doing it like in this video.
https://youtu.be/nqNw4TFMVrs
Funny is the fact that I did it like that yesterday with no success. I'm on 1.5 now and happy with it. Living with 2.0 would have not be possible. The notifications are terrible. You don`t see if you have a notification or not. My Samsung Gear S3 shows a yellow point so you know that there is an unread message. If I wheren't able to downgrade I would have sold my only 5 days old Huawei Watch.
TheSt33v said:
OTAs only work on the firmware that they were designed for. There were a total of 3 updates that were released between M6E69F and the 2.0 rollout. You need to find those OTAs and install them in sequence. I found the OTAs that you need last night because I'm working on a flashable zip that will give everyone M9E42C with OTAs disabled. I'll upload those OTAs and post them here in a few hours.
EDIT: Here is a zip containing the 3 OTAs: https://mega.nz/#!D0Y30DJY!AjjxAjRo1nuVxedsPZKRYEZVnBtlzVtFJS2j269n7Ws
1. Extract update1, update2 and update3.zip.
2. Install update1 via adb sideload in recovery.
3. Reboot normally and allow the watch to complete the "android is upgrading" process.
4. Repeat this process with update2 and update3.
Click to expand...
Click to collapse
Flashing the updates now, thanks!!!!!
i managed to downgrade my HW1 to 1.5 from 2.0
BUT HOW i disable and remove update notification from 1.5 to 2.0???
jdsm said:
i managed to downgrade my HW1 to 1.5 from 2.0
BUT HOW i disable and remove update notification from 1.5 to 2.0???
Click to expand...
Click to collapse
https://forum.xda-developers.com/hu...aw-1-5-build-m9e42c-to-downgrade-2-0-t3607859
TheSt33v said:
Yes. Use the non-preview image here: https://developer.android.com/wear/preview/downloads.html
Click to expand...
Click to collapse
That link doesn't work anymore. There are no images there =(
jambaj0e said:
That link doesn't work anymore. There are no images there =(
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=745425885120748838
Thank you so much for this. I was about to return my newly purchased watch but found this. 2.0 sucks.
Huawei Watch 2 Classic 1.5 from 2.0
Hi All! First time posting and visiting the Forum. I previously had a Moto360 1st Gen with AW 1.0, and just got the Hauwei Watch 2 Classic with AW 2.0 pre-installed. AW 2.0 IS GOD-AWFUL! Especially when compared to 1.0. I found a 'downgrade to 1.5' guide on the forum for an LG Watch. My question is this -
Am I able to downgrade my Huawei Watch 2 Classic to AW 1.5? I assume it is the same process as the LG guide, but with different files? Any help would be appreciated as my search so far has come up empty.
I should add that I need some type of step by step guide as I'm a noob to this