Search Results for 'cloning'

[George G]

Hi Kyprianos,

Not sure why your method is not working, but I can tell you that cloning with Macrium will work, assuming that your SSD works.

In Macrium free, you simply drag all the partitions one by one from the source drive to the target drive. You will resize the Windows partition (C:) as you go by clicking the “Partition properties” link under the graphical interface. Remember to leave some room for the last recovery partition, which I resized to 1 GB just to be safe.

After cloning is complete, go to Windows Disk management built into Windows 10. Make sure that the second cloned drive shows.

Then boot into the UEFI/BIOS. You should see two boot managers listed there. Simply select the boot manager that corresponds to your SSD (press “enter” to determine which one) and set it to the first boot position 1. Save and exit.

Reboot and check that your SSD is now C: drive. The eMMC should show as D: drive. I did not wipe the eMMC and left it as a backup.

I hope this helps. Please let me know how it goes.

 

[George G]

Hi

Did you solve your problem?

Did you look in Windows disk management to confirm that the SSD is listed and showing the correct partitions?

Which SSD did you use?

You might try cloning it again, or use a different program. Others on the forum have had success with Aomei. I used Macrium Reflect free v6 to clone my SSD.

Changing the boot order is pretty straightforward. You should see two boot managers listed there, just make sure you select the correct one that corresponds to your SSD.

Beyond that, there should be no other UEFI/BIOS settings required for an SSD boot.

[George G]

I installed the cheapo KingSpec SSD part number NT-128 ($45) and had no problems except for removing the SSD retention screw under the M.2 hatch (in V4). It was poorly machined so I had to use a pair of needle nose pliers to loosen it. Luckily, the SSD comes with a good retention screw so I used that one instead.

Benchmark results are similar to what is posted above. When cloning, remember to resize the Windows partition to fill the SSD. I resized the recovery partition to 1 GB as well. After installation, check disk management in Windows to make sure the new drive is showing. Upon reboot, the UEFI/BIOS will show two boot managers if you did not wipe the eMMC. Just press enter to select the NT-128 for the first boot position.

I did not reformat the eMMC and decided just to keep it for backup. The 120 GB on the new drive is plenty for my needs.

All in all, I paid a total of $275 for the laptop and the new SSD. Not bad!

 

[Darren Lindsay]

Hi

Installed a Crucial MX 300 525GB SATA M.2 2280SS SSD. It is being recognized in my Jumper EZBook 3 Pro but when I try to run the accompanying Acronis software to clone Windows 10 over to the M.2 drive the software looks to work until it gets to the reboot and leaves the laptop in a mode that says “Acronis is loading please wait”. I’ve left this for hours without any further progress and I end up restarting the computer without the process completing. Once back into Windows 10 the cloning has not taken place.

Can anyone please let me know what steps I might be missing to allow this migration.

Thanks

Darren

[Alessandro Gioffredi]

Thank you very much for the delusions: you always learn little more things and different procedures. Everything makes culture. The directors you sent me have already downloaded them from your previous post. My came a week ago, dual band AC version. Are they okay? On the Jumper site I did not find anything … ne driver dump. Less bad I always have the habit of making a ghost clean image before working … When I tried Cloning the eMMC on SSD I used HD Clone Professional 4.3 but I think it’s old … and not suitable for making copies of UEFI …I do not know. Or it does not start because it simultaneously finds two identical copies of WIN 10 … I could try, after cloning, only to clear C: leaving the recovery partitions of the eMMC and see if it starts from SSD. What do you think about it?

[Alessandro Gioffredi]

Hello bigboybig. I did some discoveries and something has improved. I tried to install win 10 from external dvd and with amazement and doing the same operations, the installation started. But each time it was booming at different rates. Then in the end I downloaded a iso from microsoft and put on usb with their media creator … now win 10 you install to great !! And above all, it never stops. But I still have problems and I would like to ask you for help: I ​​installed win correctly but I can not get all the drives installed properly because the pc that now has win starting at m.2, is very ticking and 20 mins goes freez and locks . In short, always climb … what package did you use? Are there any special curiosities? To have no doubt I ordered a m.2 2280 Crucial x300 from 275Gb not to rule out that it is not good ZTC 128Gb I’m using now. Otherwise I had thought of cloning with clonecd and then erasing emmc …. because it goes freez every few minutes is destructive

