Database Info

[Q] KitKat update OTA freezes

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

Help needed - Stock Firmware reinstallation via KIES caused Boot Loop

Hi guys.
I have a little problem with my tab now . Originally my machine had a little hiccup ever since I upgraded to Lollipop. The problem was that it tried to upgrade apps to Lollipop every time I did a boot cycle. Usually ending with a message that an app called "a...a" closed. I did not bother me much for a while. But Today I thought it was past time I resolved this so I tired to reinstall the firmware with Kies. Bad idea in retrospect, since it caused a boot loop at first (I did not touch it for 1-2 hour) than after seeing that it did not progressed. I tired a forced restart by holding down the power button. Strangely somehow after 2 or 3 tries it did started to do something. Saying that it has to update 190 apps and it did so, after then I found myself at the first setup page. However it did not worked because a lot of warnings come up constantly like: google process stopped, maps stopped, etc... making it unusable to set up anything, since even if you OK the warning the next comes up constantly. Also Kies no longer detects the phone, so I was forced to use Odin to reflash it. But here's the twist: even after reinstalling the same version of the stock image via Odin the continuous boot loop occurs again and again. (The image I got it from samdownloads de). I'm unsure where the problem can be, the only thing I can suspect is that I only used AP with Odin since the rar did not contain any bl cp csc or anything (I also tired full wipe via recovery but it did not help). So if anybody have any idea as to what direction should I take, please say so. I would really appreciate the guidance.
Disclaimer: My machine is completely stock with an untripped Knox, and it was bought from Germany.

quarros said:
Hi guys.
Disclaimer: My machine is completely stock with an untripped Knox, and it was bought from Germany.
Click to expand...
Click to collapse
Try to flash your AP file with Bootloader
http://forum.xda-developers.com/showpost.php?p=62573251&postcount=21

Beut said:
Try to flash your AP file with Bootloader
http://forum.xda-developers.com/showpost.php?p=62573251&postcount=21
Click to expand...
Click to collapse
Thanks for the tip. My problem is that I don't know how different region Bootloader relates to my machine.
The linked one is for the US version of the machine. And I'm unsure whether flashing a different region's
ROM trips the Knox or was there any difference in hardware between units sold to different region
(seems very unlikely but not impossible). My tablet is from Germany with the DBT region firmware.
So is it right to mix the two parts together?

quarros said:
Thanks for the tip. My problem is that I don't know how different region Bootloader relates to my machine.
The linked one is for the US version of the machine. And I'm unsure whether flashing a different region's
ROM trips the Knox or was there any difference in hardware between units sold to different region
(seems very unlikely but not impossible). My tablet is from Germany with the DBT region firmware.
So is it right to mix the two parts together?
Click to expand...
Click to collapse
There is no problem as all region is the same hardware, the one sold in Europe has no different than a tablet sold in US.
For example, software for UK has more languages than US, the rest is the same. I used to load UK or Korean version for the US tablet to fix Bluetooth issue, go back and forth Kitkat and Lollilop without tripping Knox as the firmware is official.
Like this one, I loaded Korean firmware to an US tablet
{
"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"
}

Beut said:
There is no problem as all region is the same hardware, the one sold in Europe has no different than a tablet sold in US.
For example, software for UK has more languages than US, the rest is the same. I used to load UK or Korean version for the US tablet to fix Bluetooth issue, go back and forth Kitkat and Lollilop without tripping Knox as the firmware is official.
Like this one, I loaded Korean firmware to an US tablet
Click to expand...
Click to collapse
Thank you so much for the info I'm sure it will come handy later on (Probably I wont be so nervous to install custom rom next time). :good:
Thankfully it is now solved even without flashing a new bootloader.
For future reference here is what I did:
I used a different freshly installed computer with Windows 7 to flash it.
I also downloaded Odin version 3.10.7 form the forum (I previously used 3.09, also downloaded from here)
I started up the Tab booting to recovery (p + home + volume up). Erased data and wiped cash.
Than immediately rebooted to Odin mode (p + home +volume down) as to not let anything written to the previously wiped partitions.
Than with Odin I reflashed it with the previously downloaded firmware I got from samdownloads de (P900XXU0BOI1_P900DBT0BOH1_HOME)
All seems working properly now. And the initial problem also went away.
Thanks again

