[BLISS ROMS Development] ElfinJNoty:
Just have to be patient ? thanks for giving your feedback

---------- Post added at 04:09 PM ---------- Previous post was at 03:42 PM ----------

The log file should be saved to either the root of the drive you are running the installer.exe from, or the target drive selected in the installer. So you stated C: and F:, check root of each of those. But as you stated, the log output is shown within the installer.exe and you've already copy and pasted :good:

If you created and formatted a new drive or partition, should have been done in NTFS.

On my laptop, I have 7zip installed natively, as well as WinRAR and WinZIP. But I have 7zip as default for certain file extension associations(.zip, .7zip, .rar, and pretty sure .iso's). Please verify if you have other archive file managers, that they are not set as default for an archive file type. If Windows is trying to force a default program for .iso that is not 7zip, might be causing a conflict.

Also ensure you have permissions correctly for read/write access on your drives.

Have you tried to run the installer.exe as admin?

Have not encountered this error you are reporting before, but it is a good indication when you get those errors prior to the installer launching that there is something preventing it from running specific to your userspace on your windows install.

I'd suggest installing to your C: drive first for test purposes. Have the installer on your C: drive when you launch it, and select C: to install to. This is just for test purposes. If you want to later remove the installation, just use the "remove Android" button in the installer after the fact. You can even move the entire installation directory(from one drive to another, or rename it. For example, I change the AndroidOS folder to "Bliss-OS" in my C: drive) but you will have to modify your grub boot menu entry for Bliss to reflect the correct directory of the installation in order for it to load the files at boot correctly.

And also, if you still have a previous install in place, you can simply extract the .iso to a folder on your desktop, and replace the original install directory contents with the files of the same name in your new extracted .iso(just look in original install location for which files exist, then only replace those files with those from new .iso) off the top of my head I think it's just system.sfs, kernel, init, and data.img... but again, look in existing install directory for exact files present, then drag and drop the new replacements. <<~~~this is how our team typically does quick testing of a build, and is the benefit of using the installer.exe from within Windows to install BlissOS(because you have simple access to the installation directory)

Note:the above method should not be done using two different versions of BlissOS. For example, if going from a 7.x install to a 10.x install, should be a full clean installation(remove Android using installer.exe, then install as normal like in YouTube video)

---------- Post added at 04:17 PM ---------- Previous post was at 04:09 PM ----------

Can either of you or both of you use a logging .apk or via terminal to capture a log? There are tutorials ball over the web and YouTube on how to achieve this.(adb shell will require su privilages by sxtracting the system.img from the system.sfs file. This is described in the OP and following posts, or can be searched for in this thread for explaination). Once logging is enabled, reproduce your usage until the touch quits responding? We need to see what is taking place on the kernel level in order to determine the cause of this. Search Google for "catlog via terminal" or "catlog apk Android" to find solutions to do this if needed