How do you get in windows safe mode?

[Reinier]

Thanks for the instruction.

Im stuck after list disk.

see image from my pc

Attachments:

You must be logged in to view attached files.

[Reinier]

i have mounted the iso with ultra iso, my usb is F: and the win iso is G:

Attachments:

You must be logged in to view attached files.

[Reinier]

I made the win10 bootable usb like you instructed, but when i put it in the iwork8 air and set it as the boot device in the bios i still get the notmal bootup menu, maybe something has to be changed in the bios?

[OptoMan]

hey Reineir — seems you got further, but just in case ..

after list disk, in this case would be select disk 1 . then could clean, convert, create, format, exit.

also your computer you’re prepping this on seems to be win10, which does have built in iso mounting capabilities. very cool .. one less program to worry about being broken or ill configured.

anyways .. if you think you’ve made your boot disk, and can even explore that udisk and see all the stuff there, it really should be good. (I have to say this, again we did not record a boot sector so this will not boot on any computer that requires a bios/mbr style boot drive. this will boot only on modern computers looking for uefi boot stuff .. in particular, gpt partition table, at least one ‘common’ filesystem on one of the partitions like fat or ntfs, and in there a folder called EFI along with some special files. this can tell you something about your prep machine if you happen to leave it in and reboot. no more no less but that’s a fib =)

here’s what’s left and this can be surpising and yet a subtle and deciding factor — the OTG adapter .. if it’s low quality, it might not work for this purpose. make both ends are fit in all the way and move on to bios next but maybe come back and try a different OTG adapter. dono if you’ve ever had a failing micro to usb-a cable but it’s hard to flash a tablet or sync a phone even tho you just bought the cable. the ones that come with the devices usually are the ones to hide away just for this — for instance, a recent exception of mine, I got a quick-charging station/usb-hub that came with a long and a short cable. they look great and such but I will use them for charging only it turns out. the otg that came with my cube seems great — showing silver connection is starting to grow on me. you can see from inspecting bios that usb chip is set to use all its usb 3.0 smarts whenever possible — even though we’ll always go the speed of our udisk, and number of pins on our cable (usb 3 cables have more pins, sidecar) this thing is probably picky about noise — let’s not do that during boot sequence.
and this is wrong to not say — you are probably using a hub — so you can boot udisk and have input — the x: prompt you were at might come from recoery mode from your tablet and otg’d keyboard alone, I hope you have a hub — and _that_ could be part of the problem. check for good quality cables, and if it worked the other day .. exactally.

in bios — you _can_ safely choose the option to reset to defaults. I have tested this, further supporting that this bios is for this model device and there are different ones for slightly different versions of same tablet — they used one or two different chips in making different lots of the tablets. but each separate release bios has proper settings for that device.
if that seems good — I don’t like trial and error, more like process of eliminatioin but playing in the bios isn’t fun. things for us to check —
manual set OS Image ID to ‘Windows 10’ under [advanced] system component .. this is how win10 udisk boots for me
some people turn off ‘fastboot’ — I haven’t had to yet. it’s a feature of newer windows (not necessarily exclusive to microsoft) that is a blend of hibernation and shutdown so that the os boot process can do somethings just like last time instead of, hey service, what do you want to do?

with udisk inn good otg adapter, image id, should be able to go to bios, exit tab and select your thumb drive visible at the bottom. this is the stuff that can drive people desparate but you seem quite patient — very nice, only way to be

[OptoMan]

another reply — looking at your listing at your file explorer drive listing — I see your 16gb udisk and I see your external cdrom. I don’t see a mounted image file, for a moment I was going to wonder what image you had mounted .. again looks like there’s not one mounted. being accurate and complete, lol, mount with file explorer built in, the windows 10 media you downloaded from microsoft — your edition (home unless _you_ know otherwise, really) and language/country, and for x64 bit not x86 — that’s also paramount.

this is really cool stuff because these tablets are real 64 bit computers with intel chips,, graphics, sound all the stuff. the internal sd storage throws people off. remember most android devices run arm-cortex processors, totally different breed. I’m not linking to microsoft or intel sites, but the search you probably have made is ‘windows 10 media creation tool’

[OptoMan]

pretty much last follow up — there’s not much left. you shouldn’t have to buy any hardware (adapters, cables, hubs) — everything above is most all there is to it ..

