PowerBook G4 17" Boots into Open Firmware; Won't boot from HD or Disk

This PBG417 (1GHz/512MB/60GB) has an complex recent history directly related to this problem. It was thought to have a dead logic board, and was given to me for a very insignificant amount of money. I discovered today (at an Authorized Apple Repair center) it merely had a ribbon cable disconnected from the logic board which kept it from powering on, which, when rge cable was reconnected it did on the spot, fully booting (imagine my satisfaction). However, upon getting home, it booted into Open Firmware instead, and offedrs a choice of typing mac-boot or shut-down. Mac-boot takes it to the grey screen where the question mark/Finder guy blink and nothing happens. I put a grey PowerBook G4 17" system disk in, but not the one that shipped with it, hoping it would do. When I try to boot from disk, it goes to Open Firmware, I enter mac-boot, it goes to happy Finder with no question folder, but stays there with the optical drive occasionally making movememts and sounds. If you enter any command besides shut down or mac-boot, iot says unknown word; the command prompt itself is 0> .
I'm not sure the hard drive is seated correctly. When I got the computer, the drive was removed; I put it in an enclosure and installed Tiger on it and put it back in, but apart from connecting the ribbon cable, it just sat in its bay not fixed down. However, it booted correctly the first time it was successfully started.
Finally, the previous owner removed all 23 bottom case screws when he took out the drive and lost them; the Apple repair tech mustered up about 9 and put them in the crucial locations but it's still not screwed down everywhere, although the one time it booted correctly, it had no screws in it.
It seems the computer doesn't read the hard drive or the disk, but the hard drive mau be installed wrong and the disk, while for a 17" was not the one that shipped with this PowerBook 17". The computer is missing many case screws, bnutg booted properly only when there were none it place. I also tried resetting the PMU but am not sure I did reset it because the Apple article isn't clear about which models have which processes. I tied Target Disk Mode but it woujldn't mount/boot.
How can I get the disk out and how to make it boot to the desktop?

You can try to reset NVRAM here is KBase from apple site:
http://docs.info.apple.com/article.html?artnum=42642
and after that reset PRAM in your unit, here is the kbase:
http://docs.info.apple.com/article.html?artnum=2238
If needed you can also tried to reset PMU, here is the kbase:
http://docs.info.apple.com/article.html?artnum=14449
Make sure you choose the correct step for your unit.
If after all the steps your unit still booting up to open firmware then there is possibility that you have corrupt NVRAM which could not be fixed by doing reset except replacing logic board.
Good luck. Hope this help
Flippo

