Database Info

i bricked my honor, is there anything i can do?

So I had an unlocked H8 with LOS. As I wanted to install EMUI, I put the proper restore Update.app into the dload folder and started Huawei's recovery. Everything went well, I formated data and wanted to install the EMUI 4.1 ROM using the same method.
Unfortunately my H8 is bootlooping and there is now way into erecovery nor any other recovery. It simply reboots on every single known vol up or down key pressing combination. The only thing I can go to is fastboot mode when holding down vol down and plugging in usb wire. But, it says frd locked and I can't install nor boot twrp. It's simply gone and reboots all the time.
Any hints? I can't even turn it off.

I wanted to give away that phone that's the reason. Last time I did it this way, I could flash the EMUI 4.1 since it's signed. But not this time.
Interesting part is, that although fastboot says frd locked, I still get the "phone unlocked" warning on every reboot. dload method isn't working, as it simply keeps rebooting.
It's my hardest brick so far I ever encountered

the same thing happened to me.....on my phone lock/unlocked frp and bootloader were tweaked for some reason(I mean that what was written wasn't the reality) so how did I fix it? I kept on to flash rollback package many times and I tried to unlock/relock bootloader again, at the end the phone let me to flash the firmware, I didn't know how but the phone allowed me to flash things throw recovery(using dload method). At the begin I only could access to erecovery and fastboot. I suppose that I broke system and data partition and while I looked/unlocked the bootloader, the wipe fixed the partition table. Sorry I'm tired and I know that my English sucks, I hope you understand what I have written.

How did you enter erecovery as this isn't working for me.... What did you flash over fastboot?

Have you tried flashing the firmware separately using adb on computer?
For this you just need to extract the Update.app using the firmware extractor for huawei. Then flash them individually using adb commands in cmd.

I can't access any state that would allow to do adb.

faeArai said:
How did you enter erecovery as this isn't working for me.... What did you flash over fastboot?
Click to expand...
Click to collapse
sorry. I'll try to explain better, however on Huawei/honor devices there are not one but two recoveries, so one is the normal recovery flashed in recovery partition, the second one is the Huawei recovery that is flashed in recovery2 partition, so if you didn't touch recovery2 partition, your erecovery is still there, now, if you press VOL+ VOL- and POWER it will reboot to recovery2 and it starts to flash something from dload in your sd card, so in my opinion you should do this things, first try this method to flash rollback package(this is the transition package from 7 to 6 and you will find it on honor site) if this is still not working try locking and unlocking again your bootloader(I hope this fix partitions of your device) then try to enter recovery and do a wipe and then boot your device, if this doesn't work flash rollback package(now it would work) and then flash an emui 4 full firmware image, always using dload method. trust me... I did the same... and it worked for me. let me know if it works for you :good:

faeArai said:
So I had an unlocked H8 with LOS. As I wanted to install EMUI, I put the proper restore Update.app into the dload folder and started Huawei's recovery. Everything went well, I formated data and wanted to install the EMUI 4.1 ROM using the same method.
Unfortunately my H8 is bootlooping and there is now way into erecovery nor any other recovery. It simply reboots on every single known vol up or down key pressing combination. The only thing I can go to is fastboot mode when holding down vol down and plugging in usb wire. But, it says frd locked and I can't install nor boot twrp. It's simply gone and reboots all the time.
Any hints? I can't even turn it off.
Click to expand...
Click to collapse
I ran into this issue not that long ago. What you have to do is relock your bootloader using ADB. The ADB commands and instructions can be found in this thread.
Just a FYI, do not use the links to the software listed in that thread as it is a little outdated. The method still works but the software will probably not work. Just be sure to get the most recent/appropriate version of SuperSU and TWRP via their official threads (This is if you want to re-root). There are Honor 8 specific TWRP files if I remember correctly, so be sure to check around the Honor 8 forums for the correct files.
A quick summary of what I did:
1) Power your phone off and then boot into fastboot by holding Vol down + Power; as soon as it boots up, plug your phone into your combuter via your usb cord.
2) With ADB running, type:
Code:
fastboot oem relock [COLOR="LightBlue"]################[/COLOR]
NOTE: The '#' should be replaced with your unique unlock code that you obtained to unlock your bootloader.
3) Wait for it to format and reset your phone and go through the setup. BE SURE TO BYPASS all google registration; skip everything you can to get into the phone itself. If you do register, it will reactivate FRP and you'll have to start over again.
4) Turn on USB Debugging and every other setting that enables developer administrative navigation and control just to be safe. USB Debugging being the most important one, though.
5) Restart your phone and boot into fastboot again using Vol down + Power.
6) Unlock your phone again with:
Code:
fastboot oem unlock [COLOR="LightBlue"]################[/COLOR]
7) Once the command is entered, it'll reset your phone once more and - as stated before - bypass/skip all google (FRP) registration.
8) Enable developer options and USB debugging again and make sure that OEM Unlocked is checked and grayed out.
9) Reboot into fastboot mode to confirm that FRP is disabled and you should be able to install TWRP now via ADB.

