Ok So I just bought this att s3 from Craigslist. As soon as I got home it started restarting , it will reboot like after 10 seconds.
It boots as far as the Samsung logo then restarts. Sometimes it goes all they way to att splash screen then reboots.
What I have tried to fix.
1) boot to recovery whipe data and dalvik, but it won't give me enough time to copleate the command before it restarts.
2) boot to download mode but won't stay on enough time to hook it up to my pc the use odin on it.
3)Booted safe mode and the phone booted up all the way then the power menu came up then restarted.
Im out of ideas Do you think the mother board is messed up?
Plzz help thank you for looking and for your help/...
kipster3001 said:
Ok So I just bought this att s3 from Craigslist. As soon as I got home it started restarting , it will reboot like after 10 seconds.
It boots as far as the Samsung logo then restarts. Sometimes it goes all they way to att splash screen then reboots.
What I have tried to fix.
1) boot to recovery whipe data and dalvik, but it won't give me enough time to copleate the command before it restarts.
2) boot to download mode but won't stay on enough time to hook it up to my pc the use odin on it.
3)Booted safe mode and the phone booted up all the way then the power menu came up then restarted.
Im out of ideas Do you think the mother board is messed up?
Plzz help thank you for looking and for your help/...
Click to expand...
Click to collapse
Did you ask if this was rooted before you got it ? So you got the phone home and had done nothing to it before it started rebooting or did you do something and it start ?
I've heard this happen when someone had a wipe for bad and the recovery gets borked but it could be the power button as well. The hard reboot happens after the power button has been pushed for 10 seconds. This could explain the constant reboots/ Mess around with it and see if that helps. I had this happen on a skyrocket and cappy and the button got "unstuck"
hednik said:
Did you ask if this was rooted before you got it ? So you got the phone home and had done nothing to it before it started rebooting or did you do something and it start ?
I've heard this happen when someone had a wipe for bad and the recovery gets borked but it could be the power button as well. The hard reboot happens after the power button has been pushed for 10 seconds. This could explain the constant reboots/ Mess around with it and see if that helps. I had this happen on a skyrocket and cappy and the button got "unstuck"
Click to expand...
Click to collapse
its not rooted when i manage to get in into download mode its official and the counter is 0 .
the recovery is stock. I did think that It could be the power button stuck but the button clicks . Im gonna have it checked anyway to see if it could be the power button
kipster3001 said:
its not rooted when i manage to get in into download mode its official and the counter is 0 .
the recovery is stock. I did think that It could be the power button stuck but the button clicks . Im gonna have it checked anyway to see if it could be the power button
Click to expand...
Click to collapse
Does it reboots even when plugged/charging?
Did you try another battery?
kipster3001 said:
its not rooted when i manage to get in into download mode its official and the counter is 0 .
the recovery is stock. I did think that It could be the power button stuck but the button clicks . I'm gonna have it checked anyway to see if it could be the power button
Click to expand...
Click to collapse
It's not really a matter of it not clicking physically on the outside but something sticking under that button.
From your initial post to you stated it not always restarting at the exact same point during the boot up. Tend to make me think physical.
If its not rooted and has stock recovery someone might have rooted it before and then tried to put it back stock and borked it somehow.
Have you tried downloading Odin 3.07 and see if it's recognized ?
Did it boot when you bought it ? Please don't tell me you bought it without seeing it boot up first...
hednik said:
Did it boot when you bought it ? Please don't tell me you bought it without seeing it boot up first...
Click to expand...
Click to collapse
+1
Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
JasePK said:
Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
Click to expand...
Click to collapse
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from (TWRP or CWM) (how to: https://sites.google.com/site/tomsgt123//adb-fastboot)
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: http://www.reddit.com/r/htcone/comments/1rkvy0/help_stuck_in_bootloop_without_access_to_recovery/
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Techngro said:
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from -snip-
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: -snip-
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Click to expand...
Click to collapse
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
JasePK said:
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
Click to expand...
Click to collapse
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
cdresor said:
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
Click to expand...
Click to collapse
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
JasePK said:
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
Click to expand...
Click to collapse
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
cdresor said:
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
Click to expand...
Click to collapse
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
JasePK said:
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
Click to expand...
Click to collapse
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
cdresor said:
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
Click to expand...
Click to collapse
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
JasePK said:
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
Click to expand...
Click to collapse
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
cdresor said:
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
Click to expand...
Click to collapse
No that's alright, I just wanted to know if it was something I should avoid. :laugh: I'll use Odin to flash the official firmware back on regardless.
I had this happen to me, what had occurred was that the efs was corrupt. Here's the fix:
http://forum.xda-developers.com/showthread.php?t=2507403
Now to implement this fix, you must first be able to get into download mode. To do so:
1. Pull the battery
2. Wait 10-20 secs
3. Reinsert battery WHILE holding power button and (volume down + home???, whatever the key combination is)
5. Phone will boot directly to download mode, no logo
6. Flash twrp via odin
7. Phone will reboot into bootloop again
8. Repeat steps 1-4 except this time use the key combination for recovery
9. You must now use adb and push the file I linked to earlier
10. Then without rebooting you must flash it
11. Reboot and problem solved
Fixed issue with continuous recovery boot
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
This is exactly what I posted above lol
LOL Sorry. When I flash the TWRP file it just rebooted the phone back into the Hyper Drive Rom I'm using, did it do the same for you?
Thanks to everyone who has provided information and tried to help me! Thankfully, T-Mobile simply sent me a new phone. However, I'm definitely going to keep this topic bookmarked for future reference. This seems to be a rather uncommon problem, considering I had to make a topic to find a solution since all of my searches didn't give me any results.
Thanks again to everyone!
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
I'm having the same problem with my TMobile Note3 after using Kingo after upgrading via Kies to the latest Firmware. The only difference is my phone immediately starts rebooting as soon as I put the battery back in. It doesn't appear that any keys stop this and the USB isn't recognized by my computer in time before the reboot cycle starts.
Is there anything else to try other than sending the phone back for warranty replacement?
tim
Yeah Kingo has given me nothing but trouble, I'd steer clear of that software. I'm assuming you have no access to recovery mode? I have had that issue before on an S3 and was able to finally get it into download mode, but the battery being inserted immediately boots the phone up. So what you have to do is 1. Take battery out and unplug usb cable. 2. Plug USB cable in and Hold download mode buttons with BATTERY OUT (vol+, home and power) 3. insert battery simultaneously while holding buttons down, phone will boot up.. After holding down for about 10 seconds phone will manually reboot, 4. When screen shuts off (potentially vibrates) release download mode buttons, then IMMEDIATELY press and hold download mode buttons again (must perform this step FAST, the key is to do it right before the screen turns on if you can.) 5. The manual boot you've performed should allow you to trigger download mode. I was eventually able to get this to work (about 3 tries. ) I believe your download mode is still intact, you just have to use this method to access it. Remember that because your phone atuo boots with battery inserted download mode will only be available by manual reboot not battery insert.
Give thanks if I assisted you.. Your phone isn't a hard brick so Jtag service should be unnecessary at this juncture.
---------- Post added at 05:09 AM ---------- Previous post was at 05:01 AM ----------
Awesome!! Glad I could be of such assistance
---------- Post added at 05:13 AM ---------- Previous post was at 05:09 AM ----------
R187J said:
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
Click to expand...
Click to collapse
Awesome man!! Glad I could be of assistance!!
Give thanks/thumbs up!
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks
hi!
suddenly my n7100 does reboots again, and again.
on start with the n7100 logo - while charging, the bat icon, it reboots - i can not go even into download mode.
if i disconnect the bat power, and leave it for 1 or 2 days it is working again, a few seconds.
i flashed new rom, wiped cache, and new recovery. sadly: no success. still in a boot loop.
i have looked in the internet and of course in this forum - does anyone know what to do, to get it alive again (well it is, but it is rebooting(((?
is the board broke? or the switch ( it is working as far as i see) - or some ram?
any help would make me glad
tia,
rasp
I guess it's not working when charger is connected ? So I understand from your post.?
Also which bootloader are you on? And which rom you flashed?
If you using kitkat notice that the bootloader is better to be the one from the kitkat rom.
Or do you used rom with Ultra saving mode the first time you got those bootloops.
Sent from my GT-N7100
note2nooby said:
I guess it's not working when charger is connected ? So I understand from your post.?
Also which bootloader are you on? And which rom you flashed?
If you using kitkat notice that the bootloader is better to be the one from the kitkat rom.
Or do you used rom with Ultra saving mode the first time you got those bootloops.
Sent from my GT-N7100
Click to expand...
Click to collapse
yes. charger is also not working. rebooting....
i used for about one year (!) - including wanam rom... this BL:
BL_N7100XXUEMJ5_1903221_REV04_user_low_ship
and reflashed it yesterday again without any success. well the rom i did not reflash... only bootloader and recovery.
any tips to get this baby working again?
if i put a fully charged battery in it, it also reboots...
raspberryswirl said:
yes. charger is also not working. rebooting....
i used for about one year (!) - including wanam rom... this BL:
BL_N7100XXUEMJ5_1903221_REV04_user_low_ship
and reflashed it yesterday again without any success. well the rom i did not reflash... only bootloader and recovery.
any tips to get this baby working again?
if i put a fully charged battery in it, it also reboots...
Click to expand...
Click to collapse
So you're saying your phone reboots by itself as soon as you put the battery inside? Can you get into download mode without pressing the power button just press volume down + home button if download mode opens up that means your power button is messed up (either it's pressed all the time or you need a new power button)
Firstly, yes, I am sure that the info that I need is on here somewhere, but I have spent the last hour reading threads and I am not a developer and I cannot tell the difference from a soft brick or a hard brick or a boot loop.
Also almost all of the tutorials to root / unbrick involve enabling USB debugging on the phone first, but I can't boot my phone to do this anyway....
So, I got 2.19 OTA update and installed it normally. Phone is not rooted, totally stock 550ML WW model.
But in the last update I got a few bugs so I wiped the cache from recovery mode by following a tutorial, no problems and the bugs went away. So I decided to do the same this time....
I got to the boot menu OK and selected Recovery Mode, then got the Error / sleeping droid screen, so I tried to hold power / vol up to get into the recovery mode and the phone turned off. It was at about 35% battery and plugged into the charger so I'm pretty sure it wasn't a battery issue.
Now I can't get it to turn on / boot at all. If I hold the power button down it just vibrates once and does nothing else, same for vol up and power.... Is this some kind of brick?
Problem is I am going travelling for a month tomorrow and I can't be without my phone so I have to fix it in less than 24 hrs.
Can anyone help me without using terms like "flash image" or "sideload" unless you explain exactly what they mean?
Thanks in advance. :silly:
Can you press vol down and power and see if it turns on?
Sent from my ASUS_Z008D using Tapatalk
Vol down and power has done something!!
The phone vibrated twice and the led has lit up showing that it is charging!! Also I have the battery graphic on the screen.
Should I just now turn it on normally?
Sorry to sound so dumb but I really don't want to screw this up...
Thanks for answering by the way.
You can try to boot like normal but my guess it would still be stuck with the android logo. Happened to me when I rebooted my phone while wiping cache.
Anyway go to the link and follow his instructions. Let me know if there's any problems. Cheers!
http://forum.xda-developers.com/showthread.php?t=3101556
Sent from my ASUS_Z008D using Tapatalk
i experienced shutting down during wipe cache.bad times then.i resolved with this : forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
remember for bootloader press power+volume up.when it vibrates release power and keep pushing volume up.you should be in booloader.scrolling with volume up volume down you can choose recovery..may will be wrote installing update and then an error message.just press power and immediately after volume up for a bit.you should be in recovery.if you reached recovery do a wipe cache.REMEMBER IT CAN TAKE 15-20 MIN TOO ! check if it power on.
if you still cat access bootloader...for me you have to use warranty.say to asus you just did an ota and then phone bricked.dont use the word brick say just it won't power on.approach is the key in this cases.approach to them like a total noob.call them,don't email them.if you are young,let someone older to talk,a relative or someone like this and give to him a text to follow.is difficult to think a noob thinks to do some difficult moves as root,unlocking bootloader....they think "this is a noob.he never thinked to root or modify phone" .so they can think your seller sold to you a rooted device (updating with root takes to brick,bootloop etc.) and so they will give to you a new phone.if it not power on they cant see if it is rooted or not
good luck bro
Many thanks to all of you that contributed, it seems that I was pretty lucky.
After the "reanimation" as per Aceazzay's suggestion, I left it charging for about an hour or so (just in case it was battery related) then booted it normally and it worked (upon booting the battery was over 90%, so it was certainly not a shutdown due to battery).
I have now been able to do a Cache partition wipe correctly and all is good.
I don't know why it shut down in my first attempt, perhaps clumsy fingers, or something more sinister? I guess I'll never know, but this site has certainly saved me some grief!!
Overandout said:
Many thanks to all of you that contributed, it seems that I was pretty lucky.
After the "reanimation" as per Aceazzay's suggestion, I left it charging for about an hour or so (just in case it was battery related) then booted it normally and it worked (upon booting the battery was over 90%, so it was certainly not a shutdown due to battery).
I have now been able to do a Cache partition wipe correctly and all is good.
I don't know why it shut down in my first attempt, perhaps clumsy fingers, or something more sinister? I guess I'll never know, but this site has certainly saved me some grief!!
Click to expand...
Click to collapse
happy for you :good:
So last night everything was normal when I just placed my phone on the table and opened an app (Telegram). Soon after it auto rebooted and ever since then it's stuck on the Samsung logo. It resets when I hold down volume down + power, but never progresses. Any thoughts on what I should do next after these steps that I've done / things that happened?
Flashed latest stock fw (SamMobile) for my device - March 2022, CSC Smart, PH - via Odin. I always updated my phone whenever it appeared so it was on the latest already.
First tried HOME_CSC, next did CSC when it didn't work.
Also tried an update one month down to see. Didn't work.
Cannot go into recovery - Waited until battery drained so it can shut down, I plugged it to my PC, held volume up + power until logo showed up many times. Didn't work.
Plugged it into the charger, lightning icon shows but no number. Only happened once and I never saw it again when I tried. When the phone turned off from 0 battery, plugging it into the charger will boot it to the logo again.
There were never any signs of slow down, crashes, reboots before. This was a surprise.
Phone is about 3 years old. Never dropped. Never used for heavy gaming or all day media.
Battery drained faster, but I'm still able to last half a day with normal usage.
Left it running entire night (4+ hours) when I gave up, I noticed some burn in but it faded after I kept rebooting.
I recently tried flashing the earliest Android 11 update but it would fail according to the Download mode screen so I did not continue.
Any ideas? How do I tell if it's a software/firmware issue or if it's already hardware related? If I cannot go into recovery, is that a sign that it's hardware or am I doing it wrong? Thanks.
sochansam said:
So last night everything was normal when I just placed my phone on the table and opened an app (Telegram). Soon after it auto rebooted and ever since then it's stuck on the Samsung logo. It resets when I hold down volume down + power, but never progresses. Any thoughts on what I should do next after these steps that I've done / things that happened?
Flashed latest stock fw (SamMobile) for my device - March 2022, CSC Smart, PH - via Odin. I always updated my phone whenever it appeared so it was on the latest already.
First tried HOME_CSC, next did CSC when it didn't work.
Also tried an update one month down to see. Didn't work.
Cannot go into recovery - Waited until battery drained so it can shut down, I plugged it to my PC, held volume up + power until logo showed up many times. Didn't work.
Plugged it into the charger, lightning icon shows but no number. Only happened once and I never saw it again when I tried. When the phone turned off from 0 battery, plugging it into the charger will boot it to the logo again.
There were never any signs of slow down, crashes, reboots before. This was a surprise.
Phone is about 3 years old. Never dropped. Never used for heavy gaming or all day media.
Battery drained faster, but I'm still able to last half a day with normal usage.
Left it running entire night (4+ hours) when I gave up, I noticed some burn in but it faded after I kept rebooting.
I recently tried flashing the earliest Android 11 update but it would fail according to the Download mode screen so I did not continue.
Click to expand...
Click to collapse
Any ideas? How do I tell if it's a software/firmware issue or if it's already hardware related? If I cannot go into recovery, is that a sign that it's hardware or am I doing it wrong? Thaitit
I have same issue and its was fixed today, just press both vol for 3 second than plug your phone tu pc, after that you will enter download mode than just flash your firmware..thats all hope this comment will help you and other people
same problem here. and adam i thing he did already flash a stock rom. i flash one and it dosent solve the problem with recovery or not charging the phone. and bootloop ofc.
wollert60 said:
same problem here. and adam i thing he did already flash a stock rom. i flash one and it dosent solve the problem with recovery or not charging the phone. and bootloop ofc.
Click to expand...
Click to collapse
Try press power +voldown + volup until the phone shutdown than press voldown + volup to enter edl mode
Adamkimiey said:
Try press power +voldown + volup until the phone shutdown than press voldown + volup to enter edl mode
Click to expand...
Click to collapse
stock firmware wont boot. but I somehow managed to get into recovery. from there i was able to install fresh 3.2.2 and it boots normally again.