Hello friends I have already more than 3 months with the phone so brick paperweight, I led him to more technical 7 where live in santa barbara de barinas-Venezuela, also went to the neighbouring cities and nothing in any side give me solution most say is the screen I really very much doubt it because that made long before that big donkey to install the twrp when already had the CWM as recovery. I have read forums and forums and I'm trying to do it through gives you the ADB, I want to fix my phone because it buy a new one in my country currently with our monetary situation is buy a new cell phone and hold 1 year of hunger... to be able to buy it. do I hope that if some expert in android 4.4 software. 4kitkat read this I throw hand, and friends else this case is cataloged as a SoftBrick, HardBrick or a BootLoop? Thanks again and Merry Christmas to all. Here below I explain what happened. Buy the Samsung Galaxy Grand prime duos SM-G530H with android 4.4.4 as two weeks ago, as you can see this practically new what happened was the following rootee the terminal as it had already done in my terminal most everything went well. then download the TWRP MANAGER application from the store play gave him super user permissions and locate a TWRP recovery for the grand prime not found for model SM-G530H. There was when I made the stupid more large I have echo I found recovery for other models of samsung and download the recovery for the Grand duos the download and cell phone install it from the same application I turn off and turned on the screen but this look with blue screen with black and vibrates and turns off and again it does the same thing again and again you can see and not start. promise them is that not come to think that my cell phone was going to stay dead, the issue is to remove the battery if so have worked and the same. attempt to start mode recovery and not or it worked I was the same lit blue screen with black and vibrated and turned off. so I spent in download mode, lit in blue with black screen and turned off. Friends I am desperate because I tried everything and not me because I've taken the battery more thousand times, pc does not recognize me the device that simply does not fit into download mode. not load by gets blue screen with black. try a USB jig you buy from eBay and not worked a and also one of the technical goals that the to revised happened a jtag I think q is called so is seemed to a usb jing but saw that the changed him as voltages but none worked and told men that this fried. So no longer will be if they had some experience regarding my case would appreciate... translated by google
Did you get this sorted out ?
Sent from my SM-G530H using XDA Forums
[sm-g530bt] I am exactly with the same problem : /
haet2016 said:
Hello friends I have already more than 3 months with the phone so brick paperweight, I led him to more technical 7 where live in santa barbara de barinas-Venezuela, also went to the neighbouring cities and nothing in any side give me solution most say is the screen I really very much doubt it because that made long before that big donkey to install the twrp when already had the CWM as recovery. I have read forums and forums and I'm trying to do it through gives you the ADB, I want to fix my phone because it buy a new one in my country currently with our monetary situation is buy a new cell phone and hold 1 year of hunger... to be able to buy it. do I hope that if some expert in android 4.4 software. 4kitkat read this I throw hand, and friends else this case is cataloged as a SoftBrick, HardBrick or a BootLoop? Thanks again and Merry Christmas to all. Here below I explain what happened. Buy the Samsung Galaxy Grand prime duos SM-G530H with android 4.4.4 as two weeks ago, as you can see this practically new what happened was the following rootee the terminal as it had already done in my terminal most everything went well. then download the TWRP MANAGER application from the store play gave him super user permissions and locate a TWRP recovery for the grand prime not found for model SM-G530H. There was when I made the stupid more large I have echo I found recovery for other models of samsung and download the recovery for the Grand duos the download and cell phone install it from the same application I turn off and turned on the screen but this look with blue screen with black and vibrates and turns off and again it does the same thing again and again you can see and not start. promise them is that not come to think that my cell phone was going to stay dead, the issue is to remove the battery if so have worked and the same. attempt to start mode recovery and not or it worked I was the same lit blue screen with black and vibrated and turned off. so I spent in download mode, lit in blue with black screen and turned off. Friends I am desperate because I tried everything and not me because I've taken the battery more thousand times, pc does not recognize me the device that simply does not fit into download mode. not load by gets blue screen with black. try a USB jig you buy from eBay and not worked a and also one of the technical goals that the to revised happened a jtag I think q is called so is seemed to a usb jing but saw that the changed him as voltages but none worked and told men that this fried. So no longer will be if they had some experience regarding my case would appreciate... translated by google
Click to expand...
Click to collapse
Can you solve it? I am exactly with the same problem: /
I installed TWRP and my GRAND PRIME does not turn on. It does not go into fast boot mode. Only a blue and vibrating light is blinking.
Video Link:
https://www.youtube.com/watch?v=vM_9warqENU
Related
That is what happed this morning:
Woke up, whatsapp for a bit, suddenly, reboot itself, stuck in siya logo.
waited for 30mins, no luck, hard turn off (long press power button)..
after that, no more reboot, no download mode, no CWM, try the three button trick no luck, remove battery and three button trick no luck......
Here is what I have done with my phone before, It runs perfectly for like months:
Resurrection Remix Rom 2.2
Siyah Kernal (latest S2 version)
BLN
Overclock (200-1300) but stable with siyah
Apex launcher...
I sincerely beg for all genius developers to give me a hand...........
Try a download jig and see if that makes it respond.
St0rmzx said:
Try a download jig and see if that makes it respond.
Click to expand...
Click to collapse
ordered.... still waiting for that..
any other solution yet to be discovered?
bump
as i didn't "flash" dead my phone, I think there might be some solution.....
...
you are damn right, I can't live without it...
my phone is out of warranty plus flashed count.......
plus still looking for a shop that do jtag in sydney...
...
Call wireless provider tell them a crazy story about an accident you had and your phone is crushed and bloody and if they provide upgrade then ask for an early upgrade due to no warranty that is what I did for my $3
Sent from my SGH-I747 using xda premium
i just hardbricked my galaxy2
no download screen, no recovery screen no boot...
its only a week old! in virgin warranty...
have you had any luck with finding a shop to to jtag in sydney????
only option is to claim on insurance...
duleim said:
i just hardbricked my galaxy2
no download screen, no recovery screen no boot...
its only a week old! in virgin warranty...
have you had any luck with finding a shop to to jtag in sydney????
only option is to claim on insurance...
Click to expand...
Click to collapse
If there is jo Jtag shop in Syndey, you can send it overseas for Jtag repair. But I suppose it costs a lot of money.
Alternatively, you can send it to Samsung, play stupid (phone didnt turn on this morning) and keep your fingers crossed.
Wish you luck mate.
Sent from my Galaxy S2 GT i9100
Could anyone shed some light on all these bricked phones that were bricked out of the blue - without users fault? I mean, there are so many threads about bricking phones while doing nothing - the phone was just normally used, or even with the screen off, and it just turned off by itself/rebooted itself/froze and there was no way to recover it... Similar thing happened to me month ago - I was on a safe stock 4.0.3 ROM with safe kernel (mmc_cap_erase disabled), I have just started a game that I play regularly, the screen froze, I have waited for some time, then tried to do a hard reboot, got stuck at booot logo, and that was it. Recovery was erased - no way to enter it, download mode was still alive but it was stuck while trying to flash anything - there was an error while trying to write rom, kernel etc. I had to sent it to repair centre...
Thos was just an example, one of many. So, the question is - is this bad Samsung hardware in action, or software bugs that are causing hardware malfunctions or something else? I mean, I had few HTC Android phones before, and I have never saw anything like SGS2 Q&A forum - every second thread is about bricked phone...
Any thoughts?
I think people jump in with both feet without doing much research.I don't blame them,as I just flashed RR3 and I didn't fancy reading 62,000 posts.
Plus its a very popular phone,so maybe its only a tiny %age that are faulty.
Sent from my GT-I9100 using xda app-developers app
dear
i have a Samsung note 2, with all the original stuff no root , original software and no major system changment, 2 months ago my device started to restart automatically and once the device stopped at the restart point where the screen shows the name of the model, i replaced the battery tried to switched on again but the screen is all white without any indication, the recovery mode also gives me a white screen, the only screen that is showed correctly is the screen for rooting the device, well i can't root it because it did't see the computer when i connect it however it still take charge from charger. i searched the problem and called Samsung it looks like a ROM problem well i don't have my guarantee and i live in small town so there are no good agency to repair the device i want to ask how i can repair it myself or can you advice me to someone of your members that is neaby my town i can give him money to repaire it to me thanks in advance
best regards
Taher
Hi everyone. Thank you for reading.
I am posting for help with a friend's phone. I, personally, have an S3 on Sprint and haven't had much experience with T-Mobile phones. He has rooted his S5 (T-Mobile, obviously) using galaxys5root.com (I'm now not fond of that site due to his bad experiences that consistently happen) and has not put a new ROM on yet. It has been successfully rooted for several weeks, but today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on. He's getting a replacement anyway, but we want to unroot it before sending in the defective device. I'm wondering (and to my knowledge it seems like) if it's a boot loop. Nothing shows up on the screen at all, not even the back light is coming on. I have yet to connect it to Odin to see if anything comes up. I'm just seeing if this has happened to anyone else and if they have figured out a way to resolve it. My suspicion is that there's a problem with either the boot sector or the recovery sector, as it does not go into recovery.
Any insight would be much appreciated. Thanks again!
caderyn19 said:
today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on.
Click to expand...
Click to collapse
It sounds like the LCD display has gone bad if the vibration and blue light function normally but you cannot see anything ever.
When they get the new device you might want to suggest that they follow the rooting instruction in this forum on XDA instead of going to a website to do it. Just my opinion.
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
caderyn19 said:
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
Click to expand...
Click to collapse
Normally, even in a boot loop you see the initial Galaxy splash screen when it first starts booting. Then you see it over and over again. If you see nothing, it normally means the LCD is bad and unfortunately it's the most expensive part of the phone.
Good Luck with it.
If I've been helpful, please hit the thanks button.
That's what I figured... Thanks for your help! (I hit the button )
caderyn19 said:
That's what I figured... Thanks for your help! (I hit the button )
Click to expand...
Click to collapse
Wouldn't surprise me if the device is rebooting itself trying to fix a hardware fault. Might be detecting the LCD has stopped forcing itself to reboot.
But yeah, stick to XDA from now on We are good people here Welcome to the family!
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
caderyn19 said:
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
Click to expand...
Click to collapse
Well get your friend over here too!
Sent from my SM-G900T using Tapatalk
Hi there! Long time reader, first time poster (TL;DR below...but it should be a quick read anyways )
So I've been using this S2 of mine for almost 4 years now, haven't had any trouble (other than a couple of battery swaps). For the past 6 months or so I've been using CM 12.1 nightlies without issue.
The events:
- The other day, my phone froze (I wasn't using it when it froze, it was when I went to use it that I noticed...it was on the wifi selection screen if it matters), so I held the power button to shut it down, and when I powered it back up, it just froze at the Samsung boot screen (with the usual yellow triangle).
- At this point, I was able to reboot into download mode at will, but any attempt to boot to recovery just led to the freeze at the Samsung boot screen. Also, the phone would automatically reboot itself at this point any time I inserted the battery (I was of course putting the battery in and out trying everything I could).
- I would have reflashed from Odin at this point, but since I was away for a few days I just kept trying to reboot into recovery, to no avail. On one of these attempts (power+vol up+ home) it showed the Samsung boot screen, and then immediately shut down and I haven't been able to get anything onto the screen since
I'm now home, and I can't seem to fix it. If I plug the phone into a charger, the top half or so of the phone gets warm, and it also seems to get warm if it isn't plugged in and I try to power it up. I was thinking maybe the phone was maybe doing the same thing as before and just not showing anything on screen, but I blindly do the steps to get it into download mode, and Odin doesn't recognize anything (drivers are definitely installed). I have also tried other batteries, no luck.
Any ideas of what I might try? I'm willing to do anything. For the record nothing happened to the phone at all when this all happened (no dropping or water damage or anything, just my attempts at booting into recovery). Maybe I should try a jig? I'm also open to opening the phone if there's something I can do, though I don't have experience with this.
Thanks so much for any suggestions!
TL;DR: phone froze (running CM 12.1 nightly), held power to shut it down, and then consistently froze at the boot screen on any attempts to power it on. After a few attempts at booting into recovery (the phone would only freeze or enter download mode) the screen suddenly shut off and I haven't seen anything on it since no matter what I try. I can't think of anything that happened to the phone I'm open to any and all suggestions! Thanks
One sentence amongst your description stands out like a 'sore thumb'.....
That the device heats up towards the top when you attempt to charge it.......
Until you try a jig I can't be certain, but that heating coupled with a dead/unresponsive screen along with a lack of recovery and/or download modes (download mode is 'hardwired' into the device, and NOTHING should be able to corrupt it) are the primary symptoms of a failed motherboard.......
That is my opinion based on my experience in these forums and personal experience with a (now dead) S2 (one of two that I own).........
Get the jig just to be sure, but I'd be surprised if it had any effect.....sorry to be typing something you don't want to read, but you said it yourself, the device is 4 years old....it's been in service roughly twice as long as most smartphones, and they don't last forever....
http://i.imgur.com/rVnFwJM.jpg
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
smacsmac said:
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
Click to expand...
Click to collapse
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Sorry it took me a while...the jig was in the post haha. It didn't do anything at all (no response when I plugged it in) so I think it's safe to say you were bang-on and the motherboard failed! Happily using a new S2 (with CM13.0 now ) on behalf of my friend though.
Thanks again.
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Elaias said:
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Click to expand...
Click to collapse
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Its hard to tell you and hard to accept. You can almost give up the hope, your NAND Chip is just what we call " wear-out ". In the most cases no write is possible anymore, the funny part is -> sometimes read is still fine. If that is the case: The system is booting and working, but saving just nothing. The NAND is frozen to its state before it broke.
At our local store, customers come to us with issues like " Factory Reset impossible ", "Can't delete my Files" "Can't create files". All these Devices have inaccessible NAND's and inaccessible Recovery. Only Bootloader is working, but as the NAND is broken, flashing doesn't change anything.
smacsmac said:
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Click to expand...
Click to collapse
yeah, flashing with odin did the trick. now running cm13 and everything works fine. sorry to hear that your phone turned to brick.
Hi everybody i am asking for advice on trying to repair a phone for a family member the phone is a galaxy alpha F variant UK stock rom, factory unlocked and unrooted the problem started after finishing a call the handset was left un attended and when it was later picked up the screen was black but does not appear broken aywhere and does not appear to respond to touch
i have tried un successfully to get it into recovery or download modes the handset turns on and the blue lights come on and you can hear the start up tone but see nothing on screen, it also charges and i have tried a new battery, odin does recognise a device but as i cant get it into download i cant flash a stock rom which i have already downloaded.
So my question is, is there any software that i can download to diagnose whether or not the screen is dead or whether it is a f/w issue or is there a way around this where i can use a different tool to get into the handset and flash a new stock rom in case the current f/w is corrupted
Thanks in advance for any useful help and advice
Please understand that i am a newb to this so if i have made some mistakes or my questions have been answered elsewhere previously i do apologise
I think it seems pretty obvious that the problem is the display itself
Hi BigHands,
I faced a problem having the exact same symptoms as yours twice in the last few month: screen was staying black but phone reacted to some "external" actions (ON/OFF), blue light.
Not sure what happened exactly, but removing the battery and trying to restart the phone finally brought the device back to life after trying more than than 10 times!!!
So in my case, the display was probably not the (only) root cause.
Really weird however that I needed to reboot the phone >10times to make it work: usually when software is screwed either one single power cycle will bring the device back to life or it will never power up again!
Anyways, a FW issue is still a possibility considering the number of bug this phone has (for the price it was sold, that phone is definitely the worse gadget I ever owned!)... But it seems there is a bunch of FW updates on going on this model accross the world, so there is still a little hope things might improve... Samsumg may have woken up; who knows...
JF