@Numerics thanks. The thing is, that I can't boot anything. I can't even go into eRecovery. Nor can I flash a stock EMUI 4.1. It just boot loops all the time and I can only access fastboot.

If you can flash twrp..........Install los or other Rom ..................Go back to stock.......you must flash b360 ober adb...... because los is 7.1...............if you on b360 you can usw the rollback for emui 4.1........,..............sry for bad english

I can easily go to fastboot. But I can't flash anything. I extracted the img from the update.app but can't flash. It simply says that it's not permitted.

faeArai said:
I can easily go to fastboot. But I can't flash anything. I extracted the img from the update.app but can't flash. It simply says that it's not permitted.
Click to expand...
Click to collapse
With my method, you don't need to flash anything. Just relock your bootloader via adb in fastboot mode and let it reset. Unless I'm not understanding your issue entirely.

@Numerics as I said, in won't boot anything as it is constantly boot looping. There is no way to access any kind of recovery nor erecovery. There is no boot into Android. The only thing accessible right now is fast boot (which is not ADB). But even in fast boot I can't do anything als operations are not permitted.
after boot looping and starting fast boot mode, I can see a "Android reboot reason" section saying:
AP_S_PANIC
data is invalid
There is still a lineageos installed on system as firmware but as I tried to get rid of it by going back to stock EMUI, I guess Huawei's rollback did something wrong and killed recovery (although I did it in the past successfully).
I tried to run HiSuite to recover my phone, but it just says, that my phone is not supported.
Speaking of this, Huawei messed up with that whole fastboot locking bull****.

faeArai said:
@Numerics as I said, in won't boot anything as it is constantly boot looping. There is no way to access any kind of recovery nor erecovery. There is no boot into Android. The only thing accessible right now is fast boot (which is not ADB). But even in fast boot I can't do anything als operations are not permitted.
after boot looping and starting fast boot mode, I can see a "Android reboot reason" section saying:
AP_S_PANIC
data is invalid
There is still a lineageos installed on system as firmware but as I tried to get rid of it by going back to stock EMUI, I guess Huawei's rollback did something wrong and killed recovery (although I did it in the past successfully).
I tried to run HiSuite to recover my phone, but it just says, that my phone is not supported.
Speaking of this, Huawei messed up with that whole fastboot locking bull****.
Click to expand...
Click to collapse
No, I know ADB isn't Fastboot. What I'm trying to say is that you should be able to still run ADB via CMD on Windows when you're in fastboot mode to relock your bootloader with the directions I gave in my previous post. It'll force-restore your phone to a non-bricked/vanilla state. At least that is how I fixed mine.
Like... You can't even try using the 'fastboot oem relock ################' function via the ADB console while in fastboot?

