I don't know if there is any benefit to doing nightly reboots but I figure it couldn't hurt so I'm trying to find a script that can restart our Vogue automatically every night at x:xx.
I tried using phoneprioritizer and other widgets but reboot/restart commands don't seem to do anything. Is there anyway to reboot our phone at all besides powering off/on?
you might want to try CM6, since it has reboot option.
Related
Hi,
My roger's dream decided to stop working today (i've only had it for like a week). It's rooted, but I haven't done anything major to it. It was running stably for a couple of days after rooting it so I'm fairly confident that it's unrelated.
I wasn't doing much at the time, messing with Klaxon i believe, but it randomly shut off and now whenever it tries to boot, it gets stuck at the splash screen (just playing it over and over).
I've tried booting in safe mode (w/ Home button) and it won't come up. That's about all i know how to do. can anyone help me out with this?
Thanks so much, i'm in a state of crisis right now.
Yea just wipe the phone, reapply the update.zip and it should be good. If that fails. You may need to backup your sd card, wipe that, redo it and put just the apps and apps-private folder back in and link it. (Unless your rom automates that for you)
You can also try in the recovery console from cy the alt-x to terminal, then type fix_permissions and do a fix ext filesystems. That may restore you as well.
Does pressing Power + camera key get you into the fastboot screen?
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
since you have tried a lot of things already, you may need to flash the rc29 image in bootloader and re-root your phone, if it still will not work after the rc29 flash, then it is hardware related altogether.
RC29?? Couldn'ty I just flash to 1.5 if it came to that?
themoebius said:
RC29?? Couldn'ty I just flash to 1.5 if it came to that?
Click to expand...
Click to collapse
to unroot you flash the DREAIMG.nbh file because it will overwrite everything.
themoebius said:
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
Click to expand...
Click to collapse
Try adb, USB debugging is usually on with these modded ROMs. See if you can get a logcat to someone who is much more knowledgeable.
Hold on...not to call you out, but im pretty sure cm 4.1.999 HAS NOT been out for 2 weeks...please clarify...did you flash the newest update THEN had problems?
themoebius said:
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
Click to expand...
Click to collapse
I am having the EXACT same problem with CM4.2.4. I certainly hope its not hardware, but it sure "feels" like it. Especially when my G1 is even shutting down from the Recovery Menu. I'll try to unroot and see if that resuscitates it.
Another one....
Have a look at my current issue on this thread: http://forum.xda-developers.com/showthread.php?t=582576. Check to see in bootloader mode what your board type is (it states it at the top for those who don't know).
Mine is currently showing an EVT board, which doesn't exist. I've pulled the battery out and am leaving it for a while. It could be a hardware issue, but I'm not sure. I was having the "fading screen" issue and eventually got back to RC7 (when I could get into recovery).
Which recovery are you using?
I'm running CM 5.0.6. I ran into some weird issues with my phone the trackball not working and the screen not registering touches properly. I thought it was the CM rom so I started messing around with the Modaco sense rom not realizing I was on the wrong radio. So I go back to cyanogen and I can't reboot to the actual rom without going through fastboot because the phone automatically reboots into fastboot. Anyone know why?
Drotheman said:
I'm running CM 5.0.6. I ran into some weird issues with my phone the trackball not working and the screen not registering touches properly. I thought it was the CM rom so I started messing around with the Modaco sense rom not realizing I was on the wrong radio. So I go back to cyanogen and I can't reboot to the actual rom without going through fastboot because the phone automatically reboots into fastboot. Anyone know why?
Click to expand...
Click to collapse
You mentioned your trackball wasn't working. Is it possible that the trackball is permanently in the "on" position, and so always boots to fastboot? You could try fixing the trackball somehow (not really sure...).
Just my opinion on what the problem might be...
Try flashing the radio again, then CM5.0.6.
if the problem was the trackball, would the phone boot in safe mode when it is rebooted using the command line fastboot?
Sounds to me like it can't boot the kernel or system. Try reflashing whatever ROM you're running and make sure you have enough system space for it, i.e. if you wan't to flash an ICS ROM, be sure to have the ICS hboot scheme.
So this morning my phone started rebooting itself every few minutes. I am running Cyanogen and pershoots UC/UV kernal. I having been running this combo with no problems for some time. Anyway this morning I get the reboot problem so I re-flash the rom but not the kernal. Things have being going OK since then (however the phone has frozen twice today). This evening I can not install anything from the Market as it never installs. It just downloads and then force closes before install.
Anything to try short of a full wipe and reinstall?
Try these commands to see what caused the kernel panic/reboot:
cat /proc/last_kmsg
adb shell cat /proc/kmsg
Well I ended up having to wipe and reinstall last night, so I am sure running the log will not work anymore. Let me know if it will and I will run and post it. In the future if I have problems I will remember to do it so that devs can figure out if it is a bug etc.
Hi everyone,
I have a problematic Nexus One. I've googled the issue and read all the corresponding threads and none of them seem to have boot loop issues as bad as mine. At least I dont think so, anyway.
Where should I start? I recently bought the phone off ebay. The seller did clearly state the phone's issues and that he couldn't be bothered fixing it, let alone paying over $200 to send it back to Google to be repaired or replaced (from Australia). Call me a sucker for punishment, but I do like dabbling in electronics so I thought I'd give this a go and hopefully will be successful. It wouldn't bother me if it rebooted once every few days then rebooted again normally but this isn't the case. I'll try to describe it's behaviour as precisely as I an and I sincerely hope the collective expertise on this forum will be able to help me successfully resolve this issue. BTW, I've been using a gorgeous Desire since July.
The Nexus one is running Modaco r21, 4.06.00.12_7 radio, 2.6.32.9 kernel, CMR 2.5.1.0.
1. When the phone has been powered down for at least 5 mins, it will power up as normal. If left alone on the bench or very lightly used ie a few minutes, then pwr button sleep, no problem. If I continue 'sleeping' the phone every few minutes while using it it continues to function normally for a few hours. If I don't 'sleep' the phone and use it continuously, then after about 20 mins it goes into a reboot cycle with the static 'X' going on and off every few seconds then ending up with the continuously on "X" with the unlocked padlock underneath, which is unrecoverable until the battery is pulled.
2. Battery reinserted immediately after removal and the reboot cycle continues. I can boot into the white Recovery or Fastboot sreens but when I select an action like Recovery, the boot loops starts again. Battery pulled and reinserted again, boot loop occurs again. Pull battery and leave it out or powered down with battery inserted for 5 mins, reboots normally. Then point '1' above continues.
3. I have Rom Manager, Titanium and Superuser Permissions installed. I received the phone with Eclair installed and after many attempts managed to install the new radio and Modaco R21. Last night I tried doing a back up via Rom Manager since I cant get into the black Recovery screen and now Titanium and SU are force closing.
This is all I can think of right now and will update with more info as they come to light. I've been trying to install setcpu to see if underclocking will help however I have been unsuccessful due to SU force closing. I am an Android and Linux noob but am always willing to learn. I really would like to get more stability in this phone so I can either use it as my primary or back up.
Thanks in advance for all your help.
Edit. I magaed to do a factory reset when it dont momentarily allow me into Recovery mode. Wiped all data and davlic as well.
My first instinct is that the phone has suffered or is suffering from a heat problem of some type.
Do you have the android SDK set up on your computer? You should be able to flash an aftermarket recovery using the "fastboot flash" commands. You could also use the "adb reboot recovery" command to reboot the phone directly into recovery mode.
I'll give your suggestions a try. What fastboot commands should I be entering? I am an absolute virgin with all this.
Sent from my HTC Desire using XDA App
I think this thread should have some good information for you
Thanks for the link, mate. I'll have a read and I'm sure there'll be more Q's soon.
Sent from my HTC Desire using XDA App
Hi again,
I've installed Android SDK and usb drivers. Where do I go from there? I am a complete newbie at this so please be kind.
julian.kueh i was posting to ask how things have been progressing along this matter?
I got the same problem. No matter what I do, I can get into Recovery. It stay in loop with X
I change twice recover and nothing.