Related
hi
i bought a phone "s4" a year ago
it's works fine for only month and start crashing and sound not working. etc....
so i replace it with the Warranty
works fine for 5 months
now it's dead
i mean not responding for anything
its been like that for about 3 months
today i decide to try to fix it but nothing happen
i tried every think
3 hours of trying without any result
i put it charging from the laptop usb port
suddenly after 1 hour i saw the battery logo
and it's work perfectly no lag or anything like that perfect
now i want to install a new rom so i download app "quick boot" from app store to get into recovery mode
"my volume up button not working"
and it's back again to death not working at all
the laptop not recognizing it
sorry for my bad language
i hope you can help me with that
work
ok it's somehow works fine but i want to install a custom rom
so i decide to install echoerom
but it's stuck on samsung logo
the big problem is that the volume up button isn't working
can't get into recovery mode or anything
please help
flash back to stock
Just use odin to flash back to stock dont need volume up to access downlode mode.
Hi people, something quite terrible happened to my phone when I woke up today. Before I went to sleep the phone worked and was charged by about 40% but some apps were force closing like crazy so I turned off the device before I went to sleep, cuz why not, eh? Then I woke up and turned on the phone and it showed the screen to choose if I want to go into downloading mode, I pressed cancel and the phone shutdown and now it wont turn on.
I tried soft resets, tried to charge it for 10 minutes, but the thing is the phone is like its hard bricked for no apparent reason... even the charge indicator when phone is off doesn't show anymore, no lights, no nothing. Please help me. If anyone has an idea what to do it would be greatly appreciated. It worked this morning, no one else touched the phone. :crying:
if it doesnt boot then its a battery problem, even in hard brick, it has some kind of flights flashing.
if Its hard brick then its paper weight, sorry.
Chord_Hugo87 said:
if it doesnt boot then its a battery problem, even in hard brick, it has some kind of flights flashing.
if Its hard brick then its paper weight, sorry.
Click to expand...
Click to collapse
If it's the battery what can I do here at home? At least try? I don't think it's a hardbrick cause I didn't do anything iregular to the phone, it was working before I shut it down and went to sleep. Idk how I hardbricked it by turning it off. :/
theSperks said:
If it's the battery what can I do here at home? At least try? I don't think it's a hardbrick cause I didn't do anything iregular to the phone, it was working before I shut it down and went to sleep. Idk how I hardbricked it by turning it off. :/
Click to expand...
Click to collapse
well the storage drive could fail, that could be another possibility which if I think about it now that seems to be the case. best bet send it to samsung.
if you plug your phone into your computer and it does not read or register, you really dont have any other choices. This goes for all phones, the forum can help you with soft brick, not something like this, this looks like a hardware failure.
Chord_Hugo87 said:
well the storage drive could fail, that could be another possibility which if I think about it now that seems to be the case. best bet send it to samsung.
if you plug your phone into your computer and it does not read or register, you really dont have any other choices. This goes for all phones, the forum can help you with soft brick, not something like this, this looks like a hardware failure.
Click to expand...
Click to collapse
The phone rebooted constantly and force close apps from the day I bought it. I thought it was software issue... I went to my carrier to complain but they said nothing is wrong with the phone (way back few months ago). So my last question is this, can a phone force close apps and restart constantly with a software issue? or does it happen only to devices with hardware issues?
theSperks said:
The phone rebooted constantly and force close apps from the day I bought it. I thought it was software issue... I went to my carrier to complain but they said nothing is wrong with the phone (way back few months ago). So my last question is this, can a phone force close apps and restart constantly with a software issue? or does it happen only to devices with hardware issues?
Click to expand...
Click to collapse
that sounds like a storage drive failure...no apps doesnt do that and phone doesnt restart for no reason.
Chord_Hugo87 said:
that sounds like a storage drive failure...no apps doesnt do that and phone doesnt restart for no reason.
Click to expand...
Click to collapse
Ok so good news! Today I plugged it in the charger again and it booted! As I see it when I turn it off it doesnt really shut down properly and it stays in some kind of a phase and doesnt let me reset or do anything really... but It drained the battery that it had left and it bugged out. I know this cause I shutted it down again via the android option and its "bricked" again. Now I will wait for it to lose charge again so I can boot it.
Can you please tell me how to properly flash via odin to the latest nougat firmware? The phone was from Vodafone in Germany, few months ago I flashed a Netherlands firmware, then some other one few weeks down the road. Can you please tell me how to flash it back to full stock and what firmware should I download? The model is SM-G935F and the S/N is RF8H61YE4CP. I prevously tried THIS firmware from sammobile. Is this the correct one for my phone? I tried using samsung smart switch but it says "Secure Check Fail : Bootloader" when it tries to emergency restore it in the download mode, and the smart switch software says just error. Also whenever I flashed with Odin, BL never wanted to flash cause of just one file in every BL md5 file and that is the param.bin one, everything else flashes like it should. Please write me a guide on how to flash it properly and "upgrade" everything to the latest version correctly for my phone. (many settings in Odin that I never touched)
theSperks said:
Ok so good news! Today I plugged it in the charger again and it booted! As I see it when I turn it off it doesnt really shut down properly and it stays in some kind of a phase and doesnt let me reset or do anything really... but It drained the battery that it had left and it bugged out. I know this cause I shutted it down again via the android option and its "bricked" again. Now I will wait for it to lose charge again so I can boot it.
Can you please tell me how to properly flash via odin to the latest nougat firmware? The phone was from Vodafone in Germany, few months ago I flashed a Netherlands firmware, then some other one few weeks down the road. Can you please tell me how to flash it back to full stock and what firmware should I download? The model is SM-G935F and the S/N is RF8H61YE4CP. I prevously tried THIS firmware from sammobile. Is this the correct one for my phone? I tried using samsung smart switch but it says "Secure Check Fail : Bootloader" when it tries to emergency restore it in the download mode, and the smart switch software says just error. Also whenever I flashed with Odin, BL never wanted to flash cause of just one file in every BL md5 file and that is the param.bin one, everything else flashes like it should. Please write me a guide on how to flash it properly and "upgrade" everything to the latest version correctly for my phone. (many settings in Odin that I never touched)
Click to expand...
Click to collapse
i had a simmilar problem i couple months ago when i flashed a custom kernel.
i was overclocking the cpu but caused the phone to freeze actually without being able to to anything
i thougt my battery was dead also
when i charged it nothing came up into the screen also.
you just have to hard reset it but just keep on pressing your volume down button together wih your home button and the power button
it may take lonnger then you can normally do it cuz your phone freezed
but eventually your phone will just reboot into download mode then eand you can hit the volume down button to reboot your phone then
I attempted to root my Galaxy Tab A 10.1 WI-FI (SM-T580), and something went wrong.
I'm very new to the android scene, and was trying to use odin to install twrp.
The install passed, and my tablet rebooted, but I didn't press up, home, and power in time, and it started the regular boot process.
I powered it off, and tried to boot with the power up, home, and power button combination, but when it booted, the tablet went to a screen with hundreds of little horizontal streaks.
I am still able to boot into the power, home, volume down combination (where you can install a custom os), but I have no idea what to do from here.
could someone please walk me through what I have to do to get my tablet back to a working state?
I'd prefer to have root access if possible, but as of right now my only concern is not owning an expensive brick.
I attempted to follow Tech Alpha's video, which was posted at the beginning of this year (February 17, 2018), and it didn't work.
I tried to use Odin3_v3.12.7 to install twrp-3.1.1-0-gtaxlwifi.img.tar to my device. and that's where the problem started.
Thanks in advance for any help with this problem.
edit:
I fixed the problem, as it turns out, all I needed to do was search for an updated version of TWRP, and it worked fine.
Hi everyone,
When I tried to restart my Galaxy s8 it entered some kind of hardcore bootloop where I couldn't stop it from looping except by entering the download mode, letting it drain the battery or simply disconnecting the battery. When I exit the download mode it will just continue looping. It is also impossible to enter the recovery menu, which makes things much worse.
I have tried opening the phone and disconnecting everything except power supply (either battery or charger) and screen to see whether some detachable component is failing it (camera, speaker, etc.). But nothing.
I have also tried reinstalling the firmware (BL + CP + AP + HOME_CSC), it installs successfully but it doesn't fix the bootloop. I have also tried two most recent firmware, also without success. Somewhere on the Internet I have found a recommendation to install the firmware from June 2017 which I have tried but it doesn't work anymore because it's not possible to install earlier version of firmware on Samsung phones anymore (since November 2019 I believe).
Now I have started to believe that this could be a motherboard failure but it doesn't really make whole lot of sense because the phone can enter the download mode and reinstall firmware just fine. Or maybe there is a component which can make it able to enter the download mode, but nothing else would work?
Has anyone experienced something like this? How could it be fixed? Any recommendations? Is there any hope?
Edit: The phone has never been rooted, means it is in its original software state (currently on Android Pie with build number G950FXXS8DTC1). Is there any way to install anything on it (custom ROM, TWRP, etc.)?
Come on guys! Please don't tell me that I've tried everything and exhausted all the possibilities...
If there is still warranty on the phone, then send it in for repair. If there isn't, then I would take it to a repair shop and see what they can do about it. It is wierd that you can enter download mode, but can't flash stock firmware. I think it might be a motherboard problem
Nevin1901 said:
If there is still warranty on the phone, then send it in for repair. If there isn't, then I would take it to a repair shop and see what they can do about it. It is wierd that you can enter download mode, but can't flash stock firmware. I think it might be a motherboard problem
Click to expand...
Click to collapse
Unfortunately, there's no warranty and I'm pretty sure no one would repair this kind of failure for a price lower than the price of a used and fully functional Galaxy s8.
Yes, I can enter the download mode and I CAN flash stock firmware, but I can flash only the ones which are newer or the same as the one installed on the phone.
Yes, most probably it's a motherboard failure. In some YouTube videos I have seen people fixing similar issues by replacing the CPU (which I am unable to do by myself). Other suggestion I found on iFixit says that I could soak my motherboard in 99% Isopropyl alcohol and leave it overnight in it (I am going to try this if I get my hands on the alcohol).
BTW: One interesting thing I experienced while flashing the phone without its battery connected is that the phone's screen will go black when you press 'Start' button in Odin, but nevertheless the installation will finish normally and you can track its progress in Odin. At the end you'll need to restart your phone manually.
roberta-xda said:
Hi everyone,
When I tried to restart my Galaxy s8 it entered some kind of hardcore bootloop where I couldn't stop it from looping except by entering the download mode, letting it drain the battery or simply disconnecting the battery. When I exit the download mode it will just continue looping. It is also impossible to enter the recovery menu, which makes things much worse.
I have tried opening the phone and disconnecting everything except power supply (either battery or charger) and screen to see whether some detachable component is failing it (camera, speaker, etc.). But nothing.
I have also tried reinstalling the firmware (BL + CP + AP + HOME_CSC), it installs successfully but it doesn't fix the bootloop. I have also tried two most recent firmware, also without success. Somewhere on the Internet I have found a recommendation to install the firmware from June 2017 which I have tried but it doesn't work anymore because it's not possible to install earlier version of firmware on Samsung phones anymore (since November 2019 I believe).
Now I have started to believe that this could be a motherboard failure but it doesn't really make whole lot of sense because the phone can enter the download mode and reinstall firmware just fine. Or maybe there is a component which can make it able to enter the download mode, but nothing else would work?
Has anyone experienced something like this? How could it be fixed? Any recommendations? Is there any hope?
Edit: The phone has never been rooted, means it is in its original software state (currently on Android Pie with build number G950FXXS8DTC1). Is there any way to install anything on it (custom ROM, TWRP, etc.)?
Click to expand...
Click to collapse
I have an S8 with a similar issue. I can get to recovery menu but following similar steps to above by flashing combination firmware and still got stuck in bootloop. Subscribing to this thread in case anyone has a fix.
Just wanted to share a video I found. This is exactly how my s8 bootloops: https://youtu.be/gBlIcAJzgVA?t=5
PS: Obviously, the solution explained in the video didn't work for me.
PS2: This issue started by just restarting the phone. Before the restart it was in a perfect state, fully working, never had any hardware issues. Although there were some software issues introduced by an update (October or November 2019 I think) which made my phone need to restart 2 times to fully boot once if I wanted to restart it or turn it on after it was turned off. But those software issues were solved by a latter software update.
kjaved373 said:
I have an S8 with a similar issue. I can get to recovery menu but following similar steps to above by flashing combination firmware and still got stuck in bootloop. Subscribing to this thread in case anyone has a fix.
Click to expand...
Click to collapse
i know it's already an old comment, but was your phone also completely stock?
Leberkuchen said:
i know it's already an old comment, but was your phone also completely stock?
Click to expand...
Click to collapse
Yeah I believe so.
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
PinkElf said:
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
Click to expand...
Click to collapse
Hi, try to flash the stock firmware otherwise I really don't know :/
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
PinkElf said:
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
Click to expand...
Click to collapse
Are you using Lineage OS? If yes, then definitely yes. On my Xiaomi, I couldn't get into fastboot mode or into recovery, I don't know why and somehow I got there, I don't even know how I think I held the power mode for a long time and when the phone turned on I held the volume up button to get into recovery finally succeeded on the umpteenth attempt and from recovery I restarted the phone in fastboot mode and flashed the stock firmware. And yes, being able to boot your phone into fastboot is a good sign. It would be worse if it wasn't possible.
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
PinkElf said:
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
Click to expand...
Click to collapse
Yes, you can use download mode to install the firmware via Odin. Look
That means giving up hope for my personal data...
But even if I want to do this, I run into the problem, that I can't install anything due to "could not find PIT partition"...