Database Info

[HELP ME] Honor 5x softbrick

So i was changing roms, and when i did this i accidently flashed the wrong boot image. After that i boot into a green screen with a red and blue squares then a message following it "boot image verify fail, please update to the authorized images. I can boot into fastboot recovery but i have no access through adb, i can preform a few adb amd fastboot commands but cannot flash or access my phone. It also boots into Huawei eRecovery and will let me try to download the latest recovery but fails each time, no matter if its highspeed internet or hotspot i always get a download failed message, can anyone help me out? I miss my x5 already and have tried almost everything i can and have done research on.

XT1557 Fall-through from normal boot mode Moto g Turbo

Hello,
A few days ago I found my Motorola Moto G Turbo, model MERLIN XT1557 , turned off. When I switched it back on, it did not boot successfully but instead redirected to the bootloader with the message:
"Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant."
"AP Fastboot Flash Mode (Secure)"
"failed to validate boot image"
"ERROR: Failed to pass validation, backup to fastboot"
"Fastboot Reason: Fall-through from normal boot mode"
"CID Read Failure"
"Invalid CID status 0x69"
I have not unlocked the bootloader or tried to install any custom firmware. As far as I can tell, this occurred spontaneously and without warning (my best guess would be an update that went wrong). For this reason, I have not enabled USB debugging either, so the phone doesn't even let me unlock the bootloader.
Recovery mode does not work, this merely gives the message "failed to validate recovery image". Nor do "Factory", "BP Tools" or "QCOM" do anything (barcodes works). Thus even if I wanted to perform a hard reset, I cannot seem to do it.
Strangely, I seem to be able to access two different types of bootloader interfaces, one with just text and another with a picture of an android. Neither seem to be of much help, however interestingly the one with the android picture states "Software Status: Official" while the pure text one sometimes (not always for some reason?) states "Software Status: Modified". Again, just to reiterate, I haven't performed any custom android modifications.
After all i tried to flash stock firmware, it installed successfully without even a single error and then again the same thing starting to happen, firmware installed but didn't solved the problem, same dual bootloaders menu start appearing.

ok, at last i am able to just boot into my phone,
used
fastboot oem config bootmode factory
Click to expand...
Click to collapse
and reboot. Phone opened in factory mode but still recovery is not accessible.
Working on figuring how can i get into recovery. Flashed twrp, didn't booted in recovery, flashed stock recovery, same result..

leagoo t5 wont boot after unlocking bootloader

Had a bad idea this morning and decided to try to root the phone, leagoo t5. The last time Im going to go messing with a phone that wasnt broken! after spending 10hrs trying to sort it! I downloaded adb tools and and twrp. I unlocked the bootloader with fastboot and installed twrp. However when I rebooted the phone it just booted straight into twrp. I cant get it to boot normally. I reinstalled the firmware but it will still not boot. I can get into recovery and factory modes but thats it. what can I do? Thanks

pcfreeze said:
Had a bad idea this morning and decided to try to root the phone, leagoo t5. The last time Im going to go messing with a phone that wasnt broken! after spending 10hrs trying to sort it! I downloaded adb tools and and twrp. I unlocked the bootloader with fastboot and installed twrp. However when I rebooted the phone it just booted straight into twrp. I cant get it to boot normally. I reinstalled the firmware but it will still not boot. I can get into recovery and factory modes but thats it. what can I do? Thanks
Click to expand...
Click to collapse
Have you tried factory resetting in recovery?

ktmom said:
Have you tried factory resetting in recovery?
Click to expand...
Click to collapse
Yes I did. No Joy. When I power on I just get the leagoo logo coming on and off repeatedly. Pressing the power button then will not turn the phone off again. I can switch it off by pressing vol- and pwr together though.
Is the problem caused by unlocking the bootloader with fastboot or that the firmware I installed is not suiting? Rebooting the phone after unlocking the bootloader before reflashing the firmware caused the leagoo logo to come on and off repeatedly accompanied by this message in very small text "Orange State - Your device has been unlocked and can't be trusted, Your device will boot in 5 seconds". After flashing the firmware with Sp Flash Tool this message is not being shown. Does reflashing firmware undo the action of unlocking the bootloader?

