Related
Using Elixir and QuickBoot, you can create a widget in the notifications dropdown with working buttons for power off, reboot, and boot to recovery. The attached screenshot shows mine, which also has four Audio Manager profiles.
I'm using ICS SMOOTH ICE and don't seem to have any reboot or shutdown freezes when I use the options from the power menu. Can anyone else confirm this?
Or you can use switchpro and use the reboot button.
Flash cwm touch, then flash this kernel. This fixed shutdown and reboot for me. Or just hold the power button down for 10 seconds.
http://forum.xda-developers.com/showthread.php?t=1571882
Sent from my fully functional SAMSUNG-SGH-I727 using xda premium
NightHawkUndead said:
Flash cwm touch, then flash this kernel. This fixed shutdown and reboot for me. Or just hold the power button down for 10 seconds.
http://forum.xda-developers.com/showthread.php?t=1571882
Sent from my fully functional SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
What does the expression "fully functional " mean? To me it would mean 100 % bug free, and we all know that is a pipe dream. Of course it could mean "everything works and I haven't found any bugs... yet." But that just means you haven't been using it enough, LOL!
I just got a kick out of the expression. The is a certain arrogance it conveys, though I am pretty sure that is unintentional - I think my Skyrocket will be "fully functional" when it can get up before me and make the coffee.
Freeze shutdown app in titanium. It works fine.
Sent from my SAMSUNG-SGH-I727 using XDA
My new fix
After flashing too many ICS ROM's and mods, I had the restart/reboot freeze and my screen would not automatically turn off, no matter what the timeout setting. Here is how I fixed both:
wipe data/factory reset x3
wipe cache x3
wipe dalvik x3
Darkside wipe x3
flash Superlite 4.2 ROM
wipe data/factory reset
reboot
now, so far, all works - reboot works, screen off is back to normal, ICS goodness.
There shouldn't be any shutdown freezing issues
vatipa said:
I'm using ICS SMOOTH ICE and don't seem to have any reboot or shutdown freezes when I use the options from the power menu. Can anyone else confirm this?
Click to expand...
Click to collapse
Yeah the dev fixed the problem in the ROM so that the shutdown actually worked instead of froze. On the v2 changelog it mentions the shutdown/reboot bug is fixed
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.
I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app
CounterSolar said:
I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Getting into fast boot is tricky...hold down arrow and push power, then release vol after boot.
Are you flashing boot.img properly in fastboot?
OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app
CounterSolar said:
OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The One S isn't offically supported by CWM. It sounds like you need to try and flash the boot.img in fastboot.
Try TWRP...it will be better
Sent whit HTC ONE S
That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app
Yeah dc211 was right. I'm using hboot 1.14, had to go and flash boot.img in fastboot. Install went smoothly after that. Thanks for the input y'all.
Sent from my Nexus 7 using xda app-developers app
boot loop
CounterSolar said:
That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.
I was able to flash 10.0.0 without removing qrngd. So far it hasn't been a problem. I read somewhere that file is some sort of random number generator, but that it isn't clear whether its even used anymore. Also, they say its more of a problem with earlier nightlies, especially with people using HBOOT < 1.14. It might be just junk DNA in the system files, or they may have patched the problem. I will keep my eye on it though, and will report back if I get any spooky behavior.
Sent from my Nexus 7 using xda app-developers app
jazz452 said:
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.
Click to expand...
Click to collapse
That was fixed in the 11/09/12 nightly, so its not an issue anymore.
http://forum.xda-developers.com/showpost.php?p=33867937&postcount=2209
This is the Q&A for the unofficial CM 10.2 for the SGS4G.
Sent from my SGH-T959V using xda premium
Is it just me or is fix permission missing from CWM.
So, apart from GPS not working, as far as you know everything basic is working well?
sent from me
getochkn said:
Is it just me or is fix permission missing from CWM.
Click to expand...
Click to collapse
Yeo, it is. I didn't touch anything related to the recovery except the recovery fstab that I must update to b compatible w the new JB so idk if I have to do anything else to have that feature back or it was CWM by default then, I will find out bout it soon.
itzik2sh said:
So, apart from GPS not working, as far as you know everything basic is working well?
sent from me
Click to expand...
Click to collapse
You can say so
Sent from my SGH-T959V using Tapatalk 2
Damn... I thought there was a chance GPS would somehow be possible I'm starting to think its wishful thinking... Come on samsung
Sent from my SGH-T959V using Tapatalk 2
getochkn said:
Is it just me or is fix permission missing from CWM.
Click to expand...
Click to collapse
I believe koush decided to throw away the fix permissions button in CWM because he said it was largely placebo effect and had no real purpose anymore.
Sent from my Nexus 4 using xda app-developers app
Thanks for all the solutions and answers that I have collected from users around here, I have been able to update the OP for the FAQ (post 3) in the main thread. So either a question is answered here or not, please also have a look over the FAQ @ post 3 in the dev thread to track down the answered common questions, thanks .
Sent from my SGH-T959V using Tapatalk 2
so do you know if external mics work on this Rom?
Ok guys i have flashed near every rom this phone has ever had and never ran into a bootloop problem. So i had CH 10.2 on my phone for 2 days with no hiccups. Then today after letting my phone die completely "battery death" i pluged it in and now it keeps bootlooping and i cant get it into recovery if i hold down volume down + power it loops at the galaxy s 4g starting screen. If i let it go of the power button at the correct time it just bootloops. anyone have any ideas?
http://www.android.com/about/jelly-bean/
Vismis said:
Ok guys i have flashed near every rom this phone has ever had and never ran into a bootloop problem. So i had CH 10.2 on my phone for 2 days with no hiccups. Then today after letting my phone die completely "battery death" i pluged it in and now it keeps bootlooping and i cant get it into recovery if i hold down volume down + power it loops at the galaxy s 4g starting screen. If i let it go of the power button at the correct time it just bootloops. anyone have any ideas?
Click to expand...
Click to collapse
The Recovery Is Volume Up + Volume Down + Power Button
Sent from my SGH-T959V using xda premium
1234west said:
The Recovery Is Volume Up + Volume Down + Power Button
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Ok if i hold that combo it loops the galaxy s 4g splash screen if i hold the combo then let go of the power button at any time during the splash or right when it turns to black then it just normally boots into the Cyanogen boot screen then sits there spinning for going on 2 hours then i just pull the battery any ideas?
Vismis said:
Ok if i hold that combo it loops the galaxy s 4g splash screen if i hold the combo then let go of the power button at any time during the splash or right when it turns to black then it just normally boots into the Cyanogen boot screen then sits there spinning for going on 2 hours then i just pull the battery any ideas?
Click to expand...
Click to collapse
Battery Pull. Hold Vol Up + Vol Down + Power. Whenever The Samsung Galaxy S 4G Splash Screen Comes On, Let Go Of The Power Button And Keep The Volume Buttons Held Down. Should Take You To Recovery
Sent from my SGH-T959V using xda premium
OMG YES!!! I have no idea what i did but i pressed the combo when i plugged it into my computer and it looped the battery screen twice then went straight into CWM recovery did not go through the splash screen like a normal CWM recovery start but whatever i got to remove the rom and flash the new Slim Rom . Anyone have any idea what could have caused this just so i know what to or what not to do in the future ?
Try using adb
Sent from my SGH-T999 using xda app-developers app
To get to CWM recovery on this ROM, simply download 'Quick Boot' application and use it to get to recovery. It works.
Apex launcher crashes as well. I think issue is ROM related. Also, ROM is very heavy, I couldn't find why.
Edit: ROM is snappier after using CM performance features and letting cache do its work.
sent from me
jeffreylin_ said:
That's not very helpful if you can't get past the CyanogenMod splash though.
Click to expand...
Click to collapse
I got through the splash screen on 1st try.
You should check if you worked according to ROM instructions.
I usually always format system as well as wipe everything twice before flashing any new ROM.
I was referring to :
1. the lack of recovery button on power menu.
2. The inability to use hardware keys to get to recovery after flashing this ROM.
Heimdall One-click (in download mode) and try again.
You're right - I missed that option in developer features - it's called 'advanced reboot options'.
I'd suggest you get to download mode - one click heimdall and reflash this ROM after dowble wiping dalvik, cache, and format system.
I've flashed numerous ROMS to my phone before but have never ran into a problem like this.
-I went back to stock
-flashed CM7, as recommended from the OP
-downloaded and flashed CM10.2 but it gets stuck around 75%
I've been on this thread, and the rom thread as well as waiting a bit, hoping to find a solution or it figures itself out. Nothing! Is it unsafe to pull my battery when its at 'Installing update' (75%) for an extended period of time?
Also, i am on CWM 5.0.2.8
Thanks
I flashed it from ICS (Ultragen) and had no problem.
You can try that as well.
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.