I flashed skyicecream everything is okay but there is no status bar at the top of the screen where the att signal, time, battery and wifi and gps logos show when using. Any ideas how to get it back on there.
That usually happens when you flash both the rom and the update at the same time. Flash the rom, then boot up the phone set up Gmail boot back into recovery and flash the update. Reboot and then you're good to go
Sent from my SAMSUNG-SGH-I727 using xda premium
Thanks for the quick response.
Related
My phone was working fine. No changes or mods recently. I unlocked it to check my messages and it went into a reboot loop. Not just a reboot...but a reboot loop. I had to take the battery out. This I am using CM7 Nightly 25 with Og kernel.
Did you try to flash your current rom again via cwm recovery?
Remove the battery from the phone. Put it on it then press vol up plus power button and hold. Choose recovery then try to flash cm7 zip file again without the custom kernel? Does it work?
Sent from my Nexus S using XDA Premium App
What do you mean by unlocked it to check my messages ? Were you referring to SMS & screen lock ? Are you using a setCPU screen-off profile ? Generally such unexplained ghosts tend to disappear across a reboot. It simply could be because you are on a Nightly build which could still have bugs waiting to discovered. You may want to migrate to RC2 release of CM7 for better prosperity.
this just started happening on the new sky ics (real thing) build, and now on superlite-mx 5.1.. ill press a button and even somtimes just pulldown notifcation bar and it will restart and vibrate over and over till i press the power button to restart the phone
Girn said:
this just started happening on the new sky ics (real thing) build, and now on superlite-mx 5.1.. ill press a button and even somtimes just pulldown notifcation bar and it will restart and vibrate over and over till i press the power button to restart the phone
Click to expand...
Click to collapse
Sounds like left over data, bad download, bad flash, or a combo of those
Girn said:
this just started happening on the new sky ics (real thing) build, and now on superlite-mx 5.1.. ill press a button and even somtimes just pulldown notifcation bar and it will restart and vibrate over and over till i press the power button to restart the phone
Click to expand...
Click to collapse
I'm going to make a shot in the dark and ask if u have uclcl5 installed as ur radio. If so I causes major flash issues for me on a fresh rom install. So much so I have to flash cla4 first, then a new from, then cl5 again to get it to work
icenight89 said:
I'm going to make a shot in the dark and ask if u have uclcl5 installed as ur radio. If so I causes major flash issues for me on a fresh rom install. So much so I have to flash cla4 first, then a new from, then cl5 again to get it to work
Click to expand...
Click to collapse
No im using cla4.. I followed all steps and did superwipe. Why is it still bad flashing?
Sent from my SAMSUNG-SGH-I727 using xda premium
Girn said:
No im using cla4.. I followed all steps and did superwipe. Why is it still bad flashing?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
sometimes for no reason band corruption occurs. I suggest the following in can
factory reset 3x
format system 3x
wipe dalvik cache 3x
dark side 2x
Odin back stock
reboot twice
Odin can
dark side again
flash custom rom
I had similar problems to you and this looking procedure cured them.
I have the same problem with my fiancée phone which I am on right now. Shuts off and starts repeatedly vibrating on a stock non rooted phone.... I never got around to rooting this phone, unless she did it and didn't tell me.but assuming this isn't rooted what do I do?
mistaashby said:
I have the same problem with my fiancée phone which I am on right now. Shuts off and starts repeatedly vibrating on a stock non rooted phone.... I never got around to rooting this phone, unless she did it and didn't tell me.but assuming this isn't rooted what do I do?
Click to expand...
Click to collapse
Could be a sticky power button
Sent from my A500 using Tapatalk 2
StolenVW said:
Could be a sticky power button
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
That
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Pull the battery plug in the USB cable and put the battery back in. Charge it. Mine did that when the batt died. Wouldn't even charge etc.. gotta trick it into booting then leave it for a while let it charge. Wipe battery stats if your rooted cwm etc...
Sent from my SAMSUNG-SGH-I727 using xda premium
Dear,
I have strange battery status. previously with gingerbread my battery life normally around 18hrs. After update official OTA to ICS my atrix2 only last 8hrs.
From battery battery information i found out my wifi keep active. From setting wifi already off.
I was wondering this wifi consumes by battery.i already turn on and turn off wifi again.but still same.from battery info still wifi green.
Is there any way to stop wifi consume my battery?
Sent from my MB865 using xda premium
Try re-flash the ROM or wipe battery stat in cwm
Sent from my MB865 using xda premium
atrix2 said:
Try re-flash the ROM or wipe battery stat in cwm
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Sounds like he's on the official OTA so reflashing isn't an option. Go to your wifi settings and hit your menu button. This will bring up "advanced" options. Uncheck all the boxes where wifi may be automatically searching for an access point. Hope this helps.
Thank you all..
My wifi now is ok after i go to recovery mode (default recovery mode) and wipe data/factory reset yesterday. Now battery status was normal,i got 16hr battery life and still have 23% more.
Sent from my MB865 using xda premium
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
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.