What your are describing is a bootloop. It sounds like the device can not find the system kernel to boot to. Did you boot the device after unlocking but before doing anything else?
Where did you get the TWRP recovery from?
Isn't this a mediatek chipset? If so, I think you need to use SP Flash Tool*to install.
I would look for a stock ROM for this device to revert to.
I'm not experienced on mediatek devices, but maybe @SubwayChamp could help.

pcfreeze said:
Yes I did. No Joy. When I power on I just get the leagoo logo coming on and off repeatedly. Pressing the power button then will not turn the phone off again. I can switch it off by pressing vol- and pwr together though.
Is the problem caused by unlocking the bootloader with fastboot or that the firmware I installed is not suiting? Rebooting the phone after unlocking the bootloader before reflashing the firmware caused the leagoo logo to come on and off repeatedly accompanied by this message in very small text "Orange State - Your device has been unlocked and can't be trusted, Your device will boot in 5 seconds". After flashing the firmware with Sp Flash Tool this message is not being shown. Does reflashing firmware undo the action of unlocking the bootloader?
Click to expand...
Click to collapse
Then to unlock bootloader is not normal that Android refuses to boot normally but when you flash a custom recovery or modify other partition this usually could happen so either or both you have to do a factory resetting/format data as @ktmom said or/and flash a kind of DM-verity for your device, this last avoids that bootloader checks the integrity of the partitions and can boot normally to system.
The warning message is normal then to unlock bootloader and reflashing the stock rom doesn´t relock it, you have to relock it at similar way that you unlocked it via fastboot command, most commom is "fastboot oem relock" but there are other variants and keep in mind that you have to return completely to stock before to apply it.

SubwayChamp said:
Then to unlock bootloader is not normal that Android refuses to boot normally but when you flash a custom recovery or modify other partition this usually could happen so either or both you have to do a factory resetting/format data as @ktmom said or/and flash a kind of DM-verity for your device, this last avoids that bootloader checks the integrity of the partitions and can boot normally to system.
The warning message is normal then to unlock bootloader and reflashing the stock rom doesn´t relock it, you have to relock it at similar way that you unlocked it via fastboot command, most commom is "fastboot oem relock" but there are other variants and keep in mind that you have to return completely to stock before to apply it.
Click to expand...
Click to collapse
I relocked the boot loader with the command "fastboot flashing lock". small white text dialogue on phone screen stated bootloader was locked successfully. rebooted phone then and it was still stuck in the boot loop. For a few seconds in between the leagoo logo a strange circular graphic was displayed on the phone with word "erasing" under it. What does this mean?
Can you tell me more about how to flash DM-verity?

pcfreeze said:
I relocked the boot loader with the command "fastboot flashing lock". small white text dialogue on phone screen stated bootloader was locked successfully. rebooted phone then and it was still stuck in the boot loop. For a few seconds in between the leagoo logo a strange circular graphic was displayed on the phone with word "erasing" under it. What does this mean?
Can you tell me more about how to flash DM-verity?
Click to expand...
Click to collapse
Ok, then to relock bootloader I guess that you did successfully boot to system again, right?
When you unlocked bootloader first then device is formatted to avoid a new user can access to the user´s data and when you relock it again the same happens.
As for DM-verity, newer devices strictly since nougat can´t boot to system after any partition was modified like happened when you flashed a custom recovery on it, here is when DM-verity can be useful, is used to avoid bootloader checks the integrity and allow a modified device can perform a reboot and more custom actions not officially permitted. You had to flash it through a custom recovery, sometimes flashing only Magisk is enough but not always.

You *might* be able to use this universal dm-verify script. It can be flashed only in a custom recovery and I'm not certain that is available to you.

