I have, apparently, one of those sw3's that will not accept the MM OTA so that the watch will work after is successfully installs. I am having to reinstall the LCA43 ROM in order to get the watch to work. While I would like to have MM, I can't seem to find the right ROM to install and XC is no help in either the software repair or update. The issue is when MM is on the watch, it continually stops at the 4 dots or symbols and never goes any further. I am using Ubuntu to connect to the watch for repair.
Is there a way to stop the OTA updates while still being connected to the phone via BT? I was happy to get this watch going again, but was disappointed this morning when it tried to boot in MM without me installing it.
Edit: This may be resolved. I installed a different ROM yesterday, 5.1.1.2, and it did not automatically try to upgrade last night so I may be good to go.
Related
Hi All,
Last week I received a system update for my Nexus 7 for Lollipop. At that time I didn't want to update so I dismissed the notification. The problem is that I can't get it to re-appear. I've already tried to check for updates 100 times over a couple of days. I've also cleared the Google Play Services and then check for updates, but didn't work.
Is there a simple way to get the update notification again?
Thank you for your help!
Yes, wait for the OTA to become available again. There's a possibility that the latest OTA (5.0.1) was pulled and is no longer available. If you really want the update, download the firmware from Google and flash it manually.
Edit: someone got the notification today. So who knows why you haven't received the notification.
I thought one you dismiss the notification and don't take the update you go back to the end of the queue - so it could be weeks before you get it again.
Happened to me as well. Got the notification last week for 5.0.1, didn't update but didn't dismiss it either. After a couple of days it just disappeared and so far hasn't shown again.
I'm still waiting on 5.0 here. Getting annoyed and was looking for sideload update options but if other people are still waiting on it I guess I'll hold off a bit longer.
If you're now running a modified stock rom, you will most likely have issues updating with the OTA. Here's a way to update without having problems or waiting for the OTA with no loss of data: Download the rooted rom from Scrosler found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , use Wugfresh's NRT 1.9.9 to update the bootloader that's also mentioned in Scrosler's thread, and then dirty flash (no wipes) the 5.0.1 rom with TWRP.
Phibernaut said:
I'm still waiting on 5.0 here. Getting annoyed and was looking for sideload update options but if other people are still waiting on it I guess I'll hold off a bit longer.
Click to expand...
Click to collapse
Stop waiting and do it manually. Why is everyone so consumed with sideloading? You can flash the latest firmware in fastboot without losing anything.
When I lost my update (long story) it took 3 days to come back. A little less than I was expecting but still a little more than I wanted. I'd expect you'll get it back in 2-3 days.
Same here! But will download it now instead. Tierd of waaiting
Hello everyone
I have a lenovo vibe p1a42
When i bought this phone i was initially able to update without any problem til build no. S147_151288_ROW. But after that when i received notification of new update available, i downloaded it bt I cannot update it. I tried it several time. Every time it jist takes me to recovery mode, starts updating then at 24% it fails. I tried updating manually. I also tried using Lenovo Smart Assistant. But all of them give same result.
I am unable to uodate any furture. Can u tell me what should i do? I hear that this phone has now MM update too, bt i'm stuck.
Also, my phone has stopped vibrating. No vibration on anything. The vibration does works sometimes, bt again stops working in few min. I dont know whether this is software related or h/w prob. I will take it to service center if the problem doesnt solve on updating the os.
niranjand147 said:
Hello everyone
I have a lenovo vibe p1a42
When i bought this phone i was initially able to update without any problem til build no. S147_151288_ROW. But after that when i received notification of new update available, i downloaded it bt I cannot update it. I tried it several time. Every time it jist takes me to recovery mode, starts updating then at 24% it fails. I tried updating manually. I also tried using Lenovo Smart Assistant. But all of them give same result.
I am unable to uodate any furture. Can u tell me what should i do? I hear that this phone has now MM update too, bt i'm stuck.
Also, my phone has stopped vibrating. No vibration on anything. The vibration does works sometimes, bt again stops working in few min. I dont know whether this is software related or h/w prob. I will take it to service center if the problem doesnt solve on updating the os.
Click to expand...
Click to collapse
Hello,
Try upgrading your phone via QPST and not OTA
Good luck
dreigosh said:
Hello,
Try upgrading your phone via QPST and not OTA
Good luck
Click to expand...
Click to collapse
I wanted to try tht but i cannot find a link for s152 version file. I tried contacting lenovo through their official forum, they said bring it to service center. I think i ll just do that only. Since i anyway had to go there for my vibration problem.
BTW Thank you for reply.
Sent from my Lenovo P1a42 using XDA-Developers mobile app
niranjand147 said:
Hello everyone
I have a lenovo vibe p1a42
When i bought this phone i was initially able to update without any problem til build no. S147_151288_ROW. But after that when i received notification of new update available, i downloaded it bt I cannot update it. I tried it several time. Every time it jist takes me to recovery mode, starts updating then at 24% it fails. I tried updating manually. I also tried using Lenovo Smart Assistant. But all of them give same result.
I am unable to uodate any furture. Can u tell me what should i do? I hear that this phone has now MM update too, bt i'm stuck.
Also, my phone has stopped vibrating. No vibration on anything. The vibration does works sometimes, bt again stops working in few min. I dont know whether this is software related or h/w prob. I will take it to service center if the problem doesnt solve on updating the os.
Click to expand...
Click to collapse
I understand your pain.... lenovo OTA updates are very finicky. If you want marshmallow you can straightaway flash that ROM (the latest one is S285).
But please make sure to backup your data since this will definitely wipe all your data (same as factory reset). There is thread in on this forum which gives a fairly easy steps on flashing ROMs folr Vibe P1.
If you want to root your android 6.0 though, thats a different story.
Still have a look here - http://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650
You can flash ROM fairly easily from flashing steps mentioned in above thread. If you feel rooting steps are complex, you can still stay on unrooted rom, at least it will be the latest one.
As i've wrote in another Thread (Bootloop at M1D64T), my SWR50 has this behaviour since this Update.
So, i've manually rolled back to Lollipop - discribed in the Thread " How to Fix SWR50 with working Fastboot".
Now, everytime the Watch comes at the Point to Update from Lollipop to Marshmallow, it's endet in the Bootloop with the four Dots...all Updates to higher Lollipop-Versions works like a charm...
Another strange observation i've made when i tried to change to the chinese Fitware....all went fine, but i don't like these Software and rolled back to AW. The Fitware put my Watch back to LDZ22D.
The Watch seddle up, all was fine and after a while the Watch want performe an Update. At the the end from the Update, the Watch booting, but it don't show the circling Clock, no, the four Dots come up, but only for two seconds, then the Watch stays in Recovery...no warning about a failed Update...After i've booting manually from Recovery to System, all runs good and the Watch was on LDZ22D.
So at this point, it can't be the Update to LCA43 by OTA, the Watch says im at the actually system...
Now i will try an manually update to LCA43 and ignore the Update Message to MM....
I'll hope, Sony release an Update to correct this Issue...
Cliff notes: rooted/unlocked xl on stock 8.1 ota. that I sideloaded. Phone installed 9 ota, requested restart, now im on 9. I honestly do not remember accepting update.
How can this happen? and will there be issues?
More Details:
So an odd thing happened to today. My phone, a rooted/unlocked running stock rom, got a notification for an update to 9. I have had my phone since 1/17, and I have been rooted unlocked since day one. This is the first time I have received a update notification. I ignored it figuring ill just get the ota and sideload it like i have done previously. Later today my battery was low and I get a message stating the update install is paused due to low battery. Once it charged enough it told me to restart phone which i did, then quickly realized it may have been a bad idea. Phone booted, told me i had an unlocked phone blah blah, then I noticed my custom loading screen was replaced by the standard google screen. 30 seconds later android 9 boots up. everything works fine, lost root though.
specd_out said:
Cliff notes: rooted/unlocked xl on stock 8.1 ota. that I sideloaded. Phone installed 9 ota, requested restart, now im on 9. I honestly do not remember accepting update.
How can this happen? and will there be issues?
More Details:
So an odd thing happened to today. My phone, a rooted/unlocked running stock rom, got a notification for an update to 9. I have had my phone since 1/17, and I have been rooted unlocked since day one. This is the first time I have received a update notification. I ignored it figuring ill just get the ota and sideload it like i have done previously. Later today my battery was low and I get a message stating the update install is paused due to low battery. Once it charged enough it told me to restart phone which i did, then quickly realized it may have been a bad idea. Phone booted, told me i had an unlocked phone blah blah, then I noticed my custom loading screen was replaced by the standard google screen. 30 seconds later android 9 boots up. everything works fine, lost root though.
Click to expand...
Click to collapse
my phone is still on 8.1 and a check say's up to date, I have downloaded 9. ppr ota , would like to know before i side load, have you got root back ? I use magisk .
I have not attempted to get root back.
Did you have TWRP? Honestly, I'm in a situation where I'd like that to happen. Unfortunately I don't have access to my PC and would like to take the final OTA to Pie, but I'm rooted with Magisk, and.have TWRP installed, I'm worried about a bootloop.
I'm just trying to figure out if there is a way to force my phone to get the OTA update the normal way. My Pixel picked it up as soon as I manually checked for an OTA Update. My daily driver Pixel XL has been saying that I am up to date for the past 22 - 23 hours since the update went live, so I'm still stuck on 8.1.0. Does Google drip feed the update out in blocks based on IMEI to limit the impact on the download server?
Hi team
I recently purchased an ex Demo HTC One M9 as a cheap replacement to my broken Galaxy S7 Edge, as soon as I received it I decided to flash TWRP and a new ROM on it. I was able to unlock the bootloader via HTCDEV.com easily enough and I was able to flash TWRP onto it without issue but when it came to the ROM's I ran into many problems.
Any version of Android that is Nougat or lower would not boot, the phone would go straight to the white bootloader screen every time. Oreo and Pie ROMs were able to boot but I ran into separate issues with them, I could not make or receive phone calls as the whole phone would freeze and there was no audio in from the speaker. I was also unable to play any videos in Facebook, YouTube, Snapchat etc.
I tried every single ROM available here on XDA and ran into these issues. I stupidly also did not make a TWRP backup of my system so it was quite hard to revert back to what it came from factory, I managed to get a stock Marshmellow running thanks to a User here posting a TWRP backup so thanks.
Is anyone able to help me with upgrading to Nougat? I would really like to get the Viper ROM working if possible, is it a known issue getting stuck in the bootloader menu every time?
I've tried just updating through the OTA process in the menu but it says there is no update file available.
Cheers