Related
My SGS II is currently running on:
ROM: CheckROM RevoHD V4
Baseband: I9100XXKI4
Kernel: Dark Knight v2.5.2
Sometimes, the touch screen will no response to any touch. nothing happen no matter how hard i try to press the screen. but the buttons are all working fine.
the only way to get back to normal is i have to switch off the phone by taking out the battery, put it back and restart the phone. and i need to perform this a couple of time before the touch screen get back to normal.
any idea how to rectify this problem?
i already tried a different kernel but the problem still persist.
Sounds like you are having a SOD (Screen of death). Usually happens due to the CPU being overclocked or undervolted.
I would recommend checking with SetCPU or Voltage control apps if you are undervolted.
Another thing worth trying is to create a Nandroid backup of your ROM with CWM then trying to flash a different custom ROM (Hyperdroid, Villain or Foxhound Batista) to see if it persists.
You sometimes don't need to do a battery pull to reboot your phone. If you hold the power key for 10 seconds it will reboot from an SOD
PM me if you need any help
Go back to/reflash stock firmware & see if the problem persists. If it does, then it *might* be an issue with your screen/something else. If not, then it's clearly a rom/kernel issue.
Tq for your suggestion.
Before I flash a different ROM, how to reset the configuration of CPU?
Sent from my GT-I9100 using Tapatalk
Not sure what you mean by "reset the configuration of CPU" What exactly do you mean by that ?
MistahBungle said:
Not sure what you mean by "reset the configuration of CPU" What exactly do you mean by that ?
Click to expand...
Click to collapse
What I meant was to ensure that the configuration is as per stock ROM.
Btw, I already flashed to the stock ROM, as suggested. Now, just wait and see.
Unfortunately, using the stock ROM, I lost the video feature of Google Talk. :-(
Sent from my GT-I9100 using Tapatalk
If you're running stock then you'll be unable to overclock/underclock, etc without root, so the CPU will run up to 1200mhz if that's what you mean ?
I've never used Google Talk (was one of the first things I froze when I rooted my phone), so I can't say how/why it doesn't work for you.
Re: whether you can reproduce the problems you were having with screen responsiveness, let us know after a day or so of running stock whether that issue has resolved itself. As mentioned previously, if not, then there's obviously something with your previous rom/kernel causing that. You could then ask the dev/users of either or both the rom or the kernel for advice about maybe fixing that problem when running same.
gjoe77 said:
What I meant was to ensure that the configuration is as per stock ROM.
Btw, I already flashed to the stock ROM, as suggested. Now, just wait and see.
Unfortunately, using the stock ROM, I lost the video feature of Google Talk. :-(
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
At first I was thinking of configuring the CPU as per stock ROM without flashing it.
But, on second thought, I think it's better to flash it to the stock ROM.
Unfortunately, I am not able to reproduce the error. So, need to monitor it for a few days.
Will update you on the outcome.
Thanks!
Sent from my GT-I9100 using Tapatalk
I just flashed "phone-bricker" ICS rom on my phone. I went to install the roms update, and when it restarted it froze on the first boot up screen.
I've tried to get to:
download mode
CWM
and normal restart
it always freezes on that screen
is there any way I can un-brick my phone?
Am i being trolled?
any power = not bricked
LiLChris06 said:
Am i being trolled?
Click to expand...
Click to collapse
lol no this is really happening, if it means anything it was a cool rom till i shut it down.
felixnigh7 said:
lol no this is really happening, if it means anything it was a cool rom till i shut it down.
Click to expand...
Click to collapse
I just had the same problem with another ICS Rom. I ended up going to recovery and and wipe data/cache.
Pretty sure it's one of the apps that I downloaded since yesterday. Probably Antutu battery saver.
I appreciate all the hard work and sacrifice made by early adopters.
Anything that underclocks your device WILL cause it to crash - this is the case for all I9100 ICS kernels, stock or custom.
It almost surely applies to the I777 leak kernel too, since that build is an older codebase.
Entropy512 said:
Anything that underclocks your device WILL cause it to crash - this is the case for all I9100 ICS kernels, stock or custom.
It almost surely applies to the I777 kernel too, since that build is an older codebase.
Click to expand...
Click to collapse
+1 Don't underclock I had my phone enter a sleep of death and then got really got while it was in my pocket. It then would freeze on boot until I wiped data.
Sent from my GT-I9100 using xda premium
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
avus_m3 said:
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Click to expand...
Click to collapse
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-6
avus_m3 said:
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Click to expand...
Click to collapse
You may want to try a jig, if you haven't updated the bootloaders.
Were you switching between these using nandroid backups?
dandrumheller said:
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
Phone has been plugged in the charger for awhile now...nothing.
AJ Newkirk said:
You may want to try a jig, if you haven't updated the bootloaders.
Were you switching between these using nandroid backups?
Click to expand...
Click to collapse
I only used a nandroid backup for restoring back to the stock rom. For everything else, I used CWM and a zip install.
I'd try pulling the battery and leaving it out for 10-15 mins.
I find it hard to believe that you would brick your phone using a known good .zip file in CWM.
The bootloaders should be intact - so it should be recoverable.
Something else is at play here. Either it is hard locked-up or you have a hardware issue.
I'd also suspect battery or hardware.
Try to get into download mode with the battery out. Use the same sequence, vol+ and vol- then plug in the usb cable. The usb will supply the power. If it won't go into download mode that way then I would suspect hardware rather than battery.
Did you flash ld3 using the one click odin or thru a cwm file?
If a jig doesn't work than the bootloader is most likely corrupted.
10 char this
AJ Newkirk said:
I'd try pulling the battery and leaving it out for 10-15 mins.
I find it hard to believe that you would brick your phone using a known good .zip file in CWM.
The bootloaders should be intact - so it should be recoverable.
Something else is at play here. Either it is hard locked-up or you have a hardware issue.
Click to expand...
Click to collapse
That's what I thought. Like I said, it started the flash but then look like it hung. The progress bar did not move at all. After a bit the phone turned off. What is hard locked-up? I do remember when I first plugged the charger in after the phone died/suspended it did vibrate.
creepyncrawly said:
I'd also suspect battery or hardware.
Try to get into download mode with the battery out. Use the same sequence, vol+ and vol- then plug in the usb cable. The usb will supply the power. If it won't go into download mode that way then I would suspect hardware rather than battery.
Click to expand...
Click to collapse
Phone is basically new. I tried leaving the battery out and holding down the vol keys and plugging into USB. Screen does nothing.
c0ldburn3r said:
Did you flash ld3 using the one click odin or thru a cwm file?
If a jig doesn't work than the bootloader is most likely corrupted.
10 char this
Click to expand...
Click to collapse
As I posted above I only used Odin from the original rooting. Everything else was CWM.
I guess I need to find out how to make a jig and try that as my only remaining option??
Same thing happened to me earlier today when flashing the latest MIUI V4 from UCLD3 in CWM. It flashed without any errors, but upon hitting reboot the device shut off and would not respond to anything. Tried leaving battery out for an hour, tried USB jig, and several other tricks to try to boot into download. Sent the phone off to Mobile Tech Videos for repair
avus_m3 I think your bootloader is corrupt just like mine.... but how?!?
w1209 said:
Same thing happened to me earlier today when flashing the latest MIUI V4 from UCLD3 in CWM. It flashed without any errors, but upon hitting reboot the device shut off and would not respond to anything. Tried leaving battery out for an hour, tried USB jig, and several other tricks to try to boot into download. Sent the phone off to Mobile Tech Videos for repair
avus_m3 I think your bootloader is corrupt just like mine.... but how?!?
Click to expand...
Click to collapse
That's not what I want to hear
I just don't understand how this can happen. Even if lets say worse case scenario the rom is screwed, my battery dies during the update or whatever...I should still be able to get into CWM or at least download mode right?
It's very odd indeed considering MIUI doesn't have a bootloader included either, and according to CWM it flashed without any problems. The only other possibility I could think of is that the ROM got corrupted while copying onto the phone. I checked MD5 checksum after downloading onto my computer but not on my phone before flashing. Still, could a corrupt ROM without bootloader hardbrick the phone? I thought the SGS2 was supposed to be very hard to brick when not flashing something like a bootloader
If the boot loaders and param.lfs are intact you should be able to get download mode (as long as there are no hardware problems).
Recovery on the other hand is in the kernel on our phones so if the kernel did not flash properly it could cause recovery not to work.
I have read somewhere a while back where someone had their battery die during a flash and they had to get different battery altogether to get the phones to power back on - don't know if that is the case here. It was as though their battery would not charge in their phone after it died during the flash. But if you guys know someone close to you that have the same phone I would try their battery just to see. There could be some other hardware malfunction also.
I don't know if cwm recovery touches any of the boot loaders or the param.lfs in the nandroid backup/restore process. As far as flashing a cwm zip one needs to check the zip to make sure the zip dies not contain boot loaders or param.lfs - as long as the zip being flashed does not contain those then it should be pretty safe to flash.
Sent from my SGH-I777 using XDA Premium HD app
If a USB jig doesn't work, I guess call up Samsung and play dumb? Worst thing that will happen is they'll send your phone back to you. Sorry to hear about your bad luck :/
Here's an odd idea... you didn't happen to get water in it, did you?
I hard brick too! I can't get jig to work at all and can't connect to download mode. I was at ~40% battery and flashed AOKP coming from ld3. I hit reboot in recovery and the screen went black.
If I can't get it working tonight I going to AT&T in the morning
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
dayv said:
If the boot loaders and param.lfs are intact you should be able to get download mode (as long as there are no hardware problems).
Recovery on the other hand is in the kernel on our phones so if the kernel did not flash properly it could cause recovery not to work.
I have read somewhere a while back where someone had their battery die during a flash and they had to get different battery altogether to get the phones to power back on - don't know if that is the case here. It was as though their battery would not charge in their phone after it died during the flash. But if you guys know someone close to you that have the same phone I would try their battery just to see. There could be some other hardware malfunction also.
I don't know if cwm recovery touches any of the boot loaders or the param.lfs in the nandroid backup/restore process. As far as flashing a cwm zip one needs to check the zip to make sure the zip dies not contain boot loaders or param.lfs - as long as the zip being flashed does not contain those then it should be pretty safe to flash.
Sent from my SGH-I777 using XDA Premium HD app
Click to expand...
Click to collapse
Using the odin one-click I tried to flash using Mobile ODIN, it only flashed the param.lfs (this was before the helpful instructions from entropy on how to extract properly). Don't know if that has any effect on my problem.
nakedninja42 said:
I hard brick too! I can't get jig to work at all and can't connect to download mode. I was at ~40% battery and flashed AOKP coming from ld3. I hit reboot in recovery and the screen went black.
If I can't get it working tonight I going to AT&T in the morning
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
Using the odin one-click I tried to flash using Mobile ODIN, it only flashed the param.lfs (this was before the helpful instructions from entropy on how to extract properly). Don't know if that has any effect on my problem.
Click to expand...
Click to collapse
Not sure, but if your param.lfs got corrupted that could be your problem.
Sent from my SGH-I777 using XDA Premium HD app
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
w1209 said:
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
Click to expand...
Click to collapse
Yes....coincidence. I have flashed form UCLD3 to AOKP (and CM9) & back more than a few times without issue.
@avus_m3, w1209, and nakedninja42:
With three similar hard bricks, there is a patern. We should gather as much information as possible. What package did you use to put UCLD3 on the phone immediately before the bad flash? Also, exactly what parts did the AOKP or MIUI package that resulted in the bad flash contain?
I used the latest version posted in the thread (I think there is only one LD3 package?): hxxp://goo.im/devs/task650/SGH-I777/Task650_I777_UCLD3_signed.zip
(not allowed to post links yet)
Same for MIUI: hxxp://goo.im/devs/ktoonsez/downloads/miuiandroid_I777-2.4.13b.zip
(not allowed to post links yet)
I know for sure that the MIUI MD5 checksum matched after downloading to my computer. Will see what the MD5 checksum is of the file on my phone after I get it back from MTV. If it is the same there is a definite pattern. If not it was just bad luck and my fault for not verifying it on phone before flashing
w1209 said:
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
Click to expand...
Click to collapse
Just to be clear this did not happen to me directly - just responded as I remember reading somewhere about a battery dying during a flash and that person needing to get another battery to get their phone back to life - again the battery may not have anything to do with what happened hear.
But it does look like this happened to two people after flashing away from ld3 leak - though it just may be coincidental hardware issues. we will see if there are more people who have trouble after flashing the leak.
Sent from my SGH-I777 using XDA Premium HD app
Hello,
For the past months I've been experiencing a lot of problems with my device: The device frozes or slow up with no apparent reason. It happens either when I'm in Whatsapp, or Facebook, or just listening music. It doesn't look to have any special app to behave like that. Locking and unlocking the screen becomes a pain and at some point after freezing it just turns off or reboot. Sometimes it just reboots even when I don't use it.
At the beginning I thought that the problems were related to the operator stock rom, then I jumped to Rootbox rom and nothing has changed. The phone keeps freezing and rebooting.
I've read that it might be related to a RAM issue, but I don't know if still have warranty so I'd like to check out everything else before taking it to a specialist.
Any idea or advice?
Fer
When you were on the 'operator stock ROM', was it rooted stock? My only idea is that it's possibly kernel related, ie unstable kernel. Try flashing full stock unrooted and see what happens? Else yes, probably hardware unfortunately
Sent from a galaxy far, far away
Hopper8 said:
When you were on the 'operator stock ROM', was it rooted stock? My only idea is that it's possibly kernel related, ie unstable kernel. Try flashing full stock unrooted and see what happens? Else yes, probably hardware unfortunately
Sent from a galaxy far, far away
Click to expand...
Click to collapse
before anything. Thank you for your response.
I had experimented this problems with Siyah on stock and The kernel that comes with rootbox (different pone).
i've noticed that battery life has been also greatly reduced.
Fer
I'm not 100% sure what you mean... I'm asking if you've had this problem with stock ROM & stock kernel? No root / custom kernel.
Sent from a galaxy far, far away
I'm 95% sure your battery is about to die.
Is it a genuine samsung battery?
Swap it and see how it goes.
Also, going stock to see if the device behaves funny would be wise, as hopper is trying to tell you there.
Sent from...this is not even my S2
gastonw said:
I'm 95% sure your battery is about to die.
Is it a genuine samsung battery?
Swap it and see how it goes.
Also, going stock to see if the device behaves funny would be wise, as hopper is trying to tell you there.
Sent from...this is not even my S2
Click to expand...
Click to collapse
My wife's phone has the exact same problem. However I had recently returned her phone back to stock jelly bean. I downloaded the original software from sammobile for her carrier (Bell) and didn't expect to have any problems. I think I may try to swap out the battery.
gastonw said:
I'm 95% sure your battery is about to die.
Is it a genuine samsung battery? 2
Click to expand...
Click to collapse
Yeah, it appears to be a genuine Samsung battery.
However, I'll jump back to stock toda y and see how it goes. If that doesnt work I'll get a new battery. Finaly, if that doesnt work I might start thinking on a new phone :'( .
Thanks again to everyone
esponges said:
Yeah, it appears to be a genuine Samsung battery.
However, I'll jump back to stock toda y and see how it goes. If that doesnt work I'll get a new battery. Finaly, if that doesnt work I might start thinking on a new phone :'( .
Thanks again to everyone
Click to expand...
Click to collapse
Can you please keep me updated. My samsung is already on stock. I flashed it using ODIN, using the official carrier firmware and the problems actually started after flashing it. My wife said her keyboard freezes as well. Sometimes the Samsung logo appears and then the phone shuts off, or she is forced to shut it off herself.
What ROM were you currently using?
rizzyc said:
Can you please keep me updated. My samsung is already on stock. I flashed it using ODIN, using the official carrier firmware and the problems actually started after flashing it. My wife said her keyboard freezes as well. Sometimes the Samsung logo appears and then the phone shuts off, or she is forced to shut it off herself.
What ROM were you currently using?
Click to expand...
Click to collapse
This morning I reflashed to stock rom from my carrier, NO ROOT (stock kernel). So far I've had no problems. The phone runs smoothly and the battery life is okay. I have not experimented any of the problems like the ones listed above.
I'll keep informing along the week.
A factory reset + dalvik wipe combo would be wise.
Tho you need CWM or Mobile Odin to wipe dalvik.
PS: Root has got nothing to do with this.
Sent from the little guy
rizzyc said:
Can you please keep me updated. My samsung is already on stock. I flashed it using ODIN, using the official carrier firmware and the problems actually started after flashing it. My wife said her keyboard freezes as well. Sometimes the Samsung logo appears and then the phone shuts off, or she is forced to shut it off herself.
What ROM were you currently using?
Click to expand...
Click to collapse
Sorry, the ROM I was using was Rootbox and the kernel before with stock rom was siyah.
gastonw said:
A factory reset + dalvik wipe combo would be wise.
Tho you need CWM or Mobile Odin to wipe dalvik.
PS: Root has got nothing to do with this.
Sent from the little guy
Click to expand...
Click to collapse
excuse me, but root doesnt change the kernel to a kernel with custom recovery? I say this cuz now with stock kernel im not experimenting any issue, which I had with stock+siyah and rootbox ROM.
No, root gives you admin access to your device.
A custom kernel will give you CWM.
Of course the only way to keep it all stock with root is with Mobile Odin Pro EverRoot option, framaroot, ExynosAbuse and any one-click-root.
Sent from the little guy
I will be eternally grateful if you can help me.
So half an hour ago I was browsing the Internet on my phone when it suddenly turned off. Then it started to start at the Galaxy I9300GT black screen, and booting on that black screen. And the biggest problem is that I cant access to the Recovery Menu (I have latest Philz)
I have not tried to remove the battery, nor accessing the Download Menu, since I am in class now and I cant return to home in about 4 hours. Also, I was using NeatRom 6.3, boeffla kernel 5.1 beta 17, and in the last flashing I formatted the internal SD card, so basically I did a clean install. I can not guess what is happening. This is similar to when I had a brick installing some Xposed software, and I solved it installing old CWM recovery, which I could access into, and basically wiping the hell of it. Is this a problem of Xposed....Or am I facing a SDS..in Android 4.3....
Partition corruption during the unplanned shut down, without recovery you will need Odin to flash a full stock rom or philz.
If you are lucky the emmc chip is still okay, this exact same thing happened to me once.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Partition corruption during the unplanned shut down, without recovery you will need Odin to flash a full stock rom or philz.
If you are lucky the emmc chip is still okay, this exact same thing happened to me once.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Luckily I can access to the Recovery Menu....but for some seconds. Its weird. When I am in the Select Option screen (the one which says if you proceed or you cancel and restart the phone) it shows for some seconds until it then starts again at the title screen, like it autoreboots. Also, there is some insane battery drain, because the back of my phone is somewhat hot. I tried to remove the battery, and plug it again, and although I could not access to the recovery menu for a while later I could get back to the recovery...until it fade off like I previously describe.
Luckily I too have a full stock ROM stored in my home computer. But as I said to you before I had Philz installed and it doesnt show up. So I am planning to install the old Clockworkmod, because the last time I experienced something similar it worked for me.
So, basically, do you think I should be fast and get to the Odin menu before the Select Option screen fades off and gets back to the booting title? And also, what can I do to prevent partition corruption? Is there a way to avoid having that problem again? Mind that before flashing the ROM I formatted the SD card, so it was clean install...
For these moments I will keep the battery on the phone, I dont want more unexpected problems, but I fear for it, since it is consuming battery slowly....
And, if it happens that the emmc chip is not okay...what could I do?
You mean download mode, where you volume up to connect with Odin. If download mode is weird then you may have bigger problems.
To prevent future partition corruption you need to avoid unplanned shut downs -kernel panic due to mods are a likely cause.
I would suggest removing the battery until you can use Odin, there is no point in leaving it to drain.
If the emmc chip is dead then a new motherboard is required.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
You mean download mode, where you volume up to connect with Odin. If download mode is weird then you may have bigger problems.
To prevent future partition corruption you need to avoid unplanned shut downs -kernel panic due to mods are a likely cause.
I would suggest removing the battery until you can use Odin, there is no point in leaving it to drain.
If the emmc chip is dead then a new motherboard is required.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Dude.....I dont know what happened....its REAAAAAAAAAAAAALLY WEIRD.
I REPAIRED IT BY FLASHING CWM.
I could access to Odin, which was Version 3.04 "Model Name ", and then flashed the Clockworkmod, version 6.0.3.2.
And then automatically the phone booted again! I could get to the Neat ROM working again!
Sincerely, I dont know it this was a kernel problem, seeing as how an old CWM got the phone working again. I just cant explain it. I hope you can, because I am now confused and scared of changing to another recovery, seeing how this old CWM works even better than Philz.
I even tried to reboot the phone twice, and it has worked. Strangely the boot sound from Neat ROM has been activated. CWM asked me if I wanted to disable flash to stock recovery option, and I ticked no. It then followed that it may flash stock recovery and lose root access, and event then I ticked no. But when I restarted the ROM I had the root access, and as I said I rebooted twice to recovery, and had CWM, so it was kinda...ok. Maybe Neat ROM doesnt flash the stock Sammy kernel as default option, who knows...
I havent done any wipe, seeing as this is working wonderfully again, without any problem whatsoever...which is reeeally weird. Yeah, I am shocked that I somewhat magically fixed it. Normally this takes about 2 hours...lol.
Also, I have more questions for you. You talked about unplanned shut downs, due to kernel panic because of mods installed. Can you explain this kernel panic thing to me, or share with me a link to a post that explains this problem? And more, do you know about a kernel that doesnt "panic" so much? I have Boeffla 5.1 beta 17, but I am questionig keeping using this, since this problem...
Or maybe it was a panic caused by the recovery? Can recoveries origin such problems? And what recovery do you recommend? Because CWM seems rock stable to me...
Oh, and thanks for your help. I removed the battery as you said...and now that my phone is working again I could check that it was at 20% battery...thank you, I could save a little battery for an emergency flashing thanks to you :good:
Also, this morning while turning on the phone I noticed that there was no boot sound when showing the Neat ROM animation...why suddenly the ROM stopped using the boot sound, when last night it was active after flashing the CWM recovery? I even rebooted the phone twice that night and the sound was activated...but not this morning, why?
Actually boot sound is not a very important feature for me but I am puzzled of why it was working before and not now, and that without touching any boot options....
Check if you still have boot sound PowerOn.ogg in system/ media /audio/ui
JJEgan said:
Check if you still have boot sound PowerOn.ogg in system/ media /audio/ui
Click to expand...
Click to collapse
Yes, it is there, as you said.
I have a similar problem .. what exactly fixed this?
flashing an old CWM? mind guide me to that ...