Hi there,
Have been using ICS on my galaxy s for a couple of months. However this is the second time out of the blue it's decided not to boot for me.
The first time I thought it was because I dropped it and reinstalled gingerbread through Odin, then went back to ICS which was a very lengthy process.
I haven't installed anything, and now after just using the phone as per normal and it's decided to stop working? Any tricks I can do?
Basically it boots up, gets to the loading screen and just does that forever. I can boot into recovery but not sure what I should be doing next.
You could try reflashing your rom from recovery .
I think it's necessary to know which ICS-rom, for example slim ICS 2.8 needs to flash kernel first and then the rom ...
Sent from my GT-I9000 using XDA
Thanks imgibby123, if that is the last resort I may as well try it.
I've actually forgotton which one it is, I flashed ages ago and was very stable it just literally broke itself (a number of apps where crashing this mornign (reader, gmail etcc), so I held down the power button, turned it off as per normal, now the phone won't get passed the loading boot animation).
It was cynogen something, team platypus - I feel stupid I can't recall the details. But the ROM is still on there so I'll try reflashing from recovery.
Edit: It's ICS 4.0.3 RC3.1, so obviously still a RC but still! It worked flawlessly for months before
Thanks for the help.
Related
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
cumanzor said:
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
Click to expand...
Click to collapse
Did you ever get this problem fixed? The reason I ask is because I'm in this same situation.
We seem to be having the same problem also... Nothing has worked for me so far
http://forum.xda-developers.com/showthread.php?t=960419
Pull your battery, pull your sd card, hold the volume button and plug in the usb cord, this will get you into download
Sent from my GT-I9000 using XDA App
Keep hope alive glaze!
Sent using XDA App
Im going to get a jig hopefully all goes well.
This is just so i can learn for if this happens again in the future.
I have been running the cm9 nightly (26th) and today downloaded the 26th GT7 (based on cm9) using goo manager. After flashing the zip i was stuck at the Samsung boot screen and could not enter recovery. I have managed to get my tab back using download mode and restocking using the Overcome guide. the funny thing is, a similar thing happened last night whilst updating my sons Galaxy S.
Is this likely to be simply faulty downloads? Could I have done some thing less drastic to recover?
Cheer
have you checked if md5 hash of the rom you just downloaded is the same?
this problem happened to me once, after i successfully flashed a cm9 rom i was somewhat stucked on the boot animation. the difference is i can access recovery mode. but then i tried reflasing again, minutes haved passed on the boot animation and im close to calling it and reverting back to my nandroid backup but the unexpected happened and my boot up pursued.
lesson is: it pays to wait 5 or maybe 10 minutes before quitting the boot up process.
sorry if i cant provide you much useful information. taking long boot animation is rare(only happened to me once).
Deleted the originally downloaded files and didn't check the md5. Used the goo manager on tab to download so assumed it was fine.
Maybe waiting a little longer during boot would have solved it. I waited a couple of minutes.
Cheers for reply.
Sent from my GT-P1000 using Tapatalk 2
no problem sir! just keep me posted regarding this matter.
cheers!
Apologies for opening a new thread for this. I am unable to reply on the dev thread as I have less than 10 posts. So in reference to the following post, I'd like to contribute some experience I had in the last two weeks.
http://forum.xda-developers.com/showthread.php?t=1627689
Across the space of two weeks, I have had a chance to note this symptom on three devices.
Device 1 SGS i9000
Rooted phone and have been on CM9 for as long as I can remember. Wake up one morning to find phone with BLN on, but no ability to wake the phone (power button, home button, volume buttons, nothing works). Popped the battery out, and the bootloop / no recovery went on forever. Had to Odin flash back to Stock 2.3.6 to start again. Since then, any CM9 (nightlies or RC2) attempted always end up in the bootloop, i.e. stock > flash rom, first boot = bootloop. I figured then if I had to go back to 2.3.6, I'd rather go to JB. First JB tried was HellyBean, and the same thing happened. It was only trying pawitp's current alpha CM10 that it worked. Days later reverted back to ICS (Paranoid Android v1.6) due to lags and bugginess.
Important to note, the CWM kernel I have gone through are 6.0.0.3, 6.0.0.8, 6.0.1.0. And Paranoid Android put me back to 5.5.0.4.
Device 2 SGSi9000
Rooted phone and have been on CM9 for as long as I can remember. Phone cut off and rebooted in the middle of a phone call and ended up in bootloop with no recovery. Exactly the same symptom attempting to get the phone back into any of the CM9 roms (nightlies or RC2). Ended putting the phone on Paranoid Android as well.
Device 3 HTC Sensation
Had a lot of trouble trying to flash CM9 on this using CWM. Random bootloop with no recoveries. CWM at that time was 6.0.0.8, which I had lots of trouble flashing Gapps on. More on this device posted here: http://forum.xda-developers.com/showthread.php?t=1786703
And finally, one other observations across all these devices. Somehow with CWM v6.x.x.x I had rather poor battery life. For instance, on CM9 Nightly 07/23, say I started with 100% charge in the morning at 8am, by 12pm, I would be looking at 80% left. Once a week, I will let the phone shut itself down on low power, and charge without switching the phone on. On any other evenings, I would plug the phone and leave it charging overnight, e.g. at 10pm with only 30% left. I have constantly noticed that within a few minutes, it jumps back to 40%, which is rather odd. A 10% charging achieved within minutes is rather unusual.
I have also noted that, when the SGS i9000s ended in the bootloop / no recovery situation, the phone can never be charged. Plugging the phone for charging will the a blank battery icon lit up, with the swirly thing on top of the icon appeared frozen and it stays that way.
Being on lower version of CWM, in this instance, v5.5.0.4., I can observe the units (observed being the keyword here) charges "normally", i.e. no funny 10% charge achieve within minutes. Also, battery life are much better as well, i.e. only 10% drain between 8am (100%) to 12pm (90%).
So, not being a developer but someone that likes to tinker and observed:
- Is it possible that newer version of CWM potentially have some impact to battery life?
- Is it possible that how CM9 is being flashed onto a phone has potential issue? I find it a bit disturbing on an initial flash from stock to CM9, I had to pop the battery out after the flash initially loads a new CWM onto the phone. Then start the flash again with the newly loaded CWM.
I am hoping all these I have experienced in a short amount of time can be helpful to potentially looking into where issue might be. Most people have one phone and tested across different kernels and ROMs. I had the luxury of testing across three devices on a narrower choices of kernels and ROMs.
For the first SGS paragraph I can relate. EVERY ROM would boot loop. I had to flash to stock With repartition ticked. And then flashed semaphore kernel, and formatted system, data and cache. Then I flashed to whatever ROM and was okay.
Also I seem to have the problem with having to pull the battery after a flash to the new recovery. Only happened a few times, but non the less, still happened. Just make sure you flash twice afterward to make sure
Sent from my GT-I9000 using xda premium
AlwaysDroid said:
For the first SGS paragraph I can relate. EVERY ROM would boot loop. I had to flash to stock With repartition ticked. And then flashed semaphore kernel, and formatted system, data and cache. Then I flashed to whatever ROM and was okay.
Also I seem to have the problem with having to pull the battery after a flash to the new recovery. Only happened a few times, but non the less, still happened. Just make sure you flash twice afterward to make sure
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Yup, on every occasion I mentioned above, wipe (system/data/cache) are part of the ritual. Just didn't mention them.
I just think the battery-pulling feels rather odd. Can understand why it's needed, but just feel odd. Wondered if it'd be better to keep kernel and ROM separate, e.g. flash new kernel via Odin, then simply do ROM. This might be a 'cleaner' method perhaps? It feels almost like flashing kernel as part of the process is like modifying Windows files whilst still in Windows, then do a reboot.
For now I have fear against v6.x.x.x kernels. But will likely go back to it once CM10 is stable. We'll see.
I installed Eryigit's Android 2.3.6 ROM onto my SGP 5 and have this battery charging boot loop. Are there any solutions for this yet?
I have been using RemICS 1.3 with Semaphore kernel on my phone for a few months. I had a few problems with bootloop at first, which was solved completely after i flashed the Semaphore kernel and my phone has been running smoothly ever since.
However, today my phone started freezing and giving errors out of nowhere. I open a simple application like alarm clock and it says the application is stopped. I was only be able to open a few applications. So, I rebooted the phone thinking it would go back to normal. Unfortunately, rebooting revealed that my phone no longer can boot. It passes the kernel screen, goes to the RemICS animation and gets stuck there. Since I could go into Recovery Mode I have tried to restore from the backup I had from 10 days ago when my phone was running perfectly. Did not work. I had another backup from July, did not work, actually made things worse by stucking my phone at Samsung screen. Wiped cache, Wiped dalvik cache, did not work.. Made things worse by putting my phone into loop boot. I have tried flashing Devil kernel and another version of Semaphore kernel. Did not work.. Phone back into being stuck at RemICS logo.
Nothing I do seems to work. It just won't boot. I could try flashing a fresh firmware but I have some info on my memo application that i need to save as well as some text messages.
I really don't know how this happened out of nowhere. How can I save my data? Please help?
I've tried lots of ROMs, and been stuck in boot loops many times.
I've always got out of them by using Odin, and trying different kernels until one works, semaphore, devil, and an old GB one. Out of all the boot loops I've been stuck in there's never been a single time that one of those kernels hasn't worked...
Maybe I've just been lucky??
Edit: on reading again tho it looks to me that its your ROM that is the problem not the kernel.
I recommend using SMS Backup+ (free) from the play store next time
Sent from my GT-I9000 using Tapatalk 2
Hi guys
I have a problem with my Note. I have installed several roms over the last year without any problems. Recently though I had a problem. I had been using about a week or two the ROM SuperNexus but a few days ago the powerbutton started not to work. It would at some moments work and some other moments it wouldn't. Very frustrating. I reinstalled the ROM, still didn't help. Then I installed a different ROM. It worked but not for long. Now it also started to reboot itself every 5 minutes or so. No idea why. I decided then to flash a new kernel. Abyss didn't work like I wanted so I installed Speedmod kernel and then installed the stock JB rom. Now that worked all fine and well. No problems at all, but the weird thing is when it gets to about 20-30% on battery, it reboots and then gets stuck at the bootscreen.
Why would this be? I'm afraid there is something really wrong with the phone. Does anyone have an idea what this could be or how I may be able to fix it?
Thanks in advance
Daniel
Edit: Also should not when it gets stuck at boot, wiping data/reset factory helps. Also when it's stuck at the bootscreen, it does get warm I find.
I just did a test with the App eMMC BrickBug Test and it said that Yes. Insane chip.
DanielG27 said:
Hi guys
I have a problem with my Note. I have installed several roms over the last year without any problems. Recently though I had a problem. I had been using about a week or two the ROM SuperNexus but a few days ago the powerbutton started not to work. It would at some moments work and some other moments it wouldn't. Very frustrating. I reinstalled the ROM, still didn't help. Then I installed a different ROM. It worked but not for long. Now it also started to reboot itself every 5 minutes or so. No idea why. I decided then to flash a new kernel. Abyss didn't work like I wanted so I installed Speedmod kernel and then installed the stock JB rom. Now that worked all fine and well. No problems at all, but the weird thing is when it gets to about 20-30% on battery, it reboots and then gets stuck at the bootscreen.
Why would this be? I'm afraid there is something really wrong with the phone. Does anyone have an idea what this could be or how I may be able to fix it?
Thanks in advance
Daniel
Edit: Also should not when it gets stuck at boot, wiping data/reset factory helps. Also when it's stuck at the bootscreen, it does get warm I find.
Click to expand...
Click to collapse
1. Boot your phone in recovery and flash the latest kernel from here
http://forum.xda-developers.com/showthread.php?t=1789397
2. Restart and allow some time to settle.
3. reboot and do wipe data /factory reset, wipe cache, wipe dalvik
4. Use pc Odin to flash stock ROM from sammobile.com
5. Check if it works and update...