Thanks.
I’ll do the paranoid backup. Is my understanding correct on the process? I do a regular qubes backup using the qubes os backup utility which if I remember correctly makes an encrypted .bin. Then on the fresh qubes install instead of gui qubes backup restore, use dom 0 with the following command,
qvm-backup-restore --paranoid-mode --ignore-missing -d sys-usb /media/disk/backup.bin
Thanks everyone for all the help.
Tried doing in dom0
qvm-backup-restore --paranoid-mode
And --plan-b
Returns qvm-backup-restore: error: unrecognized arguments: --paranoid-mode
Anyone know why?
Yes, and re-appeared in R4.1 (done properly now, using DispVM to do all the complex processing).
@marmarek @adw little new to all this. Unless you think I’m going to run into a million other problems I’d like to give this a try. I found r4.1 GitHub - QubesOS/qubes-release-configs could you give some guidance on make? I only did this once before for something else. Basically I downloaded the folder from github, then ran make then a file name or something like that. But never did this with qubes, so I’m not sure of the exact process. I’d need to create burnable file for usb stick install. Or that’s what I’m accustomed to. Thank you.
Testing is intended for advanced users only. Given that you say you’re new to all this, I would recommend sticking with the stable release. However, if you wish to read more, see:
and
Ah the build system, that’s what I was looking for. Thank you.
What do you think about this work around to access the paranoid mode. Setup r4.1 on a temporary drive just for the purpose of using paranoid mode to import and hopefully clean those templates of concern, then backing them up again, then importing them back to a clean install of 4.0.4 system so I don’t run into stability issues that I don’t have the skills to troubleshoot.
I spent a few hours on those docs preparing to build this .iso. Then I found this: Signed Q4.1 alpha iso
Is there any way to update the docs myself to simply state “if you want to downloaded a signed rc .iso, here’s the ftp page”.
If the RC iso are signed and I just want for general testing, I’m not sure the benefit of spending all that time building myself. Obviously it would give me greater experience. But I have a --paranoid backup and android-x86 compatibility problem and need a quick solution and could put the additional experience gaining on hold. 
Instructions for submitting doc changes are here:
It is not entirely clear to me whether this change would be a good idea, however. For one thing, an alpha and an RC are completely different (almost opposites on the pre-release spectrum). For another, users should probably not go to the FTP page expecting there always to be an up-to-date alpha ISO there. Most likely, there would be some kind of post or announcement when one is available (like the one you linked), which then obviates the need for separate documentation.
Whoops. Missed this. We could have saved you those hours. 
You also have weekly signed ISO. But after the updates they should be pretty much the same. Just FYI: QubesOS 4.1 Signed Weekly Builds
Plus, a beta is now available:
Tried the beta last day. Didn’t install. I tired all the install options. Same. Says error halting install, check logs. On recommended hardware too. 
I’ll give up this for now and redo my system and all templates manually. It will probably take a month, but that is life in our great reset era.
If posting the logs somewhere might help future installers, please tell me where to post those.
You can drop .log files here on the forum’s editor. They will show as attachments.
Or you can use details: (from the editor’s 
menu)
some random log line
some random log line 2
....
The issue with the details thing is that you easily exceed the post’s max characters (32000) I think.