Hi all,
I tried to update my (rooted) SWR50 to the latest release after it sat unused for some weeks, during the update process it fell over so I thought I'd roll back and start again. Since I rolled back to LWX48P, I can't update beyond this; the watch tried to update, fell over and now say there are no more updates available.
I've tried downloading the OTA zip files but stock recovery isn't seen by ADB, fastboot or device manager. I can't sideload or flash via TWRP and quite frankly I'm all out of ideas.
Can anyone help me out?
You have two options. One, download a twrp loadable update, or two, install the adb drivers for the stock recovery. They are the standard Google drivers, but not the pdanet ones.
Oh, before you mess with drivers, did you try to click sideload update on your watch before trying to connect with adb? That is necessary.
Related
Hi,
I just noticed this was ready to download on my phone today. I downloaded and went to install, but the ClockWordMod Recovery doesn't let me install the update saying, "Image Verification Failed". I assume the problem is that the phone is rooted, and searching through the forums I heard this update isn't really anything big, just removing some German apps or something.
Is there anyway I can stop this update from notifying me? Or anyway to install? My phone is rooted but I'm not bothered about keeping it rooted as at the moment, there is nothing I need the phone to be rooted for. So, either way is fine for me.
Thanks!
If you want to unroot it, just flash generic ruu, more info here http://theunlockr.com/2010/06/07/how-to-unroot-the-htc-desire/
Than simply check for updates and update it
Or wait for few hours for rooted version of this rom
Hi!
I have a branded Desire and installed the update via Recovery. I had to disable the verification to do that (Goldcard inside). But all I got was a boot loop and my phone was derooted. I tried much (e.g. delete my data) and after a couple of hours I found the simple solution: Simply install the update again. Then I rooted my phone and restored the NANDROID Backup I made before I started the update because all of my data was gone.
Then I installed the Update again and this time it worked at the first time. All data was still there. I rooted it again and everything is fine. Don't know why my phone got a boot loop after first try but second try was perfect!
My suggestion: copy the zip from the download folder to the SDcard (made to a Goldcard!!!!) root and to the PC. Just if you need it more than once. Then make a Backup in the Bootloader. Then Install the update via Recovery. If anything goes wrong install the update again!
Hi Guys,
so this morning my SW3 told me there was a system update, cool, so i said yes to the update and let it do its thing.
on coming back, the os version was still the same (LDZ22D) which i thought was odd.
I then did a search and found that there was indeed a new version out (LCA43) and thought something sus was afoot.
I got the twrp from this post http://forum.xda-developers.com/smartwatch-3/development/lwx49k-rooting-easy-t3107501 and booted from twrp
i then pushed the rom i downloaded form here http://www.xperiablog.net/2015/08/2...-update-lca43-intros-interactive-watch-faces/ and promptly tried to flash it like i would any custom rom i would normally flash on any of my other android devices.
I got an error, saying it was expecting "test keys" from a LAZ22D device or a LWX49K device, and that I had LRX22G test keys.
I also tried an ADB sideload which also didn't work.
Am i doing something wrong? Has anyone else ever encountered this?
Full disclosure, I also installed supersu a few months ago, but have had many factory resets since then (new roms on the paired fone) which i wouldn't have thought was an issue?
Cheers for any help you can give
That update only works on stock recovery. Go to my rollback thread and install the complete system of 5.0.1. I put links and directions to all the files. Then roll forward.
Thanks for that @lekofraggle, but I found an easier option, install Sony companion software, reflash "latest" firmware (apparently LAZ22D) then sideload the original update zip. Worked just fine. Just to clarify, I never flashed twrp, just hot booted from it, wondering if root did break ota...
Sent from my Nexus 7 WIFI using Tapatalk
Yes, root breaks most otas, but adb sideload usually works. Glad it was simpler than my doomsday thoughts.
Hi there
I have the Sprout 4 phone and it is not rooted. Twice today my phone has downloaded the OTA update and then informs me that it will restart and install the latest security update. On both occasions, the phone restarts and then I end up with a dead android logo with an 'Error' message.
I have also tried to update it from a thread in the forum using stock recovery but this aborts fairly early in the installation process.
Any ideas/solutions?
Thanks in advance
chrome307 said:
Hi there
I have the Sprout 4 phone and it is not rooted. Twice today my phone has downloaded the OTA update and then informs me that it will restart and install the latest security update. On both occasions, the phone restarts and then I end up with a dead android logo with an 'Error' message.
I have also tried to update it from a thread in the forum using stock recovery but this aborts fairly early in the installation process.
Any ideas/solutions?
Thanks in advance
Click to expand...
Click to collapse
Try to clear the data of Google play services then install it again
@ Dsbhai
Thanks for the suggestion, I have tried it and I still encounter the same problem.
Still receiving the updates OTA from the server, but it fails to install each time.
I'm still unable to update my phone with this update and have even done a 'factory reset'. Initially I thought I had bricked the phone as it was stuck in the boot animation loop, however after awhile it did restart.
Is it possible to install the update using ADB or even with a Custom Recovery?
You may be able to update using a custom recovery
And as you have done a factory reset already why not flash the ROM through SP Flash tools and then update accordingly
Hi there
I'm reviving this old thread as I still have been unable to update the security patches from Google ie stuck on trying to install March 2016.
It's really really strange as each time I go online the March update is flagged up to be installed.
Can this be correct? Surely, Google stops the OTA links after a set time?
If anyone could provide me with some basic steps to undertake to get control of my phone back, it would be appreciated.
I'm still on stock 6.01 and have only the stock recovery options available to me.
Thanks for reading this post (again!).
BTW Why are the stock roms for sprout4 & 8 not listed here ??
http://forum.xda-developers.com/canvas-a1/help#romList
I fixed (to a certain degree) a bootlooped watch by installing a stock Lollipop Rom. It does not work though, because watch cannot connect with Android wear and therefore not complete installation. (It does pair up with the phone and says wait a minute) Any suggestions?
baronimus said:
I fixed (to a certain degree) a bootlooped watch by installing a stock Lollipop Rom. It does not work though, because watch cannot connect with Android wear and therefore not complete installation. (It does pair up with the phone and says wait a minute) Any suggestions?
Click to expand...
Click to collapse
Our watches must be brothers as I have had the exact same scenario. I did however get it back going to LP, paired, etc to the smartphone. What I had to do was fastboot format cache, then userdata, then fastboot reboot. I then fastboot flash the .simg file, the recovery.img file and the boot.img file, then fastboot reboot. I then connected to XC which did not work all the way through, but gave me access to be able to use twrp.img (for some reason, twrp would not boot in LP). Then in twrp I adb pushed the LP rom that is signed and after pushed, installed it. Then, I had to leave it alone for the battery drain as it was locked up or something. After it drained, which was evident because it was not warm, I charged it and it is now working again...but only in LP. I cannot get MM installed.
IF you happen to get MM installed and working, please advise your steps.
golfnut22 said:
Our watches must be brothers as I have had the exact same scenario. I did however get it back going to LP, paired, etc to the smartphone. What I had to do was fastboot format cache, then userdata, then fastboot reboot. I then fastboot flash the .simg file, the recovery.img file and the boot.img file, then fastboot reboot. I then connected to XC which did not work all the way through, but gave me access to be able to use twrp.img (for some reason, twrp would not boot in LP). Then in twrp I adb pushed the LP rom that is signed and after pushed, installed it. Then, I had to leave it alone for the battery drain as it was locked up or something. After it drained, which was evident because it was not warm, I charged it and it is now working again...but only in LP. I cannot get MM installed.
IF you happen to get MM installed and working, please advise your steps.
Click to expand...
Click to collapse
Thank you for your reply. I will certainly let you know of any progress. The procedure I followed was somewhat more simple. I flashed the twrp with fastboot, booted twrp up, transferred the downloaded rom image from the pc to the watch and booted the rom from twrp. It then starts up but fails to play with wear.
baronimus said:
Thank you for your reply. I will certainly let you know of any progress. The procedure I followed was somewhat more simple. I flashed the twrp with fastboot, booted twrp up, transferred the downloaded rom image from the pc to the watch and booted the rom from twrp. It then starts up but fails to play with wear.
Click to expand...
Click to collapse
Regarding the pairing with phone, I had to go in the phone settings, application manager, open android wear, and clear the data and cache in order for it to recognize my watch. I had previously had it linked to another phone and had the phone connected to a different watch so I think it was getting confused.
Regarding getting past the 5.0.1 update, I have found this post http://forum.xda-developers.com/smartwatch-3/orig-development/tut-how-to-fix-swr50-fastboot-t3258918 and am currently getting OTA updates as I write. I don't know how far I will get, but so far I have had two updates. I did not flash the updates, only the original rom. Then I went into the watch settings, about, and pressed the software or system update (I've been doing it manually each time).
Edit: It allowed me to update all the way to MM, however I got the 4 dots /symbols again when it was rebooted. Up to that point, which the last update was the LCA43, the watch appeared to be working fine. I did not test it much as I was just trying to get all the updates I could. So, while it did not go all the way thru to MM, I still was very happy that I got up to that update.
golfnut22 said:
Regarding the pairing with phone, I had to go in the phone settings, application manager, open android wear, and clear the data and cache in order for it to recognize my watch. I had previously had it linked to another phone and had the phone connected to a different watch so I think it was getting confused.
Regarding getting past the 5.0.1 update, I have found this post http://forum.xda-developers.com/smartwatch-3/orig-development/tut-how-to-fix-swr50-fastboot-t3258918 and am currently getting OTA updates as I write. I don't know how far I will get, but so far I have had two updates. I did not flash the updates, only the original rom. Then I went into the watch settings, about, and pressed the software or system update (I've been doing it manually each time).
Edit: It allowed me to update all the way to MM, however I got the 4 dots /symbols again when it was rebooted. Up to that point, which the last update was the LCA43, the watch appeared to be working fine. I did not test it much as I was just trying to get all the updates I could. So, while it did not go all the way thru to MM, I still was very happy that I got up to that update.
Click to expand...
Click to collapse
I now succeeded in pairing up with the phone. What I did was to flash another Rom which I found in the forum. It's called ROM_SW3_5.1.1.2_LCA43. Now the watch works just fine on Lollipop and updates automaticly. I am going to try and upgrade to MM but I fear its going to get stuck on the infamous four symbols when I do. I am happy though to have the watch up and running again, it was deemed paperweight for a while
Ok stuck again. Still at Lollipop version 5.1.1.2
baronimus said:
I now succeeded in pairing up with the phone. What I did was to flash another Rom which I found in the forum. It's called ROM_SW3_5.1.1.2_LCA43. Now the watch works just fine on Lollipop and updates automaticly. I am going to try and upgrade to MM but I fear its going to get stuck on the infamous four symbols when I do. I am happy though to have the watch up and running again, it was deemed paperweight for a while
Ok stuck again. Still at Lollipop version 5.1.1.2
Click to expand...
Click to collapse
Does yours actually have 5.1.1.2 in the about section? Mine says 5.1.1 with the build as LCA43.
golfnut22 said:
Does yours actually have 5.1.1.2 in the about section? Mine says 5.1.1 with the build as LCA43.
Click to expand...
Click to collapse
Indeed it does. The Rom comes from here: http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
Since the problem occurs only when updating to MM I am led to think that we have a kernel issue?
baronimus said:
Indeed it does. The Rom comes from here: http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
Since the problem occurs only when updating to MM I am led to think that we have a kernel issue?
Click to expand...
Click to collapse
I may have stopped updating one to early. Anyway, my watch updated by itself last night all the way to MM, now it is stuck again. I'll have to search and see if there is a way to stop the automatic OTA updates.
I have seen where people have flashed only the kernel. I have not. At this point, it would be nice just to keep it at the last LP. I'll let you know if I find anything. Thanks.
[HELP][G3][VS985]issue connecting to PC on fastboot, need to reflash TWRP & SuperSU
Hello, thank you for this great forum with helpful members, I'm having an issue with an LG G3 VS985, fastboot won't recognize it while in bootloader, I need to reflash TWRP.
First of all, thank you for reading this long testament [most important details in bold if TL;TR], wanted to be as detailed as possible, maybe it will help you help me better hehe sorry about that.
Let me give you the event sequence if it helps.
> Phone had Cloudy G3 2.5 rooted with SuperSU and TWRP 2.8.6.0 since I rooted it back in 2016.
I was having some issues with phone not recognizing micro sd card and OTG-USB after messing around with encrypting it, I was curious but didn't need it, anyways. Although I dropped the phone in water a couple weeks prior so there is a chance the issue is hardware related.
That was like 4-5 months ago.
Finally decided to do a file backup and reinstall everything yesterday apr-5-2019.
> Rebooted into TWRP and erased everything (data, cache, dalvik, system, even internal storage) because I wanted a new install on everything.
> Flashed the latest official TWRP version for my device (3.0.2.0)
> Had a lot of issues flashing crDroid, found out I downloaded the wrong build, although I had to edit updater-script on the right one to make it work.
> Flashed crDroid 5.2_20190326 with open GApps for Android 9.0 Stock
> First issue encountered, I couldn't charge the phone turned off, because the battery logo appears but but doesn't do the animation and reboots the phone, I read it might be an issue with TWRP.
> Tried to flash SuperSU 2.82 SR5 with TWRP but had a LG secure boot error and couldn't boot up android.
> RE-flashing android and open GApps fixed this issue.
> Re-attempted the process several times, even wiping everything down more than a couple times, including re-flashing android several times to no avail, I was not able to flash SuperSU successfully.
I even flashed an old tool "MR.Bump" but system kept unrooted so unsuccessful.
> Reflashed Android for the last time and start reading again (after 8 hours attempting to do it well), I read that TWRP version might be the problem to flash SuperSU, so
HERE is where I have the current issue:
> Downloaded the official TWRP version 3.1.0 and flashed it.
There is no official support for 3.1.0 for the VS985 so I'm guessing it was a generic .img, of course I messed up TWRP.
> Downloaded and installed official LGMobile Drivers 4.2.0 (latest), downloaded android drivers (15 second ADB installer 1.4.3) and Android platform tools 28.0.2 on windows.
> When conected in PTP and transfer files in win7 it recognizes all the drivers well, was able to reboot the phone into bootloader from android platform tools successfully, means there is good communication between the device and PC.
The issue is once the phone is in the bootloader and trying to flash TWRP, win7 has issues installing CDC serial drivers, in the end in device manager all drivers seems installed but win notification center says there was a problem installing LGE AndroidNet for VZW USB Modem, seems to be issues with CDC Serial or something, when trying to access the properties on the VZW USB Modem it freezes so there's an issue here.
That means when doing adb devices or fastboot devices command, doesn't find anything.
Tried the same in win10, had different driver problems but in the end everything gets installed after rebooting. Same issue, no response from phone when in bootloader.
Message is "Waiting for any device".
Maybe there is an issue with some low-level driver/kernel/firmware that is creating this issue, I would even consider to flash stock LG Android to start from scratch, if you have any guide on how to do it please provide the links!
Additional note: When connecting the phone in USB Tethering win7 gives bluescreen.
> FORTUNATELY I messed TWRP but the phone can still boot android so it's not rendered unusable (yet lol).
I must admit I wasn't super careful downloading some stuff, I did it old school (trial and error) and most of the times it works, I consider myself being a little tech savvy, but right now I'm stuck, I guess I could continue using the phone like this but if I have any issues it would be difficult to resolve and I would lose functionality without root (I could live unrooted though but I wanna resolve this) and honestly I love the G3 so why change it? haha.
BTW I found these on the net, do you recommend it? what TWRP do you recommend for the VS985?
I downloaded and wanted to install this one https://forum.xda-developers.com/lg-g3/development/recovery-unofficial-multirom-twrp-artx-t3657524
and found this one supposedly 3.2.1 for the vs985 here: https://basketbuild.com/devs/yshalsager/TwrpBuilder/lge/vs985
Any help will be greatly appreciated.
Cheers.
I posted it on a different area and got no response, so here it is the G3 area.
@disrupted_mind, wow, that was a great detailed post. Alas, can't think of anything much to suggest at the moment. Just a few things come to mind.
Make sure to use a USB 2.0 port on the computer. I've heard of issues with USB 3.0.
Use a good cable but I assume yours is good or original.
There's another TWRP from @HardStyl3r, v3.2.3. Since he's one of our last ROM devs I'm sure it might be the one to use, especially if you're trying Pie.
https://forum.xda-developers.com/showthread.php?t=3813552
[RECOVERY][3.2.3.0][UNOFFICIAL] TeamWin Recovery Project for LG G3
Let us know if that one works or not.
LG G3 D851, AOSPA-L ROM, Nebula Rev9.3 Kernel, microG (NoGapps), MultiROM, XDA Legacy
marcdw said:
@disrupted_mind, wow, that was a great detailed post. Alas, can't think of anything much to suggest at the moment. Just a few things come to mind.
Make sure to use a USB 2.0 port on the computer. I've heard of issues with USB 3.0.
Use a good cable but I assume yours is good or original.
Click to expand...
Click to collapse
Thank you for replying, now that you mention it, all the ports on the PC's I've tried are USB 3.0, I think I have an older lappy with USB 2.0 and I will try that next. If that doesn't work I was planning on rooting the phone temporarily with kingroot or kingoroot, so I can use flashify and re-flash TWRP (just thought about it last night hehe) and then re-flash the ROM since according to this thread, kingroot and kingoroot might be malware.
marcdw said:
There's another TWRP from @HardStyl3r, v3.2.3. Since he's one of our last ROM devs I'm sure it might be the one to use, especially if you're trying Pie.
https://forum.xda-developers.com/showthread.php?t=3813552
[RECOVERY][3.2.3.0][UNOFFICIAL] TeamWin Recovery Project for LG G3
Let us know if that one works or not.
LG G3 D851, AOSPA-L ROM, Nebula Rev9.3 Kernel, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
Thanks, yes, precisely yesterday I kept reading trying to find a solution and bumped into @HardStyl3r's version, already downloaded it
I like Pie very much by the way, but I think it drains the battery a little faster than CloudyG3 (android 5), maybe the old hardware struggles too much haha, but I will keep using it for some time. By the way, do you think AppOps is still necessary with Android integration to allow/deny permissions (sorry, noobie question since I'm just transitioning from old to newer android with that feature).
Any ideas on the charging the phone off issue?
I will update the thread with any news
Cheers.
I have good news and bad news.
I was able to reflash stock KitKat using TOT method, only way it could work since I had no connection to PC with fastboot commands on cmd.
Updated android over the air and PC, it update to 5.0.1 over the air and wanted to go faster so tried to do it from PC, what a mistake, when I was downloading Marshmallow info on xda I found that it might be difficult to root android 6, so cancelled the operation from LG Update Software on PC. That went "fine", didn't update to Marshmallow.
Rooted the phone using the One-Click root method, worked fine apparently. Installed flashify and flashed the Unofficial 3.2.3 TWRP, that didn't go well, I dont have access to Recovery mode nor Bootloader/Download mode now. "Recovery" ("vol-" + "Power Button") mode gives "certificate/secure boot error", Regular "Bootloader/Download mode" is non-existant or I can't access it in any given way, tried "vol+" while off + "Power Button", tried to reboot to it from Rashr, nope, it just continues to boot android, the other "Download mode ("Vol+" + "Connect USB cable to PC")" (don't know if it's the same as Bootloader) gives "certificate/secure boot error". I even flashed the latest official TWRP for vs985 and 2.8.6 that I knew definately worked before, didn't work.
I was able to boot into fastboot following "this" thread but it doesn't perform commands.
When booting to Android I kept receiving notification that I had a pending update, I managed to wipe /data and /dalvik from adb shell, that resolved that issue.
Attempted to reflash stock KitKat again, but I can't, since phone doesn't have bootloader or recovery no more.
At least I still have working rooted 5.0.1 Lollipop, but have the other issues. I want to attempt to re-flash aboot.img, laf.img and sbl1.img to fix those issues but since its my main phone don't want to hard brick it right now.
Any input is welcome and appreciated, will keep reading a lot, think I might open a different thread for this.
Cheers.