I've flashed CM 9.1 rom 2 weeks ago. Everything was perfect (well, ok camera app was a bit laggy). I installed it through CWM, like wiki says.
2 days ago, I was using phone as Navigation, and battery depleted to 0 (phone switched off). When I plugged it into a charger, battery charging animation was displayed, then phone switched off and so on (loop). Same situation is when I power on. CM logo endless loop.
Recovery doesn't start, download mode is working tho.
I checked different battery, same thing.
Is it software related problem ? Should I just flash phone again via ODIN or Heimdall?
I had something similar like this a few months ago because my nephew was pressing random buttons. I did indeed just reflash the phone again. Lucky for me I had a backup of my data so that fixed most of my problems.
Hope you figure it out,
Currently, I've flashed hardcore Kernel (CM wiki page) to flash CM9.1 rom.... it gives me Status 7 error (get.prop("ro.product.device")). Same with CM 10 Nightly.
Flashing Slim ICS gives me Status 0 error.
What should I do?
Hey just flash stock GB firmware via Odin then u r good to go...
Do post results
If my post helped, don't mind hitting THANKS
Yes it helped. Thanks.
Strange tho, stock 2.3.6 feels faster than CM9.1
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.
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.
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?
Hello,
FYI; I'm running a Galaxy S i9000 with Slim Bean 3.1 (4.1.2) and semaphore kernel 2.6.5 (was 2.6.0)
So today I woke up my battery was a low at 5%. But everything was normal and had been for a long time. I fell back asleep as I have the day off.
Woke up an hour or two later and my phone was dead. So I put my phone into charge.
Came back about 40 minutes later, enough charge to boot the phone, check my messages, but as I pressed the power button it just went into bootloop. And it hasn't done anything but that since. Every time I try to turn the phone on, the Galaxy S logo appears, then semaphore kernel logo appears, then disappears and reappears and then the whole process repeats.
And I tried plugging in the phone again to charge, but every time I do, the empty battery icon appears, it disappears and reappears, then turns off and turns back on again to do the exact same thing.
So on and off charge, it won't do anything but repeat a few steps over and over.
I cannot enter recovery, cannot boot the phone, the phone does not respond to being plugged into the charger, but I can enter download mode.
So I started googling and trying to fix my problem.
So far I have tried:
- Several three button combos to enter recovery.
- Using ADB to enter recovery (but as the phone isn't on, this doesn't do anything)
- Pulling out the battery, putting it in holding three button combos
- Trying different batteries
- Charging the phone
- Flashing semaphore JB 2.6.5 using ODIN
So basically the phone is bootlooping; when in charge, charge looping (is that even a thing?); and won't respond to any attempts to boot into recovery or boot at all.
I'm trying to avoid just wiping the phone using ODIN and reinstalling from GB to JB (which I have done before, and know how to do).
I'm currently leaving it to bootloop until the battery is actually dead and then I'll see if I can try all over again. Doubt it though.
Try a Devil I9000 kernel .tar from here:
http://rootaxbox.no-ip.org/derteufel/jellybean/
Bejda said:
Try a Devil I9000 kernel .tar from here:
http://rootaxbox.no-ip.org/derteufel/jellybean/
Click to expand...
Click to collapse
What would that do?
It can be or battery this happens with me if the battery is dead it will only go into download mode.....
Sent from my GT-I9000 using xda premium
Zorigo said:
What would that do?
Click to expand...
Click to collapse
Flash it like you did with semaphore .tar,there's good chances your device will just boot fine as if nothing happened.
Such boot loops are a long unexplained story but if you want to use semaphore try 2.6.6 version if it matches your rom,I was having many cwmless bootloops like you had and it didn't happened anymore since this version.
Ahh thanks for the info
I just got impatient and reinstalled everything from the ground up so everything's okay now and I have semaphore 2.9.x on slim (4.2.2)
Well first things first, I was running a stock Tom lollipop 5.0.1 have a custom twrp 2.8.2 I believe, still have it been having it for a while tried 3.0.2 no difference so I switched back anyways I tried flashing stock rom all of them from T-Mobile starting with the original KitKat rom, I tried the stock 5.1.1 T-Mobile Canadian rom and it worked but it rebooted about every 3 minutes , so after trying many Roms also deleted everything off the phone first through teamwin recovery, I finally got a semi stable Tom which is resurrection remix I have 5.7.0 but had 5.6.9 anyways now it works almost perfect reboots maybe 3 times a day and thats with heavy use, by the way the annoying thing is when it attempts to reboot it gets stuck in the Samsung logo, I remove the battery and reinsert it and it boots like a champ, also if reboot trough os same thing happens, sometimes it won't turn on or take a charge unless I leaves the battery removed for a few minutes about 5. It's gets very annoying have tried so many things nothing seems to fix it and I have 3 batteries so if can't be that and original charger could it be a bad power supply ? I will upload pics in a sec one battery is worse than the other two holds no charge,. Stock rom would get stuck in the T-Mobile logo.
http://i296.photobucket.com/albums/...ds/Screenshot_20160704-231050_zpseseysxpj.png
http://i296.photobucket.com/albums/...ds/Screenshot_20160630-152248_zpsx5s1ybst.png
Well for anyone that has tried everything on their note 4 and ir gets stuck in a bootloop but it does power on and reboots very often, i replaced the battery didnt work so i replaced the power switch and that did the trick, no more reboot or bootloop or the phone not wanting to charge