USB Installer creator not working

Comments

21 comments

  • Joe

    The reason why Dual-Boot is no longer a Thing is cause the Windows Updates for 10 messes with some Files and just use the Google Recovery Tool from the Chrome Browser and if you don't have Chrome use the WiN32 program LINK

    (In order to use the Image you have to set the File Type to * )

     

    0
    Comment actions Permalink
  • Forrest Smith

    You can download a CloudReady image and image it to a disk any way you want - some examples are in our guide under "Manual" USB creation steps.

    Note that the CloudReady image file you can download here is a zipped binary file. Depending on the tool you use, you may need to rename it to ".iso" for it to be recognized (Etcher, Rufus, Win32DiskImager all may require this). If you use the Chrome Recovery Utility, as in our guide, you can leave it zipped and not change the file extension

    1
    Comment actions Permalink
  • Radziu

    Hello. How to download cloudready 76.2 manually. I have version 74 and the system does not start during the update. I have Asus t100tam which is not officially supported. Or how to download development versions manually. I like to experiment and try to fix some errors myself.

    0
    Comment actions Permalink
  • Forrest Smith

    you can download v75 in an unstable preview here:

    https://go.neverware.com/previewrelease

    Install that and set it to the dev update channel to get v76.2

    0
    Comment actions Permalink
  • Radziu

    Thanks. I've tried it already and 75 does not boot. There is only a black screen. That's why I wanted to try clean installation 76.

    0
    Comment actions Permalink
  • Forrest Smith

    There's no major differences between v75 and v76 in terms of what kinds of hardware will be supported.

    Your hardware should, in theory, be able to boot based on the chipset inside, though. So I would advise you to focus on troubleshooting the install itself.

    * What kind of USB are you using?

    Have you confirmed that, once imaged with v74.4, it boots successfully on any other devices?

    Confirming that the USB works somewhere is a good way to confirm whether the issue is with device compatibility/settings or with the USB.

    0
    Comment actions Permalink
  • Radziu

    I use Kingston datatraveler 104 16gb. 74 boot fine. I try updated from devel channel to 75 and no success (Black screen). Then i download v75 ZIP manually and try to boot with no success again black screen. Now i think this is something with new kernel. And my Kingston boot 74 fine on Lenovo y700.

    0
    Comment actions Permalink
  • Forrest Smith

    I understand - v74 works on this device, but after the update you boot to a black screen. I was a little confused before, thanks for clarifying.

    That definitely could be an issue with the new kernel.

    Let me see if I can find any similar devices in-house here having an issue - if so, we could aim to fix this in an upcoming release. For now, staying on stable channel v74 is the best option for you.

    0
    Comment actions Permalink
  • Radziu

    Yes 74 boot fine. Things not working is:
    Bluetooth
    Rotate screen
    Backlight
    Camera.
    After updated to beta or devel channel dont boot. With clean 75 on pendrive dont boot. Only 74 worka fine except knowing Bugs.

    Thank You for interest with my problem.

    Sorry for my weak english.

    0
    Comment actions Permalink
  • Forrest Smith

    Hi Radziu,

     

    In a similar device (same chipset) we found the following:

    v75 and v76 fail to boot, as you've seen, but can be fixed. To make them work properly, look in the BIOS and adjust settings to target "64bit OS" or similar. That gets the device booting again (or allows install).

    Let me know if that works for you?

    0
    Comment actions Permalink
  • Radziu

    Hi. Dont have any option on bios that's let install 64bit os. Only had a secure boot that is disabled. Maybe problem is that the Asus t100ta can install 64bit system but its has a 32 bit uefi and its need a bootia32.efi on EFI/boot folder..I do not know if it will help. I tried to install linux manjaro and after upgrading to 4.19 kernel the system booted but after switching to 5.2 kernel it was black screen.

    0
    Comment actions Permalink
  • Forrest Smith

    Sounds like the 5.2 kernel (which is much newer than what's in CloudReady) may have bugs for this hardware as well.

     

    I don't think the 32bit uefi should impact CloudReady's ability to boot by design, but there could be a bug present.

    0
    Comment actions Permalink
  • Radziu

    If there is no bootia32.efi on the installation disk, then the system will not boot. This is the problem with this device.

    0
    Comment actions Permalink
  • Forrest Smith

    Are you saying you've verified that the bootia32.efi file that was present on v74 is now missing on v75+?

    On v76.2 in the Home Edition beta channel, I can see a 32bit uefi file:

    0
    Comment actions Permalink
  • Radziu

    No i dont verified that. If bootia32 is in EFI that must be something wrong with Kernel or maybe video drivers. Really dont know.

    0
    Comment actions Permalink
  • Radziu

    Is there any option to boot cloudready on text mode without ui? Will try install 32bit version of OS and then update to dev channel.

    0
    Comment actions Permalink
  • Forrest Smith

    Sort of - once booted, if you're stuck at a blank screen or similar, you can try pressing ctrl+alt+f2 (some devices will need the fn key as well).

    If the device is able to boot and the UI/graphics is the only issue, you should land in a console where you can specify username: chronos  and then have access to the cmd line.

    If you find that keystroke doesn't work, then the issue is not with the graphics only. 

    0
    Comment actions Permalink
  • Radziu

    Ctrl+alt+fn (with and without fn) dont work. Screen dont even blink, no reaction. Is there any link for v75+ 32bit?

    0
    Comment actions Permalink
  • Radziu

    Ok v76.2.12 32bit boot fine but sadly for me bluetooth still not working.

    0
    Comment actions Permalink
  • Forrest Smith

    We have a fix that applies widely for bluetooth coming in our next v76 update.

    0
    Comment actions Permalink
  • Radziu

    Im trying manually add driver for my bluetooth but its not working. The driver is bcm4324b3.hcd according to tutorial how to install Ubuntu on t100ta (https://github.com/5bentz/linux-asus-t100/blob/master/T100TA_guide.md).

    0
    Comment actions Permalink

Please sign in to leave a comment.