I was super happy to receive my FP6 with e/OS murena installed. Unfortunately either after these 2 things I did, the phone is completely bricked:
I updated to 3.0.4
I enabled the linux terminal in developer mode (my bad)
I am now stucked in fastboot mode with the DEVICE-STATE - locked, with the (bootloader) get_unlock_ability: 0.
If I run in safe mode, I receive a message that the system is corrupted.
I cannot exit this fastboot mode nad the e/OS safemode does not help. I also tried adb shell su -c 'resetprop ro.boot.flash.locked 1' without any results.
Any help is very much appreciated and I do thank you in advance !
Locked bootloader and rooted? Or is the tag wrong?
Safe mode=recovery?
How did you update to 3.0.4?
Did you try to boot into system at least 7 times?
Either way when you cant unlock the bootloader you need to contact support.
Edit: it is possible to sideload e/OS using adb, see in the following posts and link to the e/OS forum.
Ok, I see, thanks for the insight, I have no idea how this could have happened. It’s bricked right now. I do not even know if they can find a way to unlock it remotely.
I should check if e/OS can be sideloaded indeed..but even then would not require the device to be unlocked?
Basically I didn’t unlock the OEM in the settings and that’s what makes the situation stuck. It’s not like I was trying to install any image on the phone.. I’ll contact support if there is no other solution then, thanks @yvmuell for your time!
But unfortunately the command fastboot oem allow-flashing does not exist in FP6.. And then they were able to flash another iamge >> unlock OEM >> reflash e/OS. Is there an alternative or a corresponding command on FP6?
I won’t be able to help as I’m a newbie with the FP6 and e/OS….but I’d like to understand what happened as I don’t get how you could have bricked your phone simply by upgrading to 3.0.4 orby enabling linux terminal in dev options. Your phone came from Murena installed with e/OS (v3.0.2 I guess) and a locked bootloader. So what did you do? You upgraded to 3.0.4 using OTA or by using fastboot? AFAIK, bricking usually occurs while attempting to relock the bootloader, but yours was already locked by Murena. Or did you unlock it at some point? I’m curious to know what may have happened.
upgrading to 3.0.4 (it came with 3.0.1 with bootloader locked)
enable linux terminal
The only other operations I did were using adb from my Windows terminal to load and test some apk packages on the phone. Now that I am writing I checked some old adb commands I run some days ago (I have never switched off the phone) and in one there was a adb root and adb mount to read some data on the phones (I am new to the adb word). Then today I rebooted the phone and the “brick” occured. Admitted that my bootloader was locked and I ran these commands anyway, it could have led to corruption or triggered safety mechanisms that prevent boot and corrupted the image when I switched off/on my FP?
So you mean you enabled adb root in dev options and then ran some commands as root on the phone, possibly deleting or messing with system files that would render the phone unbootable?
On the phone I enabled only USB debugging as said, but not the option rooted debugging. It’s on my adb machine that I run the commands adb root and then adb mount.
These two commands are the only two that I ran, no other manipulation or deletion was performed on the file systems.
Small question here @yvmuell , more of a curiosity: as you suggested, I wasn’t able to flash the FPOS into my blocked device fro the bootloader. But reading this (amazing) guide:
I thought this should be enabled because it must have some cryptography signature to bypass the bootloader checks, right? Unless, since I bought it with e/OS from the official store, FPOS wasn’t the original distribution image, hence not recognized by the bootloader..(?)
You picked up a small part of a very long guide, I dont have the full context at the moment.
The important part in cases when you are stuck in fastboot and no way to flash using fastboot (or as in your case sideloadusing adb): no firehose no use of EDl no way to unbrick on your own. I think thats also mentioned in the guide somewhere.
Hi, glad you liked my guide. And congrats on your troubleshooting! I’ll probably add that too, cause the way you did it was rather elegant.
The checks I was refering to are done at the booting stage in a locked bootloader. The bootloader compares the hashes of the system partition with what is has in store. If everything checks out, it boots. Else, it says “corrupted system/rom” (like you had).
I didn’t talk about the permissions regarding the writing or flashing of partitions. I suppose that the partitions are kind of read-only as long as the bootloader is locked (that would make the most sense).
To get from /e/(official) to FPOS or conversly, you still have to unlock → install → relock.
The keys business is only so that you can lock the bootloader on a given ROM. I’m not so knowledgeable about that part, but the locking can be done on FPOS and /e/ official thanks to the developers keys.
!