yes boy trust us, you haven't a working OS so it is a normal thing that your phone reboot, you cannot access to recovery because some partitions are corrupted (data partition) , so these are the steps that could help you:
1) using fastboot, relock your boot loader
2)using fastboot, unlock your boot loader (partition table would be ok now, and you would be able to use load method to flash things trow stock recovery)
4)put inside your sd card \dload\update.app(use rollback package)
3) press all the buttons while your device is rebooting(do this before the blue screen logo appear), your phone is now looking for something inside your sd card
5) if the next step doesn't work do a factory reset from recovery that now would be working
6) put inside your sd card a full android 6 (emus 4) update.app and pressing all buttons it will install the firmware
7) your device now is locked and back to stock, maybe without cust partition or maybe in test mode but it is certainly alive
8) do a factory reset and reinstall the firmware
9) your phone is now ok

You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.

faeArai said:
You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.
Click to expand...
Click to collapse
Which model do u own?
Sent from my Honor 8 using XDA Labs

The European one.

faeArai said:
You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.
Click to expand...
Click to collapse
This is not the truth.....locking bootloader will erase all your data and fix partitions....and with fixed partition you can access to recovery ......trust me the only thing that you can do is to lock your bootloader......you can't flash anything from fastboot and boot recovery or system now...... lock your bootloader and then unlock it again, try using "fastboot OEM lock *****" or "fastboot OEM relock *******" (try cmd runned as admin, people say that this makes the difference) then unlock your device again and .....magic your recovery will boot......the same thing happened to me and I fixed my phone using this trick, however, even if you had frp unlocked it would say you that isn't possible to write anything because you broke some partition, and that's the reason why you can't boot recovery, wait one second and think: why doesn't my recovery boot?

It has nothing to do with trust. I did it and device is still a full stone brick. Nothing changed by locking the bootloader besides that now I can't unlock the bootloader anymore.

[Help] Bootloop after re-locking Bootloader!

After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?

Mr Ian said:
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Click to expand...
Click to collapse
Man, when you lock the bootloader you need to make sure you're 100% back on stock without any modifications flashed. Seems to me you tried locking while having magisk flashed.
Try to see if you're able to get into recovery. Get into bootloader menu by pressing power button+volume down and the press volume upp until you get to recovery and then press power button. If you're able to get into recovery then download the full ota image for Google pixel sailfish from here https://developers.google.com/android/ota and then while you're in there should be an option to update using adb. You need to adb sideload the update from your computer to your phone. I know this should work on a non Verizon phone but I hope and assume that is what's needed this time. If you're not able to get into recovery and your bootloader is still locked then you pretty much have a bricked device.

Arju said:
Man, when you lock the bootloader you need to make sure you're 100% back on stock without any modifications flashed. Seems to me you tried locking while having magisk flashed.
Try to see if you're able to get into recovery. Get into bootloader menu by pressing power button+volume down and the press volume upp until you get to recovery and then press power button. If you're able to get into recovery then download the full ota image for Google pixel sailfish from here removed-link and then while you're in there should be an option to update using adb. You need to adb sideload the update from your computer to your phone. I know this should work on a non Verizon phone but I hope and assume that is what's needed this time. If you're not able to get into recovery and your bootloader is still locked then you pretty much have a bricked device.
Click to expand...
Click to collapse
At the minute I've taken it to a Phone shop hoping they will be able to figure a way to get to the recovery menu - baring in mind I had TWRP flashed.
Yeah, It will go to the Bootloader menu but when trying to go into recovery it will just repeat the same process as before where by it will flash the Google splash-screen then restart. Any notes on how to go about hard flashing the image?

have you tried fastboot boot twrp.img? does it bootloop aswell? if so, you might have hard bricked your pixel... last solution is to try flash stock image and then try again with stock recovery / twrp img.

Mr Ian said:
At the minute I've taken it to a Phone shop hoping they will be able to figure a way to get to the recovery menu - baring in mind I had TWRP flashed.
Yeah, It will go to the Bootloader menu but when trying to go into recovery it will just repeat the same process as before where by it will flash the Google splash-screen then restart. Any notes on how to go about hard flashing the image?
Click to expand...
Click to collapse
If you can't access stock recovery and your bootloader is locked then your device is pretty much hard bricked unfortunately. Don't think the phone shop would figure it out, they might change the motherboard as a solution if they don't have the right tools to reflash on a deeper level. Hope they figure it out. Please let us know if they managed to fix it. If not then someone else might have some suggestions. I'll try to think of something else.
Try either of these commands to see if you can unlock the bootloader again:
fastboot oem unlock
or
Code:
fastboot flashing unlock
And then try what the post above me suggests.

