Hi.....One day my galaxy 5 accidently fell down, though from a small height.....its battery came out. And after i reconnected the battery and started the device.....It started and worked normally...(btw i am using cm 10.1 v0.2)until some time and suddenly got frozen..everything on screen was as it was, i waited for almost half an hour but nothing happened.....no hardkeys worked...nothing....i had to pull out the battery and restart and again same happened.....i reflashed rom....after reflashing same rom (cm 10.1 v0.2) i got booted successfully and phone ran smooth as before but after i installed some apps it once again got frozen...and i tried cm 7 also and same happened.Not only in roms but it also gets stuck in recoery sometimes while restore or backup or flashing zip. One thing i noticed was it gets frozen when many apps start at once....I tried to flash official rom with odin but it went into bootloop and didnt even booted......PLZ helpp me...!! I saw this type of problem happened in S3....which is named Galaxy s3 suddon death syndrome and in that problem what happened was that a block in data partition(int. Memory) gets corrupted and when phone comws to write on that block it gets frozen and we have to pull out battery to start the device...I am trying the solution given there which is Dummy file generator but as soon as i start generating dummy files it gets frozen and after 2 to 3 tries, even the rom does not boot up......So please help me to solve this sudden freeze problem......I am really annoyed as i cat use my mobile....PLZZZ Help...
Related
Hi everybody... my phone died just a few hours ago.. the battery got to 0 while playing a game... now... while I was playing the game, my phone was flashing yellow bars..? like some sort of "im dying" sort of way...
its the first time that i see these flashes... right after that my phone just stopped functioning.... im stuck on the galaxy s3 logo, it doesnt even REACH the SAMSUNG logo.. so my question is...
is it possible that the INTERNAL memory of my phone, got broken..?
i think that its the internal memory that just died and now i cant use my phone.. installed other few roms and nothing, i can still get to the CMW and DOWNLOAD section but i cant get past the galaxy s3 logo.
do i need to find a samsung center and fix this?
i think that the phone itself came defective, since i've had a few problems with USB transfer ever since 2 months ago phone is "4 months old"
just not long ago i installed ultima rom and it fixed my usb file transfering situation... but now my phone just completely died. its not even ****ing bricked. thats the worst part!!!!!!!!!!!
Have you done a reset via recovery?
Sent from my GT-I9300 using Tapatalk 2
Go into recovery, clear cache and dalvik plus fix permissions then reboot. That is the easy fix, if it doesn't work then restore your nandroid backup or super wipe and reflash your rom.
If you are lucky then your sudden shut down only corrupted the system or data partition.
1. The galaxy hangs during normal work(it had custom ROM but was working fine for years), the display showed messed up image and was unresponsive, had to remove the battery(so it was caused by bug or flash storage error).
2. The galaxy could no longer be booted, it was stuck on Samsung Galaxy S II screen and in bootloop(if the flash storage partitions are bugged, I guess it can't boot the SPL and the device is stuck in the main bootloader, is it located in separate ROM chip or in the storage flash chip?).
3. It couldn't boot to recovery, only to download(odin) mode(again I guess it's part of the bootloader on the separate rom chip).
4. Tried to reflash, had to interrupt the operation because it didn't started at all(no progress on NAND write flash).
5. Tried to repartition with .pid file, again no progress with the operation.
6. After that, the device is completely dead, we tried removing the battery, using the charger and other common stuff but it can't be started anyway.
So can the failed repartition/flash operations bug the ROM bootloader so when you press the power button the CPU can no longer execute any instruction(I guess it's hardwired to some init instructions in the bootloader).
Any information about the internal storage chips or any ideas what to do?
Same problem here
Hi I've got the same problem with my phone since i've updated my cm13 on sgs II phone seemed to be working perfectly but around month later woke up and saw that my phone stuck on samsung logo (Same as your did) what i've done was restart to see is it works or recorvery boot up but nothing seemed to be happening. After some time decided to reinstall OS using odin but phone been comp[letely inresponsible to what i've tried to put on it (always been stuck on Nand write start (tried everything)). I tried to repartition it again but after that same as your phone died without any sensible reason. I "temporary" fixed it by pealing off the motherboard specific conductor. It even boot up but afterr that i runned out of charge died again. I can feel that phone is starting to be warm just like it's working but i still have black screen of death, so is there anybody who might actually help with this thread ?
HeadlessHorse said:
Hi I've got the same problem with my phone since i've updated my cm13 on sgs II phone seemed to be working perfectly but around month later woke up and saw that my phone stuck on samsung logo (Same as your did) what i've done was restart to see is it works or recorvery boot up but nothing seemed to be happening. After some time decided to reinstall OS using odin but phone been comp[letely inresponsible to what i've tried to put on it (always been stuck on Nand write start (tried everything)). I tried to repartition it again but after that same as your phone died without any sensible reason. I "temporary" fixed it by pealing off the motherboard specific conductor. It even boot up but afterr that i runned out of charge died again. I can feel that phone is starting to be warm just like it's working but i still have black screen of death, so is there anybody who might actually help with this thread ?
Click to expand...
Click to collapse
same thing happened to my galaxy grand 2
it was charging i was at 80% when i seen it last time i left it for sometime to complete the charge after 15-20min i piked it and i saw it was blank... after that till now it is dead..
I had the fabric format Android (4.2.2) and my friend helped me to upgrade to Cyanogenmod by using TWRP. It didn't work so we kept it in the lastest official 4.2.2 from Samsung. After a pair of days of working perfectly, I woke up and my phone was in the "Samsung" loading screen. I kept it for a couple of minutes and nothing happened, so I pulled out the battery and put it in again, same thing happened. Tried again, then it started normally and worked fine for a few seconds, until it froze, so I repeated the battery thing. Samsung loading screen a pair of times, then it loaded again, froze... And it kept doing that
Then I tried to format it with TWRP, but the OS was deleted too (guess I selected the wrong choice?) and it's not loading anymore.
Today I've been trying to re install the firmware via Odin with a friend, but it keeps failing at the system.img file and the error is not very descriptive...
I had the fabric format Android (4.2.2) and my friend helped me to upgrade to Cyanogenmod by using TWRP. It didn't work so we kept it in the lastest official 4.2.2 from Samsung. After a pair of days of working perfectly, I woke up and my phone was in the "Samsung" loading screen. I kept it for a couple of minutes and nothing happened, so I pulled out the battery and put it in again, same thing happened. Tried again, then it started normally and worked fine for a few seconds, until it froze, so I repeated the battery thing. Samsung loading screen a pair of times, then it loaded again, froze... And it kept doing that
Then I tried to format it with TWRP, but the OS was deleted too (guess I selected the wrong choice?) and it's not loading anymore.
Today I've been trying to re install the firmware via Odin with a friend, but it keeps failing at the system.img file and the error is not very descriptive...
Also, sorry for the repost, nobody replied in the last one, so I just copied the message. I hope you can help me, please :/ Is it hard bricked? Should I just forget about it and get another phone? Or is there any way to install another OS?
Hello guys, I have a serious predicament that needs to be solved.
I haven't did anything major to my phone in years so the past couple days have been a nightmare. Ever since I did a wipe of cache partition after trying to get rid of this "unfortunately, contacts stopped working." message, it's sent my phone into a spiraling disaster. (I have been using stock 5.0 rooted rom for at least a year so idk why the sudden issues)
I've literally tried every method imaginable. I even tried flashing with different versions of Odin and still the exact same problems.
I can get my phone into DL mode easily but Recovery mode only works if I have the phone plugged in at this point (Actually, it seems like the only time when my phone wants to work)
Every time I'm done flashing, it'll load all the way up to the T-Mobile screen then restart the loop all over again :/
Really need help seeing as I need to get this situation handled before work today, thanks!
Nevermind, after more research, I decided to order a new battery and the problem is solved.
Bootloop solved with replacement battery
gkenga said:
Nevermind, after more research, I decided to order a new battery and the problem is solved.
Click to expand...
Click to collapse
A replacement battery also solved my boot loop issue. Prior to replacement, it would boot to Galaxy S5 screen, and then reboot. Replaced battery and boots. Put the old battery back in, and it boot looped.