FP4 stuck in setup assistant after locking the bootloader

Using /e/OS Troubleshooting
, ,
1

Good morning. I just installed /e/ yesterday on my FP4 via the command line process and everything worked fine. Since I did not lock the bootloader afterwards, I wanted to do that today. I the first attempt I was not fast enough to push the volume down button and the phone booted the OS, wiping my data. No problem, but after the re-up my phone is now stuck in the setup assistant. I am able to select language, time zone and activate Wi-Fi, but that’s it. It says “please wait” and is not proceeding.

Did I waste my phone, or is there a chance to get it running again?

Thanks in advance for any help.

Sebastian

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

phone
phone427×374 173 KB

2

I do not see from where your problem come

.

For reference : [HOWTO] a Safe Guide to install "IMG-e-builds" even if the /e/ web installer fails

1 Like
3

That’s the manual I used. But I didn’t manage to lock on the first attempt, so I did the re-run you mention there. The SPL shouldn’t be the problem as it was June for the android version and July for /e/OS.

4

Did you save and can you show the terminal output for the locking commands you used?

5

I didn’t take screenshots, if that’s what you mean, but I followed the steps in the guide. I got as far as ./fastboot flashing lock_critical but than missed to push the volume down, so it rebooted. Then I followed the next steps locking the bootloader. I just checked the bootloader and it says locked.

I just remembered, that I got as far as the workspace connection, I put in my mail and password and then it got stuck.

(This platform now always tells me, I reply to fast and have to wait for 40minutes, is it supposed to do that?)

6

Critical partition must be locked first.

.

What are the output for :

7

:confounded_face:

Any chance of fixing that?

The output to ./fastboot le device-info is

(bootloader) Verity mode : true

(bootloader) Device unlocked: false

(bootloader) Device critical unlocked: false

(bootloader) Charger screen enabled: false

Okay

./fastboot flashing get_unlock_ability

(bootloader) Get_unlock_ability: 1

Okay

8

i don’t know.

Maybe redoing the right sequence (from the right state)

9

Would you say it’s safe to give it another go given the output above? (as safe as can be anyway…)

10

This is normal state with bootloader relocked
(except charger screen : false)

So i propose you to boot into recovery mode and trying to apply a factory-reset

11

That’s what I thought, anyway it can only get better. But isn’t the FP OS completely wiped of? Where do I go with that?

1 Like
12

Activate wifi during first boot setup wizard is not needed.

If the first boot setup wizard is related to /e/OS, so FP OS is gone (except hardware driver related parts)

factory-reset is expected to give a new (never used) stock /e/OS phone.

1 Like
13

Thanks a lot for your help so far!!

14

So what I am doing is a factory reset to e/? I’ll give it a try and see what’s the outcome. Let’s go.

1 Like
15

Yes if /e/OS was well installed.
If not, you are in a good position to restart installation from scratch.

1 Like
16

It did work fine before my failed attempt to lock the bootloader, so I’m optimistic.

17

Looks like it worked. Since I made no changes to the bootloader, it should remain locked, right? Going to check that later on. Thanks again for your support!

1 Like
18

Hmmm, my experience shows that if you don’t lock the bootloader there will be certain e-banking apps that will not run. this is why i did immediately after the installation.

If you don’t need such app, it does not matter, of course.

1 Like