How did you get out of the bootloop?
/e/ documentation Install /e/ on a Gigaset GS290 - “GS290”
Downloads for the GS290
Download Android 10 firmware
Unzip file gs290_10.zip
fastboot flash boot boot.img
Maybe it helps the next person to run into the same problem: I’ve extended the log uploading info by
If the log is too large even for haste and you already have an /e/ account, you can ZIP the log and upload it to your /e/ account cloud storage.
Hmm, I did fastboot flash boot boot.img, then everything else, but that didn’t work, so I went back to what is written in the doc https://doc.e.foundation/devices/GS290/install
and now it works
Thx
BTW, there’s a new version v0.12.1 out that has the GS290 support again.
But as SuzieQ pointed out that’s likely of not much help if the version it installs wouldn’t work properly.
Maybe the problem is that nobody created an issue in Gitlab? At least I don’t see any
https://gitlab.e.foundation/e/backlog/-/issues?label_name[]=Easy-installer
Yeah, I understand your request. ‘Many roads lead to Rome’ and my way goes past Gitlab.
I have followed the instructions at https://doc.e.foundation/devices/GS290/install , but I get an error at
$ ./fastboot flashing unlock
(bootloader) Start unlock flow
FAILED (remote: '
Unlock operation is not allowed
')
fastboot: error: Command failed
and this prevents further steps to be successful:
$ ./fastboot flash --disable-verity --disable-verification boot ~/Downloads/boot.img
Rewriting vbmeta struct at offset: 9797632
Sending 'boot' (32768 KB) OKAY [ 1.547s]
Writing 'boot' FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
I have the latest version of platform-tools:
$ ./fastboot --version
fastboot version 31.0.0-7110759
How can I unlock the device?
Have you allowed the unlocking in the >settings >développeurs options ?
That should be added to the instructions, right?
Definitely
The experience would have been flawless if this detail had been provided!
1 . Enable OEM unlock in the Developer options under device Settings, if present.
This note has been missing from the /e/ documentation of the Gigaset GS290 since the initial release. It’s present in various other /e/ installation instructions.
So let’s hope this Gitlab merge request is accepted soon and the documentation gets updated
Hi @Ingo_FP_Angel pl let me know the commands for unlocking the GS290 if different from the standard and I shall have them included in the documentation
One place where an extra step can be added in here https://doc.e.foundation/pages/enable-usb-debugging
@Manoj That’s a good point, adding the OEM unlock to the “enable-usb-debugging” page.
The way I understood @SuzieQ the same sentence from the jasmine_sprout instructions should be sufficient, i.e. is generic.
Steps to unlock bootloader on Gigaset GS290
To enable the ‘Developer Option’, go to your ‘Settings’
Settings
About Phone
GS290
Build number Gigaset_GS290_10.0.V06_2020
Now tap 7x on Build number
until you see a toast message ‘You are now a Developer!’
Go to > System > Developer options
OEM unlocking
Allow the bootloader to be unlocked is slightly roughened
Now activate with a tap and the screen message “Allow OEM unlocking?” is displayed
Confirm with ‘Enable’
Now is OEM unlocking
Allow the bootloader to be unlocked’ is enabled (blue)
Scroll down to Debugging and activate it
USB debugging
Debug mode when USB is connected
‘Allow USB debugging?’
Confirm with OK
USB debugging
Debug mode when USB is connected `(blue)
1 Like
Hi,
I’m also experiencing problems while installing /e/ OS on GS290 using Easy-Installer. I did every step of the easy installer (v0.12.1-beta) and the phone was flashed successfully. The installer finished with a success message. Unfortunatelly the phone not usable since that. The screen is black, no combination of power button (and volume up/down) brings any boot screen on the display. The phone is not recognized from the linux system of my laptop. I have no idea if the phone is in a bootloop as mentioned by tiro.
I used debian 10 (buster) as OS with easy-installer v0.12.1-beta.
If it helps I can provide the log file.
Sorry, I could not find the advice. Any idea of how to get the phone up and running /e/ OS?
Thanks!
Chris
I found another post describing the my problem. https://community.e.foundation/t/stuck-on-fastboot-flashing-unlock-now-black-screen/26847/4
When I plug the phone via usb cable into my notebook the kernel detects a device but fails to mount it correctly. This is done over and over every minute.
Here are the syslog messages:
Mar 8 14:33:28 FJE734 kernel: [ 942.215872] usb 1-9: new high-speed USB device number 4 using xhci_hcd
Mar 8 14:33:29 FJE734 kernel: [ 942.364922] usb 1-9: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
Mar 8 14:33:29 FJE734 kernel: [ 942.364925] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 8 14:33:29 FJE734 kernel: [ 942.364927] usb 1-9: Product: MT65xx Preloader
Mar 8 14:33:29 FJE734 kernel: [ 942.364928] usb 1-9: Manufacturer: MediaTek
Mar 8 14:33:29 FJE734 kernel: [ 942.387356] cdc_acm 1-9:1.0: Zero length descriptor references
Mar 8 14:33:29 FJE734 kernel: [ 942.387370] cdc_acm: probe of 1-9:1.0 failed with error -22
Mar 8 14:33:29 FJE734 kernel: [ 942.427560] cdc_acm 1-9:1.1: ttyACM0: USB ACM device
Mar 8 14:33:29 FJE734 mtp-probe: checking bus 1, device 4: “/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9”
Mar 8 14:33:29 FJE734 mtp-probe: bus: 1, device: 4 was not an MTP device
Mar 8 14:33:29 FJE734 snapd[643]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug
Mar 8 14:33:29 FJE734 mtp-probe: checking bus 1, device 4: “/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9”
Mar 8 14:33:29 FJE734 mtp-probe: bus: 1, device: 4 was not an MTP device
Mar 8 14:33:31 FJE734 ModemManager[630]: (ttyACM0) could not open serial device (2)
Mar 8 14:33:31 FJE734 ModemManager[630]: [plugin manager] task 3,ttyACM0: error when checking support with plugin ‘Nokia’: ‘(tty/ttyACM0) failed to open port: Could not open serial device ttyACM0: No such file or directory’
Mar 8 14:33:31 FJE734 ModemManager[630]: (ttyACM0) could not open serial device (2)
Mar 8 14:33:31 FJE734 ModemManager[630]: [plugin manager] task 3,ttyACM0: error when checking support with plugin ‘u-blox’: ‘(tty/ttyACM0) failed to open port: Could not open serial device ttyACM0: No such file or directory’
Mar 8 14:33:31 FJE734 ModemManager[630]: (ttyACM0) could not open serial device (2)
Mar 8 14:33:31 FJE734 ModemManager[630]: [plugin manager] task 3,ttyACM0: error when checking support with plugin ‘Telit’: ‘(tty/ttyACM0) failed to open port: Could not open serial device ttyACM0: No such file or directory’
Mar 8 14:33:31 FJE734 ModemManager[630]: (ttyACM0) could not open serial device (2)
Mar 8 14:33:31 FJE734 ModemManager[630]: [plugin manager] task 3,ttyACM0: error when checking support with plugin ‘Via CBP7’: ‘(tty/ttyACM0) failed to open port: Could not open serial device ttyACM0: No such file or directory’
Mar 8 14:33:31 FJE734 ModemManager[630]: (ttyACM0) could not open serial device (2)
Mar 8 14:33:31 FJE734 ModemManager[630]: [plugin manager] task 3,ttyACM0: error when checking support with plugin ‘Iridium’: ‘(tty/ttyACM0) failed to open port: Could not open serial device ttyACM0: No such file or directory’
Mar 8 14:33:31 FJE734 ModemManager[630]: (ttyACM0) could not open serial device (2)
Mar 8 14:33:31 FJE734 ModemManager[630]: [plugin manager] task 3,ttyACM0: error when checking support with plugin ‘Generic’: ‘(tty/ttyACM0) failed to open port: Could not open serial device ttyACM0: No such file or directory’
Mar 8 14:33:31 FJE734 ModemManager[630]: Couldn’t check support for device ‘/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9’: not supported by any plugin
Mar 8 14:33:31 FJE734 kernel: [ 944.881095] usb 1-9: USB disconnect, device number 4
Any ideas how to recover the phone?
Wouldn’t it make sense to continue your problem in the other topic? Looking at the title here “GS290 not supported in easy-installer?” I’d assume it wouldn’t draw people’s attention about rescuing a GS290 in a “dead” state.
Hello, tried to blink according to your instructions. Unfortunately, it gets stuck in the start screen after restarting. What’s my mistake? Can I return to Ubuntu from your rom?
So your device was on UbuntuTouch before your experiment. Just to be sure: Did you follow the steps listed under " If installing /e/OS by removing a non Android OS" on https://doc.e.foundation/devices/GS290/install?