Hello.
On a Chuwi Hi12 dualboot tablet, loaded on Windows 10, I reduced the partition "Windows", by telling me that it was the first stage to pass place of Windows (that I use little) to Android (which misses it).
I used EASUS. The manipulation was made well, in the sense that Windows always works and when I have well a free place on the memory.
Other partitions, EXT3, are always there, and nothing strange under Windows. But I cannot any more booter on Android: logo Chuwi one moment then black screen.
I can switch off and reload Windows.
It seems that the table of the partitions or one of the partitions which interest Android was modified.
Attempt to reinstall Android. Using ROM of Hackerjac (http: // forum.chuwi.com / forum.php typeid%26typeid%3D6). With Phone flash Tool Intel with flash-no-erase.json, config Recover).
Many failures (fragility driver USB? Reinstalled). At the end and at best: failure repeated on the installation of the bootloader, with message on the tablet " Failed to get partition bootloader2: Not found ". Rather clear but disappointing: the partition is not recreated?
Thus I am there to try to understand what is made by flash, and how have a gpt.bin which corresponds to a chosen distribution (editor of gpt.bin).
Thank you for your help.
Related
I have a few questions about Archos' devices, in particular those belonging to the Generation 8 family. Here they are:
How is the partition table setup on the device and is the partition table signature checked? How are the partitions logically laid out?
When the SDE is installed and run, boot1 locks up boot0, itself and the recovery partition to prevent them from being modified. I would imagine that this type of setup would require keeping the partition table from being modified, thereby preventing dual boot. Can dual boot be achieved using the SDE without any extra modifications?
Are some of the partitions on Archos devices contained in compressed images and then loaded into the RAM in a manner similar to the way Damn Small Linux boots?
Is the recovery partition a minimal OS setup that exists to perform recovery operations or is it in fact copied in it entirety to the primary partition when recovery mode is entered?
I have realized/learned some things Linux that I hadn't noticed before such as the fact that folders like /home and /boot have their own partitions and that /boot may contain more than one kernel and that bootloaders like GRUB are actually represented in the filesystem. I don't if these are real partitions or logical partitions so I might have to do some relearning.
I'm bumping this thread.
Master Melab said:
I have a few questions about Archos' devices, in particular those belonging to the Generation 8 family. Here they are:
How is the partition table setup on the device and is the partition table signature checked? How are the partitions logically laid out?
When the SDE is installed and run, boot1 locks up boot0, itself and the recovery partition to prevent them from being modified. I would imagine that this type of setup would require keeping the partition table from being modified, thereby preventing dual boot. Can dual boot be achieved using the SDE without any extra modifications?
Are some of the partitions on Archos devices contained in compressed images and then loaded into the RAM in a manner similar to the way Damn Small Linux boots?
Is the recovery partition a minimal OS setup that exists to perform recovery operations or is it in fact copied in it entirety to the primary partition when recovery mode is entered?
I have realized/learned some things Linux that I hadn't noticed before such as the fact that folders like /home and /boot have their own partitions and that /boot may contain more than one kernel and that bootloaders like GRUB are actually represented in the filesystem. I don't if these are real partitions or logical partitions so I might have to do some relearning.
Click to expand...
Click to collapse
Partition tables are not locked. Devices are populated as normal in kernel. Partitions can be edited and the device repopulated with partprobe as normal.
The bootloader/recovery is held on a partition on mmcblk0, they are signed using a public/device encryption key, that has been broken. When the system is booted it mounts the recovery image and performs requested functions. The AOS firmware format is also encrypted, but has not been broken. The stock firmware is held on mmcblk0 as well, in an 256bit device key encrypted SquashFS(which has also been broken). It is mounted with a chroot as R/O at stock boot.
Dual boot can be achieved in multiple ways, easiest of which is installing the openAOS multiboot menu. A current limitation is that all OSes must use the same kernel, until we can get kexec working correctly(or other more dangerous solutions).
P.S. Folder's like /boot and /home can be many different things. Folders, partitions, images, symlinks, etc. The advantage of linux/debian is that everything is represented in the file system. Even sending commands to devices or modifying driver settings is done by "modifying files". For example, to flip the touchscreen's input on my A101, you write the letter "N" to a "file" called /sys/module/hid_hanvon/parameters/rotate180.
This is actually an interface to the driver for the touchscreen, not an actual file, so sending the letter N to "rotate180" tells the driver to flip the input coming from that device(hid_hanvon = the touchscreen).
If you tell me what you're trying to achieve, I can give you more details. If you are just trying to learn, you should come to the openaos IRC channel. Lot's of years of experience in there.
I didn't think bootloaders were stored on partitions. On PCs, the first stage bootloader is stored outside of any partition on the MBR.
Master Melab said:
I didn't think bootloaders were stored on partitions. On PCs, the first stage bootloader is stored outside of any partition on the MBR.
Click to expand...
Click to collapse
That's flashed on eMMC2. I was talking about the recovery bootloader. Basically, the bios is off limits, and the recovery bootloader allows updates, SDE flashing, etc. without risking bricking, as I'm sure you know.
So boot0, the root of all control on the device, is not stored in a partition, like the first stage bootloader on a PC while boot1 (or whatever special bootloader that exists for recovery purposes) is stored on its respective partition like a second stage bootloader on a PC?
I'm bumping this thread. Please explain further. What do you mean when you say "BIOS" and is boot1 the recovery bootloadr?
Master Melab said:
I'm bumping this thread. Please explain further. What do you mean when you say "BIOS" and is boot1 the recovery bootloadr?
Click to expand...
Click to collapse
Another bump.
I also want to know the partition layout of gen8 devices after installing SDE and UrukDroid.
I already installed SDE and when I plug the device to my computer I see 3 partitions:
/dev/sdb1 76295 469632 12586808+ 83 Linux
/dev/sdb2 1 30518 976563 83 Linux
/dev/sdb3 30518 76295 1464844+ 83 Linux
sdb1 - 13GB, doesn't contain a /system, but here's the menu.lst
sdb2 - 1GB, contains a /system (but i think it's not the stock android installation) ...maybe UrukDroid?
sdb3 - 1.5GB, contains a /system, but has only a few files, etc is missing for example
So is the stock android partition invisible?
I am bumping this thread.
Maybe this thread could be usefull for you : http://forum.xda-developers.com/showthread.php?t=1199450
I bought this tablet thinking it would be the best of both worlds. But the partition used for Android was rather small (4GB), and got full pretty quickly. It would seem like such a hassle to resize the partition used for Windows (21gb) because they were arranged like this in disk management: 64mb-16mb-16mb-etc-1gb partition for who knows what-4gb partition for Android-more 64mb partitions-windows partition-500mb recovery partition. Now I thought I'd use my 64gb micro SD and divide it into two partitions, one being an EXT2 of 20gb for apps. I'd need to use the app LINK2SD to move the apps, but lo and behold, Android was not rooted. (I kind of assumed it was)
So I tried to root the android portion of this tablet, using information from this page
(http://forum.xda-developers.com/andr...p-cwm-t2975096), selecting T4 as the trigger. It didn't show the option to install a package and I ended up selecting "recovery" instead. It rebooted into the tablet's own recovery mode, where I didn't do anything. Prior to rebooting, I got the screen to select either OS, but Windows was gone. Now what? I also tried the Kingo program via my laptop prior to the method mentioned on the link above, but it kept getting stuck at 23% and 10%, idk if that may have done something. Anyways, now when I try to force boot to Windows (by selecting "boot to windows" after pressing the power button), but all I keep getting is this command prompt-like environment. Is my windows partition lost or something? Please help.
Anybody? Help
Hey,
New to Remix OS and running into some issues.
Dual booting at the moment, Windows 7. Installed Remix successfully and booted up the first time with no issues. Everything looked to be working. I then restarted the system and selected Remix from the bootloader and it starts the boot process and then my monitor goes into standby mode and never comes out.
Went back into Windows and wiped out the installation using the Remix installer. Reinstalled again, and again no issues on first boot, all looks good. Restart again and same thing....
Has anyone run into this before?
System is an older Dell optiplex 320.
Update:
Initially I was running off the add on gfx card, Nvidia 7300 GT. While this displayed perfectly, it has the boot issue on restart. I then switched to the onboard gfx, which is an ATI Radeon Xpress 200. This takes care of the boot issue, but the image has a lot of colour distortion. Its usable, but not pleasant to use. Useless for pics and videos. I played around with the resolution (during boot, VGA=ASK) and there's no difference.
Ideas?
Reviving this old thread. I hate there being the same question everywhere with no resolution. I was able to resolve this issue, so I am posting the fix here.
This issue is because the built in formatter on the installer will format the partition table in GPT format and make it not be seen as a bootable device in many BIOS's, so GRUB never gets loaded and thus you get the blinking cursor as there is basically nothing to boot according to the BIOS.
The fix is to use a partition editor, any will likely work, but I used Hirens Boot CD and use Gparted (aka Parted Magic). On the drive you intend to install it to, wipe it and create a partition table that is MSDOS/MBR (under 'devices' in Gparted). This will create a standard MBR partition table. Create a new partition in EXT4 format, size it how you want or use the full drive, your choice. Reboot and load up the install media for RemixOS. Install it as normal again, but when the install options come up, select the drive where you created your EXT4 partition, and make sure NOT to format it. Let the install finish, and get into RemixOS again and try a reboot. It should now properly load up GRUB on boot and will boot normally now on subsequent reboots.
Just as the title says, I'm curious if there exists a touch (or hardkey, i.e. volume up/down and windoes key) enabled bootloader.
Currently i have to press arrow keys and enter to select either windows or android.
Is there such a thing? It would be amazing. Id rather not have to stop at the keyboard to boot to an os from grub.
Thanks in advance!
Well .. I had suffered from this problem for longtime and finally I solved by an app called android-x86 installer it's the only way to boot from your Windows tablet without keyboard at last what I ended up with .. so yo have to download an old version I recommend the ALPHA version and install it with android-x86 installer 2.4 UEFI version after finished installing you have to download the latest version of remix OS and extract with 7zip or winrar then replace all file with the same name in folder androidOS that the direction of ALFA you already installed now You can boot with two ways either from settings/update / recovery and then press restart now at advanced startup then after reboot choose "use a device " and last thing chose android OS wait 9 seconds in grub2 an finally the remixOS will boot or by simply choose android OS from boot menu by volume Up/down
Boot solution for XPS 12 9250
Will thank you for this post when my 'Thanks!' get replenished on XDA. I'm still only using windows 10 on this tablet PC.
It is not clear to me is this is dual boot Android/Windows, my understanding is that this particular usage of the Linux grub bootloader only boots to Remix OS which is android. Grub, as you know does have dual boot capabilities, but maybe not yet on the XPS 12 9250.
Sorry, but the instructions are not step-by-step details for me, and I seem to be not smart enough to follow them. Could you point me to a 1..., 2..., 3.... please?
Please update or PM me whenever you feel you have found a better boot solution for our 9250's. I will be most grateful.
namitutonka said:
Will thank you for this post when my 'Thanks!' get replenished on XDA. I'm still only using windows 10 on this tablet PC.
It is not clear to me is this is dual boot Android/Windows, my understanding is that this particular usage of the Linux grub bootloader only boots to Remix OS which is android. Grub, as you know does have dual boot capabilities, but maybe not yet on the XPS 12 9250.
Sorry, but the instructions are not step-by-step details for me, and I seem to be not smart enough to follow them. Could you point me to a 1..., 2..., 3.... please?
Please update or PM me whenever you feel you have found a better boot solution for our 9250's. I will be most grateful.
Click to expand...
Click to collapse
Grub can chainload the entry just fine. And when using the official tool it auto-adds an entry if it detects Windows is installed, which it will be as it's a windows tool [unless running via wine] it'll add an entry for it.
Without the tool you can do it manually. Personally I have a second easy to access efi partition that I use, if you want to do the same download a partition manager like minitool and confirm that you have 16MB of unallocated space between your efi and C: drive and I'll dig up a post/walk you through the rest tomorrow
HypoTurtle said:
Grub can chainload the entry just fine. And when using the official tool it auto-adds an entry if it detects Windows is installed, which it will be as it's a windows tool [unless running via wine] it'll add an entry for it.
Without the tool you can do it manually. Personally I have a second easy to access efi partition that I use, if you want to do the same download a partition manager like minitool and confirm that you have 16MB of unallocated space between your efi and C: drive and I'll dig up a post/walk you through the rest tomorrow
Click to expand...
Click to collapse
Very excited to pursue this, but this week is filled with close family coming here to stay for our only holiday celebration. Will post back here when I get that unallocated space, after creating a backup of the current system. May use Gparted, but will check out minitool as well.
Walk through, dual boot Remix OS + Win10 on XPS 12 9250
@HypoTurtle
Waiting on a second USB-C to USB cable so I can boot a Macrium Reflect flash drive and backup a restorable PC image to an external Hard drive. After I'm sure I can restore this image I'll try to install Remix OS.
This youtube link is straightforward and simple to follow for the dual boot installation process. I've seen many reporting hardware/software issues on the many XDA forum threads branching off of "Remix OS for PC". So obviously one size does not fit all. Compiling and replacing different Linux kernels, editing grub.cfg, initrd.img, system.img, data.img.... The very worse thing on xda forums are ignorant end-user whiners like me who want instant gratification with their perfectly working phone or tablet. This vast forum has so many xda-developers, steeped in code, gaining and sharing trial and error knowledge. So many thousands of threads where xda-developers are taken for granted to lay solutions into end-user's laps. So many of us end-users are oblivious to this baby sitting. I will try the time consuming and painstaking learning curve. The least knowledgeable member on xda-forums should try to learn and not be spoon fed. It is essential, whatever our capacity, to all become developers interested in expanding the usefulness of our devices over and above the limited and constrained manufacturer's parameters.
Good evening everyone.
I'm new on the forum, hope i guessed the section.
I just wanted to ask if it is possible to convert and run a raw android image (extracted with FTK Imager from the chip) as a virtual machine.
I tried something, but in the end the VM says that there's "No bootable medium found!".
In the program "autopsy" i can see the common partitions of the android file system (boot, recovery, system, userdata...) but most of them result as a sequence of unallocated space.
The original mobile phone was a Nokia 3 TA1032.
Can you please help me?
Thank you in advance