[Q] i9000M not booting anymore - Galaxy S I9000 Q&A, Help & Troubleshooting

I have the Bell Galaxy S Vibrant, it's been working great up to this morning (I have Doc's Bell Froyo ROM). I shut my phone last night because I was at my girlfriends and I wanted to have enough battery to listen to music on my way to work. This morning I boot it and it kept getting to my home screen for like 5 seconds and rebooting non stop. I was able to shut it down to stop it from rebooting.
Now I get to work, plug it in and boot it and I see the boot logo and animation, then it just goes to a black screen and vibrates every 10 seconds or so.
Here's the thing though, I don't think my SD card is bricked because in Clockwork recovery mode, I can still access and install the install.zip file from the card, but that didn't fix my problem. I also tried wipe to factory settings, that didn't work either.
Anything I can do? Otherwise I'll exchange it.

Anything I can do? Otherwise I'll exchange it.
Wipe phone and flash a stock rom via Odin .
jje

Related

HELP! Constant Re-Boot!

Need a little help here...out of the blue today my phone started continuously re-booting itself. Only gets to the HTC screen and then re-boots. I have done multiple battery pulls with no results. I cannot boot into recovery either, tried that many times as well. My only option is a screen that I have not seen before that asks if I want to clear all data and then reset the device. Anyone have an ideas? Running Fresh 2.3.3, had no previous problems.
I had the same thing happen today. I had just flashed Fresh 2.3.3 to try to fix the GPS issue in the CM6 830 nightly, and my phone started rebooting every minute or so. I pulled the battery and immediately booted into recovery by holding down <home> and <end call>. I was able to get to recovery, where I flashed a different ROM I had on my SD card. I hope this helps.

Nook wont boot normally after being off all night..

