Stuck at Samsung splash screen. - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Hi,
I recently tried installing the new 4.3 update onto my Samsung Galaxy S3 I747. Also, I never rooted my phone and my carrier is Telus if that matters.
When my phone finished updating, it lead to the lock screen. Just as I was about to enter my pin and unlock it, the phone restarts and gets stuck on the Samsung splash screen. I have tried entering into recovery mode and then wiping the cache and restarting it, but no luck.
I do not wish to restore my phone back to factory settings because I do not want to lose my music and apps. Is there a solution that can fix it without wiping the memory?
Thanks.
edit: i left it charging for a few minutes while it was stuck on the samsung splash screen, and then it went to the lockscreen and restarted it self
... i have to wait five minutes before i can save my edit
editedit: it just went to lockscreen for a second again
editeditedit: its going back to lockscreen quite often and restarting it self

aznpiggy said:
Hi,
I recently tried installing the new 4.3 update onto my Samsung Galaxy S3 I747. Also, I never rooted my phone and my carrier is Telus if that matters.
When my phone finished updating, it lead to the lock screen. Just as I was about to enter my pin and unlock it, the phone restarts and gets stuck on the Samsung splash screen. I have tried entering into recovery mode and then wiping the cache and restarting it, but no luck.
I do not wish to restore my phone back to factory settings because I do not want to lose my music and apps. Is there a solution that can fix it without wiping the memory?
Thanks.
edit: i left it charging for a few minutes while it was stuck on the samsung splash screen, and then it went to the lockscreen and restarted it self
... i have to wait five minutes before i can save my edit
editedit: it just went to lockscreen for a second again
editeditedit: its going back to lockscreen quite often and restarting it self
Click to expand...
Click to collapse
When you got it into recovery did you try to wipe data/factory reset??
But to be honest it sounds like your phone is soft bricked maybe. I'm experiencing the almost same problem with my AT&T sgh-i747. Mine is stuck at the Samsung Galaxy S III screen and doesn't go any further than that at all.
You will most likely have to do that same thing I am doing which is reflashing android 4.3 via odin. It may work for you, I'm pretty sure it'll work for mine. Head over here and read this thread and see if this can help if not let me know and we'll come up with somethin else to help you fix your phone. (If I'm correct following this thread and flashing via odin will not erase and of your data.)
Your only other real option is to install the 4.3 MJ2 leak via heimdall. http://forum.xda-developers.com/show....php?t=2496425
Heimdall will flash odin files. http://glassechidna.com.au/heimdall But odin will not flash heimdall files. It works much like odin flash in download mode so i'm told. I'm trying to figure it out now. I hope this helps.

I was never able to get the above Heimdall installed correctly on my pc. I am still stuck at the black and white galaxy s3 screen. I installed TWRP via odin to try my to run my nandroid i made earlier today and it says successful. But when I go to reboot It says No OS are you sure you want to reboot. I was already on 4.3.3 via the OTA update like you. And now i'm here turn phone on and it's going straight to download mode
Please HELP US BOTH Someone ANYONE

Related

Soft Bricked. Odin Fix Passes But Still Bricked.

After wiping data and factory resetting the phone everything was still working fine. I decided to format the data and system via clockwork mod but after that the phone hangs on the Galaxy S3 logo. I tried flashing a stock rom through Odin and it passed but the phone still hangs at the S3 logo. I haven't sat and waited for half an hour but I'm pretty sure it's still soft bricked. I can still get into recovery and download mode but the phone still wont boot up. I saw something about bootchains in another thread but I couldn't find anything for the T-Mobile variant. Anyone able to help?
Lock this thread. Solved the issue thanks to this thread http://forum.xda-developers.com/showthread.php?t=1897181
Had to download the entire stock image from Samsung's site.

[Q] S3 - Bricked [no recovery, sits at s3 load screen]

