Database Info

[HELP] Nexus S can't boot recovery

Hi all,
Been given a Nexus S i9023 by my brother who has been "tampering" with it and now it seems a bit messed up.
When booting up - it gets stuck on the "Google" screen with a padlock on it... I can get into fastboot and I can flash recovery but when I attempt to load any recovery - I get that same Google screen with the padlock! I've downloaded a stock rom and even flashed system etc via fastboot but that still gets me nowhere past the damn padlock!!
I've tried to "fastboot boot recovery.img" and I still get the Google screen with the padlock but it says "Fastboot status - OK" on the bottom left.
I've searched and searched but everyone just seems to give tips on how to flash recovery. I know how to flash recovery; it just seem to be going into it though! Could the internal memory be screwed?
Thanks for any advice!

Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot

albundy2010 said:
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
Click to expand...
Click to collapse
The phone stops at Google with the padlock on boot! Can't even get into the OS. Going to try to unbrick it and Odin but left my ubuntu laptop at my parents and can't be bothered to go get it... couldn't get it to work booting off cd rom. Kept giving me the "SBL Injection Failure Failed to find device" error booting ubuntu on a CD!

You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.

albundy2010 said:
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
Click to expand...
Click to collapse
No idea why I said Odin - I meant the unbrickable recovery thing.
I tried Odin with a Jig last night; got it into download mode and flashed with odin. Got the same result.
fastboot -w also gives the same issue...
If I have a storage issue - is there any way I can tell?

Basically you can tell by the issues you're having. Doing all the proper stuff to flash images etc and still having a booting/working device.
As far as a actual diagnostic tool I don't know of one. But it sure sounds like a hw issue to me.

I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance

Pironi90 said:
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Click to expand...
Click to collapse
Reflash your recovery using fastboot.

polobunny said:
Reflash your recovery using fastboot.
Click to expand...
Click to collapse
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s

Pironi90 said:
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Click to expand...
Click to collapse
Flash custom recovery.img part
http://wiki.cyanogenmod.org/wiki/fastboot#Flash_Custom_Recovery.img
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?

polobunny said:
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
I think so yes, I could access recovery before if that's what you mean by unlocked

Pironi90 said:
I think so yes, I could access recovery before if that's what you mean by unlocked
Click to expand...
Click to collapse
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.

You are entering recovery. Stock recovery
If you want a custom one either flash with fastboot or if you're rooted with a app. Goo manager. Rom manager etc.
Keep it mind that if you're on a stock ROM the custom recovery gets overwritten back to stock when the phone boots up the os
Q

UselessSniper001 said:
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
Click to expand...
Click to collapse
Then my phone is unlocked yes

polobunny said:
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
In installed the drivers and I installed the fastboot executable, but what do I have to do next? If I run the fastboot.exe, it just quickly shows a CMD-window and then disappears.
Edit:
I just discovered that, when I'm at the bootloader (I think it's called that way, the screen where you can select recovery), and I choose to reboot, I get the same 'error' as when I try to enter recovery.
Edit:
Alright, I was able to flash a new recovery, using cmd, but now when I try to enter my recovery, the phone gets stuck at a black screen with Google logo and padlock...

