Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Make a recovery disc from a Toshiba Recovery Partition


  • Please log in to reply
35 replies to this topic

#26
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,264 posts
  • OS:none specified
  • Country: Country Flag

There is something that does not sound "right" or it is however escaping me. :w00t:

 

The .SWM files are a form of a "divided into several files" .WIM file.

A .WIM file is a "Windows IMage" file, that contains an image of a partition. (actually an image of the files inside a partition)

Normally when you apply an image of a partition to a partition, the WHOLE contents of the partition are overwritten by the contents of the image.

 

How big in size is the USB stick yoiu have handy?

How big are the .SWM files?

Can you try making a single .wim out of the various .SWM and apply the .WIM instead?

Howto here:

http://www.hobwebs.c...sing-swm-files/

 

And yes, do double check (with diskpart or disk manager) which partition gets which drive letter BEFORE attempting applying the .WIM file.

 

jaclaz


Edited by jaclaz, 25 August 2014 - 03:32 AM.

  • Ntantor likes this


How to remove advertisement from MSFN

#27
Ntantor

Ntantor
  • Member
  • 6 posts
  • OS:Windows 7 x64
  • Country: Country Flag

@Ntantor, at your point #2, can you check what is actually oj your C: drive before and after the procedure ?

Did you not have any other (USB?) drive attached that could have taken the "C" letter instead when booting from your stick ? That image must have been applied "somewhere".

 

Hi, and thanks for the response! Ok, before i even do anything i had created an image of the whole notebook disk, using Acronis, on my external disk in case of anything going wrong.. I just recovered the image as the computer was when i got it.. I have noted everything in the disks and made sure than no other usb or sort is attached to the computer.

 

Here goes:

 

Partition 1: 400MB "invisible" partition with 100% free space - Healthy (Active, Recovery Partition) as stated in Computer Management - Disk Management

Partition 2 (C:\): 349.61GB visible partition Containing the OS - Healthy (Boot, Page File, Crash Dump, Primary Partition) as stated in Computer Management - Disk Management

Partition 3 (D:\): 348.63GB visible partition containing just a HDDRecovery folder with subfolders containing the imagex and .swm files  - Healthy (Active, Primary Partition) as stated in Computer Management - Disk Management

 

The C:\ partition contains the folders: Perflogs, Program Files, Program Files (x86), Users, Windows

 

After repeating the imagex procedure now, the only difference i see in any of the partitions is that a new folder is created Again in C:\

"Recovery\Windows RE" with a file "WinRE.wim" inside (195MB)

 

PS: I even double checked the USB that i used for the Windows Installation in case anything changed there.. nothing was changed!



#28
Ntantor

Ntantor
  • Member
  • 6 posts
  • OS:Windows 7 x64
  • Country: Country Flag

There is something that does not sound "right" or it is however escaping me. :w00t:

 

The .SWM files are a form of a "divided into several files" .WIM file.

A .WIM file is a "Windows IMage" file, that contains an image of a partition. (actually an image of the files inside a partition)

Normally when you apply an image of a partition to a partition, the WHOLE contents of the partition are overwritten by the contents of the image.

 

How big in size is the USB stick yoiu have handy?

How big are the .SWM files?

Can you try making a single .wim out of the various .SWM and apply the .WIM instead?

Howto here:

http://www.hobwebs.c...sing-swm-files/

 

And yes, do double check (with diskpart or disk manager) which partition gets which drive letter BEFORE attempting applying the .WIM file.

 

jaclaz

 

 

Hi, thanks for the response!
The 15 .swm files are 13.6GB in total. I am using a 64GB usb disk

I wil follow now the instructions of the link you posted. As for the partitions, i just stated every little detail in a post above :thumbup

Will let you know of the rest as soon as possible



#29
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,264 posts
  • OS:none specified
  • Country: Country Flag

Good.

 

What are the names of the .swm files?

What is the EXACT Toshiba model?

(maybe with this data we can find some related "previous art")

 

Once you have a .wim file, you should be able to open it with 7-zip to inspect it's contents before attempting to apply the image:

http://www.7-zip.org/

 

Possibly 7-zip will also allow to open the .SWM files, but never tried it:

http://forums.comput...?threadID=53952

 

 

jaclaz


Edited by jaclaz, 25 August 2014 - 08:47 AM.


#30
submix8c

submix8c

    Inconceivable!

  • Patrons
  • 4,263 posts
  • OS:none specified
  • Country: Country Flag

1. <snip>i created a bootable windows usb<snip>
2. Booted the Windows installation as you said, from the USB<snip>
3. <snip>i solved after downloading another x64 imagex from microsoft<snip>
5. Restarted the laptop but nothing happened. Booted again into my friend's "clean" windows installation.<snip>
===========
Partition 1: 400MB "invisible" partition with 100% free space - Healthy (Active, Recovery Partition) as stated in Computer Management - Disk Management
Partition 2 (C:\): 349.61GB visible partition Containing the OS - Healthy (Boot, Page File, Crash Dump, Primary Partition) as stated in Computer Management - Disk Management
Partition 3 (D:\): 348.63GB visible partition containing just a HDDRecovery folder with subfolders containing the imagex and .swm files  - Healthy (Active, Primary Partition) as stated in Computer Management - Disk Management
===========
I'm not getting a couple of things.
1. By what method and using what "source"?
2. I'm guessing you mean your "source" is an Install ISO source and not a Repair CD/DVD?
3. Um, how did you do that? You got the AIK ISO?
5a. "nothing happened"?
5b. Your "friends" is from an Original Windows 7 Install DVD?

