Hello, a friend of mine gived me an hard bricked phone.
As written in the title the phone is a Samsung galaxy A5 2016, SM510F.
Is not the first time I do things like that, but this phone is quite frustrating to work with.
I tried everything on this phone but the only thing that it does is the download mode.
It has no hardware problems, everything is working fine. The battery can't be removed.
I obviously tried to let it charge for long time. It does not even shows the battery icon while charging.
No boot, no logo.
I tried flashing 2 different version of the original ROM downloaded from SamMobile with Odin.
I tried an old and a new one.
I tried Flashing the Bootloader extracted from the ROM.
I tried flashing the 4 part ROM.
I tried flashing the PIT, since i suspected that my friend somehow cleard NAND while he was trying to flash the Root.
But out of this I get nothing. Odin gives a success but the phone only turned off and did not reboot.
I ask you if you have some different ideas, some similar experiences or some advices.
If you have some files please remember that I'm italian, so I need ITV.
I have no more ideas. Otherwise I will tell my friend to try to go to a samsung center.
Thanks.
You can try install custom recovery
Related
Sup guys. I have a problem with my S4. I doubt anyone will be able to help me find a fix but its worth a try. I hope someone will help.
Anyway, I flashed my GT-i9500 (Galaxy S4) from 4.2.2 to 4.3. Now it doesnt boot, It just gets stuck at the 2nd boot screen. Its not even a bootloop. It just hangs there. The S4 sound that plays gets cut like halfway.
I tried flashing a lot of different ROMS, and it still does the same thing. When I rooted it, I noticed the boot welcome sound plays full, but it still hangs after that.
I used Philz Recovery and mounted all the folders etc, but efs says invalid. So that means the EFS folder is messed. I get that, but I cannot repair the EFS if I cant boot the phone, I need the Samsung MTP **** for Samsung Tool to work. I have an N7100 (Note 2) Where I repaired the EFS with Samsung Tool, I was able to boot the phone.
I looked ALL over the net including this forum and found nothing. Right now the phone is just worth nothing. This is my last option, to ask here myself. If it cant be fixed I just cut my losses and get another phone.
I also flashed a PIT file, CSC file, Modem file during the period I was trying to get this fixed. If anybody knows this problem, It'll be very helpful.
Thanks.
you could try upgrading to 4.4, i have all the files for omega v21
heres the link for all the stuff from my google drive.
https://drive.google.com/folderview?id=0B_trhAurRvdmb0RkNGpoTkVNU0k&usp=sharing
instal the bootloader and phone file via odin, bl = bootloader cp = goes into the phone part of odin
then fash the rom via philz recovery, worth a try !!
good luck
That wouldn't work, thats for the Snapdragon variant I think. The i9505. I have the i9500. I'll download the Omega ROM for i9500 and try it anyway.
Thanks.
Still doesnt work.
StickyBomb said:
Still doesnt work.
Click to expand...
Click to collapse
Did you tried complete of phone, than power and vol up, at the buzz lose vol up and at loge lose power button.
and then flash with odin bl. and modem
etc.
I've flashed with Odin & Recovery.
I flashed another bootloader, XXUEMK8 & Odexed Knox Free Stock ROM XXEUMK8 & it still does the same. I dont know whats wrong with it.
Another thing I forgot to mention is if I root it using Odin, the welcome sound plays full and it hangs, and if I reboot it, the welcome sound goes back to cutting off again.
This phone probably cant be fixed. I dont know wtf's wrong with this phone. This is WORSE than hard bricked.
oh & as I mentioned before, I have a Galaxy Note 2 & had an EFS problem with it. I fixed it, the difference was this Note 2 actually booted properly with any ROM installed. I used a Z3X Box & Samsung Tool to fix up the EFS. Maybe this problem is only with i9500 or with i9500 & newer models.
Eeeer don't mean to point out the obvious here but you did do a factory reset in stock recovery after flashing stock 4.3 in Odin? That's all you needed to do at the start.
When I went from 4.2 to 4.3 I couldn't get it to boot at all unless I performed factory reset after flash.
Sent from my GT-I9505 using XDA Premium HD app
I came from a rooted Samsung org. rom 4.3 to omega v21.1 Android 4.4.2
After this i tried slimkat, and had from first start the same issue, no booting.
Nothing works
only starting with power and vol. up as descried above, I could flash XXUFNA5 bootloader & modems.
After this twrp.
And at last I flashed S4 Google Edition - 4.4.2, a ROM for the Samsung Galaxy S 4
Thanks for the help people.
I gave up on trying. I tried everything even factory reset after flashing, different ROMS, different Android versions. 4.1.2, 4.2.2 & 4.3. Today I ended up selling the phone's LCD. Atleast I didnt everything. lol. Wouldn't be buying another Samsung EVER. I was thinking I need another box and stuff, like NSPRO but I dont have that.
Hello. I'm a new user of SM G900F (SG). Running on lollipop with latest firmware
Bought it on Dec 26th, the device doesn't have any problem. I was happy back then, jumping form Galaxy Mini 2 to S5 is a big difference experience.
Running on official latest firmware, i only updated the phone once., around 1st - 2nd week of January.
The problem is, on Jan 14th, the G900F fail to boot (bootloop) after i set a new lockscreen from my gallery. It failed to boot, after several attemps, and wipe cache + wipe data, it booted. Haven't backed up my data yet, but i'm happy my phone is working.
On 15th, the same things happened. I set a new lockscreen. It's stil fine. But when a web-browsing on Chrome, the screen is automaically turn off (when not in use in a periout of time), but i immediatey press home button to wake the screen up. the screen didn't turn on, i press the power button. Then the bootloop happened. And this time, i can't go to recovery mode.
I've tried to re-flashing the phone using odin with official firmware, the SG one. But it didn't work. It showed Reset! with blue box on it. But still, m phone is bootlooping. My phone is still bricked. Can't go to the recovery mode either.
P.S: The phone is 2nd handed device from Singapore. I'm an Indonesian, bought the SG version bcs the Indonesia ver (G900H) is still 3G. While the SG one is 4G already. I'm using Indonesian provider (Telkomsel) and works fine on 3G or 4G so i assume the phone is unlocked. I've test the phone imei and it showed that it's the real S5, not the replica one. Antutu test showed 48,xxx score and proved that my device is the real S5 (judge by the name of device written on antutu).
I don't use micro SD. 32 gb is enough for me.
Sorry for long post and bad english. Really desperate to bring life to my phone back. Thanks before.
UPDATE: sometimes when i plugged on the device on my PC with kies on it, it booted to the homescreen. I dont know what exactly i do that caused the device booted, i only remember after stopping the bootloop (installed boot.tar, using this *the 1st method* that caused my knox 0x0, geez i didn't know that), then i flash my phone using the latest firmware (that i believe it's the correct one), then i re-plugged it on my PC with kies open, it booted! But the samsung animation logo played waaaay to long than usual. But it worked. Tried to reboot the phone to check if it's worked completely, unfortunately the device still doing bootloop. Then i tried method 2 from this, failed on odin. Turn on the device, still being jerk by doing bootloop. I gave up. Waiting for solution.
What model number does it say in download mode?
*Detection* said:
What model number does it say in download mode?
Click to expand...
Click to collapse
G900F. I downloaded the G900F SG firmware, too. Since it came from SG.
To rule out firmware (ROM) being the problem, flash this PIT file along with the stock ROM (Same time) in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add the PIT file to the PIT section, and the ROM to the normal PDA or AP section, and flash them together
If it still bootloops after a while after doing that, it's likely a hardware issue
*Detection* said:
To rule out firmware (ROM) being the problem, flash this PIT file along with the stock ROM (Same time) in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add the PIT file to the PIT section, and the ROM to the normal PDA or AP section, and flash them together
If it still bootloops after a while after doing that, it's likely a hardware issue
Click to expand...
Click to collapse
what is PIT file? Read the PIT explanation here, i'm afraid it'd made my device being paperweight. So what's actually PIT file do for my bricked G900F?
Thanks.
firareza said:
what is PIT file? Read the PIT explanation here, i'm afraid it'd made my device being paperweight. So what's actually PIT file do for my bricked G900F?
Thanks.
Click to expand...
Click to collapse
It repartitions the phone, 100% wiping any old firmware, then the new stock ROM will be 100% clean and you will know if it is a hardware or software problem
How can something make your bricked phone a paperweight? It already is a paperweight
If you're gonna second guess everything you're told, enjoy your buggy phone
Hello there,
I've spent my entire day trying to fix my Galaxy Note 4 (SM-N910F), without much success.
So what happened was that the phone would occasionally freeze, turn it's self off and reboot into download mode and say that it wasn't able to boot normally. But it usually just booted after pulling the battery.
So I thought I would just try to install the stock firmware(4.4) and go from there. And that worked fine (eventually) but the problem remained.
Why not try again, I foolishly thought. So I tried to download a more recent firmware(6.0), but it wouldn't install completely. It got stuck in Odin around half, saying: "FAIL!(WRITE)". Tried again using the older firmware(4.4), but the same result.
Now whenever I try to turn on the phone it immediately jumps to download mode saying that something went wrong while installing the firmware.
I have done a couple of things to try and resolve this issue:
- I have tried to flash BL,CP,AP and Pit from a recovery firmware without much luck.
- I have tried using Odin 3.09 and 3.11.1
There was one thing that kinda helped once, which was flashing twrp and all of a sudden it worked and actually turned on. But genius me decided that I had to try again and update to the newest version. Which wasn't really smart because again the flashing of the firmware failed.
If anyone could please help me out. I have spent nearly two days trying to fix this darn thing. I really just want it fixed
Have you referred this thread :
https://forum.xda-developers.com/showthread.php?t=3488114
Reporting Via N910G
yashthemw said:
Have you referred this thread :
https://forum.xda-developers.com/showthread.php?t=3488114
Reporting Via N910G
Click to expand...
Click to collapse
I hadn't, I google searched multiple times for such a topic, but didn't find any.
Besides using the SD card to flash the firmware I had already tried what was listed there.
But for the sake of it, I tried again. For some reason, this time it did work!
Many thanks for the tip!
I'm just left with one question, the recovery firmware you provided in the topic is german, but I have a Dutch phone. Will that create any issue's with network connectivity?
SmileyFace said:
I hadn't, I google searched multiple times for such a topic, but didn't find any.
Besides using the SD card to flash the firmware I had already tried what was listed there.
But for the sake of it, I tried again. For some reason, this time it did work!
Many thanks for the tip!
I'm just left with one question, the recovery firmware you provided in the topic is german, but I have a Dutch phone. Will that create any issue's with network connectivity?
Click to expand...
Click to collapse
First, flash that recovery firmware, once your device starts working normal, flash your region specific stock rom from sammobile.
Reporting Via N910G
Thank you so much for your help. I tried to see if the initial problem was resolved, but it still isn't. The phone sometimes doesn't boot and goes straight into download mode. I'm starting to think that it's a hardware issue, but I'm not sure. Any ideas?
SmileyFace said:
Thank you so much for your help. I tried to see if the initial problem was resolved, but it still isn't. The phone sometimes doesn't boot and goes straight into download mode. I'm starting to think that it's a hardware issue, but I'm not sure. Any ideas?
Click to expand...
Click to collapse
Must be hardware.
Anyway, i would do this
- flash twrp for Note 4 (look for it) from odin
- fladh rom from twrp (not from odin)
Sent from this galaxy
So basically my S7 Edge ended up in a bootloop and I don't know why.. It had some problems, ended up in a bootloop from time to time, but after the battery drained I could restart it and it worked.
Since 3 days ago it constantly is in a bootloop, when I try to start the phone. Tried to let the battery drain, but still if I try to restart the phone, it's in a bootloop. Then I even can't access recovery or download mode...
I can access the recovery mode and download mode, after draining the battery.
I already tried: wiping cache and factory reset. Still bootloop, if I start the phone.
I had the idea of flashing a custom rom, but I didn't enable the OEM unlock..
What else can I try to get this phone back to work?.. [I am currently using my old Galaxy Nexus from 2011 and it runs surprisingly fine ]
EDIT: I got stock rom and stock recovery, so basically untouched stock.
Thank you guys in advance
Hayalamm
download stock rom from sammobile and flash through Odin after booting into download mode. search google or go through the guide section of the forum on how-to do it. you should be fine.
Do I have to install the Stock ROM of my carrier? I bought the phone via Vodafone in Germany, but I dont think, that it is branded.
woomera said:
download stock rom from sammobile and flash through Odin after booting into download mode. search google or go through the guide section of the forum on how-to do it. you should be fine.
Click to expand...
Click to collapse
I did like you said and it still gets stuck on the Samsung logo and after that bootlooping all the damn time.. It passes the "Samsung Galaxy S7 Edge screen, but always gets stuck after that..
EDIT: Tried to get into recovery mode an the display got wierdly stuck on the first screen at "installing system update".. There was a wide black stripe at the lowert part of the display and many many thin black stripes thoughout the whole display. Since then it is unresponsive for anything..
Are you sure that your phone doesnt have any hardware issues?
If not then search for details on Odin's options. Maybe theres an option for a more theral wiping.
Other than these i honestly dont know what else can be done exccept for sending to samsung support center.
woomera said:
Are you sure that your phone doesnt have any hardware issues?
If not then search for details on Odin's options. Maybe theres an option for a more theral wiping.
Other than these i honestly dont know what else can be done exccept for sending to samsung support center.
Click to expand...
Click to collapse
Sending in won't help I think, because my display is shattered a bit. Had the problems before that too..
I have a similar situation. So far I have not found a solution. the phone is lying around idly. I store it for experiments)))
Hi ladies/gents,
I've just flashed my Samsung S5 (SM-G900F) with the latest UK BTU stock firmware from sammobile.com for my unlocked device (I've used SIM cards in the device in 3 different countries fine).
I reset the device into Boot mode, cleared the cache and factory reset, then boot the phone into download mode.
Using Odin I flashed the .tar.md5 file under the "AP" section of Odin with auto-reboot & F.Reset Time checked , the process was a success (according to Odin), and then when the phone restart: nothing but being stuck on the Samsung S5 boot flashing boot screen.
I've tried clearing the cache and factory resetting again, as well as installing the AP file again, to no joy.
I'm pretty dumbfounded by this as it seems this is the most straight forward and "safe" flashing to do on the device, yet now I seem to have bricked the phone in doing so.
Most of the advice I can find on the internet to fix the boot loop issue suggests doing the exact process I have just ran through, so I'm pretty close to calling it quits and looking at another brand of smartphone.
If anyone has any advice on how I can try and recovery the use of my phone, I'd be most grateful.
Thanks.
Okay guys/gals in the time it took me to feel sorry for myself and get desperate enough to create a post here the phone seems to have just turned on and working fine
I did restart the phone a bunch of times, but it seems just leaving it 20-30+ minutes does the trick.
Patience is a virtue!
Hi
I am having exactly the same issue with a G900I - tried everything!
Any advice??