[Jukelea]

I’ve taken a M.2 SSD from Transcend in 2242. After formatting in Windows it was detected and I could install Windows on it (cloning from the EMMC). All running fine.

[OnDreek]

What I recognized: after cloning with macrium free I went directly into bios to change boot manager and switch to the ssd. After that the new ssd was automatically set to c: (windows). So there weren’t any problems with the search engine / index function.

 

[Ernst]

Hi,

Perhaps the owners of a LapBook 14.1 have noticed that after cloning Windows on the eMMC to an SSD, the search function from Windows 10 doesn’t work properly. Most noticeable when searching for “Windows Update”. If it finds links to this, for instance “Windows Update Settings”, and you click on it you will get an error.

Most PC Settings in search give this error. This is caused by the fact that Windows sees two harddisks with two identical Windows setups. Windows uses a number of ID’s (called GUID) to identify a Windows setup. There are now two harddisks with the same volume name, and important here, the same indexer GUID.

The solution is here:

https://answers.microsoft.com/en-us/windows/forum/windows_10-win_cortana/windows-10-indexing-selects-wrong-drive/685ec87b-e7f3-454b-89c9-c485b94bb69d

What worked for me:

• Create a Windows recovery drive (USB) and boot into it
• Open the command prompt (from within Troubleshoot -> Advanced Options)
• Type del “D:\System Volume Information\IndexerVolumeGuid”
• Reboot

And then rebuild the index (which will take a while) in Control Panel, Indexing Options, Advanced. Make sure that you include (not exclude) the c:\users\<your username>\appdata directory too. If the settings show you that this directory is disabled make sure that within File Explorer hidden files are shown, then you can deselect this directory. It is a hidden directory.

The appdata directory stores a large number of pointers to all the various PC Settings so that they can be found from Windows Search.

I used a very slow old USB 2.0 flashdrive. Creating the recovery drive took several hours…

Take care.

Ernst

[Kunc]

hi Guys!!

 

So, i had no luck with the cloning attempts, both using Macrium or the one you suggest failed with different symptoms (the macrium caused the driver for camera worked poorly, wifi and bluetooth didnt work), the other made the startup failed.

So, i tried a fresh install of Windows 10, and ended up with pretty good result. My Cube i7 book works fine now. But one other problem happened, the camera is not working.

Have checked to the thread mentioned above, but seems mine has different problem cause the two Control Logic drivers are in the same version as required in the thread solution.

So, don’t know what to do know cause every single driver already installed with success message on each installation.

 

Btw, the way i cloned using macrium and the other one was something like this:

1. Start up Cube i7 windows, and install the cloning software.
2. Start the cloning software and make clone of the drive C (which is in cube i7 should copy everything, including the system, recovery and the other partition)
3. Dismount the old SSD and mount the new one (the bigger one with cloned windows from previous SSD)
4. Start the Windows, and…..
   1. Macrium –> windtab32.dll error at logging in, camera wifi bluetooth not working
   2. Aomei –> Going to the Repair windows screen, and couldnot do anythin
5. So decided to put back the old SSD

 

Okay, forget what i’ve done with the cloning,. anyone help me with the camera please…

[Katagiri]

Kunc wrote:

Thanks God the problem is not the hardware, cause after put the old SSD back and start, everything was just fine. Let me try the tool you recommend and get back to you once done. Thanks a lot mate!!

That happened before with the same tool you used, maybe it’s not cloning everything. At least Aomei says it works well with SSDs even cloning HDDs to SSDs.

If it doesn’t work you can try a clean install like Wylver said.

[Kunc]

Hi,

