This is an abbreviated transcript of a thread from Telegram 10 March 2021.
Caller: Hi, my GS290 stops at the “fastboot mode”, screen is black, on screen is only “fastboot mode”. The installer stops right there and does not continue.
Support: I was able to continue, by running windows update, which downloaded phone driver for windows, after that Easy installer was able to continue
Caller: After I downloaded and run the easy installer, I tried to restart Windows and had a “blue screen”. I had to reset the system.
Now, after all updates that I could find, it worked!
So the problem was with Windows!
So thankful to have finally /e/ on my phone!
Does anyone else has the problem to log in into the account from the phone?
If Easy Installer seems to fail in Fastboot mode and you get a small orange warning triangle in Windows device manager the advice would be to be sure to fix the Windows warning.
You can try with Windows update, sometimes Windows may need additional driver. If you run windows update when in fastboot mode, it should detect the device and download necessary driver. Credit @shenol.
Failing that, carefully close the connection to your device. Restart Windows. Perform necessary steps to update. It is significant that “device” is your device in Fastboot mode. Does the warning still persist when you connect the device in Fastboot mode? Once the warning has gone try Easy Installer again.
Testing, do those two steps fix the problem?
If the warning has not gone, there could be satisfactory ways to introduce the GS290 drivers to Windows. (Please post below if you follow this path!).
Thanks @SuzieQ for this image. I have no Windows so I cannot see. Edit x 2: in the event that Easy Installer has introduced such “ problematic driver” does Windows Device Manager helpfully pop up for you?
Yeah @aibd, since I’ve very different Android devices in the test, from Galaxy to Gigaset GS290 to Google Pixel and OnePlus as well as Xiaomi, and my Windows host machine constantly complains about missing drivers depending on the ADB/fastboot status, I always have my Windows Device Manager open and in view in order to quickly select the appropriate driver for the situation. They are all already available in Windows and therefore only need to be changed with a few clicks.
I used the /e/asy-installer for a short time only for testing purposes. Now it is being shelved again. I prefer to flash manually in the old fashioned way.
When the /e/OS ‘Q’ upgrade for the GS290 was released, the /e/asy-installer was a bad recommendation, because it installed /e/ OS 'O’reo-8.0.0 instead of ‘Q’ 10.0, leaving the GS290 unusable. Now, weeks later, the bug is fixed, after tens of us/e/rs have fallen into the installation trap, and the installation with the Windows version of easy-installerv0.12.1_beta runs as it should, apart from the Windows driver stumble discussed.
I had a good experience until the end, except that in the end the phone is broken and there is no black screen.
I feel like I’m alone, no one to help me.
New phone
Thank you very much for sharing.
I am having exactly the same problem that I am stuck in “Rebooting in bootloader mode”
Windows is fully up to date.
I even tried to follow the steps here according to the guide suggested by SuzieQ: GS290 No recognition on PC
But, the problem is that when I connect the phone in recovery mode, it is not recognized by windows neither.
In the device manager the GS290 is listed under USB devices.
When I right click on it for updates, it says Windows determined that the best drivers are already installed.
I even installed Android Studio hoping that that might change something, but, still the same, always stuck in “Rebooting in bootloader mode”
I am running windows 10 on a Thinkpad t440
The easyinstaller is version 0.12.1.
Thank you all.
Thanks for replying so quickly, and sry in advance if I cannot follow all your advice, I am completely new to this.
So, the GS290 is currently listed under Portable Devices, the driver it uses is called “MTP USB Device” - There is the option to install a driver manually, so, I guess that would work, but, which one would that be?
And, what do you mean when you say that “device” is your device in Fastboot mode? And what is the log you are referring to?
To do a job like this I find that I have to read the instructions three times before I start!
The source of the log is mentioned by me in the post immediately above your first.
From what you say, as you have Windows 10, “choose your own driver” won’t happen, please disregard that line!
Your phone can boot as a phone. It has two other bootable modes. Recovery and Fastboot. I guess you need to do some more reading if this is all gibberish!
Edit: Our documentation refers to “Bootloader Mode”, but is it clear that within Bootloader Mode exists Recovery Mode and Fastboot Mode
Thank you so much
Ok, I put the phone in Fastboot mode now, connect it again, and play around a bit, see what happens, if there are other update options etc, and meanwhile do some more reading.
Hello aibd!
The instructions you give are all correct; I entered the bootloader mode via the mentioned command line and the key combinations on the phone, and the fastboot mode with the key combinations on the phone. in the picture, pls see the menu you enter after pressing the powerbutton and volume up button at the same time - here yoyou select between Recovery, Fastboot, and Normal.1615987151631|375x500
problematic driver” does 
.