Hey, did you ever figure out a solution to this? I did the same thing to myself today...

any solution??
---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------
Mr Ian said:
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Click to expand...
Click to collapse
Did you managed to unlock it???

You can unlock the bootloader with htc-fastboot if you have a bricked android 7-8.
They patched it on Android 9.
On android 9 your only chance is to reflash it in edl mode. Anyone here who can help me to enter edl mode with my pixel?

can not access fastboot

Hi guys, I need some help. I flashed 1.6 in edl EU firmware with MiFlash. Now when I load the phone it comes up saying that the bootloader is unlocked and press power to continue. This stops me from holding down power and volume to get into fastboot. I have also tried going into recovery and reboot into bootloader but still no fastboot. Just bootloader is unlocked and press power to continue as I have mentioned before.
Please help! ? As need fast boot to install recovery!

ztxaxonjay said:
Hi guys, I need some help. I flashed 1.6 in edl EU firmware with MiFlash. Now when I load the phone it comes up saying that the bootloader is unlocked and press power to continue. This stops me from holding down power and volume to get into fastboot. I have also tried going into recovery and reboot into bootloader but still no fastboot. Just bootloader is unlocked and press power to continue as I have mentioned before.
Please help! ? As need fast boot to install recovery!
Click to expand...
Click to collapse
What does it say in developer options?

In development options it says bootloader is unlocked under OEM unlocking
also I turned on USB debugging

ztxaxonjay said:
In development options it says bootloader is unlocked under OEM unlocking
also I turned on USB debugging
Click to expand...
Click to collapse
Plug in your phone to your cable to your PC. Reboot the phone and soon as it turns off, hit the sound up & sound down button along with the power button. Hold these down until your PC sounds and verifies you are in EDL mode. Once in EDL, start the app on PC using admin privileges. Once the program has started, run unlock bootloader (option 4) again. Once it's complete, reboot the phone to the OS. Reboot holding power & volume up. This will take you to recovery. Now go to reboot to bootloader. When in fastboot follow the directions to install TWRP. Do not skip any steps! Apparently, steps are being skipped.

jim262 said:
Plug in your phone to your cable to your PC. Reboot the phone and soon as it turns off, hit the sound up & sound down button along with the power button. Hold these down until your PC sounds and verifies you are in EDL mode. Once in EDL, start the app on PC using admin privileges. Once the program has started, run unlock bootloader (option 4) again. Once it's complete, reboot the phone to the OS. Reboot holding power & volume up. This will take you to recovery. Now go to reboot to bootloader. When in fastboot follow the directions to install TWRP. Do not skip any steps! Apparently, steps are being skipped.
Click to expand...
Click to collapse
Hi Jim so I've followed your instructions and that has managed to get me into fastboot thank you but still not able to flash recovery it's just saying no partition and when I use the unlock boot tool it failed on the last bit for fastboot I've add photos

ztxaxonjay said:
Hi Jim so I've followed your instructions and that has managed to get me into fastboot thank you but still not able to flash recovery it's just saying no partition and when I use the unlock boot tool it failed on the last bit for fastboot I've add photos
Click to expand...
Click to collapse
I said you need to follow directions. In the directions to run <fastboot boot TWRP.img>, not flash. Then flash the installer if you wish to make it permanent, but I wouldn't recommend making it permanent to allow OTAs to work properly.

Sorry I'm not sure where I've gone wrong here I followed your instructions but when I run the axon edl tool it managed to unlock the bootloader and give me back fast boot with out any stop's on boot up but when I run the axon edl tool I got the error at the end which I posted in the picture so then after that didn't work I put it into fastboot and tried to flash the recovery myself and That didn't work either that's why I posted a photo of that as well

