Related
Hi, everyone! I in need of some dire help right now. My S4 (Jfltemo) running Mahdi Rom 2.7 Won't boot. Now I flashed the phone several times before: Paranoid Android, Cyanognenmod, Android Open Kang Project, and Stock. I tried Mahdi Rom last Night since it was new and since it was stable. I clicked on the Reboot option on the Power menu after flashing it because i was going to go into recovery mode. Now my phone won't even boot fully. It goes to the Samsung Galaxy Splash Screen then quickly boots off. I changed the battery to my other to see if it was a power problem but instead the phone tries to turn itself on when plugging in a battery. I tried putting it in download mode but it turns off within a few seconds of entering download mode. I cannot enter recovery because it turns off soon after.
I'm kinda screwed here. Help?
Much appreciated. Fast Help Appreciated
Your power button is probably faulty. Either you have to replace it or try to fix it somehow.
Lennyz1988 said:
Your power button is probably faulty. Either you have to replace it or try to fix it somehow.[/QU
Its not that. I was able to boot into Download mode without problems after leaving my phone alone for a few hours. But now its the same thing again. I know its not the power button because i was able to boot before without no problems. Has anyone had this problem before?
Click to expand...
Click to collapse
I have a TMobile/MetroPCS GS4 model SGH-M919N that got stuck in a boot loop last week. I was finally able to find working firmware last night and used Odin to flash. Once it got to PASS my phone automatically rebooted with the blue recovery boot text in the top left, but then it just went back into a boot loop. I tried all other firmwares and none of them got to 100% so now I don't know what else I can do.
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
alesu69 said:
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
Click to expand...
Click to collapse
Have you tried replacing the battery? I figured I would try that but I havent gotten around to it yet
Not yet, i have no spare battery. Looks like when i plug the charger my phone just vibrates, like it's rebooting, and it's not showing anything. I found a similar issue here: http://forum.xda-developers.com/showthread.php?t=2532447
Looks like one guy did solve his problem.
*need to mention that by dead I mean it shows the "Samsung Galaxy S4 GT-I9505" logo and also shows "RECOVERY BOOTING", even though I didn't enter in recovery mode. Looks like now it doesn't shows anymore "RECOVERY BOOTING", but still, it doesn't boot. I was able to flash firmwares via odin and kies, but still no luck.
LE: It start booting by.. magic, i got to samsung boot logo, but that's all, crashed again.
After flash with Odin, immediately boot into recovery, perform a factory wipe, and reboot.
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
alesu69 said:
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
Click to expand...
Click to collapse
How did you manage to get into recovery?
harary said:
How did you manage to get into recovery?
Click to expand...
Click to collapse
Yes, but if I leave my phone in recovery (stock or custom), it just either freezes, either reboots, even though i don't do anything, just let it idle.
I can't manage to boot into the ROM 'cause eventually it will reboot. I couldn't finish the setup wizard.
OK so I don't know if this helps, but I managed to at least get past the "blue recovery boot" part. When the phone vibrated I let go of the power while still holding home + vol up, and I managed to get to the android guy with a blue progress bar below him. My phone shut off as the progress bar got 80-90% but now I know it's not impossible to start recovery.
Well, nothing works. After flashing pit file, an 4.4.2 odin prerooted image from here, cf auto root and then twrp, it will still randomly reboot. I manage to get past the boot logo into setup wizard, but phone just freezes after a couple of minutes, can't finish the setup wizard. Also, if i idle in twrp it will reboot sooner or later, tested already.I left my phone idling in twrp just to recharge my battery.
At least i have no more "unable to mount /data" errors.
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Operation Ivy said:
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Click to expand...
Click to collapse
What do you mean with back and forth?
harary said:
What do you mean with back and forth?
Click to expand...
Click to collapse
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend who repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
alesu69 said:
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend which repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
Click to expand...
Click to collapse
I got several times into Recovery Mode now, flashed several ROMs. I had no issues with freezing, especially not in TWRP Recovery Mode. But sometimes if i am trying to go into Recovery Mode or i just want to start ROMs, the screen turns into yellow behind the Samsung logo. If i dont take out the battery this wents into a complete white, but nothing happens.
Yes please tell if you got some news..
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Joashrox said:
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Click to expand...
Click to collapse
But it is sure that the power button is working because i get this blue "recovery booting". Or am i wrong?
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
alesu69 said:
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
Click to expand...
Click to collapse
Replace power button to new one. I have the same problems with s3 and this works. Try it.
Sent from my GT-I9300 using XDA-Developers mobile app
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
alesu69 said:
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
Click to expand...
Click to collapse
If You can't charge phone... Yup, motherboard is died. If You plug the charger and see something this have to be button but if You plug charger and don't see anything this is motherboard.
Galaxy S4 I9505
Phone was second hand to me at the start of this year, though had been well looked after, always in a case etc
I flashed it with the newest stock ROM in January this year
I9505XXUHOJ2_I9505BTUHOJ1_I9505XXUHOJ2
& rooted with CF AutoRoot
It has worked fine until about 2 weeks ago, when it randomly shut down. After restarting, it kept bootlooping.
Left it off & charging overnight, & the next morning it booted ok. Managed to use spotify for a few hours.
Then it started bootlooping again, sometimes getting all the way but then crashing after a few minutes.
Managed to boot into recovery & do a 'wipe cache', that didnt fix it.
'Wipe data' didnt fix it
Have flashed the PIT file & ROM (via odin), no errors in odin, done it twice now
wiped cache & data
still wont boot past the white splash screen, only sometimes boots into recovery
(also, only the menu button lights up, not the back button.)
I've checked the power button (clicks & dosnt stick)
Dont think the batteries the issue (charges fine, dosnt get warm, isnt bulging)
What else could stop it booting?
Have you tried booting into safe mode?
Safe mode, from what I read, can be accessed by holding the menu button while the phone boots.
But you should also do some reading about it, in case I'm wrong.
The other idea would be to try a custom ROM.
GDReaper said:
Have you tried booting into safe mode?
Safe mode, from what I read, can be accessed by holding the menu button while the phone boots.
But you should also do some reading about it, in case I'm wrong.
The other idea would be to try a custom ROM.
Click to expand...
Click to collapse
Can't boot into safe mode
(& having read up on it, it would only not run apps that arn't already in the ROM)
Any suggestions for a custom ROM
& why would it work when the original official one won't?
Well, it's booted far enough to get into android & add a google account, then it bootloops again.
Then after leaving it off for a while, it will boot & let me look at settings etc, then bootloop
however
the menu soft key stays lit all the time after a boot
the top half of the phone, around the camera, gets very warm
Does that indicate it's a hardware issue?
Could it be the battery?
If it's the top half warming up without you doing anything, it's the motherboard.
Boot into recovery and and let it stand by, see if it reboots.
xedge said:
Well, it's booted far enough to get into android & add a google account, then it bootloops again.
Then after leaving it off for a while, it will boot & let me look at settings etc, then bootloop
however
the menu soft key stays lit all the time after a boot
the top half of the phone, around the camera, gets very warm
Does that indicate it's a hardware issue?
Could it be the battery?
Click to expand...
Click to collapse
The battery can't prevent the ROM from booting. It would have to turn off during the boot, which it doesn't. So, by my logic, it isn't the battery.
Try official CM.
GDReaper said:
The battery can't prevent the ROM from booting. It would have to turn off during the boot, which it doesn't. So, by my logic, it isn't the battery.
Try official CM.
Click to expand...
Click to collapse
Hello Reaper, I have exactly same problem. Please help. In my case leds are working fine, rest is exactly the same problem. And It all happened suddenly on its stock rom. I never rooted my phone before.
kingpin090 said:
Hello Reaper, I have exactly same problem. Please help. In my case leds are working fine, rest is exactly the same problem. And It all happened suddenly on its stock rom. I never rooted my phone before.
Click to expand...
Click to collapse
Try this.
GDReaper said:
Try this.
Click to expand...
Click to collapse
I am not able to go into recovery after firmware flash. The recovery bot appears and when the blue loading bar goes to half, the phone reboots and then again boot loop. I just noticed this always happened when i flashed a rom. I was never able to enter recovery on first boot.
kingpin090 said:
I am not able to go into recovery after firmware flash. The recovery bot appears and when the blue loading bar goes to half, the phone reboots and then again boot loop. I just noticed this always happened when i flashed a rom. I was never able to enter recovery on first boot.
Click to expand...
Click to collapse
Does phone go into download mode ?
gosha98_ said:
Does phone go into download mode ?
Click to expand...
Click to collapse
Yes it goes normally into download mode. Firmware always flashed without any error. But i noticed I can't enter recovery on first boot to do factory wipe.
Sent from my GT-I9300 using XDA-Developers mobile app
kingpin090 said:
Yes it goes normally into download mode. Firmware always flashed without any error. But i noticed I can't enter recovery on first boot to do factory wipe.
Click to expand...
Click to collapse
Why do you want to do factory wipe after one boot?
Its the only thing i didn't tried till now, my phone crashes and reboots everytime during boot.
Sent from my GT-I9300 using XDA-Developers mobile app
Hello guys,
I guess I won't be the only one having this issue. My phone went dead suddenly, and doesn't boot. It only give a circle with a lightning bolt but not charging, is it a battery issue ?
At the same time, I can only go to download mode, no recovery, and I can flash via Odin, with success, but it doesn't boot up still.
This is driving me crazy and I am not sure whether it's a hardware or software issue !!!
Anyone having any thoughts on this ?
Thank you.
Turn your phone off. Put it on the charger. Leave it alone for at least 1/3 of the day. I've been using Android for a long time. This usually happens to my Androids, at least once in their lifetime. It should be good to go afterwards.
PS: Make sure your charger works and don't touch the phone. Let it get a good 8hr charge w/o touching a button.
Let me know if this works for you.
caponi_dls said:
Hello guys,
I guess I won't be the only one having this issue. My phone went dead suddenly, and doesn't boot. It only give a circle with a lightning bolt but not charging, is it a battery issue ?
At the same time, I can only go to download mode, no recovery, and I can flash via Odin, with success, but it doesn't boot up still.
This is driving me crazy and I am not sure whether it's a hardware or software issue !!!
Anyone having any thoughts on this ?
Thank you.
Click to expand...
Click to collapse
rlsyoung said:
Turn your phone off. Put it on the charger. Leave it alone for at least 1/3 of the day. I've been using Android for a long time. This usually happens to my Androids, at least once in their lifetime. It should be good to go afterwards.
PS: Make sure your charger works and don't touch the phone. Let it get a good 8hr charge w/o touching a button.
Let me know if this works for you.
Click to expand...
Click to collapse
HEY brother.
my case is a bit weird
i bought my s8 running nougat used it for 2 days and it was all good , so i received the Oreo update and updated it using the over the air when I received connected to wifi.
my phone started to reboot randomly even for 30 times per day , i tried several things like wiping cashe and the only solution that reduced the problem was uninstalling my installed apps. basically normal apps like facebook , whatsapp , spotify ,and even stock apps like calculator and music player.
today as usual I woke up picked up my phone and it started rebooting so i uninstalled some apps but it kept rebooting.
sometimes it reboots and get stuck at GALAXAY s8 boot screen [ not samsung flickering screen ] and all i had to do to overcome the boot loop is pressing and holding volume down and power button.
but one time it got stuck and boot looped once and for all. I tried to press volume down and power button to make it reboot again and overcome the bootloop but it rebooted and got stuck at the bootloop.
I tried to access recovery but i couldn't access it.
I can access download mode only.
my phone switches on itself when it is plugged in to charge , i can't turn it off completely to charge it while off.
I reflashed stock firmware and it succeeded using odin but the bootloop is still there.
please help me with my problem SIR.
and thank you really a tons.
sincerely,
Zack.
Did anyone manage to solve this? My phone has started exhibiting the same behavior.
Unable to power on the phone unless it's plugged into the charger, but if plugged in just keep boot looping to the Samsung logo.
I've tried re flashing the latest stock firmware, but this hasn't made any difference.
sounds like a typical case of the battery beginning to fail
Flash twrp and a custom rom... Only solution but go to YouTube and check how to flash twrp s8 oreo? Must watch
Flash back to stock, leave the phone charged until 100% then use the stock recovery or flash twrp and wipe cache and dalvik
Thanks all for the suggestions.
I've tried to flash twrp but I get the error "Custom Binary(RECOVERY) Blocked by FRP Lock".
I've flashed the stock firmware multiple times successfully via Odin v3.1.13.1 (G950FXXU2CRF7) but this doesn't make any difference.
I still can't boot up the phone. The only thing I can do on the phone is have it plugged in and go into download mode.
I can't boot into recovery.
If I leave it plugged in it will power on, vibrate, boot loop to the Samsung logo all day. (It does not show the charging circle)
Could this be a worse case scenario and be a hardware issue? Don't want to give up hope yet, since I can still flash a firmware with Odin.
frost15 said:
Thanks all for the suggestions.
I've tried to flash twrp but I get the error "Custom Binary(RECOVERY) Blocked by FRP Lock".
I've flashed the stock firmware multiple times successfully via Odin v3.1.13.1 (G950FXXU2CRF7) but this doesn't make any difference.
I still can't boot up the phone. The only thing I can do on the phone is have it plugged in and go into download mode.
I can't boot into recovery.
If I leave it plugged in it will power on, vibrate, boot loop to the Samsung logo all day. (It does not show the charging circle)
Could this be a worse case scenario and be a hardware issue? Don't want to give up hope yet, since I can still flash a firmware with Odin.
Click to expand...
Click to collapse
Man try the latest firmware.... If its not working let me know.... Latest with july security patches.
I am currently undergoing this too, except my phone won't flash in Odin.
I have SM-G955U (TMBL)
Did anyone solve this??
zen2o1 said:
I am currently undergoing this too, except my phone won't flash in Odin.
I have SM-G955U (TMBL)
Did anyone solve this??
Click to expand...
Click to collapse
error msg?
What's happening?
IronRoo said:
error msg?
What's happening?
Click to expand...
Click to collapse
It varies depending on what firmware I try to flash it acts differently. All firmwares I try to flash will take a while in "flash analysis" and then to "setup connection" it takes so much time. After wait some time it fails.
I can send you some pictures if needed. When I get home I will.try again and send you the error.
This is what one error looked like trying to flash G955USQK2_Stock_recovery_BoxWares.tar.md5
This is the error.
<10:0/0/004> Odin engine v (ID:3.1207...
<10:0/0/004> File Analysis
<10:0/0/004> Setup Connection
<OSM> All threads completed (succeed 0/failed 1)
Also excuse for PM you, I thought you were going through the same thing but realized this morning during work that it was my post you replied to.
Any Solution??
I'm having a similar issue but I can't flash with Odin. It fails every single time
im having the same issue i flash the stock firmware but im just on a loop even after flashing but now im able to log into recovery i tried to wipe cache partition and do a wipe data factory reset but it doesn help phone is still on a loop i see a text on the bottom of recovery it says. #fail to open recovery _cause (No such file or directory)#
Hi,
Ihave the same problem,
Stuck on Galaxy S8+ and i can only enter the download mood (Odim Mood) nothing else,
I have flashed the last update 2 times and still have the same problem,
Even i cant control the powering OFF ON good,
I have already removed the back side cover to remove the battery cabel from the main board, connecting the usb Cable to be able to enter the download mood.
Hope anyone have an idea or can help.
eithar.metal said:
Hi,
Ihave the same problem,
Stuck on Galaxy S8+ and i can only enter the download mood (Odim Mood) nothing else,
I have flashed the last update 2 times and still have the same problem,
Even i cant control the powering OFF ON good,
I have already removed the back side cover to remove the battery cabel from the main board, connecting the usb Cable to be able to enter the download mood.
Hope anyone have an idea or can help.
Click to expand...
Click to collapse
what errors are you getting in Odin? also, id put your phone back together if you werent having hardware issues before this bricking situation.
youdoofus said:
what errors are you getting in Odin? also, id put your phone back together if you werent having hardware issues before this bricking situation.
Click to expand...
Click to collapse
I got no error with odin
With odin i do full flashing firmware and pass.
After that the phone try to restart but still stuck again on boot screen
---------- Post added at 06:13 PM ---------- Previous post was at 06:06 PM ----------
IronRoo said:
error msg?
What's happening?
Click to expand...
Click to collapse
I try to start the phone and still stuck on boot screen(Galaxy S8+) i could NOT Enter the recovery mood but i can enter the Download mood (Odin Mood)
So I tried to Flash the Stock Firmware 2 times and i coud do that and finishing the flashing with Odin with (green Pass)
But the phone turn off after finishing and i try to turn it on but still stuck again on Boot Screen.
I have tried 2 times to flash the firmware but same issue.
My wife will kill me if i did not repaired this phone
eithar.metal said:
I got no error with odin
With odin i do full flashing firmware and pass.
After that the phone try to restart but still stuck again on boot screen
---------- Post added at 06:13 PM ---------- Previous post was at 06:06 PM ----------
I try to start the phone and still stuck on boot screen(Galaxy S8+) i could NOT Enter the recovery mood but i can enter the Download mood (Odin Mood)
So I tried to Flash the Stock Firmware 2 times and i coud do that and finishing the flashing with Odin with (green Pass)
But the phone turn off after finishing and i try to turn it on but still stuck again on Boot Screen.
I have tried 2 times to flash the firmware but same issue.
My wife will kill me if i did not repaired this phone
Click to expand...
Click to collapse
its Odin mode, not mood LoL
get a fresh download of the firmware youre trying to flash and flash it instead. Get the Frija tool as it downloads the firmware waaaaaay faster than directly from www.sammobile.com/firmwares
https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
youdoofus said:
its Odin mode, not mood LoL
get a fresh download of the firmware youre trying to flash and flash it instead. Get the Frija tool as it downloads the firmware waaaaaay faster than directly from www.sammobile.com/firmwares
https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
Click to expand...
Click to collapse
Thank you,
Still same issue.
I have now tried another new battery but the same problem,
i am 100% sure it is not Hardware problem.
Samsung always have same these problems but needs much work or using Z3X Box.
Hope for Solution
eithar.metal said:
Thank you,
Still same issue.
I have now tried another new battery but the same problem,
i am 100% sure it is not Hardware problem.
Samsung always have same these problems but needs much work or using Z3X Box.
Hope for Solution
Click to expand...
Click to collapse
even after a new download of the 4 files?
For the past few months I've been running the Galaxy S4 I9506 on Lineage Os 14.1, I occasionally encountered random bootloops during use where the phone would suddenly die then run into a bootloop as it tried to restart. When it did this, I was able to fix it by removing the battery, waiting a while, then re-inserting it, but I've recently encountered a problem where as soon as I put the battery back it starts bootlooping without pressing the power button. I am also unable to access TWRP or Odin mode as the bootloop overrides it. Is this due to a hardware fault within the phone or is there some way I can still save my S4?
*EDIT*
In the end I was able to find a replacement motherboard and swap it out with the faulty one. The phone once again booted normally and after a re-flash Lineage OS has been working flawlessly ever since. I believe this means the previous motherboard may have just died of old age, will still try the oven trick though.
I recommend flashing the latest stock ROM using Odin, use the phone in a stock configuration to confirm that everything works.
https://updato.com/firmware-archive-select-model?exact=1&q=GT-I9506
Without installing and using the stock ROM, it wouldn't be possible to determine if it is a hardware or software problem.
audit13 said:
I recommend flashing the latest stock ROM using Odin, use the phone in a stock configuration to confirm that everything works.
Without installing and using the stock ROM, it wouldn't be possible to determine if it is a hardware or software problem.
Click to expand...
Click to collapse
Whenever I boot the phone into Odin it will sit in the download mode for about 5 seconds before cutting power and bootlooping again, does this mean that it is a hardware fault in the phone?
ShaunCB said:
Whenever I boot the phone into Odin it will sit in the download mode for about 5 seconds before cutting power and bootlooping again, does this mean that it is a hardware fault in the phone?
Click to expand...
Click to collapse
Could be a power button problem too.
ShaunCB said:
For the past few months I've been running the Galaxy S4 I9506 on Lineage Os 14.1, I occasionally encountered random bootloops during use where the phone would suddenly die then run into a bootloop as it tried to restart. When it did this, I was able to fix it by removing the battery, waiting a while, then re-inserting it, but I've recently encountered a problem where as soon as I put the battery back it starts bootlooping without pressing the power button. I am also unable to access TWRP or Odin mode as the bootloop overrides it. Is this due to a hardware fault within the phone or is there some way I can still save my S4?
Click to expand...
Click to collapse
Seems an hardware issue. The only way I know to give you a chance to boot to os and save your data is to use the trick of hoven. Put the motherboard (whiteout the camera) in the hoven at 200°C for almost 10 minutes. It seems strange but working for me. If you decide to try remember that I am not responsible of any damage!
Regards.
Edit: a thing that you can do to check if the problem is hardware related it is to remove the middle frame and try to boot. If you successfully boot the problem is the motherboard.