Anyone one else experiencing a stall when rebooting using SKy ICS 4,2F-4.5A?
If I reboot either from CWM or from using the drop down or the power button, the phone hangs up with a black screen and all the LED buttons lit up? Then I have to hold the power button down to do a hard reboot.
I have reflashed numerous times and have come through numerous updates and this one issue persists.
Anyone?
Rogers
Kernel RUXLF3
Update 4.2F - 4.5A
Radio:UCLF5
No problem here. You have installed busy box, fixed permissions, and the usual stuff?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I got the exact same issue, busy box installed, permissions fixed. Tried flashing everything again didn't solve it, kernel etc.
The only thing I didn't try is radio, are you using rogers radio as well?
Also it happens if I just try shut down the phone.
Try doing a backup in cwm, then just immediately restore that backup... often fixes that problem for me on sky ics.
kishke said:
I got the exact same issue, busy box installed, permissions fixed. Tried flashing everything again didn't solve it, kernel etc.
The only thing I didn't try is radio, are you using rogers radio as well?
Also it happens if I just try shut down the phone.
Click to expand...
Click to collapse
I got it resolved but only by fluke. Flashed 4.2-5b as well as the CYMBALINE kernel (an attempt to resolve bluetooth connection issues) and now everything boots fine.
Thanks
I flashed the kernel without it being solved. I did the backup+restore and I think it seems to have fixed it, I'll do some more checking tomorrow kinda late here but thanks!
Btw after you flashed 4.5a you didn't need to flash b
Had the same problem after doing a fresh 4.2 R2 base install. I let the phone fully cache (5 mins or so) and I tried rebooting to CWM to flash the 5A update and the phone hung on shutdown and my cap lights stayed lit up. I realized I forgot to install busybox after 1st boot-up per the OP instructions. So I held power button for 10secs, rebooted, installed busybox and it rebooted fine into CWM to flash update. Weird, never seen that before.
DudelePOWski said:
Anyone one else experiencing a stall when rebooting using SKy ICS 4,2F-4.5A?
If I reboot either from CWM or from using the drop down or the power button, the phone hangs up with a black screen and all the LED buttons lit up? Then I have to hold the power button down to do a hard reboot.
I have reflashed numerous times and have come through numerous updates and this one issue persists.
Anyone?
Rogers
Kernel RUXLF3
Update 4.2F - 4.5A
Radio:UCLF5
Click to expand...
Click to collapse
Running Rogers ICS stock here rooted and busybox first, then flashed the modded UXCLF3 Kernel, hangs on the Rogers animation and the touch keys stay on whenever I try to shut down or reboot the phone, have to pull the battery all the time, trying the Backup + Restore route now, hope it works otherwise I'll have a brick and a phone that won't turn off
howlingmoon12 said:
Running Rogers ICS stock here rooted and busybox first, then flashed the modded UXCLF3 Kernel, hangs on the Rogers animation and the touch keys stay on whenever I try to shut down or reboot the phone, have to pull the battery all the time, trying the Backup + Restore route now, hope it works otherwise I'll have a brick and a phone that won't turn off
Click to expand...
Click to collapse
It worked for me, worst case you can hold the power key for 10s to turn it off.
The issue me and I think also the other guy had was black screen and touch key lights.
DudelePOWski said:
Anyone one else experiencing a stall when rebooting using SKy ICS 4,2F-4.5A?
If I reboot either from CWM or from using the drop down or the power button, the phone hangs up with a black screen and all the LED buttons lit up? Then I have to hold the power button down to do a hard reboot.
I have reflashed numerous times and have come through numerous updates and this one issue persists.
Anyone?
Rogers
Kernel RUXLF3
Update 4.2F - 4.5A
Radio:UCLF5
Click to expand...
Click to collapse
This has been answered in the dev thread. Here is the solution . You need to flash it with cwm touch. I have no idea why but with cwm the older cwm you get hung up rebooting or shutting down. It will also hang when fixing permissions. I have also read that twrp was working also.
Cwm touch can be found here half way down the thread.
http://forum.xda-developers.com/showthread.php?t=1704630
Sent from my SAMSUNG-SGH-I727 using xda premium
I had it and I'm using cwm touch 5.8.1.3 .
if all else fails check the md5 checksums of all downlads, or redownload and check its md5, use touch cwm or as sean is using it now twrp recovery, and read my sig
kishke said:
I flashed the kernel without it being solved. I did the backup+restore and I think it seems to have fixed it, I'll do some more checking tomorrow kinda late here but thanks!
Btw after you flashed 4.5a you didn't need to flash b
Click to expand...
Click to collapse
I went from 4.5a update (fresh base install) to 5b update.
Related
Ok, so I did my first root last night with my G2x and flashed CM7 onto it using the instructions here for GB. The process didn't seem to go through at first because it kind of froze for awhile, but when I took out the battery and put it back in it loaded up. (I understand I may have made a mistake here.)
I thought all was good but then I tried to boot up Clockwork recovery to flash the GAPPs zip and everytime I tried it wouldn't go through the screens it is supposed to.
I'd hold the down volume and power buttons and the first LG (white) would show. Then it would bring up a cyan colored horizontal loading bar under the LG. I continue to hold the buttons hoping to see the cyan LG but then screen changes to a box with an orange arrow pointing to an android logo. There is a loading bar under this as well. If I let go here it loads up CM7 but if I continue holding on it takes me to the S/W screen.
I've tried this multiple times but I've kinda given up. I even tried individually installing the apks from the GAPPS zip but only a few of them successfully installed.
At a loss .Please let me know what I can do.
Let me guess. You flashed CWM via ROM manager?
Follow he guide here and let us know how it goes:
http://forum.xda-developers.com/showthread.php?t=1056847
Also, before you install the ROM use the wipe tool in my sig.
I appreciate the response but I did use that thread to flash it.
ae2012 said:
Ok, so I did my first root last night with my G2x and flashed CM7 onto it using the instructions here for GB. The process didn't seem to go through at first because it kind of froze for awhile, but when I took out the battery and put it back in it loaded up. (I understand I may have made a mistake here.)
I thought all was good but then I tried to boot up Clockwork recovery to flash the GAPPs zip and everytime I tried it wouldn't go through the screens it is supposed to.
I'd hold the down volume and power buttons and the first LG (white) would show. Then it would bring up a cyan colored horizontal loading bar under the LG. I continue to hold the buttons hoping to see the cyan LG but then screen changes to a box with an orange arrow pointing to an android logo. There is a loading bar under this as well. If I let go here it loads up CM7 but if I continue holding on it takes me to the S/W screen.
I've tried this multiple times but I've kinda given up. I even tried individually installing the apks from the GAPPS zip but only a few of them successfully installed.
At a loss .Please let me know what I can do.
Click to expand...
Click to collapse
When it get to the point where "the cyan colored horizontal loading bar" let go of the volume and power button and see if it boots into CWM.
Ok, I tried that and it went to that android logo screen again. Then it went to a black screen and then the cyan LG logo screen. From there it booted up CM7.
I just noticed when I try to boot into Clockwork it erases everything I added to it including contacts and apps I installed.
ae2012 said:
Ok, I tried that and it went to that android logo screen again. Then it went to a black screen and then the cyan LG logo screen. From there it booted up CM7.
I just noticed when I try to boot into Clockwork it erases everything I added to it including contacts and apps I installed.
Click to expand...
Click to collapse
Try rooting process all over again... just make sure battery have plenty of charge and make sure during any of the process there's no interruptions... let us know what happen after that...
Sent from my LG-P999 using xda premium
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
No need to unroot... as long as your computer still detect your phone... just flash everything again... I mean since you want to root... I would just do all the rooting process again... and reflash clock work... don't use rom manager to flash clockwork mod...
Or
And since you can't get into clockwork... you can just try flashing clockwork again... no rom manager
Sent from my LG-P999 using xda premium
Sweet, so I reflashed CWR and CM7 and I got my contacts back and several other minor issues were corrected.
I am experiencing a new problem now though. Whenever I try to download from the market it tells me "[App name] could not be downloaded due to an error."
What can be done to fix this?
ae2012 said:
Sweet, so I reflashed CWR and CM7 and I got my contacts back and several other minor issues were corrected.
I am experiencing a new problem now though. Whenever I try to download from the market it tells me "[App name] could not be downloaded due to an error."
What can be done to fix this?
Click to expand...
Click to collapse
Try flashing Google apps again. Cm7 doesn't include them in their builds.
Sent from my LG-P999
Worked like a charm. Thanks, yall are the best.
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
Rom Manager is not a safe alternative. Stay with Nvidia ClockworkMod.
Its should be a blue lg logo when you have to let go of the buttons.
Sent from my LG-P999 using xda premium
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
Every time before you re- flash a rom I would recommend doing a data/factory reset within clockwork recovery. then Wipe your cache. And then even a wipe of the dalvic cache under advanced settings. Then flash the rom then gapps. Then reboot. Its called doing a clean install. It just makes everything smoother when re- flashing. And if your apps ever not update like that again just fix the permissions in clockworkmod then reboot. It usually fixes it. And i don't recommend flashing directly from the rom manager. Do it from recovery instead. Hope this helps.:thumbup:
Sent from my LG-P999 using XDA
[edit]
Sent from my G2X.
Rocking stock CM 7.2.0-RC1
Similar issue, totally different outcome...
Ladies and Gentlemen (and low-lifes),
I have found myself in a similar situation, after recently flashing a ROM, to where I am now unable to boot into CW Recovery. The ROM flashed is working fine but when I attempt to boot into recovery I get a black screen and it never progresses beyond that. I have attempted to reflash of course via NVFlasher and from all indications it's been a successful flash. That said, the results remain the same... black screen.
FYI: I have not yet attempted to flash back to Stock Recovery.
•Current Rom - Owain's Domination v77 (a great ROM by the way)
•Current kernel - Harsh's 3.0.32
•Used Nullifier to prep device for ROM install (as I have been doing for sometime now)
If anyone has any experience w/this issue or any advice going forward I would greatly appreciate it.
UPDATE: (that was fast huh?) .................................................................................................................................................................................................
So I went ahead and flashed the Stock Recovery, tested and got access. I then flashed CWM 5.0.2.0 and to my delight was able to see the CWM console. I let go of the power and volume down buttons and the phone rebooted. Now the ROM will not boot, just sits in a forever cycle on the splash screen and the results continue to be the same as recently mentioned for attempting to get into the freshly flashed recovery.
dark ma++er said:
UPDATE: (that was fast huh?) .................................................................................................................................................................................................
So I went ahead and flashed the Stock Recovery, tested and got access. I then flashed CWM 5.0.2.0 and to my delight was able to see the CWM console. I let go of the power and volume down buttons and the phone rebooted. Now the ROM will not boot, just sits in a forever cycle on the splash screen and the results continue to be the same as recently mentioned for attempting to get into the freshly flashed recovery.
Click to expand...
Click to collapse
Ok, I will bring my concerns to an end now. I forced CWM to remain in play by not letting go of the power and vol. down buttons then using my thumb to see if I could stroll through options in CWM. Once I accessed a few it remain stable. I nullified and re-flashed my ROM and all seems ok in my personal corner of the universe. I am now able to boot into CWM without issue.
I posted a thread a few days ago about not being able to power off or restart my Samsung Galaxy s2 skyrocket on ATT. I am using SKy's ICS rom http://forum.xda-developers.com/showthread.php?t=1602216 with the newest update and I still cannot turn it off. The response I got was to use the Darkside Wipe, I tried that, loaded the base rom, then rebooted (it rebooted on its own) flashed the update, and now im back to it not being able to turn off.... I have searched every where and everyone says the issue is resolved, but its not working. Please point me in the right direction to fix this issue.
Pull the battery
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Ive lived without if i need to reboot then hold power till it reboots and if i need recovery then do the same but press volume buttons right as it shuts down
Sent from my SAMSUNG-SGH-I727 using xda premium
Thank you! Did't want to have to pull the battery anytime I needed to restart my phone. Holding the power button in for 10-15 seconds even when its froze forces it to restart. At least now I can put my case back on it....
I was wondering if anyone knew a way to stop it from freezing up? Or at least know whats causing it?
I had this problem too with the Ics roms. If you use the touch recovery to wipe factory data reset it should work. I used to one recommended in the sky Ics thread and had no problems after that.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
irtnerapleasure
Do you have a link to it? I have been looking for options and I must be missing it.
I did do the Dark Side complete wipe, and after it worked, it stopped working when I applied the update.
perkinsjm said:
Do you have a link to it? I have been looking for options and I must be missing it.
I did do the Dark Side complete wipe, and after it worked, it stopped working when I applied the update.
Click to expand...
Click to collapse
Just factory wipe, wipe cache, dalvik in whatever cwm you have
Ill try that again, and redownload the patch and see if that fixes it. Is there anyway to get an error log to see whats FCing or crashing?
perkinsjm said:
Ill try that again, and redownload the patch and see if that fixes it. Is there anyway to get an error log to see whats FCing or crashing?
Click to expand...
Click to collapse
Logcat with adb
I had to reset my phone so I pulled the battery and everything went smoothly until I hit the lockscreen. The lockscreen will load up, but at a really slow pace, I let it sit like that for a while waiting for everything to load. Once the screen went black I hit the power/unlock key and the backlight will light up, but no image will appear on the screen. I am rooted running ICS
squid4 said:
I had to reset my phone so I pulled the battery and everything went smoothly until I hit the lockscreen. The lockscreen will load up, but at a really slow pace, I let it sit like that for a while waiting for everything to load. Once the screen went black I hit the power/unlock key and the backlight will light up, but no image will appear on the screen. I am rooted running ICS
Click to expand...
Click to collapse
What did you do exactly?
I had to reset my phone so I pulled the battery and everything went smoothly until I hit the lockscreen.
Click to expand...
Click to collapse
Since when does pulling the battery reset phone?
If you have recovery, try factory reset or fxz or flash a new ROM.
Sounds like a black screen kexec problem. And possibly an OC issue? What did you flash? More info goes a lot further for anyone to help.
Sent from my MB865 using xda premium
squid4 said:
Once the screen went black I hit the power/unlock key and the backlight will light up, but no image will appear on the screen. I am rooted running ICS
Click to expand...
Click to collapse
First things first, can you reboot your phone? If so, try it and see whether it makes a difference.
If you're using BMM and haven't touched system 1 (stock ICS) and its always the same problem when you reboot I suggest you delete the rom. Delete the system partitions from BMM menu while booting.
If you aren't using BMM or if you flashed this rom on system 1 and cannot boot into anything, then fxz back to ICS.
Hope I helped, it would also be useful to give a bit more information as the previous two users have said
Sent from my MB865 using xda app-developers app
Well I reset my phone because it was running a bit slow so i figured a reset wouldn't hurt. I was running stock ICS just rooted, not OC'ed at all. I guess I was being a little too worried because it's running fine now. All I did was go and flashed ICS. Thanks for the help guys.
Hello all,
So I'm getting desperate.
I've tried everything I can think of but I'm positive my Infuse is dying. I've reset it to factory, rooted it to remove junk apps, flashed a custom rom and kernel, etc, etc. The problem is every few hours or days it will simply stop responding. I can hear the beep when I go to unlock it or turn an alarm off but the screen stays blank and the only way I've found to fix it is to remove the battery and reboot (especially annoyng if I'm using it as an alarm clock and have to remove my case, take the back off and remove the battery to stop the alarm.
Anyone have any ideas?
phazer11 said:
Hello all,
So I'm getting desperate.
I've tried everything I can think of but I'm positive my Infuse is dying. I've reset it to factory, rooted it to remove junk apps, flashed a custom rom and kernel, etc, etc. The problem is every few hours or days it will simply stop responding. I can hear the beep when I go to unlock it or turn an alarm off but the screen stays blank and the only way I've found to fix it is to remove the battery and reboot (especially annoyng if I'm using it as an alarm clock and have to remove my case, take the back off and remove the battery to stop the alarm.
Anyone have any ideas?
Click to expand...
Click to collapse
not enough info.
if you post questions..include the rom, the history, the build, the modem etc
you may be getting the infamous SOD (screen of death) - some app or kernel conflict. Touch response will stop. If you hold the power putton for 20-30 sec, the device will reboot without battery pull.
possible solution: find conflicting app or kernel
use different rom + kernel
use stock gb
use stock froyo
Oh I thought I mentioned. It's a stock rom ( that I rooted with one of the one click tools or Goomanager I'd have to check which) I have CWM recovery 2.5.1.3 Voodoo lagfix installed but everything else is stock but for the root
Either way the only way to get out of these freezes is to take the battery out. Holding the power button down does squat (believe me I've tried all the usual tricks)
Modem wise I can't remember and will have to see if I can find it tommorrow usingthe one click tool it's a USA phone on AT&T if that helps,
phazer11 said:
Oh I thought I mentioned. It's a stock rom ( that I rooted with one of the one click tools or Goomanager I'd have to check which) I have CWM recovery 2.5.1.3 Voodoo lagfix installed but everything else is stock but for the root
Either way the only way to get out of these freezes is to take the battery out. Holding the power button down does squat (believe me I've tried all the usual tricks)
Modem wise I can't remember and will have to see if I can find it tommorrow usingthe one click tool it's a USA phone on AT&T if that helps,
Click to expand...
Click to collapse
Running stock with voodoo. .. if you get sod, it could be from voodoo mismatch.
You can try:
Back up your info
Find voodoo folder in sdcard..delete
Under settings/privacy.. factory reset.
Go to download mode
Odin or heimdall back to stock with repartition
Run as stock unrooted for a few days to see if anything happens
Restore nothing...
If you still see it... it may be hardware
If you don't see it, it's something you installed or restore or file mismatch
You didn't mention but I'll add that you shouldn't add any tweaks. . They can destabilize the os
Having some serious stability issues. Was using catalysm rom and things were... okay. Tried to flash pure nexus with franco and phone didn't wanna boot then was boot looping then would hang on the little circles boot screen. Then tried Screw'd, which I'm using right now, but notice that when the phone sits it also wants to reboot itself but when it does, all it does is bootloop at the google screen or the screw'd bootlogo screen. Doesn't want to start unless I just play around with button combinations until it finally wants to act right. As my daily phone this is a huge disturbance. Also I'm on elemental 6.11
Possible power button problem that is causing the reboots?
and its all fine on stock rom?, i would flash system and boot.img, wipe cache and see how you get on, whenever you get instability problems you go back to stock and see if its hardware related
republicano said:
and its all fine on stock rom?, i would flash system and boot.img, wipe cache and see how you get on, whenever you get instability problems you go back to stock and see if its hardware related
Click to expand...
Click to collapse
Don't know about stock, got the phone rooted with catalysm installed
Sounds like power button
Sent from my Nexus 5 using Tapatalk
NexusS4gFreak said:
Don't know about stock, got the phone rooted with catalysm installed
Click to expand...
Click to collapse
Then it would be best for you to flash pure stock through fastboot to rule out software.