Partition 1 - a UEFI/GPT HDD, right? (apparently...)
Partitions 2/3 - how ODD the partition sizes. ~700GB HDD?
You got that info from the "clean install"?
Where's the "System" flag/indicator?
*Side notes -

I don't have a "Recovery Partition" flag/indicator but did apply "Reagentc /enable", FWIW.

Also booted to a Console with the created x86 Repair CD and specifically used "DISKPART" for listing as well, that you haven't done.

Indications are that you have a 64-bit OS, since you needed an x64 "imagex".

That "magically appearing" folder/file is the Recovery Environment that
- "C:\Windows\System32\Recover\ReAgent.xml"
should have an entry for. The WIM is undoubtedly "adapted" for the OEM Restore.

I'm not understanding why the BCD Store in the 400mb "hidden" partition is failing to "see" the ("System") OS. Something seems amiss (a/l to me). :unsure: Please bear in mind I have a Win7 Pro OEM (should make no difference?) "clean" (meaning from a totally empty HDD) install. It therefore shows (in a Winbuilder LiveXP) a "C:\Recovery\{guid}\WinRE.wim" instead. It appears that the F8 then "Repair" yields pretty much the same as the Bootable Repair CD except it required me to logon to an account.


Someday the tyrants will be unthroned... Jason "Jay" Chasteen; RIP, bro!

Posted Image


#31
Ntantor

Ntantor
  • Member
  • 6 posts
  • OS:Windows 7 x64
  • Country: Country Flag

I would like to thank everyone for trying to help! I finally got this working using the help from you and parts of other links you posted especially the link jaclaz gave me! Thanks a lot. Really appreciate the help of everyone!

I will tell you the steps i followed in case anyone else had the exact same problem:

 

1st i will say again what happened. A friend of mine has the Toshiba L775-15T with windows 7 home premium x64. He wanted to format the laptop but didn't want to go again through the whole windows updates procedure etc because of his slow internet connection. Hi didn't think too much of it though. He downloaded a version of windows home premium x64 including all the latest updates from a torrent site. He formatted just the OS partition ,leaving the small 400mb partition and the 3rd "recovery" partition untouched. After seeing his laptop without all the drivers and the Toshiba applications he freaked out and brought his laptop to me to do a proper format - recovery as i helped him do some time ago. But he hadn't create the recovery disk as i warned him to do so many times before.. PS: the F8 - Repair - Toshiba recovery etc. wasn't available anymore

 

Solution:

1. Since the .swm files in the 3rd partition where too big for a dvd, i created a bootable Windows Installation USB 64Gb in size using Windows 7 USB DVD Download Tool (you can use YUMI or any other similar application)

2. In the USB i created a new folder and copied there all the .swm files from the Toshiba recovery partition, along with the imagex.exe. Note: when i used the specific imagex.exe i had an error that the subsystem wasn't present and after a little search i downloaded from microsoft the proper x64 version of it (weird though that the original one wouldn't work) from here: http://hotfixv4.micr...ntl_x64_zip.exe

  -- In case you need another version of imagex you can get it from this link from Microsoft: http://support.micro...5084&kbln=en-us

3. I booted the computer from the USB and when the windows installation started, i selected "Repair the computer"

4. Using the command prompt i navigated to the specific folder in the USB i had copied the .swm and imagex files

5. I run the following command imagex /ref 15541XSP*.swm /export 15541XSP.swm 2 boot.wim (This command merged all the swm files into a new boot.wim file, in the same directory. The file was close to 7GB)

6. Then i run the command format c: /fs:ntfs /q /V:Windows  (Take care here to make sure that your OS installation was in C:\  ). In case you are wondering, i 1st ignored this step and at the end the applied image that will follow, wouldn't load properly, so i added this step and all worked fine.

7. Then i run imagex /apply boot.wim 1 C:\ and restarted the computer. The Toshiba recovery procedure started and after a few restarts the laptop came to life in its original factory state.

 

 

PS: If you get any errors (didn't happen to me) about the boot record or something like that, boot from the windows repair console and hopefully it will repair it

 

 

My friend is now with me, thanking you guys all.. He WILL BE buying the drinks tonight! Cheers :thumbup

 

 

Thanks again for all your efforts!


Edited by Ntantor, 26 August 2014 - 12:50 PM.


#32
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,264 posts
  • OS:none specified
  • Country: Country Flag

My friend is now with me, thanking you guys all.. He WILL BE buying the drinks tonight! Cheers  :thumbup

 

 

Thanks again for all your efforts!

You see the not-so-trifling advantage of helping a local friend (as opposed ot a remote one)?

 

Free Beer! ;)

 

cheers.gif

 