ztxaxonjay said:
Sorry I'm not sure where I've gone wrong here I followed your instructions but when I run the axon edl tool it managed to unlock the bootloader and give me back fast boot with out any stop's on boot up but when I run the axon edl tool I got the error at the end which I posted in the picture so then after that didn't work I put it into fastboot and tried to flash the recovery myself and That didn't work either that's why I posted a photo of that as well
Click to expand...
Click to collapse
Go into fastboot, connect to your PC and run <fastboot boot TWRP.img> then flash Magisk. Do not flash the recovery. Boot TWRP using the above command. Flashing the recovery will not work. If you read the directions, it tells you that. I have told you everything step by step. If you can access fastboot, you are done with the EDL tool, just go into fastboot and boot TWRP using the ADB command <fastboot boot TWRP. img>
---------- Post added at 06:19 AM ---------- Previous post was at 06:06 AM ----------
ztxaxonjay said:
Sorry I'm not sure where I've gone wrong here I followed your instructions but when I run the axon edl tool it managed to unlock the bootloader and give me back fast boot with out any stop's on boot up but when I run the axon edl tool I got the error at the end which I posted in the picture so then after that didn't work I put it into fastboot and tried to flash the recovery myself and That didn't work either that's why I posted a photo of that as well
Click to expand...
Click to collapse
Go into fastboot, connect to your PC and run <fastboot boot TWRP.img> then flash Magisk. Do not flash the recovery. Boot TWRP using the above command. Flashing the recovery will not work. If you read the directions, it tells you that. BTW, I don't think you read the directions. Go back and look at my previous post. You only use the EDL tool to unlock the bootloader. After you have unlocked reboot to the stock recovery and select reboot to fastboot. Then boot TWRP.

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

Pixel 4a stuck in fastboot mode

Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.

Maybe you can use this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
And start on this line in "First Step" section:
Plug the phone into a usb port of your pc.
Then complete all the tasks in "Second Step" section to get your phone at least booting in android 10.

ifixibrick said:
Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.
Click to expand...
Click to collapse
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.

Raj Pandiyan said:
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.
Click to expand...
Click to collapse
How do I do that? I seem to be stuck in fastboot mode.

ifixibrick said:
How do I do that? I seem to be stuck in fastboot mode.
Click to expand...
Click to collapse
Is it bricked? Cannot flash stock Android to remove ArcaneOS
I recently purchased a used Pixel 4a, and I now understand why the seller was offering such good price for it and why he refused to respond to me now I have it. This phone has ArcanseOS 10 installed, which has only 3 apps installed... Setting...
forum.xda-developers.com

reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.

jawz101 said:
reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.
Click to expand...
Click to collapse
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.

ifixibrick said:
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.
Click to expand...
Click to collapse
Can you type fastboot reboot recovery and get into recovery mode? You'll see a little Android guy with a red thing if you're in there.
If that doesn't work- it almost sounds as though your recovery partition is deleted or something. You can reflash the recovery from fastboot.

Hey, I had the same problem. I've got it resolved now and wasn't able to find any help on how to resolve it, but this thread is as close as it came, so in the off chance that somebody else comes along, I thought I'd write up the steps I took.
Because it was in fastboot mode, I was able to easily restore my phone to factory settings by running flash factory image script I downloaded here.
My original image was sunfish-rq3a.210605.005-factory-be541467 which I followed the steps with but couldn't get it to work. I got to the Google logo with a status bar that just ran forever. But the flash-all.sh script worked to get the phone booting again.
So what I did to get Magisk to work was to use that same factory image site to download an older version. I used a version that was listed in a different root guide with the idea that maybe the version I tried before wasn't compatible with magisk, but presumably the one from the guide was. So I tried sunfish-rq1a.210105.002, ran the flash-all in fastboot, and confirmed that it booted--it did.
Next I redid 2.2 through 3 and it worked, and the boot completed with Magisk installed. Everything seems to be working fine now.