Hello guys, I have a big problem with my GT-I9001,
I have installed the clockworkmod and cyanogenmod by ivendor, (Alpha 7) http://forum.xda-developers.com/showthread.php?t=2000828
If I try to start my Galaxy it stuck's on the Splashscreen where I can see the Galaxy S Plus and the Cyanogenmod logo. After a few Minutes the screen goes of but you have to take the batterie out of the Handy to start it again.
If I try to boot into recoverymode, after the samsung logo the screen goes off, and again I have to take the batterie out.
At both Situations, if i touch the menu or return button it lights up, but not off anymore. At Situation 2 after a few Minutes.
The Download mode still works but if I try to Flash, for example with a Stock Firmware, it seems to go through with no problem, but instead of rebooting it only gets a blackscreen.
When i have flashed it and I start it the Splashscreen still has the Cyanogenmod logo on it, also if i flashed it with a Stockfirmware.
Another thing is, that if i try to charge my Smartphone, the normal shown batterie is stuck too.
Some people already mentioned the BroodRom, but on the download mode appears the Sentence: MMC boot: MBR read failed, and at Booting normaly is no change.
I tried to connect with adb to the Handy while it is on that black screen. It works, but if i try to enter: recovery --wipe_data, but in the cmd it only says: "/sbin/postrecoveryboot.sh not found" and nothing changed.
So this is the List of things that don't work or i already tried. I hope you guys will find a solution. If not i want to ask what Smartphone you would buy.
Problem found
I searched the whole net and i think i found the problem, It seems to be the memory controller.
I came to this because if i pushed something onto my Handy via adb it was there only till a restart. And some communities tell me, that the problem can be solved by exchanging the memory controller. But i don't think i can do that.
Related
Hello,
could someone please help me with my issue about the phone, as the name says, it stops booting at the glowing S samsung galaxy s logo, does the whole animation and sound before hand but nothing after...
It only vibrates for a milisecond once and three rapid vibrationg after few seconds then repeats... and screen goes black as well...
What I did: I did what the guide to get the 3 button download mode said, I tried it while my phone was fully functional and it did enter the download mode... So I thought it worked fine, also did the rooting thing as it's said in a guide here somewhere... an icon, superuser showed up...
I had my sd card unmounted when I tried to flash my rom using this guide :
Code:
well I can't put a video link here, so I guess just the name of the video on youtube could be sufficient:
Samsung Galaxy S Full Customization Guide (Part 1 of 3)
I did everything according the guide and after I first hit Start in odin, it started flashing, then phone restarted and gave me an error... and that is the current state...
I can't go into download mode
I can go into the Clockwork recovery mode tho
I tried to press the recovery firmware but it didn't work, also tried to mount sd card in clockwork advanced settings but it gave me an error...
I also get a screen sometimes when I try to access clockwork recovery mode that says forced upload by key pressing...
Is there a way to fix this ? I am really hopeless in this...
Thank you so much in advance
My i9000 gets stuck at the GalaxyS boot logo every time I try to start it.
First it shows the Samsung boot logo, then the logo of my provider (Drei) and then it gets stuck at the S logo. After some time the screen goes off but the phone stays on (the buttons light up when I touch the phone).
I read about others having the same issue but I can't even go into recovery or download mode.I tried several three button combinations but every single one gets to the same result-> the samsung logo shows over and over.
Maybe you know how to fix it?
Thank you.
P.S.: I'm sorry for my bad english.
First you'll need to state what you did to cause that to happen?
nwsk said:
First you'll need to state what you did to cause that to happen?
Click to expand...
Click to collapse
A longer time ago I rooted it and applied the One Click Lag Fix.
Everything worked fine.
But today I installed SGS-Tools from the market, installed the hacked camera and suddenly there was no camera installed at all.
I downloaded a Galaxy S camera apk and tried to install it but it couldn't install it.
Then I installed busybox and wanted to restart the phone but it won't start again.
Hi,
I have a Samung Galaxy S3 LTE International (GT-I9305) that I have flashed with the nightly cyanogenmod about a month ago. This morning, when I woke up, the phone was stuck on the 'boot screen' that just showed the "Samsung Galaxy SIII GT-I9305" wordings. I thought, no problem, I'll just take out the battery and restart. Tried that, no help. Boot screen still there. Thought again, no problem, I'll just boot into recovery mode and flash the latest nightly again. Tried that, to my horror, I couldn't boot into my clockworkmod recovery! Tried the up-home-power button key press, but this time the same boot screen shows up, and then disappears immediately again. Short while later, the same boot screen reappears and just hangs there.
Tried booting into download mode, but that warning screen appears for half a sec, disappears, and then the same boot screen reappears and hangs there again.
Any ideas what else I can try? Is this the motherboard dead?
Thanks!
oxygenoxy said:
Hi,
I have a Samung Galaxy S3 LTE International (GT-I9305) that I have flashed with the nightly cyanogenmod about a month ago. This morning, when I woke up, the phone was stuck on the 'boot screen' that just showed the "Samsung Galaxy SIII GT-I9305" wordings. I thought, no problem, I'll just take out the battery and restart. Tried that, no help. Boot screen still there. Thought again, no problem, I'll just boot into recovery mode and flash the latest nightly again. Tried that, to my horror, I couldn't boot into my clockworkmod recovery! Tried the up-home-power button key press, but this time the same boot screen shows up, and then disappears immediately again. Short while later, the same boot screen reappears and just hangs there.
Tried booting into download mode, but that warning screen appears for half a sec, disappears, and then the same boot screen reappears and hangs there again.
Any ideas what else I can try? Is this the motherboard dead?
Thanks!
Click to expand...
Click to collapse
Try to enter into download mode and flash a stock ROM (even if the screen doesn't display information [if it was not shutdown]).
Probably a motherboard problem due to SoC overheating or defective eMMc chip (I don't know if SDS exists on S3 LTE).
OK. After further googling, looks like my phone have all the symptoms of half-SDS. I've sent it to the service center. Hoping it'll be covered under warranty even though I've loaded cyanogenmod.
Hi all,
I use CM12 from MacLaw in combination with TWRP 2.8.1.0 recovery for about 3 weeks now.
Yesterday the phone didn't respond properly, was very very slow and I basically couldn't use the phone. It felt like the CPU was at 100% all the time, so unlocking the phone, calling and so was nearly impossible. A reboot (battery removal) didn't solve it, also the pin code for the sim card came after a few minutes while usually this will come right after starting.
So eventually I did a factory reset from the menu as I did on other occasions just to get rid of this kind of problems.
Well, right after the Samsung s3 mini logo I get the TWRP logo and it will be stuck in there, I see it blinking every few seconds and that's it. When I connect the phone to USB I hear it connecting-disconnecting every few seconds (bing-bong, bong-bing sound).
After a while I flashed TWRP using Odin again, this didn't give any problem but it will still hang in this TWRP loop.
I found some references to this problem but no real solutions. Someone suggested to use ADB but I don't know how to do that, nor could I find a suitable guide on this.
Can anyone help me? Or is it bricked somehow?? I suspect not, download mode is still working.
Thanks for any help!
Hi! Couple days ago, my phone just turned off on its own. I couldn't turn it on, nor could I charge it. Nothing happened when I connect the charger. I didn't touch it for a day or two and then when I tried to turn it on, it tried to boot up, but it just vibrated shortly and only showed initial Samsung logo and then it restarted. That loop of showing only the logo and restarting then happens continuously. I can't turn off the phone using the power button, I have to pull out the battery. When I re-insert the battery, phone automatically turns on, shows the logo and then restarst again and again and again...
I have found some suggestions to try to flash the phone with custom ROM. I tried flashing CyanogenMod using Odin. Odin displays the message that everything went OK, but phone again just boots up to the Samsung logo and then restarts continuously. After that, I have tried several other ROMs using several versions of each. Same thing happens. Odin says that process went OK, but phone again won't boot.
Does anyone have any suggestions what else should I try?
Maybe try to flash all stock files via Odin?
I tried that, too, but same thing happens. Anyway, it looks like it might be some hardware problem. I took the phone to the repair shop and they also tried installing stock and custom roms, but the phone just won't start. They said it's probably some falty hardware that's causing the problem.
Try to turn it on plugged to charger.
Something similar happened to my phone so I followed this guide, then did a recovery of my back up
http://forum.xda-developers.com/showthread.php?t=2748327
janota241, same thing happens when it's on charger, after Samsung logo, it turns off and then it turns on, then it turns off at Samsung logo and so on and so on...
IsReal8a, I tried that guide, but I can't access recovery mode, though I can access download mode. When I try to access recovery mode, phone just get stuck at Samsung logo for about minute or two and then it turns itself off.
I have the exact same issue as you do.
Maybe you can replace the battery, i just suggest
*sorry for my bad english