Hello everyone,
Yesterday, a system update was offered and performed at the Edge 30. After that, the device booted (after entering the SIM PIN) to the lock screen.
Problem: Lock screen cannot be unlocked (by swiping up + PIN)! The lock screen does not respond to anything!
What can I do? Do you have an idea?
or
Thanks, but what do you mean with “switch to other slot”?
And an additional question: At lock screen there are 3 buttons, the right button is white highlited - what does this mean?
fastboot set_active other
OK, what is the meaning of this command?
What will be happen after this command?
instead of checking the active slot (a or b), and then activate slot_a or slot_b
this command simply activate the other one…
what is hoped is booting previous /e/ installed version.
avoiding potential anti-roll-back feature…
ok, but for adb communication USB debugging needs to be enabled, right?
How can I do this without access to device settings?
it is not adb but fastboot command.
ok, understand, but isn’t it necessary to have the unit in fastboot mode?
I have tried this command with connected unit via USB, but it is waiting for any device….
yes
“fastboot command is not found” is not the case here. It’s known - but it does not found the device. That’s why I am asking if the device must be set in a fastboot mode.. or…?
This is your situation. @piero did not link you to “fastboot command is not found”.
Yes; that is what the linked thread asks you to do … and
fastboot devices
must give result…
OK, I have loaded all latest Windows drivers for Android etc. according your link “How to”, which were displayed at windows update section at “optional drivers”. But I assume no fastboot driver was displayed…?!?
Then I restart the device into fastboot mode, I see the this window:
I press “start” and the device is starting up to the SIM PIN menu, PIN ok, then again I see the lock screen.
Connect it via USB, then try “fastboot devices” without any resuls
so you leaved the fastboot mode to launch the normal android system mode.
Ohh, yes, you are right! Sorry!
OK, again I set the unit to fastboot mode. Now I see with “fastboot devices”:
C:\WINDOWS\system32>fastboot devices
xxxxxxxxxx fastboot
Then I display the fastboot informations: “fastboot getvar all”, then I see a lot of information.
Some important lines are:
(bootloader) version-bootloader[0]: xxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) version-bootloader[1]: xxxxxxxxxxxxxxxxxxxxxxx
(bootloader) product: dubai
Which means: slot 0 = dubai bootloader, but what is slot 1 ???
Can I try “fastboot set_active other”?
give me https://www.stockrom.net/2024/09/xt2203-1-retbr-os14-u1rd34-80-40.html
so, slot_b can still be populated by stock OS
yes,
but you could face StockOS,
So then I get back to stock ROM, right? But how can this help?
in this case, allow “USB debugging”
and fastboot flash recovery-e on slot_a
then adb sideload e-3.3 (BUT WITHOUT FACTORY-RESET)
That means, a complete new installation then?
So in every case all data are gone?