I just upgraded my Cube i7 Book SSD to larger capacity, and already completed cloning the previous SSD to new SSD using Macrium Reflect software.
But i got problem, when i tried to start it up, found out the screen went black and a message like listing all the drive block number etc and the bottom of it was prompt to choose whether skipping startup.nsh or continue something.
Unfortunately, i don’t buy the bundled keyboard, as i planned to use bluetooth keyboard (just want to be more handy). Is there anyway i can do to startup the Windows 10?

Thanks a lot.

[Matthew Kwan]

Dual Boot instructions:

Before you begin:

DISCLAIMER: I am not responsible for your tablet getting bricked, Thanos completing the infinity gauntlet and taking out half the galaxy together with your tablet, or any other unfortunate events of personal or cosmic proportions. Proceed at your own risk!
*I have faced the issue of battery % getting stuck at 99%/100%, no idea how to fix it.
(Note: There seem to be some redundancies in creating partitions and backing up files but well, better safe than sorry)

Note: Have to rush out so the pictures and placed as attachments instead of in text, will fix them in future.

CREDITS: This method is from jigu and a very helpful English translation by lawguy, the original thread can be found in http://en.miui.com/thread-248564-1-1.html I am just consolidating some other files (thanks to Chris G of techtablets for the Windows Drivers, http://techtablets.com/downloads-drivers-roms/) and writing out the parts I had trouble understanding from their guide.

 

Download the files needed from: https://mega.nz/#F!5llEzRhR!Tv__zvfy6yM6HSHXkEeunA

Download UltraISO from  https://www.ezbsystems.com/ultraiso/ to create the WinPE and Win10 installation usb drives

Create a WinPE drive with the ISO from the folder

Copy the everything from “WinPE disk additional files” into the WinPE drive you have created.

Create an Android ESP and Windows ESP folder on your WinPE thumb Drive

Create a W10 installation usb drive by following the instructions here: https://www.microsoft.com/en-in/software-download/windows10

Makes sure you have a usb-c otg cable, usb2.0 hub (my usb3.0 ones couldn’t work with the mi pad 2), usb wired keyboard and usb  wired mouse
Section 1:

Regardless of whether you’re using the Android or Windows version currently, you will have to (re)install Android  http://en.miui.com/a-234.html (for those currently on Windows you’ll have to hold Volume +, Volume – and Power all at once for about 15 secs to enter DNX fastboot)

Follow the instructions until <b><i>step 4.</i></b>

“Step 4:Double click on the downloaded ROM file to decompress it. Open the file folder for the decompressed ROM pack, and copy its path on the computer.”

After you decompress it, replace the gbt.bin file (it helps set up the partitions, which we will be using for messing with the efi later on)

 

Section 2:

You’ll now have to install windows.
If you haven’t already, you can create a W10 installation usb drive by following the instructions here: https://www.microsoft.com/en-in/software-download/windows10
Plug in your usb-c otg cable with your usb2.0 hub, usb wired keyboard, usb wired mouse and Win10 installation thumb drive.

Reboot your Mi Pad 2. If it doesn’t boot to the Win10 installation screen, reboot again and spam F2 to get into BIOS. From there, go to Boot Manager and select the USB option.

Follow the installer until you come to the option of what kind of installtion you wish to do, <b>you must choose Custom Windows Installation</b>. Choose the partition that is about 44GB in size.

It will go through a very long installation process and reboot at the end of the installation.

When it reboots, <b>remove the Win10 installation thumb drive</b>. It will boot back into Android.

 

Section 3: Booting into Windows10

Your otg, hub, keyboard and mouse should still be attached. Attach your WinPE thumb drive as well and reboot the tablet. If you do not boot into WinPE, reboot again and spam F2 to get into BIOS. From there, go to Boot Manager and select the USB option.

On the desktop there will be a DiskGenius shortcut, double click it to run the program.

From the Mega upload at the start, there’s a program called Partition Guru Pro, it’s actually just like Disk Genius but in English (couldn’t get it to run on the Mi Pad though) You can run it on your laptop/pc so you can understand what your clicking.

 

