bonjour,
j’ai voulu mettre mon murena one en sortie d’usine, mais ça ne fonctionne plus du tout:
“dm-verify corruption
your device is corrupt.
it can’t be trusted and may not work properly.
press power button to continue.
or, device will power off in 5s”
si j’appuie sur power, ça ne fait plus rien.
que faire?
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
Hello,
I tried to set my murena one to factory default, but it doesn’t work at all:
‘dm-verify corruption
your device is corrupt.
it can’t be trusted and may not work properly.
press power button to continue.
or, device will power off in 5s’
if i press power, it does nothing.
what should I do?
How long have you had the device? What is the background to this fail? Did something happen? Maybe an image of the screen where this is seen will help. Assuming the device powers off, will it enter Recovery or Download as: Info about Murena Murena One - one
Are you in this category?
I wanted to restore it to factory defaults and formatted the two partitions. Now it doesn’t boot at all and is not detected by my computer.
dm verify coruption
‘your device is corrupt
it can’t be trusted and may not work properly
press power button to continue
or device will power off in 5s’
and then nothing
By pressing power + volume up, I was able to enter fastboot mode.
It now says ‘fastboot mode’ in small print in the bottom left-hand corner.
then nothing
Fastboot mode will give you the opportunity to reinstall Install /e/OS on a Murena Murena One - “one”. Notice how the process involves fastboot only.
Fastboot mode might be seen as a “communication channel” – nothing will happen, but the device is open to fastboot commands from your PC.
When starting working with fastboot always start with the command
fastboot devices
and ensure you get a response from the device (it will identify itself) before you start the intended task.
If in doubt, the command
fastboot getvar lock_state
should tell you whether the device is locked.
thanks for the answer
./adb reboot bootloader don’t work
$ adb devices
List of devices attached
$ ./adb reboot bootloader
error: no devices/emulators found
No, that will not work, sorry, but we only use that command to reach fastboot reliably.
You can already get to fastboot by button press.
adb and fastboot are different languages, only fastboot is likely to be available useful to you, from what you said so far.
You can also boot into fastboot mode via a key combination:
- With the device powered off
- hold Volume Up + Power to open the menu. Use Volume Up to navigate and Volume Down to select. Select Fastboot Mode
When I see this mention of a menu, be careful not to take a wrong turn ! 
Have you done this sort of thing before?
The next lines are
- Now type the following command to unlock the bootloader:
fastboot flashing unlock_critical
- If the device doesn’t automatically reboot, reboot it. It should now be unlocked.
- Since the device resets completely, you will need to re-enable USB debugging to continue.
I gave a clue about finding the lock status. Ask again if it is not clear. A non-working device like yours will not perform “re-enable USB debugging”.
OK holded volume up + power and my phone writes “>>> FASTBOOT mode …”
then in console!
$ fastboot devices
no permissions (missing udev rules? user is in the plugdev group); see [http://developer.android.com/tools/device.html] fastboot
$ fastboot flashing unlock_critical
< waiting for any device >
then noting
sudo adduser mathieu plugdev
[sudo] Mot de passe de mathieu :
adduser : L’utilisateur « mathieu » appartient déjà au groupe « plugdev »
[sudo] Password for mathieu :
adduser : The user ‘mathieu’ already belongs to the ‘plugdev’ group.
The fix is on the same page Run apps on a hardware device | Android Studio | Android Developers.
Worst case you may need Fix Insufficient permissions error in Linux.
$ fastboot devices
0123456789ABCDEF fastboot
$ fastboot flashing unlock_critical
if I say no (volume down)
OKAY [ 63.224s]
Finished. Total time: 63.224s
if I say yes (volume up):
$ fastboot flashing unlock_critical
(bootloader) Start unlock flow
FAILED (remote: '
Unlock operation is not allowed
')
fastboot: error: Command failed
$ fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata' FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
like i’d said before:
Please give the output of
fastboot getvar lock_state
$ fastboot getvar lock_state
getvar:lock_state
FAILED (remote: 'GetVar Variable Not found')
Finished. Total time: 0.003s
I am not certain of the next step, but I suggest not sending more “install” commands.
I think this is the situation I warned of in Post #9.
I suspect USB debugging is not allowed in Developer options. This is the reason I suggested doing
fastboot getvar lock_state
in Post # 6.
Did you buy the device from Murena? as Post #3
Please give output of
fastboot flashing get_unlock_ability
https://source.android.com/docs/core/architecture/bootloader/locking_unlocking#unlocking-bootloader
here’s why I’m only answering today :
An error occurred: We appreciate your enthusiasm, keep it up! That said, for the safety of our community, you’ve reached the maximum number of replies a new user can create on their first day. Please wait 11 hours and you’ll be able to create more replies.
$ fastboot flashing get_unlock_ability
(bootloader) unlock_ability = 0
OKAY [ 0.005s]
Finished. Total time: 0.005s
I wanted to reset the phone from the factory.
I came across a ‘reset factory’ menu.
I then formatted the two partitions (user and system) and it is why it no longer works.