ktmom said:
You *might* be able to use this universal dm-verify script. It can be flashed only in a custom recovery and I'm not certain that is available to you.
Click to expand...
Click to collapse
Good news and bad news! I got the phone to boot! I reinstalled twrp and the "magisk","no verity opt encrypt" and "disable dm verity" zips from the ext sdcard with fastboot. Twrp stated the zips installed ok but there were also some red line failure lines in the dialogue as they were being installed. I rebooted the phone via fastboot but this just resulted in it booting direct to twrp as before. I tried normal boot from twrp but it still booted straight back to twrp. I then tried selecting normal boot from the fastboot, normal, recovery option menu accessed on the Leagoo T5 by powering off the phone and then pressing the pwr and vol+ buttons together but this still resulted in it booting straight to twrp. I then decided to uninstall twrp by flashing the stock firmware recovery image to try to boot from stock recovery. I did same and rebooted from fastboot and it booted to system.
The bad news is there is an imei failure message and the sim is not connecting to the network.I googled imei failure and saw that its can happen when firmware is changed. I installed the "mobileuncle" app but according to a youtube video I watched, when I tap "Engineer Mode" there should be 2 further options available, one being MTK Mode. I am only getting one option "Engineering Mode (Android) which when I select just results in being returned to the previous menu. please say this is not a major problem!

@pcfreeze you quoted me, but as I said earlier, I'm not experienced with mediatek devices. You'd be better off quoting @SubwayChamp

pcfreeze said:
Good news and bad news! I got the phone to boot! I reinstalled twrp and the "magisk","no verity opt encrypt" and "disable dm verity" zips from the ext sdcard with fastboot. Twrp stated the zips installed ok but there were also some red line failure lines in the dialogue as they were being installed. I rebooted the phone via fastboot but this just resulted in it booting direct to twrp as before. I tried normal boot from twrp but it still booted straight back to twrp. I then tried selecting normal boot from the fastboot, normal, recovery option menu accessed on the Leagoo T5 by powering off the phone and then pressing the pwr and vol+ buttons together but this still resulted in it booting straight to twrp. I then decided to uninstall twrp by flashing the stock firmware recovery image to try to boot from stock recovery. I did same and rebooted from fastboot and it booted to system.
The bad news is there is an imei failure message and the sim is not connecting to the network.I googled imei failure and saw that its can happen when firmware is changed. I installed the "mobileuncle" app but according to a youtube video I watched, when I tap "Engineer Mode" there should be 2 further options available, one being MTK Mode. I am only getting one option "Engineering Mode (Android) which when I select just results in being returned to the previous menu. please say this is not a major problem!
Click to expand...
Click to collapse
It could be many reasons why device didn´t boot to system. Then to flash it you had to format data + flash DM-verity. Also is possible that this TWRP version is not completely suitable for your device or is unable to mount/unmount partitions correctly, you have to check from where you downloaded it and if some users are experiencing similar issues with it.
As per you IMEI lost, better is ever take a backup of the NVRAM through TWRP before to go further then it´ll be easy to recover it. In almost all firmwares for mediatek devices you´ll fnd inside the zips SPFT and SN Writer that is to recover your IMEI. Your IMEI is not really lost only got actually covered by blank codes due to a bad/incorrect flashing/wrong sequence firmware, so be careful what you do with Mobile Uncle tool if you´re not experimented with otherwise you´ll lost permanently.

SubwayChamp said:
It could be many reasons why device didn´t boot to system. Then to flash it you had to format data + flash DM-verity. Also is possible that this TWRP version is not completely suitable for your device or is unable to mount/unmount partitions correctly, you have to check from where you downloaded it and if some users are experiencing similar issues with it.
As per you IMEI lost, better is ever take a backup of the NVRAM through TWRP before to go further then it´ll be easy to recover it. In almost all firmwares for mediatek devices you´ll fnd inside the zips SPFT and SN Writer that is to recover your IMEI. Your IMEI is not really lost only got actually covered by blank codes due to a bad/incorrect flashing/wrong sequence firmware, so be careful what you do with Mobile Uncle tool if you´re not experimented with otherwise you´ll lost permanently.
Click to expand...
Click to collapse
I got into engineering mode via dialer code. CDS option was missing from connectivity. I installed https://m.apkpure.com/cds-mobile/com.doubleapaper.cds.cds_mobile but CDS is still missing from engineering mode

pcfreeze said:
I got into engineering mode via dialer code. CDS option was missing from connectivity. I installed https://m.apkpure.com/cds-mobile/com.doubleapaper.cds.cds_mobile but CDS is still missing from engineering mode
Click to expand...
Click to collapse
Sorry, just realised that this is the wrong app! nothing to do with cds in engineering mode! I triedhttps://apkcombo.com/common-data-service/com.mediatek.connectivity/
but got message that the file was corrupted and it would not install

