Window won't boot after factory restore

Hi:
My notebook is Pavilion dv4 -1435dx, running Vista 64, before i did system restore, windows was running very slow after log on, won't be able to work on it at all.... so i decided to do a factory restore. I tried 4,5 times of factory restore,(but failed, stuck at startup repair). And last, finally have it completely restore. right after that, I did windows upate the first thing. After downloaded and installed of windows update, Windows need to restart.... and then it stuck at startup repair again.....now it won't logon to window......
Please help!! Thank you.

Hi
1) Once unit is powered on keep tapping F2 run the test and check if all test passes. If any test fails you need to replace the part.
2) If test passes you might need a set off recovery disc.
Order Recovery Discs for Windows 7, Vista, or XP
Let us know how it goes!
"I work for HP."
****Click the (purple thumbs up icon in the lower right corner of a post) to say thanks****
****Please mark Accept As Solution if it solves your problem****
Regards
Manjunath

Similar Messages

  • IMac won't boot after factory setting restore

    I stupidly changed all the permission settings on my day old iMac HD. The folder of work I migrated was showing up as read only, so I unwittingly changed the whole HD to read and write permission.
    Since then I have been unable to boot the computer up. The screen goes straight to grey screen, the apple logo appears then the loading wheel graphic.... and it sticks at this.
    I have done the following to try and rectify:
    1. Removed all peripherals. Unplugged are replugged.
    2. Repaired disk in disk utility (no problems found)
    3. Repaired permissions in the disk utility (disk repaired sucessfully)
    4. Booted to reset NVRAM/PRAM
    5. Erased and reinstalled OS (twice)
    Nothing has worked so far.
    Can anyone advise, before I have to speak to a Genius?
    Thanks

    Like Barry, I can only think of trying an SMC reset: http://support.apple.com/kb/ht3964
    Failing that, unless someone else has some other suggestions, it's looking like a call to a Genius.
    Good luck and let us know what the fix was if the Genius manages to get it going.

  • Windows Won't Boot after resizing partition

    I am having problems with Windows not rebooting after I resized partition to reduce Mac side and increase Windows side. I do not see the BootCamp partition labelled as such while running disk utility. Upon startup, the Windows partition shows up when I boot up while pressing the ALT key. However, when I try to run Windows, it says " error loading operatig system".
    I also followed instruction and went through to run gdisk successfully. Results towards the end.
    What can be done? Windows still does not boot and It shows ? Suspicious MBR at sector 0.
    Below is information based on typical questions asked here.....
    diskutil list
    /dev/disk0   #:                       TYPE NAME                    SIZE        IDENTIFIER
       0:              GUID_partition_scheme                        *120.0 GB     disk0
       1:                                           EFI                         209.7 MB     disk0s1
       2:                         Apple_HFS Macintosh HD            78.5 GB     disk0s2
       3:                       Apple_Boot Recovery HD             650.0 MB     disk0s3
       4:                   Microsoft Basic Data                         31.7 GB      disk0s4 
    sudo gpt -r -vv show disk0
    gpt show: disk0: mediasize=120034123776; sectorsize=512; blocks=234441648
    gpt show: disk0: Suspicious MBR at sector 0
    gpt show: disk0: Pri GPT at sector 1
    gpt show: disk0: Sec GPT at sector 234441647
          start       size            index       contents
              0          1                             MBR
              1          1                             Pri GPT header
              2         32                            Pri GPT table
             34          6       
             40     409600           1            GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
         409640  153240016      2            GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      153649656    1269544     3            GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      154919200   17628896       
      172548096   61892608    4            GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      234440704        911       
      234441615         32                       Sec GPT table
      234441647          1                        Sec GPT header
    sudo fdisk /dev/disk0
    Disk: /dev/disk0 geometry: 14593/255/63 [234441648 sectors]Signature: 0xAA55
             Starting       Ending
    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
    1: EE    0   0   2 - 1023 254  63 [         1 -  172548095] <Unknown ID>
    *2: 07 1023 254  63 - 1023 254  63 [ 172548096 -   61892608] HPFS/QNX/AUX
    3: 00    0   0   0 -    0   0   0 [         0 -          0] unused    
    4: 00    0   0   0 -    0   0   0 [         0 -          0] unused 
    sudo gdisk /dev/disk0
    GPT fdisk (gdisk) version 0.8.7
    Warning: Devices opened with shared lock will not have their
    partition table automatically reloaded!
    Partition table scan:
      MBR: hybrid
      BSD: not present
      APM: not present
      GPT: present
    Found valid GPT with hybrid MBR; using GPT.
    Command (? for help): r
    Recovery/transformation command (? for help): h
    WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,
    just hit the Enter key at the below prompt and your MBR partition table will
    be untouched.
    Type from one to three GPT partition numbers, separated by spaces, to be
    added to the hybrid MBR, in sequence: 4
    Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): y
    Creating entry for GPT partition #4 (MBR partition #2)
    Enter an MBR hex code (default 07):
    Set the bootable flag? (Y/N): y
    Unused partition space(s) found. Use one to protect more partitions? (Y/N): n
    Recovery/transformation command (? for help): o
    Disk size is 234441648 sectors (111.8 GiB)
    MBR disk identifier: "DELETED INFO"
    MBR partitions:
    Number  Boot  Start Sector   End Sector   Status      Code
       1                               1    172548095   primary     0xEE
       2           *     172548096    234440703   primary     0x07
    Recovery/transformation command (? for help): w
    Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
    PARTITIONS!!
    Do you want to proceed? (Y/N): y
    OK; writing new GUID partition table (GPT) to /dev/disk2.
    Warning: Devices opened with shared lock will not have their
    partition table automatically reloaded!
    Warning: The kernel may continue to use old or deleted partitions.
    You should reboot or remove the drive.
    The operation has completed successfully.

    So here's what I think happened. Upon resizing the OS X volume, a 5th partition was created. When that happens, diskutil removes the hybrid MBR that's needed to activate the EFI firmware CSM (BIOS emulator) which is still presently used for booting Windows on Apple hardware. Upon removing the hybrid MBR, Windows is no longer bootable. So what you probably did was used Disk Utility to reverse what you did by deleting the extra partition. When you do this, diskutil recreates the hybrid MBR but with the wrong partition type code. It sets it to 0x0C, and therefore thinks it's FAT32, whereas it should be 0x07 for NTFS. Disk Utility will then let you run a disk check on what it erroneously thinks is a FAT32 volume, but is in fact NTFS. If any writes are done, which it appears is the case, it corrupts the NTFS file system.
    So this is just yet another Bootcamp data loss story, without any warning in either documentation or Disk Utility whatsoever.
    What version of OS X is this?
    The easiest, but most tedious thing to do is to totally start over with everything: obliterate the entire drive with Disk Utility making 1 partition only, reinstalling OS X and files from backups, use Bootcamp Assistant to resize the OS X volume the way you really want it, reinstall Windows and restore from its backup. All of that can be done in the GUI.
    You might still use the Windows install disk to run Windows startup repair. It might fix the Bootcamp volume. The remaining problem in that case is what to do with the large pile of free space, but I'll make those suggestions later once you get to that point.
    If Windows startup repair can't fix the Bootcamp volume, and you don't have a backup, then you'll need to download and install testdisk, and read how to use it to try and find your data. It's an iterative process. Once that's done, while it probably won't fix it and make it bootable again, you'll have a basic backup of files. The remaining thing to do is use gdisk remove the broken Windows partition, make a new one that also includes free space you presumably wanted Windows to have, and make a new hybrid MBR adding partitions 2 3 4. Then reinstall Windows, your apps, and restore your data from backups.
    So that's the gist. Ask if you have more questions.

  • Upgrading to SSD! But windows won't boot after copying drive.

    I recently bought the great HP TM2t 2100 with all the bells and whistles along with an Intel x25m 120gb SSD (and Apricorn housing to use the old HDD as a backup drive.) 
    I followed all of the steps on the ez gig III software and copied the hard drive to the ssd without any errors. When I physically install the ssd (very easy!) and turn on the computer it says that Windows cannot be recovered. And will not  boot windows. I did make Device Recovery discs but those are not able to be read either. Any suggestions on this? I have been trying to find an answer to no avail.
    In the mean time I reinstalled the HDD and will try again after updrating all the drivers.

    Well, I couldn't get the copied SSD to work, but as of right now I'm using the repair disks to restore windows to factory settings, the comp is only a weekend old and has no files of importance on it so I think this will be the best way. I will report my findings. 

  • Windows won't boot after 9.1 flash (K8T Neo2-F)

    Hello,
    I tried flashing to 9.1 to be able to use dual channel mode, but when i try to boot windows xp (sp2) won't start. I just get a blank screen.
    I changed the bootorder correctly (1: CD 2:PM Maxtor).
    I can boot fine from a CD or floppy when i press F11 or change bootorder.
    Also when i try to put the Floppy as first bootdevice it just checks the floppydrive for a bootable disk, then halts.
    When the CD is the first bootdevice and HD second, i get a few (about 3) weird colored characters on my screen.
    When i try to boot from the second harddrive (40GB on primary slave), i get the message 'Missing operating system'.
    I've had a similar problem before when i went from 3.3 to 9.1 and changing the LBA mode on the harddrive fixed that but now it doesn't change.
    Could this be because the drive was formatted in non-LBA mode (although i doubt that's the case...)?
    Any idea's?
    Thanks.
    System:
    300W power supply (no brand)
    MSI K8T Neo2-F (VIA K8T880)
    AMD Athlon 64 3000+ (Venice)
    Corsair TWINX1024-3200C2 (2x512MB)
    Nvidia Geforce 3 (64mb) AGP
    Maxtor 6Y080L0 (80GB), primary master
    Seagate ST340016A (40GB), primary slave
    BenQ CD/DVD writer (16x): secondary master

    And what about optimized defaults? We have already found this to be a problem if you don't set that first before setting up the Bios.
    I mentioned the PSU as all you listed is watts and that as I say does not help us at all here. However 15a is asking for problems as you have nothing in reserve to operate from is say the PSU gets warm and loses efficiency, which by the way drops fast, or during startup you can have issues as well and may not even know it as this is the time that PSU's are asked for the most power. Also as you have a GF3 vid card, which at the moment is likely saving that PSU from even more stress, you aren't using 12v on that card, but if you upgrade sometime to a better vid card you will certainly go over the power budget that PSU has available and burn it up or maybe more. What I am saying is that we already know from experience here with people having issues that 15a don't cut it.
    So now that I have had to repeat that all over again in yet another thread... You shopuld at least have a look at what you already have as needing an upgrade and while hopefully not at the moment as we already know it runs wether well or not, you should considure upgrading it before you do much else with that system. Not that you need to replace it this very moment. I am just making you aware that your already looking at a possible problem at some point there.

  • Macbook Pro won't boot after TM restore

    Hi.
    My MacBook Pro was running snow leopard with all the latest updates, when the hard drive crashed. I booted from the dvd that came with the macbook, osx 10.5.4, restored the latest Time Machine backup. Everything seemed fine until I try to reboot. I get the grey screen and the message:"You need to press the powerbutton for several seconds". I've reset the pram, powermanager and ran a hardware check that turned out ok. Does anyone have any clues as to what's wrong?
    Any help would be greatly appreciated,
    Regards, Espen Noreger

    enoreger wrote:
    Hi.
    Hi, and welcome to the forums.
    My MacBook Pro was running snow leopard with all the latest updates, when the hard drive crashed. I booted from the dvd that came with the macbook, osx 10.5.4, restored the latest Time Machine backup. Everything seemed fine until I try to reboot. I get the grey screen and the message:"You need to press the powerbutton for several seconds". I've reset the pram, powermanager and ran a hardware check that turned out ok. Does anyone have any clues as to what's wrong?
    Yes. You need to use your +Snow Leopard+ Install disc, not the Leopard one.

  • Iphone 4 won't activate after factory restore? help, please?

    I did a restore on my iphone 4 earlier. This is the first time I have ever done a restore-I have only had this phone for about 2 weeks. However, I was having battery problems so I chose to restore.
     It went through the entire process and even came up the "activating, this may take some time" or whatever screen. It said that it had synced and it was okay to disconnect. Now, however, I have no service at all, it says that the network is unavailable, and it keeps popping up and saying that it is not activated and if it continues to call some 1800 number. It is connected to my wifi, however.
    Do I have to call the *228 number or something, like I did when I first got it? Or what? I'm really confused and frustrated...I just want my phone to work.
    16GB
    Software: 4.2.10
    Iphone 4

    swells wrote:
    I did a restore on my iphone 4 earlier. This is the first time I have ever done a restore-I have only had this phone for about 2 weeks. However, I was having battery problems so I chose to restore.
     It went through the entire process and even came up the "activating, this may take some time" or whatever screen. It said that it had synced and it was okay to disconnect. Now, however, I have no service at all, it says that the network is unavailable, and it keeps popping up and saying that it is not activated and if it continues to call some 1800 number. It is connected to my wifi, however.
    Do I have to call the *228 number or something, like I did when I first got it? Or what? I'm really confused and frustrated...I just want my phone to work.
    16GB
    Software: 4.2.10
    Iphone 4
    swells wrote:
    Oh, and on itunes my phone number is now listed as "00000000" and a few other numbers instead of my actual phone number.
    That "00000000" number thing could be the issue, I have never activated my iPhone over iTunes (mine was preactivated when I got it), but it sounds to me that when/if iTunes goes to "activate" the phone, iTunes could be telling your iPhone that 00000000 is your actual phone number, so the iPhone self activates it thinking that is your actual number, so when that number doesn't match up with any number on Verizon's servers, it fails activation (while many may say that iTunes "activates" the phone, I am pretty sure that iTunes just forwards that information to the iPhone and automatically does the "*228" activation on it's own based on the information entered into iTunes)
    I would say yes, go ahead and try *228 opt 1 and see if that works, or see if you can change the number to your real number in iTunes

  • Z580 won't boot after Windows 7 Install

    Hi,
    After a clean install of windows 7 on the hard drive, Lenovo Z580 wont boot up but when hard drive it put into my old Acer laptop, boots fine. 
    Initially had to remove the hard drive from the Lenovo and put into another laptop to install windows 7 as lenovo wouldnt boot from usb or CD. And then after install tried putting hard drive back into Lenovo and just doesn't boot at all. Just goes to boot manager sceen and then blank in a continous loop.
    Please help! 
    Thanks in advance!

    Welcome to the forum!
    "remove the hard drive from the Lenovo and put into another laptop to install windows "
    You stated the exact reason for your problem.  You can't install Windows 7 on one laptop and expect it run on another by swapping the hard drive.  It doesn't work.  During the installation Windows inventories the installed hardware and configures itself accordingly.  Since they are two different machines, Windows won't boot.  You are going to have to resolve the USB or Optical drive boot problem on the Lenovo laptop you wish to install Windows on.  
    During bootup have you tried using the Boot Menu to boot the machine specifically from the optical drive?
    Owner & Operator of the following:
    ● Lenovo Ideapad Z570 w/ Win 7 & Win 8.1 Dual Boot ● Lenovo Yoga 3 Pro w/ Windows 8.1 ● Toshiba A75-S206 w/ Win 7
    ● IBM Thinkpad T-23 w/ Win XP ● IBM Thinkpad T-22 w/ Win XP • As well as multiple desktops dual/triple booting XP, Vista and Win 7.
    ★ Find a post helpful? Thank that member by clicking on the ☆Star☆ to the left awarding them a Kudo.
    ★ Posting a problem and a reply is helpful and it answers your question, please mark it as an "Accepted Solution"
    ★ I'm not a Lenovo employee, just a volunteer geek who likes to help folks. Enjoy your time here, pay it forward by helping others !
    ★ Sorry, I don't answer questions via Private Messages. Posting in the appropriate forum is the best way to get assistance.

  • [SOLVED] Arch won't boot after I created a separate /var parition

    Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
    I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
    Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
    The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
    I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
    # Filesystem information
    # /dev/sda5 LABEL=fs_root
    UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
    # /dev/sda9 LABEL=fs_var
    UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
    # /dev/sda2 LABEL=fs_boot
    UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
    # /dev/sda6 LABEL=fs_home
    UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
    # /dev/sda7 LABEL=fs_swap
    UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
    # /dev/sda3 LABEL=fs_win
    UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
    # /dev/sda3 LABEL=fs_share
    UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
    I would greatly appreciate any help.
    Last edited by richcocoa (2015-05-03 18:04:44)

    Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
    cp -rax
    and you can add -v switch to verbose output. I have my own /var moved the same way.
    The simples way is:
    -boot the arch iso cd
    -mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
    -copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
    -umount all of it
    -reboot.
    Last edited by firekage (2015-05-02 07:49:20)

  • MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear.

    MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear. Computer won't even start in safe mode.

    My daughter's MacBook Pro was doing exactly the same thing.  I don't know if it had anything to do with the latest update.  She called me about a week ago saying that her MacBook began running slower by the day .  She then called me Friday and told me that it wouldn't get past the gray screen and the gear just kept on spinning.  I did everything I could over the phone including Safe mode which it wouldn't go into and thought maybe it was the hard drive.  She took it to the Apple store.  Originally, they also thought it was the hard drive.  It ended up being a corrupted operating system (Lion).  Apple genius simply re-installed Lion and she's back up and running.  Good thing she backed up right before it crapped out.  She'll be restoring everything tonight.  Don't know if re-installing Lion will help your situation, but it did the trick for my daughter.

  • Mac won't boot after the latest update. It is loading the update and suddenly shuts down

    My MacBook Pro won't boot after a minor update. The update was all fine and my Mac acted like it used to but when I tried to boot my Mac it just loads the the update then goes back to the Apple logo and then shuts down.
    I hope that someone has got a solution because I do not want to restore my Mac for the 4th time.....

    Hello JonasHallund,
    We've an article that contains information and steps that can help get your MacBook Pro to boot again.
    Troubleshooting: My computer won't turn on
    http://support.apple.com/kb/TS1367
    Cheers,
    Allen

  • Macbook pro won't boot after installing update 10.9.3

    macbook pro won't boot after installing update 10.9.3

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode.
    Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Test while in safe mode. Same problem?
    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • Mac won't boot after updating to OSX 10.6.4

    I am on my 3rd Mac that won't boot after updating to OSX 10.6.4. One MacBook Pro and two iMacs. I fixed one but the last two are getting the better of me. HD is not fried. Have tried every keyboard shortcut on startup, Disk Warrior via. Target Disk, repairing permissions in single user mode. The machines will not boot off of a CD or DVD and it will not boot up in safe mode. Something in the startup files is preventing startup. I am suspecting Sophos antivirus. I tried to uninstall it and trash it but I think it's still blocking something. Any help would be appreciated.

    Got it! Not sure if removing Sophos had anything to do with it but here's what I did.
    1) boot dead machine in Target Disk Mode (iMac)
    2) boot good machine off Snow Leopard disk (MacBook)
    3) install OS to dead machine- I found this next part very curious. When the install was complete the MacBook restarted as the iMac.
    4) ran software updates
    5) shut down MacBook then shut down iMac
    6) rebooted iMac- all was good
    I actually did this twice because a co-worker had the exact same problem on her MacBook Pro. Got both fixed today.
    Thanks everyone for your help!

  • My MacAir 1st gen. won't boot after latest OS X Lion update.

    My MacAir 1st gen. won't boot after latest OS X Lion update. tried safe boot(didn't work) tried disk repair, said it was successful, but my mac won't start up. Just get white screen.  Also been having trouble with it overheating. Fan seems to work. But when it get too hot whole interface slows down.

    Yikes, I hope you have AppleCare on it still, I think it needs to be taken in, but as a last ditch effort...
    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.

  • Mac mini won't boot after RAM upgrade.

    Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
    Things I've tried so far:
    1. Resetting the PRAM, no luck.
    2. Holding option at start-up, shows no icon.
    3. Holding shift, no luck.
    4. Holding X, nothing.
    How do I get it to accept a CD if it won't boot?

    Welcome to Apple Discussions!
    You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
    If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
    It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

Maybe you are looking for