Similar Messages

  • PowerMac G5 will not boot into Open Firmware, or Boot Manager

    I have a PowerMac G5 and it refuses to boot into Open Firmware. I used Command + Option + O + F and held down the Option key. I have tried 3 different Keyboards but no avail.

    Hmmm,
    Does it boot to Single User Mode, CMD+s keys at bootup, if so try...
    /sbin/fsck -fy
    Repeat until it shows no errors fixed.
    (Space between fsck AND -fy important).
    Resolve startup issues and perform disk maintenance with Disk Utility and fsck...
    http://docs.info.apple.com/article.html?artnum=106214
    Does it boot from your Install Disc, or show boot choices  when holding alt at bootup?

  • PowerBook G4 boots to Open Firmware without keyboard access

    Summary:
    Let me provide a little backstory.
    According to the [DARPA Visitor Guidelines|http://www.darpa.mil/body/visitor_guidelines.html] wireless network technology is prohibited from DARPA facilities. Laptops with a wireless card are required to be "disabled at the BIOS level".
    Before an upcoming visit to DARPA I was told that I would need to make sure my laptop wireless card was disabled. I mentioned that Macs don't have BIOS but I'd look into doing it in Open Firmware. The response from DARPA was that no one has ever successfully brought an Apple laptop into the facility, and that I should procure a PC laptop for my visit. Ah, a challenge!
    I booted into Open Firmware (⌘⌥OF), located the wireless card in the device tree, and removed two properties I figured the driver would be searching for: the vendor ID, and the product ID. I exited Open Firmware and continued to boot into Mac OS X v10.5.2.
    Sure enough the System Profiler showed that no wireless card was installed. Success! Now I just need to make the device tree modifications persist between reboots.
    It seemed the solution was to place the Open Firmware commands I issued to disable the card into nvramrc. So I set nvramrc to contain the same commands, and set use-nvramrc? to be true. I rebooted the machine but the card was still detected.
    A bit [more research|http://docs.sun.com/app/docs/doc/805-4436/6j4719c8v?a=view] revealed that the device tree is not created by Open Firmware until after the nvramrc is executed. The solution is to build the device tree in the nvramrc and tell Open Firmware not to rebuild it. The documentation states that this is accomplished with the probe-all, install-console, and banner Forth commands. I added those commands to my nvramrc and rebooted. The contents of nvramrc:
    probe-all install-console banner
    dev wireless
    " device-id" delete-property
    " vendor-id" delete-property
    The outcome... well technically the laptop has wireless disabled. Almost everything is disabled. The machine now boots directly into Open Firmware with a few ominous bits of output and no response from the keyboard.
    no active package
    Apple PowerBook5,6 6.4.9.1f1 BootROM built on 01/21/05 at 10:51:16
    Copyright 1994-2005 Apple Computer, Inc.
    All Rights Reserved.
    Welcome to Open Firmware, the system time and date is 05/06/2008 10:00:00
    Command security mode
    To continue booting, type "mac-boot" and press return.
    To shut down, type "shut-down" and press return.
    ok
    0 > _
    The first sign that something has gone wrong is no active package. The second message just throws another wrench into the works: Command security mode. Yes, the Open Firmware password was enabled. In retrospect this was a bad thing to have set when mucking about in OF. I knew of the RAM change trick (see below) so this was not an issue at the time.
    Question:
    So the question is: What actions do I need to take to return the laptop to a useable state. That is, booting into Mac OS X.
    *Attempted solutions:*
    +1. Reset nvram+
    The first and most obvious solution is to reset nvram using the snag key combination ⌘⌥PR. Unfortunately do to the firmware password being set, [all snag keys have been disabled|http://support.apple.com/kb/HT1352]. This means no target disk mode (⌘T), boot from CD (⌘C), boot from network (⌘N), etc... In any case an attempt at resetting nvram yields an additional message being appended to the Open Firmware screen:
    Release keys to continue!_
    +2. Reset nvram after changing amount RAM in system+
    Luckily there is a work-around to firmware password protection. Changing the amount of RAM installed in the machine should allow the nvram zap snag to function. I removed one of the two 512MB DIMMS in the laptop and started up while holding down ⌘⌥PR. This results in the same message as above:
    Release keys to continue!_
    Not so lucky.
    +3. Reset the Power Management Unit+
    [Resetting the Power Management (PMU)|http://docs.info.apple.com/article.html?artnum=14449] is accomplished by removing the battery and disconnecting the power cord, and then holding down the power button for about 5 seconds. This had no effect besides resetting the system clock to 01/01/1904 00:00:41.
    Getting more desperate...
    +4. Search logic board for CUDA+
    I [opened the machine|http://www.ifixit.com/Guide/Mac/PowerBook-G4-Al-15-Inch-1-5-1-67-BT-2-0 -LR/64] to search for a hidden [CUDA button|http://docs.info.apple.com/article.html?artnum=86760]. As expected, a CUDA button does not exist on this model and the PMU reset is accomplished as noted in attempted solution 3.
    +5. Remove internal battery+
    Well the laptop is open now, so I tried removing the internal memory backup battery and revisited each of the above solutions. No success.
    +6. Remove hard drive+
    Again, since the laptop was open, why not remove the hard drive and see what happens. The machine wasn't even making it to the boot-loader hand-off so I didn't expect this to produce any results. No results produced.
    Thinking crazy thoughts...
    +7. Attempt a firmware update+
    Firmware updates have a side effect of resetting the nvram. Also firmware updates are initiated very early in the startup process by holding down the power button until a tone is heard and the power light flashes. My thought was that I would grab a previous firmware update for this laptop and force it to be reapplied. Unfortunately there have been no updates to this model's firmware.
    +8. Write my own firmware update script+
    While investigating solution #7 I realized that the file BootROMFirmware installed by the firmware updaters for G5s and G4s machines are just Forth programs with a binary payload attached to the end. I learned [Forth|http://en.wikipedia.org/wiki/Forth(programminglanguage)]. The BootROMFirmware files are really cool, since they do everything from drawing the progress bar during the update, uncompressing and check-summing the binary payload, and generally making sure you don't brick your machine. In any case it seem entirely doable to write my own program in Forth and undo the evil I did before. I really only need to flip one bit. I needed the use-nvramrc? variable set to false. So I created this very simple Forth program:
    \ debrickifier
    setenv use-nvramrc? false
    reset-all
    The original firmware file had additional attributes set, a creator and file type of fw99. So I set those two attributes on my file as well. I ran strings on the firmware installer program and guessed that it was copying the file to /System/Library/CoreServices. So this is where I placed my Forth file. Reinstalled the drive and rebooted the laptop while holding down the power key to initiate a firmware install. No dice.
    Its hard to tell why this is failing. The file may in the wrong place, have the wrong permissions. From what I've reviewed in the original files, the setenv and reset-all words should be available. Maybe the Firmware Update utilities are setting some other magic in nvram before the reboot.
    I think I've covered all the different major solutions that I've attempted. Their might be a few more that I've forgotten to mention (like using an external USB keyboard). I still think that getting some Forth to execute via the firmware update mechanism could use some more exploration. My current worst case is that I'll replace the logic board, although I'd hate to do that when I know there are only a few bad bits flipped in a CMOS somewhere.
    I'm hoping to snag the attention of the resident hardware/firmware guru that can shed some light upon the firmware update process, but any help or suggestions would be greatly appreciated.
    Cheers,
    Mark

    For your next DARPA visit, another option might be to buy the cheapest possible third-party wireless card — it doesn't even need to work. Insert it into your Powerbook's CardBus slot before visiting DARPA, and turn Airport off in System Prefs. On arrival at DARPA, remove the card from the Powerbook and hand it to the security guard. Retrieve it from the guard as you leave, and turn Airport back on again when you get home or back to your office. Unable to comply with the letter of the dunderheaded regulation because you have no BIOS, you will be complying with the spirit of it instead, and no one will be the wiser.

  • G5 Boots to Open firmware on Startup every time.

    I have a 2004 model Dual 1.8GHz 2.2Gbs RAM. The problem is that it keeps booting into Open Firmware. Once it gets to Open Firmware and i can mac-boot and start up off the Tiger disc, but I can't get it to find an external firewire OS. I don't have a hard drive in there at the moment but that should not effect this issue, Although I can see the firewire 800 in disk utilities but not on the Firewire 400. And still no Start up folder when i go to startup disk 800 or 400. If I put a hard drive in which i will when the new one arrives I believe i will be able to start up with it but I still think that it might boot into Open Firmware again. (I think a bus is bad maybe the Firewire bus if it is can't I bypass it somehow? so that is won't boot into Open Firmware.
    Note: everything passes Hardware Test
    I have Reset PRAM and NVRAM Rest all

    (Sorry this is in here twice - I'm pretty experienced with Macs and PCs but a little new at message boards - pls forgive)
    Had the same problem. I took mine into a "Mac Genius" at the retail store and he thought he had fixed it by rebuilding the directory. It booted and shut down perfectly while in the store. When I got home it was went right back to booting into open firmware.
    I figured out by accident that the reason it was booting fine in the store was because he was using a cheap SVGA monitor on the DVI output - not the ADB connector I use with my older Apple monitor. Note that Apple has phased these type of connectors out. It gave me a great excuse to upgrade my monitor to a 20" cinema display and everything is working great (can't believe how I've deprived myself all these years).
    If you have an older monitor that uses an ADB connector, try a different monitor that uses the DVI output on your video card. Even a DVI-VGA adapter (one probably came with your computer) with a VGA monitor is sufficient for testing. If your computer boots up, it's either the older monitor, or the ADB output on the video card that is bad. There is no easy way to know where the actual problem resides (the Geniuses couldn't tell me - they have no monitors in the store with ADB connectors), but I can tell you that my computer is working fine now. I do know that the ADB connector ran power, USB and video all together and that seems to be the reason they quit using them. The newer desktops have only 2 DVI outputs (instead of 1 ADB + 1 DVI), while the new monitors run power, USB and video separately.
    Hope that helps,
    Jeff

  • Computer Beeps and loads into open firmware

    Hello there!
    I've been having this beeping problem intermittently for some time now. Randomly before the startup chime I would hear a single beep from my computer before it restarts and loads normally. According to Apple.com/Support it is a memory problem, I didn't give it much thought since my chips are from my brothers QS2002 G4 1) preinstalled 1) purchased from the Apple Retail Store the computer was purchased from.
    Well I popped open the case recently and noticed there was a strong collection of dust around one of the banks (lacking an air can + my vacuum couldn't get to it) I just moved the chip to the opposite bank. Problem Solved! Right?
    Not! Last night my brother cold booted the computer and I heard from the kitchen the same beep plus this time it booted into open firmware.
    So could this be a problem with my logic board? The Apple Speaker sound port is damaged but I believe it should not affect the rest of the board.
    PM G4 DP 800Mhz 256Ram ~80GBHD   Mac OS X (10.4.9)   2 xtra 512 ram chip, remvd 256 chp. Maxtor 200gb Ext FW H.D.

    Just wanted to update this post with the current status.
    I ran all the tests I could think of (TechTool, Apple Hardware Test) several times with all of the hardware tests passing (the software ones said that some of the bundles of custom/noncustom icon bits were on/off but I used to receive that message thousands of times with Norton back around the turn of the century.)
    While I personally have not heard any tones or seen it boot into open firmware my brother says it still doesn't that randomly and intermittently at times.
    I'm not going to bring it to my Apple Store since if I can't find anything wrong then they probably can't either (that plus I don't want them charging me upwards to a $G for a new logic board "just incase that might be the problem" or not.)
    I'm going to leave this post open until further notice ("just in case" I find something else that is causing it, "just in case .
    QS2001 PM G4 DP 800Mhz 256Ram ~80GBHD   Mac OS X (10.4.9)   2 xtra 512 ram chip, remvd 256 chp. Maxtor 200gb Ext FW H.D.

  • HT3024 after installing airport extreme card into g4 ibook 1.07ghz 512 ram it will only boot to open firmware, any ideas why? please help!

    after installing airport extreme card into g4 ibook 1.07ghz 512 ram it will only boot to open firmware, any ideas why? please help!

    Hi David,
    Have you done a PRAM reset, CMD+Option+p+r...
    http://support.apple.com/kb/HT1379
    In fact, do 3 in a row, takes a bit of time.
    Tried resetting the PMU for PB/iB?
    http://docs.info.apple.com/article.html?artnum=14449

  • Long tone on start up and then goes into open firmware

    I stumbled upon the older posts here and thought I'd add a solution.
    http://discussions.apple.com/thread.jspa?messageID=6115258
    It was about an emac starting up with a long tone and the led flashes a few times and then goes into Open firmware, and when doing "mac-boot" in open firmware, it attempts to start, shows the apple symbol, the screen goes dim and crashes.
    It could be a bad power switch. To confirm - you can remove the emac case, be careful not to touch the motitor's picture tube. Find the cable to the power switch; with a small wire just touch together the black and red wires on the power switch cable (or it might be red and green). This will start the emac. If it boots up and runs OK then the power switch was bad. Not sure where to buy a new switch. I soldered and glued my switch together.
    <Edited by Moderator>

    Or, you'll find both the short pigtail-cabled nVidia graphics driven power switch and the version with a longer cable used with the AIT graphics driven models here* for a good deal less.
    Note that the later ATI version can actually be used with either product generation.
    *I may receive compensation as a result of parts or services being ordered by users specified at the link shown in this message.

  • What command do I type into open firmware to make it install from firewire

    Hi All I am trying too get Leopard onto my G4 cube using the open firmware to fake the clock speed using the below:
    For single CPUs, use the following three lines:
    dev /cpus/PowerPC,G4@0
    d# 867000000 encode-int " clock-frequency" property
    boot cd:,\\:tbxi
    However, my installation is going to be via FIREWIRE so what command do I type into open firmware to make it install from firewire and not CD?
    Many thanks
    Garry

    Hello,
    I wanted to do exactly the same until I discovered LeopardAssist!! No need to bother with code lines! It works just fine and its free!
    http://www.macupdate.com/app/mac/26562/leopardassist/
    Hope this helps.

  • Can't Get into Open Firmware

    Hi there,
    I've got a G3 All-in-One and I can't seem to get into Open firmware properly. I've got the right combination (Option-Apple-O-F) but the screen just goes black. I've tried this on two different units and they do the same thing. Am I missing something?
    Thanks in advance...

    every once in a wile mine does the same thing. but it really is at open firmware its just the screen is so dark you can barly see anything even in a room at night with all the lights out. try doing it in a very dark room and look real close to the screen.try resetting pram first to see if that helps and then try to go into open firmware. I have 2 beige G3 AIO's both do this try to hold the key combo as soon as you start to hear the start chime, then if this dont work try to hold them just after the start chime, and try to hold them at diffrent length's of time first start by trying to jusk keeping the key combo held down, then try realeasing then just after start chime, one of these combo holds should work. but make shure you are in a room that will be dark with the light's turned out cause very faintly you should see the open firmware prompt at the very top left of the screen.
    good luck

  • Strange boot bug; open firmware not working

    Hi!
    I have a powerbook Alu 15", 1.5Ghz. It runs OS X 10.4.2 with the latest security update. My problem started last Saturday.
    The problem is that my pb will not restart nor boot on its own. The computer makes its usual chime, the hard-disk starts to spin for a few second, and then stops suddenly before anything is displayed on the screen (the display does not even light-up). If I press the option key after or before the chime, and keep it pressed, or the shift key, or the c key, or the t key, or the command-option-p-r key combination, or even the command-option-o-f key combination, the behavior is exactly the same: the disk starts to spin for a few second after the chime, and suddenly halts. The computer appears to shutdown on its own before the boot can even start.
    Here is the strange part: the computer boots normally if I press the command key (this key on its own is not suppose to do anything). It also works if I press the command-s or command-v key combination. No other key combination seem to work.
    Except for this strange boot behavior, the computer works flawlessly. I did not have any kernel panic for at least a year, the computer did not crash recently, everything works fine except for one small detail on which I will come back at the end.
    I've tried to fix the problem by the following actions:
    1) Clean install of Tiger with a new partitioning of the disk; I even zeroed the entire disk. This did not change anything so the problem is probably not OS related.
    2) Reset of the PMU with the four finger salute: shift-control-option-power combination. No effect except that I lost the date/time information. Hence the reset worked.
    3) Tried to reset the PRAM, but the command-option-p-r key combination does not seem to work.
    4) Tried to load the open firmware with command-option-o-f, but this does not work either.
    5) Memory seems ok. I have 1x256M of Apple RAM + 1x1G of RAM bought from OWC. I've had the OWC RAM for about a year without any problem. Anyway, I removed the 1G module and tried to boot on the 256M Apple module alone. Exact same behavior. Then I removed the Apple module and put back the 1G module. Exact same boot behavior. So the problem is not with my RAM, unless both modules have simultaneously developed a malfunction.
    6) Tried to run the Apple hardware tests. However, for my machine, these tests come on the install DVD, in a special hidden volume. To boot on this special volume, one needs to boot with the option key depressed, and to select the boot volume from the open firmware interface. But this does not work on my machine, the computer seems to shut down before this interface can be activated!
    So this problem is very strange. I can live with having to press the command key for booting my machine, but I would sure like to know what is going on here. Is the problem hardware related? Perhaps, but as I said, the machine works flawlessly except for the strange boot behavior.
    Is the problem related to firmware? I think that this is the most probable option. What do you think? Maybe, the firmware got slightly corrupted? Maybe a bit got flipped in the flash memory? Is this possible? I guess so. But, what can I do? Should I contact my friendly local repairman?! I have to admit that this option scares me a little bit for such a strange problem. I would need an Apple engineer with boot related experience/expertise!
    Now, here is a little bit of further information. I don't know if its related, but it is also very strange. I work with a dual screen configuration. Usually, I connect my screen and then I wake up the computer. Last week, I noticed that if I connect my second screen live, the system detects it automatically. I guess this is new to Tiger? Anyway, the strange behavior is that the computer then asks me if I want to sleep, restart or shutdown my pb, as if I had pressed the power button. But I did not press this button when I connected the dvi connector >:-o
    Many thank

    Hi Scott!
    Almost every time the PowerBook woke after sleep, I got the 'Are you sure you want to shut down your computer now...' message.
    I get this message upon wake only rarely, but every time I plug or unplug a display live.
    The strange behaviour was tolerable, so I've lived with it for several months. But then when checking out the PowerBook discussions, I read about the failing lower RAM slot problems, and just out of interest, checked out my System Profiler....
    Ok, so the good news is that my pb may continue to work for several months
    My lower RAM slot appears to be ok for now.
    Interestingly, I'm sure that the start-up problems began when I started using my PowerBook with a 23" Apple Cinema Display (a pink hued one, but that's another on-going saga) - and you too have mentioned that you use an external display, so I wonder if that's part of the cause of our start-up problems.
    Yes, I've noticed the 'Are you sure you want to shut down your computer now...' message just a few days before noticing the strange boot problem (not sure if the machine booted in between). I use ViewSonic displays (one at home and one at the office), and several different projectors in different class rooms. From what I read, it is plausible that there is a link between this problem and the dvi port. Could it be that the boot sequence of mb is affected by a hardware problem on the dvi port? But not when a press the command key?!
    Anyway, my machine is no longer under warranty, so I intend to live with the problem for as long as possible...
    But I've been doing more regular backups since then.
    Best wishes to you and your (almost) new machine!
    Marc.

  • Open Firmware Can't boot my WinXP install disc (although the OS sees it)

    So I've been unable to play ANY games on my MacBook Pro under Crossover (games that worked fine under my old 1.8Ghz MacBook Pro) because I get all sorts of weird graphical rendering issues.
    So I thought I'd reboot into windows, install the games there, and see if the problems were related to Crossover or not.
    So I launch Bootcamp Assistant to install Windows XP. I pop in the Windows XP disc (under MacOSX) and I see the disc and all the installer files, and I click to reboot into the Windows installer.
    The laptop reboots and when it comes up I can hear it trying to read the cd. I can hear it switching speedings up and down and moving the read headers. But it never starts the installer, instead it spits out the disc and prompts me to insert a bootable disc.
    Problem is I know this disc works. I've used it many times. And back over under MacOSX it reads the disc just fine.
    So I know this "new" laptop I got from work was actually refurbished, and I think they messed with it. Specifically I wonder if they mess with the open firmware. Because again, MacOSX (the software) could see and read the disc just fine. But when I'm in the open firmware loader it can't read the disc.
    Also, if I hold down Option at boot time, I get the option to select my WindowsXP disc because it sees it, but again, it can't load it...
    Is this a 32-bit/64-bit issue? I don't know. All I know is I can't boot my XP CD to install XP....
    Is there a way for me to reinstall the open firmware?

    I've now tried my buddy's WindowsXP SP2 disc and the first time, it loaded the windows installer (boot and held down Option and selected the disc) but the install failed. On reboot the windows partition will not boot.
    So I tried again, and now his disc and responding the same way my disc responds.
    I reboot, hold down Option, select the Windows XP disc, and then the screen goes black. I hear it trying different speeds to read the disc, then finally it stops and spits the disc back out and tells me to insert a bootable disc.
    So that's two separate WindowsXP install discs. Both are known to work.
    So why can this drive see the disk and files just fine under MacOSX -but not- under the EFI bootloader?? And yes I've tried resetting the NVRAM/PRAM.
    Message was edited by: general_error

  • Cant Boot Past Open Firmware Screen

    I have an iBook g4 14". Recently it started having problems. Every time i try to start it up, i goes to the open firmware screen.
    i tried typing 'mac-boot' several times and it still would not start. after the last time i tried that it will no longer allow me to input commands, i cant type anything at all. I have tried starting in single user mode and safe mode with the same results.
    I am getting the following error messages:
    BAD DEPTH= -1
    here= ff884f24
    BAD DEPTH= -1
    here= ff96c70c
    Method <SetQuietEnable> not found. ihandle=0 phandle=0
    Invalid memory access at %SRR0;
    after that the cursor shows up but it will not allow me to type anything.
    Any help would be appreciated. i would prefer not to have to wipe everything and reinstall as there is data on the drive i want to recover.

    Hi, and welcome to Apple Support Communities.
    Do you have the Install disc for the version of the operating system which is installed? If so, you could check out the Apple Knowledge Base article on Repairing the Hard Disk Using Disk Utility from the Install Disc.
    Do you have access to another Mac with FireWire? If so, you can try using FireWire Target Disk Mode to recover your data to the hard drive of the other Mac.

  • Weird Issue - CP-7975g boots into diagnostic firmware

    Greetings all, 
    This is my first post to this forum. I have a very strange issue for which I can't find an answer anywhere online, so I thought I'd take a stab at posting it here.
    I am endeavoring to put together a phone system for my church (for which they have almost no budget) and have recently acquired a job lot of Cisco CP-7975g phones fairly inexpensively.
    One of these phones boots into what appears to be a version of diagnostic firmware (Ver.:13.02.00.63)
    See Attached Picture
    Key presses on the numeric pad are recognized and are reported on the display. Pressing the # key results in ‘Enter option’ and ‘Invalid Option’ being displayed on the screen.
    I have tried performing a factory reset of the phone (hold # at boot until line buttons flash in sequence then enter ‘123456789*0#’) but the phone does not respond to the # key being held at boot and continues to start up in the diagnostic firmware.
    Could anybody throw me a bone on how to fix this problem?
    Many, many thanks in anticipation.
    Anton

    Just bumping the discussion in the hope that someone can help me.
    Thanks - Anton

  • Hard drive not accessible at boot time. Machine won´t boot into Windows.

    Greetings,
    I am trying to troubleshoot an HP Mini 110-1000 (actually a refurbished HP Mini 110-1033 CL PC). 
    When the machine boots, it attempts to connect to the network and the process hangs. I booted into BIOS to attempt changing the boot sequence to another device such as the hard disk or USB. None where found. Then, I tried to perform diagnostics on the hard drive. It was not found. 
    My guesses are:
    1. The hard drive is disconnected
    or
    2. The hard drive is broken
    or
    3. All of the hardware devices are disconnected.
    or
    4. The mother board is broken.
    I would appreciate some feedback before I start disassembling the machine. I would just go ahead, but the fact that
    none ofthe input devices are seen at boot time makes me believe that this is a mother board problem.
    In any case, a re-install of the OS is apparently in store, and I don´t have the original install disks...
    Thank you for your help and feedback.
    Regards,
    Jean-Pierre

    Hi,
    Please use the following instructions to fix:
       http://h10025.www1.hp.com/ewfrf/wc/document?docnam​e=c01443463&cc=ad&dlc=en&lc=en&jumpid=reg_r1002_in​...
    Good luck.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • Can't boot into Windows 7 after using Boot Camp

    So I installed Windows 7 on a separate 70GB partition using Boot Camp. Everything seems fine, but once installation finished and the computer restarted for the final time, the computer shows the blinking "_" on the black screen and then promptly reboots and this cycle continues without end.

    Sounds stuck at the Windows bootloader. It's not clear why. I would zap PRAM by holding command-option-p-r at the startup chime until you hear a 2nd startup chime. Let it boot back into Mac OS. Insert the Windows 7 install disk and reboot, holding down 'c'.
    Read this, in particular the 3rd option below the screen shot To open the System Recovery Options menu using the Windows 7 installation disc or a USB flash drive, or a system repair disc

Maybe you are looking for