Can't boot

I went through the process of using Smali and Magisk on my phone. Everything was good. Since I was doing this for PoGo, I decided to "clean-up" by disabling some of the settings. I turned off OEM unlocking, reboot the phone in to the bootloader and did a adb flashing lock. I rebooted the phone and not get the error "Can't find a valid operating system". I can boot in to the bootloader with the power button + down volume but I can't unlock the bootloader with ADB and fastboot.
Am I screwed?

I'm also not able to boot in to recovery. I also get the error "Can't find valid operation system"

Well probably too late to reply.
I'm not an expert, i'm newbee but when i installed my custom rom i met some problems to reboot. I solved them by re-installing firm operating system. You can do it by connecting your device with a good usb cable and go to google website : android flash tool
This will reinstall a new an clean system (but erase your data if not saved before).
After that you can install a custom rom from the begining.

Entering TWRP instead of Recovery Mode (Doogee S60)

Hi There!
I'm exeriencing a wierd problem:
On my rooted Doogee S60, i was able to enter the built in recovery mode (and from there the fastboot mode) with Vol+ and Power.
Since i've installed a twrp recovery.img, pressing Vol+ and Power will launch the TWRP UI (wich i cant use, because my touchscreen is disabled).
Normal boot won't work eighter - i flashed a corrupted system.img file as it looks like (ooops). There is also the message at the Boot Screen saying:
"Orange State - Your device has been unlocked and can't be trusted. Your device will boot in 5 seconds"
... although these 5 seconds won't countdown and the device won't boot.
If i enter the TWRP, i can still access the ADB mode. So i can sideload stuff on the device, even the sd card is shown on pc. But the command
adb reboot fastloader
will reboot the phone, but not load the fastloader/fastboot - as it stucks at boot screen (orange state).
Any other ideas to access fastboot, due to flash the recovery.img again with the original to fix?
... or simple question: did i brick it?
thx in advance

Command
Code:
adb reboot fastloader
doesn't exist.
Look inside here:
How to Reboot Android Device into Fastboot or Recovery Mode via ADB « My Digital Life
If you’re using Android phones, tablets or devices, which is proliferating across all markets, prices and channels nowadays, then you may want to familiar yourself with fastboot or recovery mode, which is useful when you need to troubleshoot your beloved phone from the like of Samsung, HTC...
www.mydigitallife.net

introjoe said:
Hi There!
I'm exeriencing a wierd problem:
On my rooted Doogee S60, i was able to enter the built in recovery mode (and from there the fastboot mode) with Vol+ and Power.
Since i've installed a twrp recovery.img, pressing Vol+ and Power will launch the TWRP UI (wich i cant use, because my touchscreen is disabled).
Normal boot won't work eighter - i flashed a corrupted system.img file as it looks like (ooops). There is also the message at the Boot Screen saying:
"Orange State - Your device has been unlocked and can't be trusted. Your device will boot in 5 seconds"
... although these 5 seconds won't countdown and the device won't boot.
If i enter the TWRP, i can still access the ADB mode. So i can sideload stuff on the device, even the sd card is shown on pc. But the command
adb reboot fastloader
will reboot the phone, but not load the fastloader/fastboot - as it stucks at boot screen (orange state).
Any other ideas to access fastboot, due to flash the recovery.img again with the original to fix?
... or simple question: did i brick it?
thx in advance
Click to expand...
Click to collapse
Hi introjoe,
Are you doing? i have the doogee s60 but i just cant root it :'( can you tell me please how did you do it, or the files you use for it? i allready tried but, when i reset and enter fastboot mode, my pc simply dont recognize it.
I want to upgrade the android system to 9 or 10, thats why im doing all o this.
Thanks in advance.

@doryan666
i wasnt able to root the device in the end unfortunately.
i tried using an unofficial twrp, but i was stuck at the main boot screen
i t seems to need some bootloader-activation-code to enter the bootloader to install a new os.
the command line would look like
adb reboot bootloader "CODE"
the activation code has not been released yet by doogee ... and most probably never will be.
sorry to say but i dont think android upgrad will be possible with this device