Hello there, short story, flashed with odin 3.12 the stock firmware a SM-531F Grand Prime, and the power got cut in the middle of the phone flashing, after i restarted the phone, he ran in Emergency Donwload mode, requesting kies recovery, i tried to reflash the firmware, but odin said is failed, i though if i restart one more time will be fine, and from this point, the phone have absolute 0 life, is not booting, is not vibrate, no light, doesn't make connection even with the pc, what should i do? as i think the phone is still locked up in that edl session, exist a test point method or something? i really need to revive this phone.
I know there is a solution, thins thing could happen on any samsung, did someone faced the same problerm?
Did you try to flash the stock rom again?
Just try flashing stock ROM again.
Related
Booted into Windows on a Macbook.
Downloaded the droid root charge kit stickied in this forum.
Installed the samsung drivers. Loaded Odin.
Flashed the voodoo kernel in seconds, no problem.
Then, when I try to flash a ROM, it gets about 75% done, either hanging during the systemfs.rfs phase, or all the way up to movin???.dll (i don't recall the exact name). The phone says, "RX_TIMEOUT". It never gets past this point.
I've tried flashing back to factory stock, using both Odin and the samsung flasher, loading up the PIN and stock EE4. Same thing. Hangs at 9%. Sometimes just crashes and says 'Error, download cancel'.
I'm waiting for my wife to come home, since she has a PC laptop. I'm really, really hoping I just need to flash it from an actual Windows machine.
Stuck with a soft bricked phone. I've tried everything possible to flash back to factory (or anything, for that matter), but it's always the same. Hangs halfway through. Can someone please assist me?
sushi_stalker said:
Booted into Windows on a Macbook.
Downloaded the droid root charge kit stickied in this forum.
Installed the samsung drivers. Loaded Odin.
Flashed the voodoo kernel in seconds, no problem.
Then, when I try to flash a ROM, it gets about 75% done, either hanging during the systemfs.rfs phase, or all the way up to movin???.dll (i don't recall the exact name). The phone says, "RX_TIMEOUT". It never gets past this point.
I've tried flashing back to factory stock, using both Odin and the samsung flasher, loading up the PIN and stock EE4. Same thing. Hangs at 9%. Sometimes just crashes and says 'Error, download cancel'.
I'm waiting for my wife to come home, since she has a PC laptop. I'm really, really hoping I just need to flash it from an actual Windows machine.
Stuck with a soft bricked phone. I've tried everything possible to flash back to factory (or anything, for that matter), but it's always the same. Hangs halfway through. Can someone please assist me?
Click to expand...
Click to collapse
your best bet seems to be what you're trying to do, try and odin back to stock on a windows pc and work your way from there if you wanna root or put roms on
blazing through on my VZ Droid Charge 4G
Let me start by addressing I know this isn't the sprint thread but there's a lot more development here which equals more help. Plus this issue seems to be able to happen to any variant.
Second, this isn't my device I'm trying to see if it can be fixed for a friend. I'm not that familiar with Samsung devices but I have been able to get them working in the past via Odin or kies but this time I need some help.
So this is what's going on, my friend recently rooted his S6(SM-920P) not sure which method he used (don't think it matters at this stage) and was on stock rom (LP5.0.2) with xposed framework installed. He hadn't changed the kernel AFAIK oh but I did install TWRP for him and everything was working. Long story short he woke up a couple days ago to his phone being unable to turn back on. I told him how to get to download mode and I asked him what did it say on the top left corner it said something like "system binary not SEandroid locked" underneath that it said fac lock
So I had him give me the phone thinking somehow it did a OTA update while he was asleep or something either way I was confident using Odin to flash the firmware would solve the issue. Had the firmware finished flashing I'm confident it would have but halfway through Odin simply froze on installing system. I figured its just gonna take a while 45 mins later it was still stuck at the same spot.
Not really thinking about it I figured I will just reboot the phone back into download mode restart the process it should be fine. Not a good idea. Now all I get is a green screen saying to access the smart switch emergency recovery system. But it gets better.
My computer isn't recognizing the device now. I installed smart switch software and it's not recognizing it. I even installed Kies and it's not recognizing either.
Is his phone toast or what? I tried emergency system recovery but I need the S/N of his phone to possibly get this thing working again, but it boot into anything anymore except the screen that says Samsung switch...
PLEASE HELP ME if it's bricked it's bricked I get that but if there's a way to figure out what to do I'm all ears. Thanks in advance
I had my phone just sitting on a wireless charger this morning and had been there for about 15-30 minutes. I noticed it was rebooting, odd I thought? I took it off and then realized it was going into a boot loop. I gave it a soft reset and then it would turn on and stay on for about 10 seconds before boot looping again. I again gave it a soft reset after a couple loops and now it seems to totally dead, as the title implies.
No button combination has worked and I've held them all down for well over 30 seconds each. I've tried plugging it into my PC and haven't gotten any response that way. The blue LED is on so I know it's not dead...I think? To make matters worse, I bought this phone off Craigslist about 5 months ago and it's the Exynos version so I definitely can't get any kind of warranty on it. I'm hoping someone has had this problem and can help or just has some advice. Thanks everyone.
EDIT: To keep this updated, I have been able to get into Odin Mode and have tried to flash stock firmware. Odin says everything went fine but the phone hangs up at the Samsung Galaxy S7 logo. I'm unable to boot into recovery mode and I've even tried to reinstall TWRP with Odin and that has not worked.
Seen the LED only problem before, waiting for the battery to drain and the phone to turn off seems to be the only known cure atm
Once it does, connect the charger for 15 mins, then boot directly into recovery and clear caches to try fix the bootloop, possible it may need factory resetting / clean flash of stock ROM
Using the MicroUSB > USB white adapter, you may be able to connect a power hungry USB peripheral to the phone to drain the battery faster, I use a USB desktop fan, but some people report it not working when it is stuck in this LED loop and have just had to wait it out
Thanks for that advice, I'll let it drain over night. However, I have been able to get it to boot into Odin Mode and Odin v.3 recognized it. I flashed the stock firmware but upon rebooting nothing happened and now it gets stuck at the Samsung logo screen. I can still get it back into Odin mode, which I believe will be the fastest way to kill the battery, but I find it odd that I can get into that but not recovery? I am rooted and have TWRP installed, if that matters at all.
If you can get into Download (ODIN) mode, then letting the battery drain probably won't help, that only seems to help when the phone is completely stuck with nothing but the LED working
Make sure you flash CSC (Not HOME_CSC) along with the other 3 sections of the ROM, using ODIN 3.12.3, that should factory reset the phone after the flash
If you successfully flashed stock with ODIN already, you are no longer rooted and do not have TWRP installed, flashing stock with ODIN replaces all that with stock
I updated Odin and once again tried to flash the 4 parts, making sure I used the right CSC file, but I'm still getting hung up at the Samsung Galaxy S7 logo. Do you have a suggestion as to which region's firmware I should use? I have been trying the Australia one from SamMobile's site.
EDIT: And to clarify, I have the G930FD(the duos one).
jonny727272 said:
I updated Odin and once again tried to flash the 4 parts, making sure I used the right CSC file, but I'm still getting hung up at the Samsung Galaxy S7 logo. Do you have a suggestion as to which region's firmware I should use? I have been trying the Australia one from SamMobile's site.
EDIT: And to clarify, I have the G930FD(the duos one).
Click to expand...
Click to collapse
Any region would work, and the F firmware works for the FD too
Hi Guys,
So the issue seems to be straightforward and I read many threads about it, but none of them actually solve my problem.
My S6 is locked to Orange Poland (which is currently running 6.0.1 Android). I wanted to flash unbranded Marshmallow rom but that did not go well and in the process of flashing Odin returned an error (Complete(Write) operation failed). That's the way my phone became bricked. I tried to reflash this rom several times (while changing ODIN versions and also I tried single AP as well as 4 files + PIT). None of this worked. So I decided to go back to the branded rom—exactly the same as it was before.
Odin this time didn't show any fail messages and the phone actually started booting up. And here is my problem, it is stuck on the Samsung logo. I tried going to recovery mode, wipe cache and then factory reset but it still cannot go through Samsung logo.
My phone was never rooted. I have up to date samsung usb drivers. I tried SmartSwitch but it fails to recover the phone every time.
Do you kind people have any ideas?
Hi again,
Just a quick update from me. I finally managed to revive my phone. It seems that the bootloop was caused by the low battery (actually 0%, while being connected to PC). Once I charged the phone to 100%, it miraculously booted up and went to the setup wizard. I have no idea if the low battery had an effect on it, but once I charged it, the phone started to work properly.
In the end, I flashed back the stock rom with Orange Poland brand. The rom consisted of 4 files + PIT file. I used Odin3_v3.12.3.
Maybe this will help someone
axapies said:
Hi again,
Just a quick update from me. I finally managed to revive my phone. It seems that the bootloop was caused by the low battery (actually 0%, while being connected to PC). Once I charged the phone to 100%, it miraculously booted up and went to the setup wizard. I have no idea if the low battery had an effect on it, but once I charged it, the phone started to work properly.
In the end, I flashed back the stock rom with Orange Poland brand. The rom consisted of 4 files + PIT file. I used Odin3_v3.12.3.
Maybe this will help someone
Click to expand...
Click to collapse
Thats why you should always charge your phone to at least 70% before doing any flash :good:
So my Galaxy Note 5 was water damaged a few months ago and I just got it back up by replacing the battery. Problem is, I was trying to flash stock rom with ODIN and it seems like it doesn't do anything at all. When I try booting up the phone myself, it boots onto odin mode instead, and if I try going into recovery, it gets stuck on the TWRP logo (it had custom firmware before it was water damaged). I use the latest ROM sammobile has. ODIN isn't frozen or anything. It doesn't say that it isn't responding. It just doesn't progress further. Can anyone help me?