Atrix error 0x1000

atrix error 0x1000

Previous Installing Atrix-MROM on an Atrix 4G with update. Who didn't tried "that kernel" as I do cz of error reports from Peopğle, Just give. › article › FAILED+TO+BOOT+0x+Help+. Hi, tried to root my phone but there was a problem. Did the motofail2go and there was no errors. But then I tried the razr i root from mattlgrof, but there was.

Atrix error 0x1000 - sorry, not

--primary] [DEVICE] [VOLUME]

vol will list all volumes

vol FRED will set as root the volume with a label of 'FRED'

vol (hd0) FRED will return TRUE if FRED exists on hd0

add --primary if you want the primary volume descriptor (as used by linux) instead of the standard volume name.

--write will overwrite the volume name (do not exceed vol name length limit)

================================================== ========================================

Part 4 - kernel, initrd, module, modulenounzip, chainloader, boot, pxe, quit

kernel [--no-mem-option] [--type=TYPE] FILE [ARG ]

Try to load the master boot image file. Other items will be used as the kernel command line parameters passed to the kernel.

Before using this command, the kernel used by the module should be reloaded.

--type Parameter for describing the kernel types, including "netbsd", "freebsd", "openbsd", "linux", "biglinux" and "multiboot".

--no-mem-option parameters for describing the Linux memory need not automatically pass mem parameter to linux


initrd FILE [FILE2] [FILE]

Initialize the virtual disk to load Linux format, and set the necessary parameters. Specify start before the real root file system access, access ramdisk images in the system.

By the following command to start the kernel and initrd Ubuntu LiveCD:

title starts Ubuntu amd64 LiveCD

# Find UBUNTUXISO where disk and set it as the current disk


# Try to load the master boot image file, followed by the parameters passed to

kernel /BOOT/UBUNTU/ boot=casper iso-scan /filename=/BOOT /UBUNTU /UBUNTUXISO

# Load Linux virtual disk initialization format

initrd /BOOT/UBUNTU/

Do not use multiple initrd lines for multiple image files, instead place all image files on same line, e.g. initrd /boot/file1 /boot/file2 /boot/file3


module FILE [ARG ]

For multiple boot image file to load the startup module (not handle the contents of the file, the user must determine their own core requirements).

The remaining arguments as "fast-mode command-line" pass, like kernel command.

This command is typically do not have access, when you want to start when the Linux system, and the system requirements for the load module file, will be used, related to the Linux system will be described, the average user can ignore this command.


modulenounzip FILE [ARG ]

Similar to the module, but disabled the automatic decompression.

As above, the average user can ignore this command.



chainloader /ntldr

Load ntldr boot file

chainloader (hd0,0) +1

Load (hd0,0) first sector

chainloader +1

Load current of the first sector of the device

chainloader --force (hd0,0) +1

Load (hd0,0) in the first sector, the sector started to ignore the validity of identity, forced to start

[Note: chainloader there are many other parameters can be modified before the start of the CPU registers, but for the average user, these things will not be used, if you want to know more chainloader parameters, refer to "Grub4Dos help documentation "]



Boot loaded operating system or chain loader sector, OK to start, usually with the use chainloader command in the menu file can be omitted, the command line mode requires.

chainloader /ntldr


Load ntldr boot file, and then start.

boot -1

Call the BIOS int18 function, according to BIOS boot order set to start next device.

boot --int18

As above, call the BIOS int18 function, according to BIOS boot order set to start next device.