Still a bit of noob here - but here's what happened:
I was running clean bean 4.2, then I successfully installed the MK3 baseband w/o any problems. I found that the wifi was broken so I flashed the wifi fix from (http://forum.xda-developers.com/showthread.php?t=2541900).
Once that flashed ok my system tried to reboot and then proceeded to sit at the samsung loading screen. After 10+ mins I hard pulled the battery and was able to get into twrp and tried a restore backup from before any changes today. Once that finished it rebooted and is still sitting at s3 load screen.
Now when I try to get into recovery nothing happens.
Powering of and on remains sitting at the s3 load screen.
Any help would be appreciated.
Update: Ok not all hope is lost - I can get back into recovery, but restore while successful refuses to load past the s3 screen.
I'm a bit at loss now what to do - would factory resetting it do the trick?
Update 2: Tried a factory reset and still nothing - still sits at the s3 load screen.
Ok - I got a rom manually back on the sd card and reflashed a base rom.
Phone boots back into android. :good:
I have learned my lesson.
Yes, lesson is do not flash zips made for stock touchwiz when you are on AOSP, or vice versa.

Issue trying to update to 4.3

(Originally posted this in the wrong forum, so I am reposting here.)
I have the Galaxy Note II with T-Mobile.
Some background: It was running Android 4.1.2. I rooted my phone once, about two weeks ago, just so I could take an image of it in case of an update issue. (I think the software was called nandroid.) Once I took the backup, I unrooted it again.
Since then, doing the Software Update check under settings never returned any results. It would just keep checking until I clicked cancel.
Anyway, when T-Mobile released the 4.3 update Monday morning, I tried updating to it using the Kies software on my PC (by connecting it through the USB cable). It got up to about 60% installation and then just hung for over an hour. So I unplugged the phone, re-plugged it back in, and then attempted the emergency firmware recovery through Kies. It went through this and got upto 76% installation and then just hung again for another hour. I again unplugged it to re-try the emergency recovery again, but every time I connected the phone, Kies would not detect it again. I re-seated the battery, rebooted my computer, uninstalled and reinstalled Kies, but Kies would not detect my phone again.
I am/was running the stock rom, but my phone won't even boot into it's normal screen. Any time I turn it again, i see the screen--"there were errors during firmware upgrade. try emergency recovery in Kies."
I can't even figure out a way to get to a screen where I can install the image I took using Nandroid a few weeks ago.
Any help or advice anyone can provide would be extremely appreciated!
Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..
Double0EK said:
Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..
Click to expand...
Click to collapse
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?
diggeryo said:
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?
Click to expand...
Click to collapse
Try installing SuperSU from Playstore
It has an option of doing a FULL UNROOT
I am sure that will help.
If not then install Rom Manager from PS
Through RomManager reboot in Recovery
1.) Wipe device 3x times
2.) Wipe cache 3x times
3.) Under advance you will Find Dalvik Cache -- wipe that 3x times
[MENTION=522570 [MENTION=1065870 [user=1879310]@@@@[/user][/MENTION]@@[/MENTION]@@
But more importantly why would you want 4.3 stock anyway?
Install TWRP Recovery or ClockWorkMod recovery and install/Flash CM1 (Cyagonemod) or any other custom roms 4.4.x kitkat
Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?
Just do this un root with chain fire root away app.
Then use triangle away app.
Then find 4.1.2 MB1 stock Odin tar. The complete package .
Odin to stock .
Reboot and then update via Ota.
You have to un root first and also have to triangle away which removes flash counter in Odin.
System modified status will not allow Ota.
That's the best suggestion I have
Sent from my SGH-T889 using xda app-developers app
diggeryo said:
Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?
Click to expand...
Click to collapse
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Sent from my SGH-T889 using XDA Premium 4 mobile app
wolfpack612 said:
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Click to expand...
Click to collapse
I have. It brings me to the same screen with the Samsung Galaxy Note II text on the black background and just stays there.
So, in summary, I can get into download mode (vol down+home+power), but it seems nothing else.
Try factory settings the phone through stock recovery and then check your phone status. It should say 'normal' but if it says 'modified,' download Triangle away and run the tracking setting (it'll make your phone say normal so you can download the OTA). Given you're on tmobile and your phone is the T889 model, check for software updates and install the OTA. Your phone will take a bit and will probably be stuck on the T-Mobile 4G boot screen for several minutes (it's normal). This should work.

[Q] help, stuck in boot mode at samsung screen

I've been running a rooted pm-600 with clean rom for a week now. I decided to try the new megablast rom and after carefully following install instructions (all wiping done and zip install via twrp2.6.3.3.) I was stuck at the Samsung screen in the boot mode. After giving it some time and not getting past the Samsung screen, I tried restarting and the same thing happened. I used was able to go to download mode and used odin on my pc to flash back the stock rom, but I am still stuck at the Samsung screen. I get the galaxy note 10.1 2014 splash screen, the start up music, blue circle, but then it just hangs at 'samsung'. I have tried restoring stock twice now with the same results. Any ideas :crying:
tmord1 said:
I've been running a rooted pm-600 with clean rom for a week now. I decided to try the new megablast rom and after carefully following install instructions (all wiping done and zip install via twrp2.6.3.3.) I was stuck at the Samsung screen in the boot mode. After giving it some time and not getting past the Samsung screen, I tried restarting and the same thing happened. I used was able to go to download mode and used odin on my pc to flash back the stock rom, but I am still stuck at the Samsung screen. I get the galaxy note 10.1 2014 splash screen, the start up music, blue circle, but then it just hangs at 'samsung'. I have tried restoring stock twice now with the same results. Any ideas :crying:
Click to expand...
Click to collapse
The only avialable option for you now is getting into stock recovery, wiping data , cache & dalvik., you will loose your data on your internal card, but no other choices.
Thanks for the advice. I discovered that this was in part triggered/or perhaps caused by the failure of a brand new Samsung micro sdxc card. Very frustrating, had just gotten it the day before and all my recent nandroid backups were on it Appreciate the help
Sent from my SM-P600 using xda app-developers app

Samsung Galaxy Tab S stuck in bootloop after flashing official ROM and factory reset.

After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
AussieMouse said:
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
Click to expand...
Click to collapse
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
It worked! Thank you so very much!
And I'm not a huge fan of updating my Android devices due to past experiences, but if this happens again, I might just update it to Marshmallow.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
@ashyx
i love you man...this worked for me too...thank you...now i need to reinstall TWRP again and see what's cooking......
I had this problem recently too, with the added complexity that the "Factory Reset" option in recovery wasn't working -- it would say something like "MDM does not allow factory reset" and then just reboot.
Fixed it by directly flashing TWRP with heimdall, then booting into the new TWRP recovery, performing a factory reset, and then rebooting the OS. This time it got pass the bootloop.
i flashed new twrp for T700 it's bootloop cannot enter the twrp menu keep bootlooping ...what's the solution for this?please help
Help ME!
What are "stock firmware" and "MM"? and where to get it?
I've replaced the power button thinking it was a hardware issue but now I'm not sure. I've also installed a few different stock roms but still have the same problem. Does anyone have any insight as to what could be going wrong and what I can try to get it fixed? Thanks for any help you can give. The device is a Samsung SM T-800

Categories

Resources