I am trying to use the cm10 updater. it has been running for over an hour. I am trying to update my December 24 update to the January 14 update. It is still running. Could it be that the server is just too busy? Something else? Ideas? Thank you.
Edit 1: It ran for about 3 hours then started over. Still running. Anyone know how to stiop it?
Edit 2:Read on RootzWiki that CM Updater did not work with TWRP. It only works with CWM. So I forced closed it. Will update with a dirty flash.
Related
Hi, all. I just installed webOS 3.0.4 and now I can no longer get to the Moboot bootloader for booting into CM7. I (perhaps foolishly) did the update via HP's official Update Manager instead of by Preware. Just posting here to give you guys a heads up if anyone else is running Android and is thinking about updating to 3.0.4.
This should be an easy fix, I'm going to just try and reinstall Moboot via novacom. I'm guessing Android is still there, but the HP update just changed the boot back to stock.
EDIT: Yup, reinstalling Moboot fixed the problem.
Similar issue
I have a similar issue, once I updated to 3.04, reinstalled moboot and CM7 now it just hangs at the CM7 loading screen and does nothing. I've downloaded all teh files 4 times, reinstalled after wiping everything clean, still not working.
Don't know if this will help resolve why. I just loaded moboot and cm7 on my 3.0.4 touchpad and it works great. Maybe you need to recover the webos original form, update tp 3.0.4, them do the dual boot. Dunno
edit oops, just saw the first post edit. LOL
You should always CMW backup before doing any updates.
3 0 4 Update Breaks Moboot
You need to run it after the first update, i think the update that breaks it is called librsvg or something similar. I had it aswell on a new install of Sabayon 7 gnome, but running the command mentioned above fixed it straight away.
Got a notification this morning that there was a new update available for KitKat. I do not know what the update is as I postponed it. I am currently running KitKat 4.4.2 Kernel version 3.4.0. The build is D80020c. I am rooted. I have no other information except that it shows that an update is pending but it will not tell me what the update is and I do not know where to find out what it is.
Anyone have any ideas as to what this is? I am concerned because the last time an update rolled out, it soft bricked my rooted phone.
I spoke with tech support at AT&T and they claim that they do not know what it is and suggested that I call LG for an answer.....
NevetsDrassel said:
Got a notification this morning that there was a new update available for KitKat. I do not know what the update is as I postponed it. I am currently running KitKat 4.4.2 Kernel version 3.4.0. The build is D80020c. I am rooted. I have no other information except that it shows that an update is pending but it will not tell me what the update is and I do not know where to find out what it is.
Anyone have any ideas as to what this is? I am concerned because the last time an update rolled out, it soft bricked my rooted phone.
I spoke with tech support at AT&T and they claim that they do not know what it is and suggested that I call LG for an answer.....
Click to expand...
Click to collapse
Don't install it, it jacked up my phone. I was running the rooted mixed partition D80020c and I can't boot or get into download mode now. All I get it a constant reboot back to recovery. Cannot install another ROM, cannot restore a backup. My daughter was playing with my phone and pushed to continue with the install and now I'm trying to unscrew it.
Jank4AU said:
Don't install it, it jacked up my phone. I was running the rooted mixed partition D80020c and I can't boot or get into download mode now. All I get it a constant reboot back to recovery. Cannot install another ROM, cannot restore a backup. My daughter was playing with my phone and pushed to continue with the install and now I'm trying to unscrew it.
Click to expand...
Click to collapse
Is there any way to force a not install or deny it? The only option I have is to postpone the install and after 4 hours, it will run again and continue to run every 4 hours unless I find a way to break the cycle. How do I force a no install option?
That is what happened to me last time with the "q" update. I postponed the install (no option to not take it) and it installed itself after 4 hours when I left my phone on one night. I woke up to a bricked phone.....
NevetsDrassel said:
Is there any way to force a not install or deny it? The only option I have is to postpone the install and after 4 hours, it will run again and continue to run every 4 hours unless I find a way to break the cycle. How do I force a no install option?
That is what happened to me last time with the "q" update. I postponed the install (no option to not take it) and it installed itself after 4 hours when I left my phone on one night. I woke up to a bricked phone.....
Click to expand...
Click to collapse
I don't know how to permanently disable the update, but I'm sure there's a way. As info, I was able to easily fix my phone with the help of this thread posted by @thecubed: http://forum.xda-developers.com/showthread.php?t=2451696. I didn't read it all, but this might be what disables the update.
I'm not rooted. I took the latest update and all is fine. It's google+ fixes and Google wallet support. It actually let me set up tap & pay! I'll have to go somewhere to try it out.
Sent from my LG-D800 using Tapatalk
I got the notification too but figured that it would probably screw things up since I'm rooted and running TWRP so I did a little searching and came across this, http://forum.xda-developers.com/showpost.php?p=50454408&postcount=3 . It's been a few hours since I changed the setting and haven't seen the update notification again although AT&T pushed the update into CACHE/FOTA sometime this morning.
Well scratch that, the notification just came back. I'll try freezing it now.
Well if rooted just use TB to freeze software update. I am also running a mixed partition D80020c. I am on Straight Talk AT&T. Before rooting I tried taking the official OTA of KitKat but for some reason you can't enter an APN type so I couldn't get or send MMS. So I flashed back to the D firmware,rooted,added custom recovery,entered the APN type and then flashed the modified C firmware. You could also use Root Freezer instead of Titanium Backup to freeze
I installed the original file using TWRP the day it came out. Now the phone wants to OTA update everyday. It's driving me nuts. How can I fix this? I've already rooted the phone and installed FK kernel which I'm sure isn't helping. Any reply would be greatly appreciated. THANKS!
Exactly which update did you install? There were two, the major YNG1TAS0YL and the incremental YNG1TAS17L. So if you only installed the first one you still have the incremental to go.
XDA Moderator
Transmitted via Bacon
As timmaaa said, your probably getting the incremental update that was released a couple of days after CM12 was released. I also get that update constantly.
(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2
Hello everyone!
I just download the last update via update in the phone and normally it boots me into TWRP then I search install it and thats it. The thing is that this last update unfortunately when the logo is installing in the middle throw me an error E1001 Error 1 and semi brick my phone, when I choose restart it literally throws me back to Fastboot.
Did anyone encounter the same fate? Or maybe my update file got corrupted?
Any ideas how can I fix this and have the last update installed for this ROM?
Thank you!
SebixWolf said:
Hello everyone!
I just download the last update via update in the phone and normally it boots me into TWRP then I search install it and thats it. The thing is that this last update unfortunately when the logo is installing in the middle throw me an error E1001 Error 1 and semi brick my phone, when I choose restart it literally throws me back to Fastboot.
Did anyone encounter the same fate? Or maybe my update file got corrupted?
Any ideas how can I fix this and have the last update installed for this ROM?
Thank you!
Click to expand...
Click to collapse
Try August 1st update. Dev quickly fixed it probably after 31st July build.
Where can I download that? on the webpage the last build with GAPPS is the 31st
Thanks for the reply
I just redownload the update for the 31st with GAPPS and now booted like a charm.
I believe my OTA Updater file got corrupted or something like that.
SebixWolf said:
I just redownload the update for the 31st with GAPPS and now booted like a charm.
I believe my OTA Updater file got corrupted or something like that.
Click to expand...
Click to collapse
Nice to hear that. Sometime, updating directly from phone turn out disaster (4 from 5 in my case). Thus I prefer to download the build in the PC then do the update manually. Please note that it may caused by my network stability also.