You may find that your device gets a notification which says that your device is corrupted and cannot be trusted and will not boot. If you are not an expert of technology, you may be worried and do not know what to do.
Well, actually I have tried the information about it and mostly this case is discussed in forums. One of the forums is Community Phones Nokia. On that forum, there was a user named Natz who had trouble with Nokia 5.1 and this user wrote that the battery is drained because of travel circumstances. After charging for an hour, tried to switch it on, it showed a message which said that “Your device is corrupt. It can’t be trusted and will not boot.”
A user named Andrian Cedric responded when he asked whether Natz had ever rooted the device or tried to install apps from an untrusted source. He added that because from the error they got here, it seemed like the Android OS on his phone was corrupted.
Then, another user named Theguynextdoor responded that factory reset is the only option, but you will lose all your data if doing this. Furthermore, he wrote that you have to connect your phone to PC in normal charging mode and then try booting to recovery mode (Power & Vol+), you should be able to boot to recovery. So, as you can read, this user suggests factory reset to solve this issue.
Well, you can try this way to solve this issue, but you need to know as said earlier that you will lose your data if you do this. So, if you are afraid of doing this and you are afraid that you make a mistake, when you have “Your device is corrupted. It can’t be trusted and will not boot” message, the best thing that you can do is to contact the manufacturer of your device. You are able to contact them via email or phone. Or, if there is an expert who understands about it and can fix it, you can go there.
How to Solve Your Device Is Corrupted and Cannot Be Trusted
When I tried to search the information about how to fix ‘Your device is corrupted and cannot be trusted and will not boot’, I found an article about how to fix a device is corrupted and cannot be trusted. I do not know whether it is the same with the problem above or not, but as you can read that in the error message above, there is an additional words: “will not boot”.
After you restart your android, your device that runs on the Android OS will perform a quick self-check to ensure that every function and feature is consistent and it will happen without any issue. However, you may find that there is a message which says that your device is corrupted and cannot be trusted.
According to the 4G Britain site, if you find this error message and you cannot boot into the system, you can fix it by following the steps below.
- The first thing that you have to do is to download the latest firmware available for your phone to a computer.
- After that, you need to copy and pass the firmware to an external SD card and then insert that card into your phone.
- In this step, you have to enter the recovery mode on your phone.
- Now, you have to scroll down, pick Apply update from SD card and then you have to choose the downloaded firmware.
- At last, the thing that you have to do is to wait for the installation to complete. Let’s say that things proceed smoothly. If so, you can boot into the system. And now, you are able to use Minimal ADB and Fastboot Tool to take care of the irregularities on your device.
However, if you get this error message, but you can boot into the system, you can fix this issue by following the steps below as explained on the 4G Britain site.
- The first thing that you have to do is to go to Settings, choose About phone and then you have to tap Build number seven times to enable Developer options.
- After that, you need to back out to Setting, choose Developer options and then you have to turn on USB debugging.
- In this step, you have to download minimal ADB and Fastboot Tool to your computer.
- Then, you need to connect your android phone to the computer.
- Now, you have to open command prompt in minimal ADB and Fastboot Tool and then you have to type these two commands:
Adb reboot “dm-verity enforcing”
Now, what do we have to do if we have this error message, but our phone automatically shuts down? Well, Android will turn off the device in a short period of time after it shows this error message. Usually, this situation takes place on rooted phones that have their bootloader relocked. According to the 4G Britain site, here are the steps that you are able to take to fix this issue if your phone automatically shuts down.
- The first thing that you have to do is to unlock the bootloader.
- After that, you have to remove the root.
- Then, you need to remove custom recovery.
- The next thing that you have to do is to relock the bootloader.
Some Tips To Keep Your Android Running Smoothly
Here are some tips or suggestions from 4G Britain site about the use of Android.
- Never tamper with Android. If you root your android, it means that you can apply customization to an assortment of aspects that you have access to previously. Rooting also brings particular risks that may wreck devices if you do that without experience and knowledge. So, it is better for you not to do that so that you can avoid messing with Android.
- You have to keep everything in your Android up to date. If the OS and apps in your devices are obsolete, there will be a lot of errors which will appear.
- You have to remove unimportant apps. As you know that apps take up resources and it is not wise if you keep too many unimportant apps on your device. It is better for you to uninstall apps that you do not need to have to optimize the operation of the system.
- You have to clear the cache. Even though cached data speeds up various processes, they also can be prone to corruption. So, to keep your phone operating consistently, it is better for you to clear cache occasionally.
On my daily job, I am a software engineer, programmer & computer technician. My passion is assembling PC hardware, studying Operating System and all things related to computers technology. I also love to make short films for YouTube as a producer. More at about me…