quarros said:
Thank you so much for the info I'm sure it will come handy later on (Probably I wont be so nervous to install custom rom next time). :good:
Thankfully it is now solved even without flashing a new bootloader.
For future reference here is what I did:
I used a different freshly installed computer with Windows 7 to flash it.
I also downloaded Odin version 3.10.7 form the forum (I previously used 3.09, also downloaded from here)
I started up the Tab booting to recovery (p + home + volume up). Erased data and wiped cash.
Than immediately rebooted to Odin mode (p + home +volume down) as to not let anything written to the previously wiped partitions.
Than with Odin I reflashed it with the previously downloaded firmware I got from samdownloads de (P900XXU0BOI1_P900DBT0BOH1_HOME)
All seems working properly now. And the initial problem also went away.
Thanks again
Click to expand...
Click to collapse
From my experiences, these things have nothing to do with flashing a firmware:
1- Fresh installed windows, I use XP or Windows 7, there is nothing different as long as you have correct Samsung USB driver.
2- Odin versions have no differences, I use old or new, they are both the same.
3- Home button is not needed to access Download or Recovery Mode
Your problem went away probably from fresh install of the system.

Display broken after root

Hi all
I'm having a strange problem with the display after rooting my Galaxy S7. The screen has stripes, is flickering and having weird colors, see image below. The touch functionality is still working.
As it was happening just after the rooting (using CF-Auto-Root), I'm still having the hope that it is a software issue and can be fixed somehow.
What I did:
- the first thing on the brand new device (unknown firmware) was rooting the device using CF-Auto-Root. This was working well.
- I installed Titanium Backup to get rid of the bloatware. Possibly I've deleted too much, after the reboot the device was hanging on the boot logo (bootloop?)
- I've downloaded latest firmware (G930FXXU1APD1 [DBT]) and installed it via ODIN
- Device was again working and everything was looking fine
- I've tryed to root again using CF-Auto-Root with the same file I did it with the shipped firmware. After one of these restarts during root, the problem started.
Except the weird screen, everything looks good so far. I've also tried to flash G930FXXU1APD1 again, but no change. Even on boot logo, in recovery and download mode, the screen looks like that. possibly something with the display driver?
I hope there is another way to fix it than bringing it back to the shop and hope that they will not refuse the repair because of knox flag (the firmware is shown as official).
{
"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'm aware of the risks that rooting brings, but I have the hope that all modifications or problems can be reverted by flashing something fresh, as long as the recovery is accessible [which is]).
Any help is appreciated.

This looks bad. Hope you can fix it!

I seriously doubt that this was caused by rooting or flashing the firmware. You've got a faulty screen.

This has nothing to do with rooting.
This is clearly a Hardware defect. Root is only a Software modification.
Gesendet von meinem SM-G930F mit Tapatalk

Have seen many people with this faulty screen. This should be a hardware issue. Get it replaced
Sent from my Silver Titanium Galaxy S7 Edge

BigMani said:
Hi all
I'm having a strange problem with the display after rooting my Galaxy S7. The screen has stripes, is flickering and having weird colors, see image below. The touch functionality is still working.
As it was happening just after the rooting (using CF-Auto-Root), I'm still having the hope that it is a software issue and can be fixed somehow.
What I did:
- the first thing on the brand new device (unknown firmware) was rooting the device using CF-Auto-Root. This was working well.
- I installed Titanium Backup to get rid of the bloatware. Possibly I've deleted too much, after the reboot the device was hanging on the boot logo (bootloop?)
- I've downloaded latest firmware (G930FXXU1APD1 [DBT]) and installed it via ODIN
- Device was again working and everything was looking fine
- I've tryed to root again using CF-Auto-Root with the same file I did it with the shipped firmware. After one of these restarts during root, the problem started.
Except the weird screen, everything looks good so far. I've also tried to flash G930FXXU1APD1 again, but no change. Even on boot logo, in recovery and download mode, the screen looks like that. possibly something with the display driver?
I hope there is another way to fix it than bringing it back to the shop and hope that they will not refuse the repair because of knox flag (the firmware is shown as official).
(I'm aware of the risks that rooting brings, but I have the hope that all modifications or problems can be reverted by flashing something fresh, as long as the recovery is accessible [which is]).
Any help is appreciated.
Click to expand...
Click to collapse
I agree with what other said. This has nothing to do with rooting. Somehow the bad display showed off it's real colors coincidentally after you root. Only way is to approach Samsung ASAP for warraty repair. Not sure whether they will check the device is in 'modifed' state (rooted) or in 'official' state for any such serious hardware issues. But you gotta say a lie about when this issue popped up. That's it. If you're lucky you will get the LCD replaced.

Hi all
many thanks for all your feedback. under the condition that we believe it is a hardware issue, I can keep my decision about doing the rooting, on the other side I will never understand why it was happing exactly at that moment.
However it seems that I had extremly luck. Today I went to the shop where I've ordered it online and they informed be about the DOA (Dead-On-Arrival) warranty, which is only possible within 7 days after purchase - today was day 7
they did just replace the device with a brand new one, they even didn't had to send it to Samsung before giving me a replacement. I was walking out with a new device :angel: :angel:
To finish here, I tried now exactly the same process as on saturday: first flashed latest firmware G930FXXU1APD1 and then I applied CF-auto-root. You can't imagine how nervous I was during these few reboots and hoping that the same problem does not reappear again (I could not go a second time to the shop with the same issue...). but this time all went well. latest firmware, rooted and now also debloated a bit.
again thanks to all of you.

Please help me! Freshly softbricked SGS7, SM-G930W8, No OS Installed

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

"No SIM card - 31000" - Galaxy S5 G9000P

Recently I have flashed my S5-G9000P for the first time with the Resurrection OS RR-O-v6.0.0-20180405-klte-Official.
After working alright for the first day or so, texts would not send. Then, at the top of my screen it says "No SIM card - 31000". I don't really know much about modding phones, so here is what I tried so far:
- Resetting the phone
- Removing the SIM card then reinserting, then resetting the phone again
- Resetting my mobile data options
So far these above options haven't helped the problem. I have looked at similar threads to this and none seem to have the same problem based on their descriptions.
Thanks for your time.
Phone - G9000P Galaxy S5
Android Version - 8.1.0
Kernel version (if that's important) - 3.4.113-lineageos-g592be94 (gcc version 4.9.x 20150123 (prerelease) (GCC) ) [email protected] #1 Thu Apr 5 13:41:19 CEST 2018
{
"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 did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.

Well I can State the Facts... has happened here tooooo..... on LineageOS 16 and 15.1. The only fix that I have done, which may help, is Rebooting the Phone.
Yep, tat was the only thing I actually have done, When and IF it happens.
Same thing though, "NO SIM Card" " Corrupt Sim Card" and I Tink there was another one too. All if which, (Knowing that it was running correctly, prior this) I just rebooted. maybe once, maybe like 3-4 times. before it actually goes away.
Now, knowing the phone was running correctly is the Key , I believe. IF your in the process of Flashing, yep, maybe restart that. However, if its running right an all, no reason to do any flashing. why--- Well, was built in the First run batch of them. the phone is rather good and all, cant even see me spending over a $1,000.00 for a new phone, that's Ficking Nutz !!! I am sure, they did built it to last a life time, but what is it, a cell phone built in 2012. Before my warranty was over, I rooted, and got rid of all thre Samsung crap. Ran smooth. Been Flashing ever since.....

E.4.113-LineageOS-g592be94 mobile data not working
Hippie459MN said:
Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.
Click to expand...
Click to collapse
You have in your signature a new rom, does that rom is working ok? The only thing that is driving me nuts is that I can’t have my data usage, I installed RR-O-v6.0.0-20180405-klte-Official on my gsm900M what do you suggest!?
Edited, i found it! just needed to edit the APN settings! i google them for my case that is Mexico, and now i have mobile data!!

Im still running lineageOS. I just havent updated my signature yet. I am going to be getting a new phone in the next week or so though. Pretty sure the motherboard (Internal storage) is taking a dump on me. Phone will work great sometimes for 2 weeks then apps start crashing like mad and only way to fix is to uninstall and reinstall and only way to fix it is to do a full wipe and reinstall the rom. Sometimes it will even start messing up within an hour or two. Things like google play services, the stock dialer, and bluetooth will randomly crash. I have tried just about everything. Different roms, going to stock software, nothing works. And when it tries to do do a backup in TWRP, it always fails in the data partition and always at different points saying it cant read the data partition or some junk. I forgot but I am giving up on it. I have another S5 but wont have it for another week or two.