You will now select the 32MB partition that holds your Android EFI. It should be ESP (6) or something like that (mine says NEW VOLUME C: after using the tablet for some time, no idea why)
You will clone the partition to the Android ESP folder in your WinPE drive.

To Clone, click on the 32mb partition and choose the option with (I) at the end of the name (once again, you can refer to Partition Guru Pro on your laptop/desktop for the English commands)

 

After cloning, click on My Computer and navigate to the bootx64.efi(~4.3mb) on the 32mb drive and copy it to your Android ESP folder.

We will be then be replacing the bootx64.efi(~4.3mb) in the 32mb drive with the same bootx64.efi(~1.1mb) that you find in the ESP folder of your WinPE usb drive.

 

Reboot (<b>remove your WinPE disk</b> so it doesn’t boot into that) and windows 10 will finish installing, you should now install the drivers from the drivers folder found in your WinPE thumb drive. Insert the WinPE disk again and copy the DiskGenius and BOOTICE folders/files onto your desktop as well.

 

Section 4: Dual Boot

Right click My PC and select Manage. Click on Disk Management and select the largest (~43mb partition) and select Shrink Volume. Create a new partition of ~100mb

 

Open DiskGenius and go to your ESP partition. It now contains the Windows booting ESP files so clone that to the Windows ESP folder on your WinPE thumb drive.

(you now have backups of both ESP folders so if any updates resets your boot order or something like that, you can boot into the WinPE drive, run BOOTICE from there and sort it out again without reinstalling everything)

 

Now extract the clone you just made and select the new 100mb partition, that you just created, as the destination. This will be your Windows booting ESP

 

After doing so, copy the backup bootx64.efi (~4.3mb) from your Android ESP folder on your thumb drive back into the 32mb partition. This will be your Android booting ESP.

 

Run BOOTICE and make sure it is setup like the screenshots below

When you want to boot into Android, select the AndroidIA option and check the box “Boot this entry next time”, hit save and close.

After doing so, check the box “boot to firmware setup UI the next time you restart computer” and then click “Restart now”.

The Mi Pad will boot into the Bios. You will not need a hub and keyboard (however, ensure that you have disabled UEFI secure boot, it doesn’t always stick at first but boot a few times between Windows and Android and it stays) Use the Volume keys to move to “Boot Manager” and select that entry with the power button.

You will boot into Android

 

To boot back into windows, simply reboot the tablet.

[Anonymous]

Hi, if there is one thing about Onda is that their cases are usually easy to open – which I don’t know is a good thing. :0)

Just gently unscrew the 4 (?) screws under the white cover at the top. Put these screws in a safe place because they’re small and easy to loose. You then need to find a section where you can find that you can separate (slightly lift) the back from the tablet body. I think I was able to do this near the sd/sim slots under the white cover.  Using a thin piece of plastic such as an credit card or guitar pick gently insert it in the slight opening and start to slide it along the seam of the tablet. Go slow and don’t go too deep with the thin piece of plastic because you might sever wires inside the tablet. When you open the tablet the on / volume buttons might come off because they aren’t attached to the body of the tablet. I put a small piece of tape between the volume up and down buttons to hold it in place when I reattached the back. Installing the new drive is easy. As a precaution I would disconnect the battery.

I havent tried cloning the o/s on  these tablets. When it comes to new hard drives I usually do a new install because of the increased size of the new drive.  If you new install remember that Android must be installed first also if you’re using the Onda install of Windows chances are it’s a hacked version which means a new install of Windows will loose activation. I guess you could make a Windows backup using the Windows backup function and restore it after you install Android but I am not sure if you would be able to adjust the partition size.

Let me know how you make out.

D

[Anonymous]

The iwork 12 will only have the same screen, battery, wifi and external build, the most relevant hardware(SoC, SSD, …) will be different even if on the outside they look the same.

And you should be able to backup the original OS as long as you can boot from a usb drive. Just create a bootable linux usb with enough space and use dd with the output set to a file in the usb itself. There are plenty of guides and forum posts about how to do just that, for example https://wiki.archlinux.org/index.php/disk_cloning#Create_disk_image .