I have same problem as wolverine_2k who made the post. My nexus, can't start, I tried reboot and recovery but didn't work. After reboot or recovery I see Google logo, than Nexus screen and that is it. It didn't move to home screen and it stay with lighting screen all the time till I remove the battery. I can't power off it and don't know what to do. I can't transfer data with my PC (it don't recognize the device - only notice that "unknown device" is connected). Please any ideas?
P.S.: My English is not good, if someone answer do it simple please
Thanks!

PLEASE HELP! Bricked Honor 8

Hi,
I was trying to flash TWRP, but now I am stuck with flashing TWRP logo after rebooting or powering the phone on.
I am unable to get to the fastboot.
STEPS I did before brick:
1. unlocked OEM via official way
2. flashed TWRP
3. after that my phone was reset however most of the apps was missing, I was trying to do factory reset once again but it failed with the message "Data partition was heavily damaged"
4. I re-locked EOM
5. brick as mentioned above
Please help, I have the phone only two weeks and I have no idea how to fix this without fastboot.
Thank you.

Meiton said:
Hi,
I was trying to flash TWRP, but now I am stuck with flashing TWRP logo after rebooting or powering the phone on.
I am unable to get to the fastboot.
STEPS I did before brick:
1. unlocked OEM via official way
2. flashed TWRP
3. after that my phone was reset however most of the apps was missing, I was trying to do factory reset once again but it failed with the message "Data partition was heavily damaged"
4. I re-locked EOM
5. brick as mentioned above
Please help, I have the phone only two weeks and I have no idea how to fix this without fastboot.
Thank you.
Click to expand...
Click to collapse
Sounds like you flashed the 3030 version of TWRP. Download the 3020 version and put it in your fastboot folder. Plug in the USB to PC
Hold power and volume up untill the phone reboots. While it's still off immediately change to power and volume down and hold till it goes into fastboot (bootloader)
Now fastboot flash recovery TWRP.img
With the 3020 version.
Unplug the USB and hold power and volume up until it says the phone is booting.. let go and TWRP will load.
Go to Wipe / format data / type yes
Reboot to system and your all set
Sent from my Nexus 6P using Tapatalk

clsA said:
Sounds like you flashed the 3030 version of TWRP. Download the 3020 version and put it in your fastboot folder. Plug in the USB to PC
Hold power and volume up untill the phone reboots. While it's still off immediately change to power and volume down and hold till it goes into fastboot (bootloader)
Now fastboot flash recovery TWRP.img
With the 3020 version.
Unplug the USB and hold power and volume up until it says the phone is booting.. let go and TWRP will load.
Go to Wipe / format data / type yes
Reboot to system and your all set
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So I've tried that but the phone is still booting to recovery (flashing TWRP logo) no matter what.
Basically the phone is always on now because if hold the power button (or any other combination) for a few second it will just reboot back.
I have an access only to ADB, but I am not able to boot to bootloader at all, it seems the bootloader is damaged somehow.
Also that warning about unlocked OEM doesn't have that text saying "hold volume up to boot to recovery" etc. like before brick.

Hi there,
Try using the Huawei Multi Tool with the Unbrick option : https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
Speaking from experience, this little fellow helped me recover my phone when I bricked it ON DAY ONE after failed root attempt... (Derp)
Let me know if it helped you
(Leave a thanks if it did )
EDIT : This tool is also useful if you want to get lazy whilst rooting. I use it constantly when flashing diffrent bits and pieces

Clearly follow My steps To unbrick and get normal device ::
Step 1 ::
Download the full firmware of your device.
Step 2 :
make sure that your bootloader is in unlocking state
Follow the video blindly ::: https://youtu.be/OMKDnBqbi3U?list=PL...eT9J26lkefvVkK
don't panic of mobile.
Step 3 :: done ..enjoy u did it
--------------------------------------------------------------------------
If you bricked on nougat then follow the below steps
step one :::
download the downgrade package to mm .
then extract the zip and open the update.app using HuaweiUpdateextrator in that select recovery and extract
1.now, boot your device into fastboot and flash the recovery (Optional)(try this if it said incompatible version on recovery)
2. on your sd card and make a folder "dload" . and copy the update.app which we have extracted earlier
3.the switch off the device and press all three buttons you will be reboot into recovery and done . you device will be okey

Meiton said:
So I've tried that but the phone is still booting to recovery (flashing TWRP logo) no matter what.
Basically the phone is always on now because if hold the power button (or any other combination) for a few second it will just reboot back.
I have an access only to ADB, but I am not able to boot to bootloader at all, it seems the bootloader is damaged somehow.
Also that warning about unlocked OEM doesn't have that text saying "hold volume up to boot to recovery" etc. like before brick.
Click to expand...
Click to collapse
Booting to the bootloader is just a timing issue
Phone must be hooked to PC with USB
And volume up and power till it goes black
Then immediately volume down and power and Hold untill the bootloader loads
Keep trying until you get it
Sent from my Nexus 6P using Tapatalk

clsA said:
Booting to the bootloader is just a timing issue
Phone must be hooked to PC with USB
And volume up and power till it goes black
Then immediately volume down and power and Hold untill the bootloader loads
Keep trying until you get it
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I appreciate your help but I've tried it multiple times always with the same result.
I also can use "adb reboot bootloader", but it will reboot again to stuck recovery.

DJ Daemonix said:
Hi there,
Try using the Huawei Multi Tool with the Unbrick option : https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
Speaking from experience, this little fellow helped me recover my phone when I bricked it ON DAY ONE after failed root attempt... (Derp)
Let me know if it helped you
(Leave a thanks if it did )
EDIT : This tool is also useful if you want to get lazy whilst rooting. I use it constantly when flashing diffrent bits and pieces
Click to expand...
Click to collapse
I've tried that, but I am still stuck as that tool is using fastboot as every other tool to flash .img files.
Thank you for the tip though.

Plug phone into computer with USB, then hold down power + volume down until it eventually boots into bootloader. I had the same scenario as you and that's how I got into the bootloader. You can flash either a good TWRP or the stock recovery, either one will work.

[GUIDE] How to Unlock Bootloader and Install TWRP

First, you’ll need ADB and fastboot, which can be downloaded here. To set up ADB, go to Settings/About Phone/Software Info and tap on build number until you get a toast notification saying “You are now a developer!” You will now have a new category in Settings called Developer Options. Go into developer options and enable USB debugging and OEM Unlock. You won't be able to turn it on if your phone is plugged in to your PC. Once you've turned it on, go to your PC, open Terminal or Command Prompt and type “adb devices”. Then plug in your phone and hit enter. You'll get a prompt on your phone to “Allow connection​s to this PC?”. Check Always allow and Allow. Now run “adb devices” again. Your device should now appear in Terminal.
If you have a SD card, download the latest zips from here and here onto your​ SD card. It'll save you a step later on.
Then you'll need to reboot to fastboot by holding down VOL- and plugging in USB while power is off. Alternatively​, you can type “adb reboot bootloader” in Terminal or Command Prompt.
Next, you'll need to unlock the bootloader. Bootloader unlocking​ will factory reset your phone! Once you're in fastboot, run “fastboot oem unlock” in Terminal or Command Prompt. Now the bootloader is unlocked.
Now it's time to flash TWRP, a custom recovery for Android. It's going to be the way you install custom ROMs and add-ons. Download Official TWRP here. Once you've extracted​ the recovery.zip, run this command: “fastboot flash recovery path/to/recovery.img”. Once the file has flashed, disconnect the USB cable and battery. The next step is important! You're going to need to boot into TWRP for the first time. With the phone off, hold down VOL- and press power until the phone vibrates and the LG logo appears. While still holding down VOL-, release and immediately press and hold power. You should now be at a white screen that says “Reset all data and restore to factory settings?” Use the volume and power keys to select yes and yes again. If you've installed​ TWRP successfully​, it won't actually factory reset your phone. Now you should see the TWRP screen. If you don't see the TWRP screen and instead see a floating ring that says “Erasing”, don't worry. Let if complete and try flashing TWRP in fastboot again.
In TWRP, you'll be greeted by a screen that says “Swipe to allow modifications?” Swipe it, then go to the Wipe tab. Go to Wipe, then Format Data, then type yes, then go to the Reboot tab and select Recovery to reboot into TWRP again. If you're prompted to install the TWRP app, don't bother.
Once you've rebooted into TWRP again, it's time to disable encryption​ and root the phone. Download the latest zips here and here. Skip downloading them if you already put them on your SD card earlier. On your PC, push the files to your phone using the command “adb push path/to/file.zip /sdcard/”. You can drag and drop the file into Terminal or Command Prompt to copy file path. Then go to the Install tab in TWRP and select the no-verity-opt-encrypt.zip, tap Add more zips, then add the root zip, then swipe to flash. Let the zips flash, then tap the Reboot System button when it's done. Your phone will take a little longer to boot and might reboot a couple times.
Once you're back in the OS, go through the setup wizard. Set up Magisk. If you stay on stock, you should install an app like Quick Reboot Pro from the Play Store to make it easier to reboot into recovery. Now reboot back into TWRP and go to the Backup tab. If you have a SD card, set it as the backup location. You can enable compression if you want. This will make a full system backup that you can restore from as long as you have TWRP. If the backup takes up too much space, you can put it in Google Drive or your PC later on.
You are now ready to install ROMs!
Thanks to @messi2050

My device will not start boot loader with command "adb reboot bootloader" or with the method of holding volume down and pugging it into the PC, it just restarts and boots like normal. i cannot even get to the stage to use the command "fastboot oem unlock"

I cant get it too boot into TWRP

? Has anyone else have had issues geting into bootloader mode on lg stylo 2 boost mobile.

meg540 said:
? Has anyone else have had issues geting into bootloader mode on lg stylo 2 boost mobile.
Click to expand...
Click to collapse
Please explain more in detail so you can be helped better In what ways? What are you doing to get into bootloader mode? I've never had any issues on my T-Mobile Stylo 2 plus. Are you trying to get into bootloader using buttons manually or through twrp or adb?

SM210 said:
Please explain more in detail so you can be helped better In what ways? What are you doing to get into bootloader mode? I've never had any issues on my T-Mobile Stylo 2 plus. Are you trying to get into bootloader using buttons manually or through twrp or adb?
Click to expand...
Click to collapse
Im trying too put my phone into bootloader mode to unlock bootloader but it keeps restarting phone and wont go into it. Also i have tryed on my computer command promt but phone into bootloader mode it. Restarts phone but not into bootloader mode. Also i have tryed power down and holding power button that doesn't work.

meg540 said:
Im trying too put my phone into bootloader mode to unlock bootloader but it keeps restarting phone and wont go into it. Also i have tryed on my computer command promt but phone into bootloader mode it. Restarts phone but not into bootloader mode. Also i have tryed power down and holding power button that doesn't work.
Click to expand...
Click to collapse
You hold volume DOWN and power then soon as screen comes on and you see LG you let go of the power button and then immediately press power again and you never let off volume DOWN. That doesn't work?
Edit

SM210 said:
You hold volume DOWN and power then soon as screen comes on and you see LG you let go of the power button and then immediately press power again and you never let off volume DOWN. That doesn't work?
Edit
Click to expand...
Click to collapse
Ill try that i think i wasnt doing it correctly i was holding down power button then i let go an i was holding down the down button. Ty for u help ill try it later today.

Hey there, I've got the LG K530F, is there any chance of unlocking it? I looked up the LG developer website and it's not listed in there, filling that form will just lead to a popup regarding that. I thought about downgrading it back to MM (Android 6.0) using the K350F10d_00_02221.kdz firmware package aiming to be able to run fastboot oem unlock, but I'm afraid of getting it bricked. Anyone tried it? I recall doing something like that to unlock the LG Optimus L9, but that one was way older and had much weaker security measurements.

Can't get into Bootloader
Hi i have a LGL82VL and when trying to use adb reboot bootloader it just restarts, And when using Vol Down and Power it just comes to the factory reset page (Hard Reset)
Any ideas on how to get to the bootloader? i checked with fastboot devices while on the hard reset page and got nothing. Any Ideas?

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

CANNOT enter recovery mode proper

The issue: When booting I get the "bad key" boot text which hangs for about 10 seconds before going to splash.
When doing power button + volume up, the bad key hangs for so long that holding down power button just SHUTS THE PHONE OFF.
I can do power button + volume down to enter bootloader, and then enter recovery mode from there, but when I do that I get NO COMMAND
Ive also tried with adb
adb reboot recovery
same thing NO COMMAND
Everything that I google about NO COMMAND comes back with "oh just do power button + volume up duh" and each time I read that as a solution it makes me a little bit more angry.
https://forum.xda-developers.com/moto-e6/how-to/rooting-e6-surfna-t3965659
Ive been following this guide to root my moto e6 and everything has been fine so far, but im stuck trying to install magisk. Magisk manager has already been installed, and I believe I have installed magisk. But I cannot boot into proper recovery to use it.
About to give up, hopefully someone can help

installed a bootlogo following this guide
https://forum.xda-developers.com/moto-e5/how-to/boot-logo-moto-e5-stock-bad-key-removed-t3869259
to see if that would help. No change. Cant boot into recovery mode proper.

alexsherman4 said:
The issue: When booting I get the "bad key" boot text which hangs for about 10 seconds before going to splash.
When doing power button + volume up, the bad key hangs for so long that holding down power button just SHUTS THE PHONE OFF.
I can do power button + volume down to enter bootloader, and then enter recovery mode from there, but when I do that I get NO COMMAND
Ive also tried with adb
adb reboot recovery
same thing NO COMMAND
Everything that I google about NO COMMAND comes back with "oh just do power button + volume up duh" and each time I read that as a solution it makes me a little bit more angry.
https://forum.xda-developers.com/moto-e6/how-to/rooting-e6-surfna-t3965659
Ive been following this guide to root my moto e6 and everything has been fine so far, but im stuck trying to install magisk. Magisk manager has already been installed, and I believe I have installed magisk. But I cannot boot into proper recovery to use it.
About to give up, hopefully someone can help
Click to expand...
Click to collapse
bad key and/or N/A is just the phone saying it has an unlocked bootloader.
NO COMMAND when entering Recovery, yes, google is right. When you see NO COMMAND, press and HOLD the power button and TAP the volume up key. You should see at the top, Android Recovery and a bunch of options below. If you don't see this, your recovery partition was probably modified/corrupt. Flash the original recovery.img from a stock rom. I don't think there's a working E6 TWRP recovery image yet.

If you still haven't figured this out I have a possible fix. I found that upon first installing the magisk_patched.img from the guide you linked, everything booted up fine and magisk and root were working. I however made the mistake of booting normally...somehow this affects the magisk boot function in the recovery and gives the no command screen. I just fastboot flash recovery magisk_patched.img again and booted straight into recovery and that fixed it again. Just make sure once you have root again to use a program that allows you to boot back into recovery again directly.

fcohen said:
bad key and/or N/A is just the phone saying it has an unlocked bootloader.
NO COMMAND when entering Recovery, yes, google is right. When you see NO COMMAND, press and HOLD the power button and TAP the volume up key. You should see at the top, Android Recovery and a bunch of options below. If you don't see this, your recovery partition was probably modified/corrupt. Flash the original recovery.img from a stock rom. I don't think there's a working E6 TWRP recovery image yet.
Click to expand...
Click to collapse
When I get to the Android Recovery which option do I choose?
I tried "Reboot system now" and Magisk was still not installed

chami_bc said:
When I get to the Android Recovery which option do I choose?
I tried "Reboot system now" and Magisk was still not installed
Click to expand...
Click to collapse
You are not going to install magisk in stock recovery
Sent from my ocean using XDA Labs