what’s left is that you could flash the stock cube windows 10 with OTG and udisk with only a single line modification to cube’s install script to make it completely automated so no keyboard needed or hub — this would mean you would lose any personal stuff you downloaded that isn’t as easy as just reinstalling something from windows store.

to back up, how you got to that x:\ prompt, says you either had touchscreen’s on-screen-keyboard or an external keyboard OTG, so you could manually copy from prompt or maybe file explorer anything you locate in directories to sd card or usb. messy, but windows wouldn’t be broken. keeping windows from breaking is a whole nother subject — running out of storage space, out of memory so now swap programs to slow internal storage, and letting too many backgound apps fight your foreground windows and the OS in the background doing important and giant configuration changes/finalizing. one setting to tweak in bios is to allot _more_ memory to graphics so it’s not adjusting so often taking a toll on the OS.

[Reinier]

Hey Optoman,

I first tried in win 7, but i have also a win 10 notebook, so i tried your instructions on the win 10 and created a uefi bootable usb disk, i checked the files and there all there, the otg cable is working fine, i can read and write in android and the mouse and keyboard works fine to thru the otg cable.

I checked the bios and it is on win 10 and try to enable and disable fastboot, but still no boot from usb.

Yeah i can be very patient, i was a helpdesk employee for 9 years first and second line.

I have solved many problems but this one goes over my head, lol

Since i used windows 10 on the tablet i did not install very much, i just wanted it to work with my mail and some other usefull stuff.

I ran into problems with changing the sd card drivers, and win 10 is in a boot loop, going to the win boot menu.

I like to go into safe mode so i can undo what did, but that is not a easy thing with win 10 in combination with the cube.

I tried so many options, but no luck so far.

Anyway thanks for all the help your giving me.

[OptoMan]

unfortunately I’m around here today, hah — you are so cool. I got this tablet cause I like projects, and it IS cool. I do computer stuff.

this is a toughy because as you can see, the udisk should load before the broken win10. I have to painfully interject that safe mode could help in theory, but we’ll probably never get there as it’s a working windows desktop with some drivers, services and softwares not running by default — no registry, bad sd access.

I’m going to try to type this, but we’re looking at safe mode and recovery which are two different thengs — recovery might be able to launch safe mode.

the x:\ prompt was from a boot to windows recovery, either from on system or from usb. it’s a small specialized version of windows that places itself in ram and gets a drive letter (called a ramdrive), which will let you mess with all other drives at the same. on the cube it’s found on another partition, again RE could also be loaded from an external

safe mode isn’t going to work I’m sure, but if you could boot to safe mode, again it’s just a modified startup of a working desktop system (working is funny here, people use safe mode when their desktop doesn’t finish booting, but it’s all the softwares that want to startup, some bad drivers [safe will load critical, basic drivers only, by choice networking or not also], and some services that are in the middle of a giant operation that probably has corrupt data or is really competing for resources with that above forementioned) — you can do RPs from recovery mode .. which ..

win10 has SR points turned off by default because they were great for older versions of windows in some respects, but they cause way more problems than actual fix-use cases! space taken, time to make points (every boot, drive thrashing, never using RP anyways), interrupting making restore points (gonna sleep, shutdown, I dono it’s doing this anyways, carry on later), and when people do use them, things are misplaced and ill configured — manual set points are neat sometimes — so …

better remind that a working desktop needs a registry. and you said boot loop. not starting desktop.

but to navigate from recovery envirnoment to uninstall or reinstall drivers and hope that’s all that takes — still have zero-ed registry files. they have to come from somewhere, basics are copied during installation and then built up to include a whole picture of the device, drivers, then software, users and all their settings. and it’s protected. identifies most everything.

didn’t catch how you got the shot of your x: prompt — you say boot loop, so I assume external drive, I don’t see windows offering recovery during a boot loop and dono how you would have gotten to the one found in the tablet — no hotkeys or button combos.

so definately need a repair installation that might even want to do a full blown windows install that won’t remove anything from existing directories which you might have to hunt through later ..

that’s what we’re looking at — and we’re back on booting to the win10 media.

[OptoMan]

I quickly booted to my windows udisk last night .. just check Image ID and select the udisk .. I’ll be thinking ..

<hr />

