Hey,
I just bought the Moto G, and tried triggering the OTA update almost directly. The first time it said it will download the update & install afterwards. I haven't seen any notifications since, and if I try to trigger it again it says it is already downloading the update.. Has been like that all day.
I have restarted the phone, killed the update processes, restarted wifi, etc etc.. When wifi is out, it mentions it will continue downloading the update when wifi is back on, and that message indicates the download is still at 0%..
Any thoughts?
Thanks!!
Sven_Vl said:
Hey,
I just bought the Moto G, and tried triggering the OTA update almost directly. The first time it said it will download the update & install afterwards. I haven't seen any notifications since, and if I try to trigger it again it says it is already downloading the update.. Has been like that all day.
I have restarted the phone, killed the update processes, restarted wifi, etc etc.. When wifi is out, it mentions it will continue downloading the update when wifi is back on, and that message indicates the download is still at 0%..
Any thoughts?
Thanks!!
Click to expand...
Click to collapse
I have the same problem, it's been saying that it's already downloading the update for a few hours now.
I've tried soft and hard resetting the phone but the same results.
flashsam said:
I have the same problem, it's been saying that it's already downloading the update for a few hours now.
I've tried soft and hard resetting the phone but the same results.
Click to expand...
Click to collapse
could it be an issue at server-side then?
Got a moto g today, with the same problem, if i turn off and on the wifi it shows a notification to turn on the wifi and the bar stays at 0%, probably a server side problem.
If i reboot the phone then the 0% notification disappears.
Seeing as we're all having the same problem i guess you're right, it's probably server problems and we'll just have to be patient.
Hopefully when i wake up tomorrow it will have downloaded!
Sent from my XT890 using Tapatalk
damn, tried installing the motorola manager for windows & plugged in my droid, no luck either.. it also says it's already installing an update.
we have to be patient then..
Sorry i forgot to mention that I'd tried that as well and it hasn't worked!
Sent from my XT890 using Tapatalk
I have the same problem with OTA update, but before couple of days i put manually kit-kat update for German device (i didnt sure if my device is German Moto G, i bought it from amazon.de). I just put Kitkat file on my root folder, then i went to check for updates and then phone automatically installed Kitkat (no-rooting or something like that) and after that my phone offer me a update to kit-kat even i have a kit-kat, but i think is because i place it manually. Now it said that update is downloading and i will be notified, update is downloading more than 5 hours and still nothing.
Do anyone know why this is a problem???
Sorry for my English!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mine magically said 'update ready to install' when I woke up..!
Me too!
Sent from my XT890 using Tapatalk
This also solved itself overnight for me.
Gesendet von meinem XT1032 mit Tapatalk
Yes mine is updating right now
Related
I gave my HTC One S to my dad after getting an S4 for my birthday. I had a rooted Stock OS on it (updated to 4.3 i think it was, and he requested I flashed Cyanogenmod 10 for him. He's been enjoying it, but today he decided to revert to the stock OS which is absolutely fine, but he decided he would do it himself. He wiped everything through recovery (including the SD card which got rid of all backups I had) and he couldn't get it working so he gave it back to me to fix. I decided "no problem i'll run an RUU and see how that works" but I can only find an older RUU which used to work for when i messed it up when I owned it, it couldn't run because it was an older version im guessing. So I found one for my latest version I have (RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe) and I get this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://i.imgur.com/K2DHEoS.png
Any help on fixing the error? I ran fastboot oem relock and so its locked.
kr00k3d said:
I gave my HTC One S to my dad after getting an S4 for my birthday. I had a rooted Stock OS on it (updated to 4.3 i think it was, and he requested I flashed Cyanogenmod 10 for him. He's been enjoying it, but today he decided to revert to the stock OS which is absolutely fine, but he decided he would do it himself. He wiped everything through recovery (including the SD card which got rid of all backups I had) and he couldn't get it working so he gave it back to me to fix. I decided "no problem i'll run an RUU and see how that works" but I can only find an older RUU which used to work for when i messed it up when I owned it, it couldn't run because it was an older version im guessing. So I found one for my latest version I have (RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe) and I get this error:
http://i.imgur.com/K2DHEoS.png
Any help on fixing the error? I ran fastboot oem relock and so its locked.
Click to expand...
Click to collapse
Sounds like a corrupt download to me, try to download again.
http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
I believe once you have run this, go to settings and do update check, install the small update to improve battery performance (and wifi I think).
Thank you so much but no, unfortunately its the same deal.
You'll need to flash stock recovery (you can find it over at Modaco) and relock your phone before running an RUU file.
Link
I installed the OTA update for the Android Paranoid ROM. When checking for updates, it mentioned something about not being able to check GApps update or something like that. I then downloaded the update and installed it through the OTA app. The phone rebooted and went into recovery mode, installed, and then shut down, it did not reboot. Now when I try to boot it, all I get is the Samsung letters, and then the phone shuts down again. I installed this rom on July 5th, and had installed an OTA update about a week ago.
What did I do wrong? What do I need to do to get it to boot and work again?
Any help is appreciated. Thanks!
tataocb said:
I installed the OTA update for the Android Paranoid ROM. When checking for updates, it mentioned something about not being able to check GApps update or something like that. I then downloaded the update and installed it through the OTA app. The phone rebooted and went into recovery mode, installed, and then shut down, it did not reboot. Now when I try to boot it, all I get is the Samsung letters, and then the phone shuts down again. I installed this rom on July 5th, and had installed an OTA update about a week ago.
What did I do wrong? What do I need to do to get it to boot and work again?
Any help is appreciated. Thanks!
Click to expand...
Click to collapse
You're going to have to factory reset it. Something broke in this update, as far as I can tell. The July 8th one is the one you should stay on until somebody from PA takes a look at why it's happening on the Skyrocket. Post about this in the Paranoid Android thread in the Android Development
forum for the device. I'm trying to throw together a bug report, but that'll take a couple hours until I get back to a computer.
crayonhead said:
You're going to have to factory reset it. Something broke in this update, as far as I can tell. The July 8th one is the one you should stay on until somebody from PA takes a look at why it's happening on the Skyrocket. Post about this in the Paranoid Android thread in the Android Development
forum for the device. I'm trying to throw together a bug report, but that'll take a couple hours until I get back to a computer.
Click to expand...
Click to collapse
Thanks for the help...I ended up doing the factory reset and installing the first rom I used back on July 5th along with the gapps from back then. Then I installed the July 8th update and haven't installed the latest update. I'm going to stay with this version for now.
tataocb said:
Thanks for the help...I ended up doing the factory reset and installing the first rom I used back on July 5th along with the gapps from back then. Then I installed the July 8th update and haven't installed the latest update. I'm going to stay with this version for now.
Click to expand...
Click to collapse
Hey! So update on this matter. There's been a new OTA update pushed out (pa_skyrocket-4.44-20140722.zip). That update works over OTA, so feel free to update to that version of Paranoid Android. Checked and running
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So i waited 4 days for the OTA and still nothing. so I've decided to go ahead and flash manually.
First i tried flashing using TWRP and things went great but as soon as phone reboots there was no signal and few seconds later signal came up and changed to H+ then 3G and went blank and kept going on a loop.
decided something wrong with the flash i did a factory reset. still crashing. so i did a fresh install still crashing.
I was helpless so i restored the Backup of my old XNPH5Q. everything great. back to LTE again. then i thought might be a lolipop issue so i flashed Oxygen os. everything works fine with LTE signal and all. Attached a 44s video on what's going on when CM12s installed. you can see signal icon crash change signal and go on a loop
Please help me fix this.
Same thing is happening to me, and I cannot connect to LTE.
It works for me http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
Fittip4ldi said:
It works for me http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
Click to expand...
Click to collapse
This did not work for me. Still no LTE and signal keeps crashing
jbass350z said:
This did not work for me. Still no LTE and signal keeps crashing
Click to expand...
Click to collapse
For some reason this method worked for me. this is what i did.
So after going between roms i decided to settle and restored my Kitkat XNPH44S backup and then upgraded to XNPH05Q when prompted. and then i flashed the XNPH05Q Modem. then i flashed the lolipop YNG1TAS0YL rom by booting in to recovery.
let the phone idle for few minutes after reboots from recovery. it took about 2-3 minutes to establish the signal but everything went smooth. earlier today i clean installed the new YNG1TAS17L OTA. so far i haven't had any problem.
Hope this helps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I've found luck being on Lollipop and flashing over CM11 05Q modem.
Currently, I'm on the daily Nocturnal build 5.1.1 or CM12.2 and this modem had fixed my problems and works with latest ROMs still.
Make a nandroid just to be incase.
CM11 05Q modem :
I have a Galaxy SM-G920A S6 fully stock that was on 5.0.2. I recently got a update OTA for it to 5.1.1. Of course this update failed to load for some reason. I then downloaded the stock update 5.1.1 unmodified firmware and flashed it via Odin. Worked perfect. Then I tried using it for my fingerprint and this error came up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried rebooting of course. I tried resetting through recovery and wiping cache but it the error still pops up when I use anything related to the fingerprint reader.
Methods that I tried to use to Fix:
I read on a past thread, that if you disable the fingerprint service in application manager and then reboot and then enable, it fixes the issue. I tried that and it was the same thing. I've been reading a few Xda threads and it seems like there is no real fix for this.
This is the name of the file I installed: G920AUCU3BOI2_CL5527015_QB6363222_REV02_user_low_ship
I'm not aware if a newer version popped up, then I guess I could flash that and update.
Thanks in advance.
KillTheSprint said:
I have a Galaxy SM-G920A S6 fully stock that was on 5.0.2. I recently got a update OTA for it to 5.1.1. Of course this update failed to load for some reason. I then downloaded the stock update 5.1.1 unmodified firmware and flashed it via Odin. Worked perfect. Then I tried using it for my fingerprint and this error came up.
I've tried rebooting of course. I tried resetting through recovery and wiping cache but it the error still pops up when I use anything related to the fingerprint reader.
Methods that I tried to use to Fix:
I read on a past thread, that if you disable the fingerprint service in application manager and then reboot and then enable, it fixes the issue. I tried that and it was the same thing. I've been reading a few Xda threads and it seems like there is no real fix for this.
This is the name of the file I installed: G920AUCU3BOI2_CL5527015_QB6363222_REV02_user_low_ship
I'm not aware if a newer version popped up, then I guess I could flash that and update.
Thanks in advance.
Click to expand...
Click to collapse
Flash proper bootloader. Simple as that.
Rakcoon said:
Flash proper bootloader. Simple as that.
Click to expand...
Click to collapse
Sorry I'm really a noob at this. Proper bootloader? What do you mean by that? I'm trying to keep it stock.
Is the firmware I flashed wrong?
what's your model? Country?
Rakcoon said:
what's your model? Country?
Click to expand...
Click to collapse
It is model SM-G920A
Full length name is SM-G920AZDEATT
I'm in the united States.
Rakcoon said:
what's your model? Country?
Click to expand...
Click to collapse
I flashed only the AP file in Odin when I updated. Should I have updated the other files as well?
I fixed it by not being an idiot, and flashing all the files in update.
D:
Hahaha good!
can you tell me how to fix it? where did you download the file? what are you using for the installing? pleasee i want to know i have the samew problem
I have tried goddamn near everything and lurked everywhere.
This is just me trying to fix a huge mistake. I got this phone yesterday, everything was fine. I just wanted to install a custom recovery so I could back up the phone.
I flashed TWRP with Odin, I may have done it wrong or something... But I'm pretty sure I followed some directions. Odin did it in a snap, my device rebooted into TWRP... but then, I just barely noticed the "No OS installed!" message.
I have attempted, in no particular order:
- Using Kies 3 to initialize my device. It will download to 100% and then stick on 0% going to install the OS. Tells me the device is not supported.
- I then tried SmartSwitch because someone told me that's what you need for Android 4.3+. Same exact thing.
- Tried flashing my stock firmware, both 6.0.1 that it came with and the 7.0 that was available before it was bricked, with Odin 13.2 (I also tried others)
What's interesting here is when I add in the AP, BL, CP and HOME_CSC and press start, I get Odin's log to fail just after cm.bin - every time.
Here is a screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
At that point, I am no longer able to re-attempt until I restart and re-enter DL mode, and a black-backgrounded red text appears on the Download Mode screen, that says:
SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1
My device is the Canadian version, in the XAC region.
I have downloaded and attempted flashing firmwares G930W8VLU2BQB6_G930W8OYA2BQB6_XAC and G930W8VLU1APG1_G930W8OYA1APG1_XAC.
Both give the exact same errors and so I don't think the firmwares I got are the issue. I just have no idea what it could be, since the only problem with my phone is there's no OS installed.
Actually, I do have a problem with TWRP, as well.
TWRP is unable to do much. It cannot mount /data (among others), and those folders are all still there as I can adb push files to the device, and I attempted pushing the actual firmware to the /data folder and I could see the progress by pressing Install in TWRP and then looking in the /data folder... but that was the only file that told me "No space left on device" once it 100% completed, when there's obviously ~30GB.
The first error TWRP gives is that it cannot find the crypto footer.
Am I screwed here? Is this a harder softbrick? What am I missing? Please reply quickly, working by tomorrow would be very ideal.
Thanks in advance!
The last time I tried to flash stock - I got errors in Odin. Disconnected phone, restarted download mode and tried again. Don't know why but it took four tries before flashing complete - good luck
Sent from my SM-G930W8 using Tapatalk
bill_in_mtl said:
The last time I tried to flash stock - I got errors in Odin. Disconnected phone, restarted download mode and tried again. Don't know why but it took four tries before flashing complete - good luck
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
I tried many more than four times. Should I be using CSC rather than HOME_CSC, just to wipe everything and maybe that'll work?
You say you got 'errors' in Odin, but it's always different for a different cause. You didn't get an error before cm.bin, did you?
EDIT: Attempting CSC rather than HOME_CSC for both v7 and v6 firmwares.
UPDATE: Ugh... I guess it's not the same every time. Using CSC with the Marshmallow md5s, I got Odin to err earlier this time, before even getting to cm.bin!:
UPDATE2: I have just tried flashing Nougat with Odin, using CSC instead of HOME_CSC, and IT'S WORKING??? WTF. Got past recovery, now going through system... Perhaps I posted too soon? Sorry for wasting anyone's time. I will update this thread if it doesn't work.
I'd say this thread isn't worth deletion because I think somebody could come by, take this information and help themselves with it.
I had similar issue - error would be different with every attempt until finally it just flashed and passed. Glad you got it working .
sent from SGH-1337M using Tapatalk
Yeah, that's the thing though... With this one, I got the same error no matter how many times I tried one specific way.
I suppose just never attempted the 7.0 firmware with CSC instead of HOME_CSC. Thanks anyway