ok so weird problem here..
my NC is fine besides this one problem.
ive rooted with autonooter to 1.0.1
if i turn my NC completely off and leave it all night, when i wake up in the morning it gets stuck on the "touch of... " screen. The only way to get past this is to reboot to recovery and select reboot..
any idea why this happens? if i just restart the NC, or just let it go to sleep this doesnt happen, only when its been fully off for a couple hours.
ive tried reverting to stock/rerooted all that to fix it, but nothing seems to work.
i know i can just let it sleep and problem solved, but id like to know why this happens or if anyone experienced anything like this before.. thanks!
Try holding down the "n" button while turning on the unit...
Other wise you might have messed up your boot partition, go to development and search for samelhaff's thread on a flashable zip where you can fix the boot.
it reboots to recovery (power+n) just fine... just doesnt reboot normally (just pressing n) .. gets stuck on touch of.. screen
after getting into CWR and selecting reboot it then boots up correctly..
dont know why it just wont reboot normally to begin with.
Same problem here.
After some testing with HC and CM7 roms i recovered to the 1.0.1 Eclair rooted with autonooter version. I turn it off and on some times and everything worked allright. Left it all night off and when i turn it on in the morning i was stuck at the "Touch the future...".
I flashed the stock boot repartition and it started normaly.
Yesterday i flashed the custom Froyo 0.6.8 and everything was allright untill the morning when i stuck again athe " touch..." screen.
I booted with CW and rebooted normally.
Same thing has happened to me twice. I've only been able to get it to boot by booting from my bootable cwr and selecting restart.
Also been noticing some oddities with it charging fully, sometimes while plugged in the status is simply "not charging", not "charging" or "dischargin" and the N symbol on the end of the cable is yellow, not green.
Now it's even worst. Every time i try to boot i get stuck in the "Touch..." screen and i can only boot through CW recovery.
Any ideas?
Glad I finally found some people with the same problem
So initially I took my stock nook (1.0.1) and ran autonooter. Worked great but I noticed it would randomly reboot. Also , same as the other posters, if I powered it all the way down it liked to automatically power up and get stuck on the boot screen. Only way to reset was boot into CWR and select the reboot option from there. I loaded CM7 and same problems so i thought it may be some kind of hardware issue.
Reverted to stock, no problems.
Back to autonooter and this time ran dual boot from EMMC with stock as main partition and HC v4 on second partition. So i don't have CWR anymore but have my SD card handy in case I need it.
Well after a couple days of normal usage the random reboots are gone. Left the unit on during the whole time. Last night I turned it off to apply my Phamtomskin and this morning woke up to find it stuck on the boot screen. Must have been doing that for a while because when i stuck in the SD card for CWR it gave me the low battery warning. After 15 minutes it rebooted to CWR and i was able to reboot normal from there.
Hopefully since a couple of us got the problem we can find some sort of fix. I would like to know if it is some kind of hardware issue or as poster #2 suggested its a simple matter of flashing the boot file. Would I loose my dual boot partition if I flash this zip? Any help appreciated and thanks what a great XDA community.
I think that it has to do with CW and boot. Can i remove CW recovery without affecting my configuration?
no change.
im at least relieved that others have this same problem and it isnt a problem with only my NC.
last night i went back to stock, rerooted 1.0.1 and all that jazz and opted NOT to install CWR and power it down over night (thinking maybe clockwork was the problem) ...
well that didnt work b/c this morning it is stuck on the "touch of" screen and worse yet, i obviously cant even boot into recovery to just reboot.
looks like another revert/reroot this morning for me...
very frustrating.
bump this?
pilotbluemike said:
im at least relieved that others have this same problem and it isnt a problem with only my NC.
last night i went back to stock, rerooted 1.0.1 and all that jazz and opted NOT to install CWR and power it down over night (thinking maybe clockwork was the problem) ...
well that didnt work b/c this morning it is stuck on the "touch of" screen and worse yet, i obviously cant even boot into recovery to just reboot.
looks like another revert/reroot this morning for me...
very frustrating.
Click to expand...
Click to collapse
Just get the bootable cwr, then you'll always have it handy. The stuck at touch of reading screen has happened to me twice, pulled out my bootable cwr, selected restart and all was well.
I've never heard of anyone having this problem with V 1.0.1. I know that a lot of people are having this same problem with V1.1. Apparently CWR and V1.1 don't coexist well. I had this problem after doing Stock Nook 1.0.1 --> Autonooter 2.12.25 --> Sideload to rooted V1.1. Some people also have the problem when going from stock V1.1 and using Autonooter 3.0. The fix in both cases is to uninstall CWR using the CWR removal tool mentioned here:
androidtablets.net/forum/nook-color-technical/6386-how-installing-using-clockworkmod-rom-manager-nandroid-backup-custom-kernels-20.html#post48469
(sorry, I can't post links yet.) It leaves the device rooted. It worked for me.

[q] need help! Black screen on my verizon galaxy tab 7

I tried a flash and think i messed my tab...now its just a black screen with a faint light in the background like its on but its no images.......my battery icon pops up then distorts away and thats it ....can get into download mode but not recovery.....tried holding all 3 buttons got this lil android dude in the corner with a sign sayin something about power reset but cant select nothing......help me please......
Put it in d/l mode and flash one of the stock roms with Heimdall.
D
i tried a stock flash with heimdall it flashed successfully but i still get the SAMSUNG logo that flashes and go away,buttons light up at the bottom,can go in download mode but not reboot mode,phone stay on with a faint light ,so i assume that its on somehow.....help
Did you follow this exactly?
http://forum.xda-developers.com/showthread.php?t=967175
One thing I missed here before was to wipe data and cache. Otherwise I go into boot loop.
how to get recovery mode
i cant wipe nothing because i cant get to recovery,just download mode
done it step by step
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
chubbyflood said:
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
Click to expand...
Click to collapse
Use UnBrickable Mod
http://forum.xda-developers.com/showthread.php?t=1341753
Although you get a black screen on boot, it might still be working....
Chubbyflood,
If you are in the same situation as I am then the tab is still working, you are just getting black screen on boot up. It played tricks on me for ages when I was first rooting by tablet; but it turned out it is just the boot up screen that isn't showing.
This is my situation:
-Press and hold Power button to turn on.
-I see the Galaxy Tab / Samsung initial boot image for about 1 second, and also hear the "boot chime"
-Then the screen goes completely blank (but you can tell it is still on with a little light showing.
-The four "hard button" lights will light up briefly a couple times
-Wait approximately 30 seconds to a minute (to be safe and give the tablet time to boot up - it is actually booting up)
-Tab the Power button once, to turn the tablet off (now the screen is clearly off)
-Tab the Power button again, and the tablet will be up and running as normal.
I am guessing the boot animation / images are failing in some way, but the tablet is booting up as normal.
I've just learned to live with it, because I haven't had a chance to figure out what's going on, but it honestly took me a good hour or so, and a few (unnecessary) flashes, before I realized the thing was up and running fine, it just need to have the button pressed on and off.
One final thing to mention; don't have the tablet plugged into anything. I seem to remember leaving it plugged into the PC didn't help (I think).
Hope that makes sense.
Cheers
Ed.
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Juiced_RL said:
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Click to expand...
Click to collapse
Have you found a resolution to this? Mine tab is doing the exact same thing as yours after the cubed rom.

[Q] Bootloop, can't get phone to stay in Download mode to reflash

Hi all
I reflashed an old i9000 with CM10.1 for my wife recently, and everything seemed to be working fine. Then it started behaving a bit funny and this week it started rebooting at random. I thought "no worries, I'll just do a fresh flash with stock GB".
However, before I could even give that a go the phone started acting even weirder. As soon as I put the battery in it powers on (without me even pushing the button) but it resets every time it hits the Samsung splash screen. Earlier today I could get it to go into CWM recovery and after clearing cache I actually got it to boot up. But by the time I had downloaded the stock GB files the phone was just constantly resetting at the Samsung logo and now I can't even get it to load CWM recovery using the 3-button method.
I can get it to enter Download mode, and it shows up in Odin just fine. But within 5 seconds it resets itself again so I can't actually perform a flash.
Any suggestions? Or is the phone just plain busted?
mrfurion said:
Hi all
I reflashed an old i9000 with CM10.1 for my wife recently, and everything seemed to be working fine. Then it started behaving a bit funny and this week it started rebooting at random. I thought "no worries, I'll just do a fresh flash with stock GB".
However, before I could even give that a go the phone started acting even weirder. As soon as I put the battery in it powers on (without me even pushing the button) but it resets every time it hits the Samsung splash screen. Earlier today I could get it to go into CWM recovery and after clearing cache I actually got it to boot up. But by the time I had downloaded the stock GB files the phone was just constantly resetting at the Samsung logo and now I can't even get it to load CWM recovery using the 3-button method.
I can get it to enter Download mode, and it shows up in Odin just fine. But within 5 seconds it resets itself again so I can't actually perform a flash.
Any suggestions? Or is the phone just plain busted?
Click to expand...
Click to collapse
I'm just going to answer my own question as I've solved the problem but it may benefit someone else to know how.
It got to the point where the phone wasn't even booting to the Samsung splash screen, but I could still get Download mode to show up for 5 seconds (not long enough to flash). Then in a moment of desperation I got the original Samsung microUSB cable and plugged that in, and booted into Download mode again. This time Download mode stuck! And I was able to flash a clean GB ROM which is now working fine.
So the take-out from my experience is this: sometimes you really do have to use the original Samsung USB cable.
Weird.
Thanks for reporting howto ...:good: good to know
mrfurion said:
I'm just going to answer my own question as I've solved the problem but it may benefit someone else to know how.
It got to the point where the phone wasn't even booting to the Samsung splash screen, but I could still get Download mode to show up for 5 seconds (not long enough to flash). Then in a moment of desperation I got the original Samsung microUSB cable and plugged that in, and booted into Download mode again. This time Download mode stuck! And I was able to flash a clean GB ROM which is now working fine.
So the take-out from my experience is this: sometimes you really do have to use the original Samsung USB cable.
Weird.
Click to expand...
Click to collapse
mrfurion said:
I'm just going to answer my own question as I've solved the problem but it may benefit someone else to know how.
It got to the point where the phone wasn't even booting to the Samsung splash screen, but I could still get Download mode to show up for 5 seconds (not long enough to flash). Then in a moment of desperation I got the original Samsung microUSB cable and plugged that in, and booted into Download mode again. This time Download mode stuck! And I was able to flash a clean GB ROM which is now working fine.
So the take-out from my experience is this: sometimes you really do have to use the original Samsung USB cable.
Weird.
Click to expand...
Click to collapse
I have a similar issue where I'm trying to flash my stock ROM on my Epic4gTouch. When it opens up the download mode error I start to flash and all seems to work before it reboots. Every 5 seconds. I tried the original cable and it did not help. Any ideas??
NerdsBestAdvice said:
I have a similar issue where I'm trying to flash my stock ROM on my Epic4gTouch. When it opens up the download mode error I start to flash and all seems to work before it reboots. Every 5 seconds. I tried the original cable and it did not help. Any ideas??
Click to expand...
Click to collapse
put the cable and press button power the phone go mode charging at this time make the phone in download mode
its ok for me:good:

Stuck on AT&T logo and cannot enter recovery mode

This is my first post, but I've had my phone rooted for a few months now with no problems until today out of the blue. What I've done to root my phone in the first place was flash to 4.4.2 NE3, root it, then upgrade to 5.0.1 OC 7 DeOdexed while keeping the root according to the link below. And then I put Xposed framework on it.
https://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355
And this has worked well for me for a few months since that was back at the end of December. Flash forward to today when my phone was being rather slow to respond to my actions so I decided to restart it. And upon restarting it, it's been stuck on the AT&T logo screen for a very long time. I can power it down with the power button, but think it actually just restarts it because then it boot ups again on its own. I cannot enter recovery mode with power+home+volume up, but I can get to the custom OS screen with power+volume down. My computer cannot see it as an adb device either. I've also tried removing the SIM card and the SD card and it's still gets stuck at the AT&T logo.
I've done nothing different with the OS or Xposed recently. The only new thing was about 2 hours prior to restarting it, I connected it to my computer to transfer some video files to the sd card. While I had it connecting to the computer and looking at the files on it through the phone's My Apps, it was sluggish to respond to my actions. But after disconnecting it, it was fine. I don't know if this is related, but I haven't done anything else different with it. Is there anyway to get my phone to boot up correctly? Or am I going to have to reflash it all over again? Thank you for any help.
Edit: I can enter recovery mode and I tried wiping the cache. It still gets stuck at the AT&T logo screen. I should also note that it no longer shows the Samsung "custom" boot screen anymore like it used to after rooting, now it just has the default Samsung boot screen, so it would certainly seem like my OS has been corrupted.

Categories

Resources