Happy everything went fine, thanks for reporting and "finalizing" the thread with the procedure that actually worked. :thumbup

 

jaclaz


  • Ntantor likes this

#33
Ntantor

Ntantor
  • Member
  • 6 posts
  • OS:Windows 7 x64
  • Country: Country Flag

Hi again.. Just an update.. The method above worked fine to have the laptop's factory condition of the OS but still had some problems. 1. The F8 - Repair wouldn't show the Toshiba recovery option and 2. The Toshiba recovery application would fail to create Recovery disks.. But that is fine for me since i saved the "boot.wim" file to a USB and could restore the computer at any time, using the method above.

This time i asked my friend to lend me his laptop for another day to try something and i prefer this method

 

NOTE: You will need an image of another toshiba laptop to clone on your computer or it's set of recovery disks.. Doesn't have to be the same model or with the same drivers. I tried both methods to be sure. I had the L775-15T and borrowed the recovery disks of a C660-1P3 that i also cloned

 

1. Copied my friend's .swm files from the L775 on my USB (the .crc files too)

2. Used the image / recovery disks to do a recovery on the L775 using the C660 image / recovery disks

3. When finished, windows wasn't activated, drivers were not functioning correctly etc

4. Renamed my .swm files to match the C660 .swm files (15541xsp*  -  14419xsp*)

5. Booted into Linux using a live cd

6. Deleted the .swm files that were on the recovery partition and replaced them with my own that i had previously renamed to match them (Windows wouldn't let me delete the files, that's why i booted into Linux)

7. Restarted the laptop, used the F8 - Repair option. The Toshiba recovery now was there. I used it and voila.. It used the new .swm files of the L775 to restore the laptop to it's original state, with all the functions working this time perfectly and allowing me to create the L775's recovery Disks, the F8 functioning etc..

 

I hope this method will help many of you guys out there!

 

Cheers!


Edited by Ntantor, Yesterday, 04:31 PM.


#34
Ponch

Ponch

    MSFN Junkie

  • Patrons
  • 3,265 posts
  • OS:none specified
  • Country: Country Flag
6. Then i run the command format c: /fs:ntfs /q /V:Windows  (Take care here to make sure that your OS installation was in C:\  ). In case you are wondering, i 1st ignored this step and at the end the applied image that

:blushing: I should have remembered this. Imagex does NOT erase existing files, it only overwrite files that are also present in the image (most probably "sysprepped") that is applied so you probably ended up with files from two different (conflicting) Windows versions and it would not boot properly.

 

 

I created a bootable Windows Installation USB 64Gb in size using Windows 7 USB DVD Download Tool (you can use YUMI or any other similar application)

...

when i used the specific imagex.exe i had an error that the subsystem wasn't present and after a little search i downloaded from microsoft the proper x64 version of it (weird though that the original one wouldn't work)

Your USB was made with (and booted) a 64bit OS whether your original imagex was supposed to be ran under the Toshiba restore system which is probably a 32bit OS (RE).



#35
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,264 posts
  • OS:none specified
  • Country: Country Flag

Yep, it is very possible that your friend, when he installed the "new" windows overwrote the MBR (or the PBR or both) with a "normal" one whilst the Toshiba may use a "special" one, and the same may have happened for the \boot\BCD on the partition that MS calls "system"(and that is actually the "boot" partition) or for other settings in the \boot\BCD.

 

JFYI, see these two thread (one about HP?s and one about Fujitsu Siemens, the former using a special MBR and the latter using the "Windows built-in F8 feature)

http://www.msfn.org/...d-not-be-found/

http://www.msfn.org/...via-f8-startup/

 

The applying of the .wim obviously affected only the partition to which it was applied, whilst re-doing the recovery "from start" (or however re-running the similar recovery before) recreated the "right" "special" MBR (or whatever).

 

I strongly suspect that what the Toshiba uses is the "C:\Recovery\Windows RE\WinRE.wim you mentioned when the F8 is pressed.

 

jaclaz


  • submix8c and Ntantor like this

#36
submix8c

submix8c

    Inconceivable!

  • Patrons
  • 4,263 posts
  • OS:none specified
  • Country: Country Flag

Yep, that's what I was saying. Please also note using merged/named "BOOT.WIM" from Index#2 to get "back" the second time

Methinks the XML inside the Combo (merged) WIM(s) needs pulled an inspected to see what is REALLY inside it.

 

Please note the First try

2. Booted the Windows installation as you said, from the USB, then “ repair your computer “, then “ Command Prompt “, went into the factoryreset folder and run "imagex /ref PREINST*.SWM /apply PREINST.SWM 1 C:\"

Now note the Second try

5. I run the following command imagex /ref 15541XSP*.swm /export 15541XSP.swm 2 boot.wim (This command merged all the swm files into a new boot.wim file, in the same directory. The file was close to 7GB)

Somewhat confusing, no? IOW, -one- of them is WinPE/WinRE(?), the -other- one is the actual Install (AFAICT).

 


Someday the tyrants will be unthroned... Jason "Jay" Chasteen; RIP, bro!

Posted Image





3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users



How to remove advertisement from MSFN