Hello,
I started OTA update to android 3.2 on my dads galaxy tab 10.1 3G (original rom and unrooted, it downloaded successfully (89 or so megabytes).
Then it restarted and updated with no problems, but then notice came up that another update is possible (~39 megabyte size).
So I downloaded it and galaxy restarted to install update.
And now it is stuck at 22 percent on logo screen almost for 1 and a half hours...
What do I do?
I believe resetting it manually is far from safe?
so no recommendations?
it's still on
moved to 10.1 sub-forum, don't know how to delete this thred
Related
hi
i upgraded my samsung galaxy note N7000XDLP5 ICS 4.0.3 official into JBroICS 4.0.4. after reboot it still loading very long time and background display 101 101 full screen.
and then i used odin3 with file N7000DXLP9_N7000OLBLP6_N7000DXLP5_HOME.tar.md5 to update on my phone. but also still running. take long time around 2h. so when i force shutdown. i received "Firmware issue".
help me how to start back galaxy note as original ICS 4.0.3.
ANother problem is : when i upgrade galaxy note from 2.3.3 into official ICS 4.0.3. and then i rooted. all function is work fine. but i wounder why WIFI is not detect. when i checked i saw 5MGH and 2.5MGH and auto frequency.
help me how to root with wifi working if after i got ICS 4.0.3 back.
Dear all,
Two days ago I got the notification update through Kies to upgrade my Samsung Galaxy Note to the latest firmware 4.0.3 ICS.
I did but sadly there are some problems with the version I installed on my Note.
It flashes sometimes, the colours of the screen get mixed together, sometimes it switched off by itself, it lags a lot.
So, I want to "re install" the ICS version all over again, I believe it is corrupted or something because when I used to download the firmware the internet was so bad at that time.
Please, how can I re install the firmware. A Fresh Installation.
Thanks.
use this guide : http://forum.xda-developers.com/showthread.php?t=1424997 ...
Hi,
I have following problem with my SGS2 GT-i9100:
as a satisfied omnirom user, I kept my device always up-to-date using the open delta update. But now updating doesn't work anymore, while I can still download and patch the new nightly build. When I reboot and flash it (TWRP 2.7.1.0) it gets stuck at the lock screen. Rebooting ends with getting stuck at the Omnirom-Bootscreen and I need to flash the backup.
It doesn't matter when I flash the device with the latest omnirom, I still can not update (same problem as described...)
currently using 4.4.4-20140825-i9100-NIGHTLY (due to stability, last ~properly working version)
Kernel version
3.0.64-OMNI-g7b7f0fb
[email protected] #1
Mon Aug 25
I'm currently in South Korea, this sgs2 is from Austria. My device's name in play store changed somehow from i9100 to SK Telecom Samsung GT-I9100. Seems weird to me :S is there any link between this and my problem? Just a question....
the thing is here, that I can't use odin to flash, the usb connection is not working anymore and yes, I installed the drivers. Even in Ubuntu I can not access the phone anymore, which used to work fine....
any solutions...?
Many thanks in advance!!
Hello,
I am also using Samsung galaxy S II GTI9100. I had a similar problem on august. For some unknown reason opendalta was displaying no notifications and manual check always resulted in no update being available.
Then I have flashed aug 11 nightly manually and since that all is working. Sometimes if I have a bit of spare time and I am in a good mood for flashing I will let opendelta to do its thing and currently I am running 20141026 without an issue.
Your message is a bit older than the version I am running so most likelly you have already flashed a working build. I will update to the current build in the mean time to see whether the issue might still be happening.
Greetings
Peter
Today my A6+ cellphone pop-uped a new update for your device featuring android pie version
It had 98% battery and i installed it but during the update it stuck at samsung logo
it is taking nearly 2 hours long
what should i do?
did you installed twrp?
i mean, how did you installed pie? via official update?
Dear XDA Community,
since 4 years iam using a Samsung Galaxy Note8 SM-N950F. It works comepletly fine until one day the device suddenly reboots by using it.
At first i wanna mention, that the Hardware didnt got conact with water and at this day and the days before it didnt fall down.
At the first reboots I always got to the home screen and could use it for a few seconds. But after a few reboots its get stucked by the logo.
After 5 hours of rebooting, the device worked like before... but only for one day. The next day its beguns rebooting again...
I try to break the loop and opened the bootmenu. From the bootmenu the device did not reboot but display the following message (Picture-1):
firmware info was not valid
Then i wiped and restartet it. I clicked through the firststart dialog after i reach the home screen and then i joined the reboot loop again.
I tooked my phone to a repair center but they said it will be a mainboard defect which i cant belive cause it dont reboot from the boot menu and from the android download mode...
The resettet and said they installed a new firmware but the error message didnt changed.
I also followed this guide to do it by my own:
[DVG5] OFFICIAL STOCK FW-update (Odin) thread (13 Aug 2022) GALAXY Note8 SM-N950F/DS
This post was originally made by @henklbr and the OP was handed over to @StevePritchard in November 2019. In this thread, You can share the Mega-Links of new firmware's (OFFICIAL STOCK) for the Galaxy Note8 (so: NO CUSTOM ROM's and/or...
forum.xda-developers.com
Also i saw the same problem for another device and followed these steps but it iam still in the reboot loop.
firmware issue Samsung Galaxy S8 (SM-G950FD)
Hi, I have a serious issue with my Samsung Galaxy S8, 64 GB, dual sim. My phone has stock android, never rooted, never modified in any way. I run it in Australia but got it from overseas. After a system update (sometime in December) my phone rebooted (precisely on 29/12/2019), and after the...
androidforums.com
If this really a hardware defect? Or is there anyway to rescue the phone?