The wise way of combining Manjaro KDE and Windows 10?

[robinhaug]

Thanks guys! You are awesome.

Let me, to conclude, tell you what I have decided based upon your knowledge:

1. I install VirtualBox. I have many uses for this in any case.
2. First VM will be Windows 10. I am in the process of downloading the ISO right now.
3. If I am unable to flash from VB, I will simply buy a SSD and set it up with Windows OR buy a cheap laptop with Windows 10.

Thus I take no risks with my current system.

I find this the wisest solution.

Again, many thanks!

[michaldybczak]

@robinhaug

Would you mind describing to me how I enable the OS-prober? And how I update GRUB?

Open /etc/default/grub with nano:

sudo nano /etc/default/grub

Find line:

GRUB_DISABLE_OS_PROBER=

if it says true, change it to false, if it’s false, you’re OK. So bascially that line should be:

GRUB_DISABLE_OS_PROBER=false

To update grub:

sudo update-grub

Updating grub is necessary every time you change GRUB’s config.

[Nachlese]

I have (briefly) looked up that phone you want to tinker with.
It appears to be some rebranded Gigaset GS290
(which is not nearly half the price as the Volla … so it appears …)
but that could be wrong.

It also appears to run some custom version of Android - which to me means that the tools for flashing are the same as those that I mentioned:
adb, fastboot (which is part of adb) and heimdall
they should also work and be usable
(meaning: no Windows would be necessary)

But this is speculation after only a brief research.

Whatever is the case, have fun and good luck with your flashing project.

[robinhaug]

Many, many thanks, Nachlese!

I will try out that!

[robinhaug]

Many, many thanks, Michal!

I just checked and, yes, my GRUB was already correct.

[michaldybczak]

Also, if you want to trigger os-prober to look for other installed systems, update grub :).

[robinhaug]

Hehe, I have updated grub, thank you!

Now that you are here, perhaps I can ask you about something mentioned in this thread: adb. When I command:

adb devices

there’s no phone listed. It is found, though, on the command:

lsusb

as: Bus 002 Device 118: ID 0e8d:0003 MediaTek Inc. MT6227 phone

I have reloaded the service with:

udevadm control --reload

I have checked the rules. They should be fine. Then I read something about a certain file that I simply can’t find, a file that can explain why device is not listed. The file is called ~/.android/adb_usb.ini.

I read that it should specify Vendor. Commanding

mhwd -lh -d 

I get this result showing info on my phone:

3: USB 00.1: 0000 Unclassified device
SysFS ID: /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.1
SysFS BusID: 2-3:1.1
Hardware Class: unknown
Model: “MediaTek MT6227 phone”
Hotplug: USB
Vendor: usb 0x0e8d “MediaTek Inc.”
Device: usb 0x0003 “MT6227 phone”
Revision: “1.00”
Driver: “cdc_acm”
Driver Modules: “cdc_acm”
Speed: 480 Mbps
Module Alias: “usb:v0E8Dp0003d0100dc02dsc00dp00ic0Aisc00ip00in01”
Driver Info #0:
Driver Status: option is active
Driver Activation Cmd: “modprobe option”
Driver Info #1:
Driver Status: cdc_acm is active
Driver Activation Cmd: “modprobe cdc_acm”
Attached to: #13 (Hub)

So what to do?

[Nachlese]

@robinhaug

adb devices

there’s no phone listed. It is found, though, on the command:

There is a database within the program (I think, meaning: I’m pretty sure of, but I don’t actually know)

… if it is not in the database …

The phone has to be properly powered on.
Which likely isn’t the case when you are dealing with a “brick”.

As stated, I cannot help you with this one
but perhaps someone else can

unlikely though, under this subject title …
or anything rather Manjaro specific in general

xda developers might be a better place

@robinhaug

Model: “MediaTek MT6227 phone”
Hotplug: USB
Vendor: usb 0x0e8d “MediaTek Inc.”
Device: usb 0x0003 “MT6227 phone”

at least now you have pretty detailed hardware info to go of off in your research

but - on a positive note:
from what you see:
the phone is still functional - not really a brick …

there is hope

(but probably not here)