alright that picture wasn’t your screenshot, if you think those registry files are missing, great — if you speak german, great .. but you need to ask help to a problem that is only as specific as you know ..

bootloop, just think registry is corrupt?  sd card drivers led to believe — really tho if you see them missing, just maybe having broken sd access told windows that what it was about to load wasn’t good and to get it the heck out of the way.  you can’t just copy someone else’s registry and further, this does not get any simper — copying a basic one is the same as installing basic windows.  all specialized knowledge is lost.  I’m not pulling the reg out of the imge for you.  might not match anyways.

I’ve seen people put a system drive from one machine to another, but they don’t touch my stuff — getting some media to boot is the current problem but where you go after that needs to be considered.  otherwise you’re getting a tour to throw out the window.

I’m venting over here — but this is why I’ll appear for a few weeks and disappear — people, not necessarily you, come up with great ideas that are usually out of desparation or MORE IMPORTANTLY, have some great idea that still leads to nothing great.  let’s brick this thing!  really tho —

getting a usb drive to boot .. I’m not gonna go on much longer .. I will direct you towards a factory flash and that’s what you should do when you’re fed up trying to repair windows with windows install media.

 

 

[Reinier]

By the way mm from the Netherlands, the boot loop i mentioned is you boot windowa give a blue screen and says it will reboot for you than you boot in the windows bootloader with repair options, none of them work only the turn of and the dos prompt, automatic repair says it can not repair and recovery has no files, so yeah the next thing to do is to install windows, the windows part of the cube has nothing important, but the android part does, so i will try to install windows, i have downloaded the file for the cube already and will study your instructions for it, thanks for the help.

And not to forget happy new year and the best wishes.

[OptoMan]

happy new years is cooler than you think, buddy — this stuff can get nuts

okay .. windows on our tablets has a pretty simple partition layout.  there’s an efi partition that is small and helps to boot.  that’s as far as you get.  the microsoft reserved (msr) partition is for storing temp data between boots, like, hey we’re actually hibernating so boot accordingly here’s some info, then the system data partition is where you find windows, and fourthly the recovery partition where windows recovery environment is.

if you can’t get to windows or to recovery but you can get the options, your efi partition (this is the windows’ efi partition, there’s other …..) will show you those but those have to be accessible to be used.
if they are corrupt or if the menu chooser can’t correctly find them, that is the problem — and let’s notice both are broke, and make conjecture about the problem later!

cool.  so — here’s a messed up chart for fun and more like warning of vocabulary confusion someone else might use or you will read later:
efi (aka “system” type on bios-mbr boot computers, important to bios — where to find a ‘boot manager’ by definition. people think bootloader.. the choices)
msr (type only used on efi/gpt windows machines)
system (where you find windows, your system — BOOT type, means there’s a boot LOADER, loads the operating system, os loader is found in windows dir that’s all)
recovery (where windows recovery environment is found)

just some fyi. so the [technically speaking] microsoft boot manager (which was found by the two-choice efi boot manager that is flashed with android that *I* like to call a boot loader– see?) is found and started but can’t find your two important partitions or start what’s supposed to be on them, and that’s where we are!  it’s some more run around, but if you could boot from usb media and get do command prompt, load diskpart, list volume, it’ll show recognizable filesystems, even ones that are not supposed to have drive letters.  you can temporarily assign letters and go to it and see if it looks like windows or recovery is there.  dir /a shows hidden and system files as well as standard, recovery might look empty but have much hidden.  it’s been a minute since I’ve reassociated windows volumes with the ms boot manager

so — that’s what to do next in these cases .. see what I mean?  hard to say all that could be said, to anyone! =|  I don’t load a ton of apps either .. I can run old android devices as best as they can .. but other people, arg!!!

 

 

grab the latest firmware from cube for *your* specific model, please be careful choosing a download, it might actually be quicker where you are then here, took me about 8 hours .. but get the proper model’s images, for instance, i1-T is not i1-TC .. if your model/serial number on the back starts out i1-T and then NOT a C get i1-T .. there might be other besides C.

the windows install is great but does need on modification and it’s not difficult. or you could just have a keyboard attached as well as the usb drive and press the damn any-key.

kudos and hollar if something looks funny! peace

[OptoMan]

I might have to blow something up .. we’ll get that

 

[Author]

Posts