Related
I have a stock GN, not rooted yet. Today my phone automatically shut off and now it starts back up, google logo shows up and all those colors come on for couple of seconds and then the phone reboots itself.
I can press both volume up+volume down + power button and get into a menu which gives me the options of Start, Restart bootloader, recovery mode, and power off. I choose recovery mode but then it goes on to an android sign with exclamation mark. After that I can't seem to get anywhere. I have tried volume up +power, volume down+power, and volume up+down+power but nothing seems to work. It just keeps on rebooting it self.
Any solutions to this problem??
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
....
FredFS456 said:
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
Click to expand...
Click to collapse
So, I did the above method and after flashing the factory stock rom it won't start up anymore. It doesn't respond to anything at all. It seems I've bricked it
Is there any way to unrbick it now? I'm assuming I can't send it in for warranty either now if it's semi bricked. Unless it's been completely bricked which means there is still a chance of getting a replacement phone.
I have the same prob on rooted SGN
This morning I switched off the airplane mode to be available, system crashed and restarted. And then still the same again - booting / android logo / restart again.. /./. I am using Android Revolution HD 2.1.5, for last month with no problems.
I tried to boot into recovery, then wipe the cache and reflash rom and radio from sd, it is still the same. I can see all the files on my int. sd with no probs.
Please help.
I'm thinking it might be a hardware issue, but I'll wait for another member's opinion before confirming.
Solved!!!
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
630263 said:
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
Click to expand...
Click to collapse
Was your phone rooted or bootloader unlocked before the problem occurred?
Anyways I've sent in my phone for warranty, hopefully samsung will fix it.
So my phone company called me today and apparently Samsung told them that it's corrosion(?) problem. When I asked exactly what does that mean they said it's moisture damage or physical damage that probably caused it. But I'm confused how could my phone possibly get moisture damage inside an otter box. I know how delegate these devices are and I know how to take care of them.
Anyhow it'll be $90 to fix it. I had no other option so I asked them to go ahead with the repairs. So frustrated with Samsung to be honest. I never dropped my phone once, never had any water damage, phone was always inside the defender case. And I still have to pay them for fixing my phone even though it's not my fault.
That's quite worrying, I just started having boot loop problems today. I've had the phone since Feb 29th and not had a problem with it yet, but today it started boot looping. I went into recovery and did a factory reset, was alright for a couple of hours then it crashed, started bootlooping again. Running stock 4.0.2 unrooted, I'm wondering if flashing 4.0.4 might help.
I'm in the same boat.... unrooting stock 4.0.1 firmware - canadian version from Negri.
April 23rd my phone crashed and started boot looping. Google logo - reboot - Google logo - reboot
Factory reset worked. I installed less apps than I had before figuring perhaps an app was corrupting something.
Yesterday - it happened again. Phone crashed. Boot loop. Factory Reset worked. Installed even fewer apps.
We'll see what happens this time around. I am hoping it is just a software thing. Hoping 4.0.4 gets pushed soon too.....
I've been having the same issue, plus sometimes my home screen it would lock up and wouldn't let me do anything, so I did a battery pull and it would boot loop for a half hour.
After the 3rd time I just took it to my Verizon wireless store, and showed them the situation and they couldn't figure it out, so their sending me a replacement, which I'm not looking forward too, don't want a semi-used phone....
Via Galaxy Nexus [LTE]
Rebooting Issue Solved.
I was also a troubled Samsung Galaxy Nexus user and my phone kept restarting more than half a dozen times everyday. Most of the times when I switched between two or more applications, or when it was simply idle on my desk.
However, I found a solution (at least in my case). All I did was root my phone, install cwm recovery, and flash a custom rom after wiping cache and factory resetting the phone, It's been about 5 to 6 hours now since I flashed the custom rom and I haven't had a single reboot or hang since.
Others who face this problem, please give it a shot, who knows? You might save your Galaxy Nexus instead of sending it back to get a replacement or spend some money on it for repairs which aren't even required in the first place.
I also had this problem unrooted. I had to give it to Samsung for the warranty
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
2stardiver said:
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
Click to expand...
Click to collapse
I could be wrong, but have you tried to clean the pin on the battery? Seems like battery and the phone isn't contracting too well
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Little update, phone did continue rebooting with original 1750mAh battery also.
I did also reset with recovery mode, and after that it did also reboot one time.
like it uses all memory/cpu and when nothing to do reboot (like windows )
I also did flash stock rom with toolkit but no help.
I will test rooting phone and flash another rom, or is it useless ?
after using couple days, not yet rooted.
Phone works and wont reboot even in heavy stress. but sometimes it just reboots by own not a single program in task list.
might reboot right after previous reboot or take hours to reboot.
stupid phone
I have been done some research.
I did one more time reflash google stock with rootkit, and forgot lock phone, it was almost 3 hours by own in wifi, no reboots at all.
when I noticed that I forgot to lock it I rooted whole phone and installed paranoid android 2.13 with CWM.
Now Ive been using 2 hours without any reboot, installing software, setting things up and using apps.
I dont understand at all:silly:
edit: noup, yesterday evening one almost reboot, paranoid android did reset itself but didnt even reset uptime. so I didnt count that normal reboot.
but after wake up this morning, it did reboot once when I put in my pocket, another just lying on table, once activating bluetooth in my car.
going to send it back to seller.
I have a similar issue, although not quite the same. Last night my phone started boot looping - it managed to boot up to the lock screen, and I can use it for about a minute before it dies and then reboots. This continues again and again (I have to pull the battery to quit it).
I have stock JB on my GSM GN, but rooted with an unlocked bootloader / CWM. I restored my old CWM backup, and had the same issue. I also wiped the cache and the dalvik just to see if that helped, but I had the same issue. I then tried to do a factory reset in CWM, but after I did that the boot loop just got to the nexus logo and died, entering a new (slightly shorter) boot loop. I went back into recovery and reflashed my CWM backup, and that at least got me back to booting into android.
I can't understand what's going on - could it be a hardware issue if it will happily stay alive in recovery, but dies after 1-2mins of android?
Thanks for your help. If it is hardware then I hope I can reflash the stock recovery / bootloader and unroot through recovery... the phone doesn't stay on long enough to do it when it's booted into full android!
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Same thing just happened to me. I have no root or anything but it will not boot the OS. I hope there is a fix for the problem because I really want to use the phone.
Same thing just happened to me.
Click to expand...
Click to collapse
No recovery for you either?
What was the latest Build you had when it was working fine?
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Druas said:
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Click to expand...
Click to collapse
Had the same thing happen - Now typing to you from my warranty replacement. Only option.
blackpaw78 said:
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Click to expand...
Click to collapse
Surprisingly, this worked. I forgot about download mode being an option. I also am not sure why this worked.
Edit: The phone boots, but is still randomly rebooting rather often. Not sure why, as everything was wiped and it should have been a fresh install of everything.
Another Edit: Back to boot looping/not getting to the Android loading screen. I didn't do anything other than let it download my apps. Maybe it is a hardware problem after all because it did successfully boot into Android a couple times.
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Janny82 said:
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Click to expand...
Click to collapse
That is actually pretty good outcome. Pixel phone is coming out soon.
Just had this happen today. Streaming music over Bluetooth and using another app, then tried switching tracks in Google Play Music and the app froze. Phone was unresponsive with app on the screen, then screen went off and wouldn't power on.
I finally got it on by holding down power for 30 seconds, but kept boot-looping to Google boot screen. I was able to get into fastboot mode and wipe everything and install the factory image. Still doing the same thing!
Just got off phone with Google. Told the rep everything I had tried and she is working on a replacement order. Supposed to call me back after chatting with higher level support. I wish they would just send me a new Pixel phone, or the 6P at least!
Ive had the same issue, where I just couldnt get passed the Google screen, the only solution for me to get back on to my phone was to let it happen until the battery died. After i let the battery die i turned it back on normally and connected it to my charger, it hasnt turned off since but im sure it will sooner or later
Edit: Issue is still happening but the only way for me to turn it back on is because the battery dies
This just happened to my and my wifes phones...all within a week of each other. I sent my wife's in about a week and a half ago to LG for warranty service. I am hoping that they are able to fix it...it is still in the 'repair' phase. I am trying to decide whether or not I want to send my phone in (which just died yesterday) before or after LG figures out what is going on with my wifes. In both cases, the phones were running fine and just shut down by themselves. The battery was not dead. Each time, the phone will boot to the Google screen, but then immediate shut down. I can get in to recovery and do actions within there, so I do not believe it to be a battery issue. However, as soon as you attempt to boot the phone, it will die.
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Its a 'known' issue. Google has confirmed there is an issue. Only solution appears to be a warranty replacement.
https://productforums.google.com/forum/#!topic/nexus/r29mtzLFS0g;context-place=topicsearchin/nexus/nexus$205x$20bootloop
---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------
Psychofrantics said:
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
on both phones, bone stock. Only difference was I was running the beta before getting the stock OTA and my wife's was full stock and received the stock OTA.
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Same HERE !!!!
the samed for me, and still now i can't light it up
sagshar said:
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Click to expand...
Click to collapse
In my opinion your EMMC probably died, but you can try reflashing factory images to see if it is some other problem.
I would only try LGUP as a last resort because it will set Allow OEM unlocking to false and lock your bootloader, making further experimentation difficult.
BTW IMO the Android 7 bootloop probably isn't related to Android 7. I think they are just saying hardware problem (EMMC failure) that happens to show up more frequently when you have large updates of OS.
The way Google worded it, it made it seem like Android 7 is killing some hardware because of some incompatibility with just some isolated hardware builds.
I would suggest you let it keep booting and flash some factory images and sometimes EMMC will come back briefly and boot. If it does, immediately backup as much as you can before doing anything else.
Same deal for me and they are sending a replacement. This is a MAJOR blackeye!
Is your phone under warranty then? I am having the same problem as everyone on here. I've tried everything. I bought the phone just over a year ago though, so am a little concerned Google will turn around and tell me it's not their problem... Even though this is clearly a fault!
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
My Galaxy Tab S prompted me for an update last night. I was at 5.0.2, so I'm not certain what I was getting upgraded to but it was about a 190MB download. The download went fine and the install seemed to go OK. However, at the end of the update install, the tablet rebooted, and that's when everything screwed up. It went through a normal reboot sequence but, when it started to come up like it was going to take me to the home screen, I got hundreds of error windows popping up one on top of the other. They all said "Unfortunately, this has stopped." or that has stopped, basically running through pretty much every default pre-installed and me-installed app on my tablet. And they kept appearing faster than I could press OK. I have just a black screen with these white error boxes. I'm never able to get to the home screen at all. I've rebooted. I've completely powered down and waited for several minutes before booting. Nothing seems to help. I keep getting a normal boot sequence, right up until the point that it would relinquish control to me, and then these same hundreds of error boxes and no home screen or any sort of control over my tablet. I have no idea what to do.
Has anyone ever heard of any behavior like this or know what I should do?
Thanks.
try to enter the recovery mode by pressing home+vol up+power button. and reset your device
or you can download your full firmware and flash it using odin.
edan1979 said:
try to enter the recovery mode by pressing home+vol up+power button. and reset your device
or you can download your full firmware and flash it using odin.
Click to expand...
Click to collapse
Just got up for the day and saw your response. I'm on nights right now, sorry.
Thank you very much for your reply. I was able to get into recovery mode. Just to clarify, when you say "reset", are you saying a reboot (the first option) or wipe data/factory reset (the fourth option)?
EDIT:
You can disregard. I went ahead and rebooted, and that did what I figured; pretty much nothing. Basically just rebooted, got out of recovery mode, and booted right back into the state that it was in before, which was screwed up. Factory resetting now.
Thanks.
OK, system wiped OK and it's restoring from a Google Backup right now. So, I guess we'll see how it goes the next time I try to update. I have the Wi-Fi version, just standard SM-T800. Isn't Marshmallow available as an update now? I'll see how things go I guess and see what updates are available.
Gotta remember recovery mode, for when all seems darkest!
Thanks again for your help.
OK, so, my tablet is back up and running, but that update won't install. It isn't causing the same problems as before, but it still won't install. I'm at 5.02 and the update is 190MB. It downloads and it starts to install after I accept the EULA. The screen goes black, the little Samsung logo pops up, then the little Android guy comes up and it says installing update 0%, waits for about two seconds, then the little Android guys is on his side with his cover plate up and it says error, then reboots. I can still use my tablet, I just can't install this update, whatever it is. I'm pretty sure it isn't the Marshmallow update, because I'd heard that was up over 1GB. Still, if I can't get this update, whatever it is, I doubt I'll ever be able to get the Marshmallow update.
Now I'm happy I have my tablet back, but frustrated because it won't update.
definitely it already has MM update. you could go to Odin way. Update it manually. can download the firmware here.
http://updato.com/firmware-archive-select-model?q=T800&order=date&dir=desc&exact=1
edan1979 said:
definitely it already has MM update. you could go to Odin way. Update it manually. can download the firmware here.
http://updato.com/firmware-archive-select-model?q=T800&order=date&dir=desc&exact=1
Click to expand...
Click to collapse
Yeah, I was thinking the same thing. It doesn't seem too hard. I'm reading up on it now. I'll download everything I need and possibly try it this weekend. I intentionally haven't reinstalled a lot on my tablet yet, thinking I was going to go that route.
Hopefully, that will take care of my issues.
Thanks again for the advice.
Well, updating with Odin went off without a hitch. After it had updated, I performed a factory reset, just to be safe, and reinstalled everything. It's running great now and I sitting pretty with 6.0.1.
Thanks again for your help.
here's what happened, the phone started freezing and restarting every 5 mins, I uninstalled some apps thinking that's what's causing it, I used it for around 10 minutes and it was fine, installed the latest security patch update, restarted and everything looked fine.
plugged it in, saw it had restarted again and it was stuck on the Samsung Galaxy A50 secured by Knox screen,
rn: I can't enter recovery mode, (the phone won't shut down and releasing the volume down and holding volume up thing doesn't work)
I can only enter download mode, Connected to Odin, flashed the latest firmware and it passed successfully, but still it gets stuck and won't boot.
any ideas?:crying:
anyone?
SallyTheDevil said:
anyone?
Click to expand...
Click to collapse
What firmware you.flashed??Stock firmware??Stuck at samsung screen?
muhamet said:
What firmware you.flashed??Stock firmware??Stuck at samsung screen?
Click to expand...
Click to collapse
yh I flashed the latest stock firmware,
n it's stuck there, like in th screenshot
SallyTheDevil said:
yh I flashed the latest stock firmware,
n it's stuck there, like in th screenshot
Click to expand...
Click to collapse
Force restart,press volume up and power button same time
muhamet said:
Force restart,press volume up and power button same time
Click to expand...
Click to collapse
Volume up and power doesn't do anything
Volume down + power restarts the phone but it comes to the same samsung black screen
Are you sure you flashed correct firmware? Tried to factory reset in recovery? Full Wipe and then flash the firmware?
You can also try 'adb logcat' to see what the error is if adb is available..
k3lcior said:
Are you sure you flashed correct firmware? Tried to factory reset in recovery? Full Wipe and then flash the firmware?
You can also try 'adb logcat' to see what the error is if adb is available..
Click to expand...
Click to collapse
I can't enter recovery mode
Volume down + power restarts but I did try to go to recovery by releasing volume down and pushing volume up the second screen goes black but it's not working
I can only enter download mode when it's connected to pc with odin running
Could it be a hard drive problem?
And I'm pretty sure i got the right firmware
Tbh not sure i got my A50 just recently, didn't even flash anything yet. Is you phone detected when you type "adb devices" in windows cmd?
k3lcior said:
Tbh not sure i got my A50 just recently, didn't even flash anything yet. Is you phone detected when you type "adb devices" in windows cmd?
Click to expand...
Click to collapse
tried it, it doesn't recognize the phone.
is there anyway to figure out if it's a hardware issue?
cuz I've heard it's a somewhat common problem in the A50 for the hard drive/storage to go corrupt.
SallyTheDevil said:
is there anyway to figure out if it's a hardware issue?
cuz I've heard it's a somewhat common problem in the A50 for the hard drive/storage to go corrupt.
Click to expand...
Click to collapse
Connect the phone to pc,press same time volume up and down.You will boot on download mode.Then flash firmware
SallyTheDevil said:
here's what happened, the phone started freezing and restarting every 5 mins, I uninstalled some apps thinking that's what's causing it, I used it for around 10 minutes and it was fine, installed the latest security patch update, restarted and everything looked fine.
plugged it in, saw it had restarted again and it was stuck on the Samsung Galaxy A50 secured by Knox screen,
rn: I can't enter recovery mode, (the phone won't shut down and releasing the volume down and holding volume up thing doesn't work)
I can only enter download mode, Connected to Odin, flashed the latest firmware and it passed successfully, but still it gets stuck and won't boot.
any ideas?:crying:
Click to expand...
Click to collapse
I am having a very similar problem to yours, so I will follow this thread. I was using my phone two days ago and it simply turned itself off and since then I am stuck in the logo screen. When the phone is loading I have no indication whatsoever of the battery percentage at all. I still can access option and factory reset and wipe cache (unlike you, apparently - but it does nothing for me). This simply does not help. I end up back at the logo Samsung Galaxy A50 screen. I have downloaded two different firmware... android 9 and 10 from Samsung mobile, and have used Odin to flash it. The process goes through ok and without errors. I get the pass message and the message that the phone is being updated. Then it is time for the logo screen again and form then on the phone simply does not start. I am lost. Can anyone help?
muhamet said:
Connect the phone to pc,press same time volume up and down.You will boot on download mode.Then flash firmware
Click to expand...
Click to collapse
done that already, it flashes the firmware successfully but still won't boot, it just gets stuck at the same screen.
JulianaO said:
I am having a very similar problem to yours, so I will follow this thread. I was using my phone two days ago and it simply turned itself off and since then I am stuck in the logo screen. When the phone is loading I have no indication whatsoever of the battery percentage at all. I still can access option and factory reset and wipe cache (unlike you, apparently - but it does nothing for me). This simply does not help. I end up back at the logo Samsung Galaxy A50 screen. I have downloaded two different firmware... android 9 and 10 from Samsung mobile, and have used Odin to flash it. The process goes through ok and without errors. I get the pass message and the message that the phone is being updated. Then it is time for the logo screen again and form then on the phone simply does not start. I am lost. Can anyone help?
Click to expand...
Click to collapse
hey there.
apart from the factory reset thing it seems like we have quite the same problem,
at this point I'm afraid it might be hardware thing
SallyTheDevil said:
hey there.
apart from the factory reset thing it seems like we have quite the same problem,
at this point I'm afraid it might be hardware thing
Click to expand...
Click to collapse
You know... I am not really sure. The only different thing I did was to accept to instal a new firmware one or two days prior. I am inclined to think that was it. Anyway... I tried to flash Android 10... Android 9 (both via Odin) and did not work. The support team instructed me to do the hard reset a couple of times ... and wipe cache and nothing. Today I sent my phone to Samsung assistance since it is still under the guarantee because that is what they thought I should do. I'll keep you posted. Hope you can get yours fixed soon.
JulianaO said:
You know... I am not really sure. The only different thing I did was to accept to instal a new firmware one or two days prior. I am inclined to think that was it. Anyway... I tried to flash Android 10... Android 9 (both via Odin) and did not work. The support team instructed me to do the hard reset a couple of times ... and wipe cache and nothing. Today I sent my phone to Samsung assistance since it is still under the guarantee because that is what they thought I should do. I'll keep you posted. Hope you can get yours fixed soon.
Click to expand...
Click to collapse
yh I installed that update too and this happened later the same night.
unfortunately for me all the shops n services are currently shut down because of the Co-Vid situation so i have to wait for now.
thanks for sharing, lemme know what happens.
I've had these same problems before. When flashing with Odin, don't populate the last slot with anything (the HOME_CSC slot). Flash it to the device without auto reboot on, restart the device manually and hold vol up + down to get to blue scrern, then unlock bootloader. Let it restart, then reflash ROM.