- This topic has 148 replies, 49 voices, and was last updated 1 day, 21 hours ago by
.
-
Posts
-
The Admin Tool is buildable from within SRS itself… If your computer is working normally – you do not need anyone to ‘let you have it’…
In my research, THIS is the only mention I found about SRS6 (and Amin Tool)
http://forum.notebookreview.com/samsung/683577-samsung-series-9-windows-8-a-57-print.html
in the answer to the query by Dannemand, is How to build the SRS Admin Tool…
Hope this is helpful
Hello,
I use Admin Tool on a USB key to recover an image backup made with Samsung recovery on an external hard drive.
I can not do it via Samsung Recovery 4 from the recovery partition, because when I run the complete restoration or I get an error message telling me it can not find the C: drive or the restoration begins with reading a hundred files then stops with a reading error message.
This is why I use Admin Tool on bootable USB drive.
Thus, once launched Admin Tool, I find myself in front of the screen (which I copied from the first page)
– I do the combination key CTRL + ALT + F10
– I enter the password SECOS
– I click on System Restore
– I click on Wizard
– A WinClon 4.0 screen appears asking me to select the source image file (step 1)
– I select the file .wcl which is on my external hard drive.
– I confirm the source selection with the Next button
– I select the destination drive where the backup back (step 2)
– I validate the Next button
– And a third screen (step 3) asks me for a password that is different from SECOS and SECCLXI desperately seek information on the second password. I have not found anything on the web.
Has someone information about this second password ?
Thanks for your help.
thanks for your contributions, they are very valuable, I have a question, I installed SRS Version 6 on my recovery partition, I have a Samsung Series 5, came from the factory with Windows 8, the problem that when installing windows 8, tells me that I can not install windows 8 on a partition GPT, I’ve changed the CSM and UEFI options without success, and the problem is, that Recovery solution 6 format the hard drive in 5 partitions, and GPT type
Hey guys, so I just spent over 8 hours recovering my initial partition after installing Windows 8.1. Most of it was figured out in this thread (thanks so much), but there’s a few key things you can do to speed-up the process and get this all done in under an hour. Here’s my initial problem:
I bought a Win7 Samsung PC. I installed a FRESH Windows 8.1. This somehow screwed up the Recovery Partition so that it wasn’t detected, even though it’s still intact and I can boot into SRS using F4, it would just say “This PC doesn’t support SRS5”. Here’s how to fix it:
First download the SRS links found in this thread (I used SRS5 since that’s what came with this tool).
Extract it onto a USB drive.
Load up whatever Windows you have currently on there. Open up an Administrator Command Prompt. Run “DISKPART”. Select the OEM partition that is your recovery partition but isn’t being detected and manually override it to NTFS. I figured this out by reading this link: http://daily-grind.net/solved-cant-access-my-recovery-partition-i-dont-have-any-recovery-cds/. Here’s the commands to use in DISKPART:
list disk
select disk 0
list partition
select partition 3
set id=12 OVERRIDEA dialog should pop-up saying it now found your drive. Explore to it. Copy all of the images files on the root directory onto your USB. The files for me were named init.w00, init.w01 and so on. You’ll know it’s them because they’re huge (4gb each because they make a recovery set). Once they’re copied onto the USB drive reboot.
Now make sure your bios settings will boot of your USB drive. Once your USB drive comes up with the SRS admin tool. Do not repartition the drive, instead use one of the options under “step 2” to re-image the recovery partition. It will ask you to insert the USB drive with the images, since you just copied it onto your boot USB drive you can just click OK. It will then copy that image back onto the recovery partition and reset the MBR and all that jazz so your computer will now recognize it again.
Next time when you boot, you should be able to hit F4 and this time the recovery software will find the recovery drive and you’ll be able to perform a restore. Thanks to the OP who found this all out. I can finally return my laptop because it has a defective video card :/.
Cheers.
Samsung Recovery Solution 3.0.0.6, 4.0.0.42, 5.0.2.5 & 6.0.12.4 – AdminTool
http://www.mediafire.com/?m03xv2mb6360s
[CTRL]+[ALT]+[F10]
Passwords :
secclx
and
secosSamsung Recovery Solution 3.0.0.6, 4.0.0.42, 5.0.2.5 & 6.0.12.4 – AdminTool
http://www.mediafire.com/?m03xv2mb6360s
[CTRL]+[ALT]+[F10]
Passwords :
secclx
and
secosTo create a bootable UFD (USB flash drive). Only use 1GB stick (no need to use larger).
1) Start a Command Prompt as an Administrator :
diskpart
list disk
select disk 1 (if disk 1 is = stick usb)
clean
create partition primary
select partition 1
active
format fs=ntfs quick
assign
exit
exit
2) Copy the contents of AdminTool_for_SRS6.iso to USB. Please use a proper tool (Nero or UltraISO) for copy.
3) Change the BIOS settings for the booting sequence, making sure that the USB device is at the top of the list.Enjoy !
dosiboxSamsung Recovery Solution 3.0.0.6, 4.0.0.42, 5.0.2.5 & 6.0.12.4 – AdminTool
http://www.mediafire.com/?m03xv2mb6360s
[CTRL]+[ALT]+[F10]
Passwords :
secclx
and
secos
To create a bootable UFD (USB flash drive). Only use 1GB stick (no need to use larger).
1) Start a Command Prompt as an Administrator :
diskpart
list disk
select disk 1 (if disk 1 is = stick usb)
clean
create partition primary
select partition 1
active
format fs=ntfs quick
assign
exit
exit
2) Copy the contents of AdminTool_for_SRS6.iso to USB. Please use a proper tool (Nero or UltraISO) for copy.
3) Change the BIOS settings for the booting sequence, making sure that the USB device is at the top of the list.===========
14/08/2014.
Enjoy !
By dosibox – popeye0Samsung Recovery Solution 3.0.0.6, 4.0.0.42, 5.0.2.5 & 6.0.12.4 – AdminTool
http://www.mediafire.com/?m03xv2mb6360s
https://mega.co.nz/#F!s8gwWBxb!uEnBImJKatdqN64rN7utww
All links are interchangeable, you can take different parts on different hosts and start downloading at the same time.SRS4_KOR_Admin_Tool.doc => http://www.datafilehost.com/d/c5cf6c61
SRS-6-Recovery-ENG-Admin-Tool_121031_Updated.docx => http://www.datafilehost.com/d/c828c7ebTo create a bootable UFD (USB flash drive). Only use 1GB stick (no need to use larger).
1) Start a Command Prompt as an Administrator :
diskpart
list disk
select disk 1 (if disk 1 is = stick usb)
clean
create partition primary
select partition 1
active
format fs=ntfs quick
assign
exit
exit
2) Copy the contents of AdminTool_for_SRS6.iso to USB. Please use a proper tool (Nero or UltraISO) for copy.
3) Change the BIOS settings for the booting sequence, making sure that the USB device is at the top of the list.[CTRL]+[ALT]+[F10]
Passwords :
secclx
and
secos===========
17/08/2014.
Enjoy !
By dosibox – popeye0Hello, can you help me? I have all the recovery partitions but it not linked with the F4 boot. Do you have the admin recovery VIII? Thanks a lot
Hello, can you help me? I have all the recovery partitions but it not linked with the F4 boot. Do you have the admin recovery VIII? Thanks a lot
Hi,
On SR V5, I’ve managed to fix it with:[Just in case you have to Restore]
- Create 2 Partitions just before the Recovery.
They can be empty but Formatted.
Here they were around 70Gb each one, – I suppose they could be smaller -.
Access your current Os or Use a Live Windows (Medicat, Hiren’s or any other) in case the Installed OS couldn’t be Launched.
Then,
Access the Samsung Recovery partition from Windows Explorer (make it visible if needed) and run RecoverySettings5.exeWinClon > Admin > Setup > Tools > RecoverySettings5.exeNow everything on Recovery should work as expected:
Fn+F4 Recovery
Recovery app from Windows.Take with you: Minitool Partition Recovery.
In case the Recovery, “Formats” your Data Partition, this App will recover it. - Create 2 Partitions just before the Recovery.
- You must be logged in to reply to this topic.