Database Develop

Softbrick achieved, need help

P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?

I tried everything in this thread:
http://forum.xda-developers.com/p8lite/general/hand-fixing-bootloop-t3464740
to no avail. One thing I noticed is that the link given in the Fastboot menu links to a Chinese (?) website - http://zh.ui.vmall.com/emotiondownload.php?mod=restore - I'm not sure if this is indicative of me having a device for the East Asian markets and if there are any software differences?

Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).

GfIsGonnaKillMe said:
Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).
Click to expand...
Click to collapse
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?

XePeleato said:
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?
Click to expand...
Click to collapse
Just the very static image, it doesn't even go into the animation.
Edit: this is a newly bought P8 Lite, the Box says Android 5.0, don't know if relevant?
by now I've wiped stuff with TWRP more times than I can count, and tried manually flashing the boot, recovery, cust and system of b132, b170, b190, and b564 to no avail

GfIsGonnaKillMe said:
Just the very static image, it doesn't even go into the animation.
Click to expand...
Click to collapse
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.

XePeleato said:
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.
Click to expand...
Click to collapse
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery

GfIsGonnaKillMe said:
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery
Click to expand...
Click to collapse
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.

XePeleato said:
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.
Click to expand...
Click to collapse
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.

GfIsGonnaKillMe said:
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.
Click to expand...
Click to collapse
[ 8.389146s][pid:1,cpu1,init]BUG: failure at /cloud/jenkinswh/ci/workspace/Alice_Channel_ANDROID/android_code/kernel/drivers/video/hisi/hi6220/balong_compose.c:613/vpu_on_notice_ade()!
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.

XePeleato said:
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.
Click to expand...
Click to collapse
It is very nice of you to look into this! Worst case scenario, the device was broken from the start and has now lost its warranty (though I booted it up once without problems right in the beginning).
For the main problem - which is my gf - I simply factory reset my own P8 Lite and put the stickers from the new one on it. Now I don't have a phone, but at least I get to keep my relationship
ninja edit: checking my terminal history, I remember trying to fix the not-installing SuperSU by trying fastboot -w and fastboot format cache as recommended elsewhere, but both failed
Playing around with it again, it seems the only fastboot commands working are fastboot flash and fastboot reboot, everything else is giving a "FAILED (remote: Command not allowed)" error, even for things like getvar
flashing b564 allows me to get into stock recovery, will try dload update now!!
EDIT: IT WORKS!!!
Things I learned from this:
- it is important to flash right update version
- use dload if you can boot into stock recovery
- recovery will only be loaded if not connected via USB, otherwise EMUI crap will launch
- vendors do not always have correct information on device package!!

GfIsGonnaKillMe said:
P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?
Click to expand...
Click to collapse
delete

For unbrick, its easy if your bootloader is unlocked.
Just need time and flash few files by adb (downgrade)and update your device's to the android version you want.
If you want I have all the necessary files.
After your device's is like at his first boot.
Sent from my SM-N9005 powered by QS-N9005-LP

SOFT BRICK using tool Xiaomi Mi A2

Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy

What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...

AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this

Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work

AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?

erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.

AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:

erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.

AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me

erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers

AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?

erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.

Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861

ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:

AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp

erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.

ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?

Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.

prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?

erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.

Fastboot no longer working

Crossposting from the Lineage 15 thread, as it may be a more general problem...
I installed lineage 15 a couple days ago.
I followed the OP, flashed the partition firmware first, then the ROM, TWRP, GAPPS, rebooted, flashed Magisk. Everything was working fine.
I took the 0210 nightly OTA. Google Play Services and all Google apps stopped working.
I figured I'd start fresh through fastboot, but now any command that would actually help (flash, boot, etc) returns "failed: unknown command". Can't boot into TWRP.
"fastboot devices" returns the device ID fine, fastboot reboot works.
Tried a factory reset based off another post I found, still in the same boat.
Any ideas?

Horror Business said:
Crossposting from the Lineage 15 thread, as it may be a more general problem...
I installed lineage 15 a couple days ago.
I followed the OP, flashed the partition firmware first, then the ROM, TWRP, GAPPS, rebooted, flashed Magisk. Everything was working fine.
I took the 0210 nightly OTA. Google Play Services and all Google apps stopped working.
I figured I'd start fresh through fastboot, but now any command that would actually help (flash, boot, etc) returns "failed: unknown command". Can't boot into TWRP.
"fastboot devices" returns the device ID fine, fastboot reboot works.
Tried a factory reset based off another post I found, still in the same boat.
Any ideas?
Click to expand...
Click to collapse
What happened is that you messed up the installation order.
https://forum.xda-developers.com/showpost.php?p=78037053&postcount=685
You only use the zip and rom before the restart and then Gapps and Magisk after.
If nothing else works, then I'd suggest flash stock and start from step one.
The factory reset only, normally, only clears the data partition.
Your bootloader and system partitions are bad as TWRP is written to the bootloader and Gapps installs to the system.
Don't quote me on the bad bootloader though; worst case, you'll want a blankflash and flash stock before starting over again.
[EDIT]
I may have alleviated worst case scenario, read the bottom: https://forum.xda-developers.com/showpost.php?p=78046198&postcount=692

dougo007 said:
What happened is that you messed up the installation order.
https://forum.xda-developers.com/showpost.php?p=78037053&postcount=685
You only use the zip and rom before the restart and then Gapps and Magisk after.
If nothing else works, then I'd suggest flash stock and start from step one.
The factory reset only, normally, only clears the data partition.
Your bootloader and system partitions are bad as TWRP is written to the bootloader and Gapps installs to the system.
Don't quote me on the bad bootloader though; worst case, you'll want a blankflash and flash stock before starting over again.
[EDIT]
I may have alleviated worst case scenario, read the bottom: https://forum.xda-developers.com/showpost.php?p=78046198&postcount=692
Click to expand...
Click to collapse
I definitely got the installation order correct for the fresh install. I used the built-in updater in lineage to update the OS, so it's entirely possible that there's a slot issue related to that...
The firmware link at the bottom of your post was the very first thing I did.
A blankflash file I found that I think should be recent enough for my device just shows <waiting for device>. I ran ADB and it shows the device as connected, so I don't think it's a driver issue. I know nada about blankflash, though.
Researching now. Thanks for the help.

Horror Business said:
I definitely got the installation order correct for the fresh install. I used the built-in updater in lineage to update the OS, so it's entirely possible that there's a slot issue related to that...
The firmware link at the bottom of your post was the very first thing I did.
A blankflash file I found that I think should be recent enough for my device just shows <waiting for device>. I ran ADB and it shows the device as connected, so I don't think it's a driver issue. I know nada about blankflash, though.
Researching now. Thanks for the help.
Click to expand...
Click to collapse
I have a whole package I created with links to different XDA threads on this device, but I don't have it with me at the moment.
You will definitely need to know what variant you're using.
I found one for XT1900-1 and one for XT1900-7.
There is a phone button combo you'll need to use and good timing.

dougo007 said:
I have a whole package I created with links to different XDA threads on this device, but I don't have it with me at the moment.
You will definitely need to know what variant you're using.
I found one for XT1900-1 and one for XT1900-7.
There is a phone button combo you'll need to use and good timing.
Click to expand...
Click to collapse
I have XT1900-1.
Thanks!

Here is my 'data dump' from my text file on what to do in the worst case scenario; I grabbed and linked what I could together below.
Don't take the words as direct advice from me as I never did this myself before.
--------------------------------------------------------------------------------------------------------
Enter download Mode: Power & Volume - (down) for ten seconds [ or volume +]
blank flash (two different files, not sure which to use)
Generic Instructions:
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Device Instructions:
https://forum.xda-developers.com/moto-x4/help/hard-bricked-how-enter-emergency-t3757472
https://forum.xda-developers.com/showpost.php?p=77847019&postcount=606
https://forum.xda-developers.com/showpost.php?p=77847374&postcount=44
https://www.aryk.tech/2017/09/moto-x4-unbrick-solutions.html
use qualcomm driver first with blank flash
MAY NEED TO ENTER PC INTO TEST MODE:
Make your PC into Test Mode.
Then run “CMD” or “Windows Terminal” as administrator and type:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
(Restart computer)
***When you no longer need it.***
###To deactivate it we will use the following command.###
Bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
Bcdedit.exe -set TESTSIGNING OFF
Once the two commands have been executed, we must restart our computer so that the changes take effect and this mode is deactivated correctly.
If process completed successful then your mobile will restart into bootloader screen and your hard brick problem has been resolved. after that you can reboot into recovery by pressing power and volume down button again if required. Once you are in recovery mode then you can flash correct stock ROM into your mobile.
use manual and brick help to load system partition
ROMS: https://androidfilehost.com/?a=show&w=files&flid=229118

Data upload
There is one more file too big or here mentioned in the PDF.

I don't know which ROM is the best to use but you should use a PAYTON_FI for the XT1900-1

dougo007 said:
Data upload
There is one more file too big or here mentioned in the PDF.
Click to expand...
Click to collapse
Massive, massive thanks, man!
Got me rolling back to being able to flash a stock rom, which is good enough for me on this device!
I'm still guessing that slots jacked something up, but I'm not going to try to replicate the problem at this point, LOL!

One last note.
I noticed that flashing stock doesn't make the device genuine.
It appears that a trick I used to use on my old device works here; rooting with Magisk will mark the phone as certified.
To make sure this is the case, install the manager and if there is one RED and one GREEN; you're good to go on the install.
[EDIT]
Also, you can remove the unlocked bootloader warning with a patched image; I don't know if these two things will conflict though.
[EDIT 2]
I also don't know if either will conflict with OTA updates, assuming they work after you fixed your phone.
You can let me know below if you can provide any useful data.
If you have any other questions, make another post/thread. @Horror_Business

Help with rom

So i flashed The pixelrom for mi8, and so far so good, but now i want to install magisk and twrp is gone, it was replaced with the stock recovery, and now when i try to do the exact same process with xiaomitoolv2 he detects my phone has pixel 4 and doesn't detect, i tried fastboot but it doesn't work either, Im running xubuntu x64
https://i.imgur.com/J9E6QmWl.png
EDIT: AFTER SEEING SOME POSTS HERE ON XDA I MANAGED TO USE XIAOMI MI FLASH TOOL WITH SUCCESS!, I NEEDED A USB HUB AND CONNECT THE PHONE IN FASTBOOT AND THEN APPLY THE STOCK IMAGES!, ANYONE WHO NEEDS HELP THIS SOLUTION CAN WORK ( ALL MY 3 USB PORTS DIDN'T WORK, WITH HUB IT WORKED )

ClaudioG123 said:
So i flashed The pixelrom for mi8, and so far so good, but now i want to install magisk and twrp is gone, it was replaced with the stock recovery, and now when i try to do the exact same process with xiaomitoolv2 he detects my phone has pixel 4 and doesn't detect, i tried fastboot but it doesn't work either, Im running xubuntu x64
https://i.imgur.com/J9E6QmWl.png
Click to expand...
Click to collapse
You do not have fastboot? ( think its more likely that you just can see the fastboot screen, but the phone is likely in fastboot mode. Because it sounds like you flashed a custom splash screen, which is causing your fastboot screen to not come up.
Also It seems that you missed some of the steps outlined in the install instructions for the Pixel rom ( I assume the Pixel 3 Q rom?)
You must install Magisk on that rom, you must use recommended TWRP,
I haven't used Ubuntu for flashing Roms recently so I can't provide solid recent steps on Ubuntu.
So I would suggest using a PC , ( surely you know someone with a PC) Enter fastboot, then you can verify that the phone actually can enter fastboot by checking Device manager, or by verifying that the phone is seen by ADB
If you are unable to access fastboot, you will need to go into EDL mode. Once in EDL
Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
Download dipper_global_images_9.6.27_20190627.0000.00_9.0_global or a newer fastboot rom such as 10 .3..5 But It has to be a fastboot rom and not a Recovery rom
Unpack the rom twice on your desktop
You will be left with a folder and inside you will see batch files and a image folder.
Doubleclick Flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in Recovery mode, fastboot or EDL
Flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
You should then Setup rom
Afterwards install TWRP and root then create a full Twrp backup and save to your PC.
This way you will have a quick solution if you ever need it again in the future.
Enjoy a working phone
Rom Link : https://bigota.d.miui.com/9.6.27/di...27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
Any images fastboot rom will work, you can use the one I listed above or you can use the recent 10.3.5 Stable images rom, just find the link via Google.
I just spent 20 minutes typing this, so be considerate and click thanks or send me a beer if you want.

tsongming said:
You do not have fastboot? ( think its more likely that you just can see the fastboot screen, but the phone is likely in fastboot mode. Because it sounds like you flashed a custom splash screen, which is causing your fastboot screen to not come up.
Also It seems that you missed some of the steps outlined in the install instructions for the Pixel rom ( I assume the Pixel 3 Q rom?)
You must install Magisk on that rom, you must use recommended TWRP,
I haven't used Ubuntu for flashing Roms recently so I can't provide solid recent steps on Ubuntu.
So I would suggest using a PC , ( surely you know someone with a PC) Enter fastboot, then you can verify that the phone actually can enter fastboot by checking Device manager, or by verifying that the phone is seen by ADB
If you are unable to access fastboot, you will need to go into EDL mode. Once in EDL
Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
Download dipper_global_images_9.6.27_20190627.0000.00_9.0_global or a newer fastboot rom such as 10 .3..5 But It has to be a fastboot rom and not a Recovery rom
Unpack the rom twice on your desktop
You will be left with a folder and inside you will see batch files and a image folder.
Doubleclick Flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in Recovery mode, fastboot or EDL
Flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
You should then Setup rom
Afterwards install TWRP and root then create a full Twrp backup and save to your PC.
This way you will have a quick solution if you ever need it again in the future.
Enjoy a working phone
Rom Link : https://bigota.d.miui.com/9.6.27/di...27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
Any images fastboot rom will work, you can use the one I listed above or you can use the recent 10.3.5 Stable images rom, just find the link via Google.
I just spent 20 minutes typing this, so be considerate and click thanks or send me a beer if you want.
Click to expand...
Click to collapse
Tried that but this happens in the batch file, also it goes to the fastboot screen where it appears fastboot and the figure, but when i press the batch he leaves that screen and goes to black screen with on top saying press to restart or shutdown, and that error occurs on the batch, even if the phone isn't conected it gets me that error

ClaudioG123 said:
Tried that but this happens in the batch file, also it goes to the fastboot screen where it appears fastboot and the figure, but when i press the batch he leaves that screen and goes to black screen with on top saying press to restart or shutdown, and that error occurs on the batch, even if the phone isn't conected it gets me that error
Click to expand...
Click to collapse
And also I only went Linux because on Windows the phone was getting detected but wasn't working, and Linux was detecting and working with xiaomitoolv2
I will try on Linux to see If the error persists, but that error can he there because the phone, the brand, model and codename are the same has the pixel 4

ClaudioG123 said:
And also I only went Linux because on Windows the phone was getting detected but wasn't working, and Linux was detecting and working with xiaomitoolv2
I will try on Linux to see If the error persists, but that error can he there because the phone, the brand, model and codename are the same has the pixel 4
Click to expand...
Click to collapse
If you are using linux and successful rebooted the phone into fastboot mode, just try to replace the recovery.
Download the recent version of TWRP for your phone and move it to the fastboot directory then open a shell in that directory.
Type in your shell: "sudo fastboot flash recovery yourtwrpimage.img"
Now, unplug the USB and you MUST reboot and immediately hold down the upvolume and power until the TWRP boots. If you miss it, the system will replace the stock recovery image again and you will have to start over.
You can then individually flash the partition images of your choice or ROM ZIP file, but you will still have to flash the full fastboot images after you get the phone recognizing as an mi8.

Agimax said:
If you are using linux and successful rebooted the phone into fastboot mode, just try to replace the recovery.
Download the recent version of TWRP for your phone and move it to the fastboot directory then open a shell in that directory.
Type in your shell: "sudo fastboot flash recovery yourtwrpimage.img"
Now, unplug the USB and you MUST reboot and immediately hold down the upvolume and power until the TWRP boots. If you miss it, the system will replace the stock recovery image again and you will have to start over.
You can then individually flash the partition images of your choice or ROM ZIP file, but you will still have to flash the full fastboot images after you get the phone recognizing as an mi8.
Click to expand...
Click to collapse
Will try soon as im home, if i get waiting for device should i wait?

Agimax said:
If you are using linux and successful rebooted the phone into fastboot mode, just try to replace the recovery.
Download the recent version of TWRP for your phone and move it to the fastboot directory then open a shell in that directory.
Type in your shell: "sudo fastboot flash recovery yourtwrpimage.img"
Now, unplug the USB and you MUST reboot and immediately hold down the upvolume and power until the TWRP boots. If you miss it, the system will replace the stock recovery image again and you will have to start over.
You can then individually flash the partition images of your choice or ROM ZIP file, but you will still have to flash the full fastboot images after you get the phone recognizing as an mi8.
Click to expand...
Click to collapse
I can try to see if he works with xiaomitoolv2, and will try what you said and post here

tsongming said:
you do not have fastboot? ( think its more likely that you just can see the fastboot screen, but the phone is likely in fastboot mode. Because it sounds like you flashed a custom splash screen, which is causing your fastboot screen to not come up.
Also it seems that you missed some of the steps outlined in the install instructions for the pixel rom ( i assume the pixel 3 q rom?)
you must install magisk on that rom, you must use recommended twrp,
i haven't used ubuntu for flashing roms recently so i can't provide solid recent steps on ubuntu.
so i would suggest using a pc , ( surely you know someone with a pc) enter fastboot, then you can verify that the phone actually can enter fastboot by checking device manager, or by verifying that the phone is seen by adb
if you are unable to access fastboot, you will need to go into edl mode. Once in edl
download fastboot dipper images rom, and use flashall.bat method to restore the phone.
download dipper_global_images_9.6.27_20190627.0000.00_9.0_global or a newer fastboot rom such as 10 .3..5 but it has to be a fastboot rom and not a recovery rom
unpack the rom twice on your desktop
you will be left with a folder and inside you will see batch files and a image folder.
doubleclick flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in recovery mode, fastboot or edl
flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
you should then setup rom
afterwards install twrp and root then create a full twrp backup and save to your pc.
this way you will have a quick solution if you ever need it again in the future.
enjoy a working phone
rom link : https://bigota.d.miui.com/9.6.27/di...27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
any images fastboot rom will work, you can use the one i listed above or you can use the recent 10.3.5 stable images rom, just find the link via google.
I just spent 20 minutes typing this, so be considerate and click thanks or send me a beer if you want.
Click to expand...
Click to collapse
i used this solution but i go i connected the phone in a usb hub!

ClaudioG123 said:
i used this solution but i go i connected the phone in a usb hub!
Click to expand...
Click to collapse
Did you try as @Agimax suggested? You have shown that the device is seen in fastboot. If you can push recovery to the phone then the issue will be easily resolved.
You should also be able to use this modified MiFlash : https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847
( Maybe you are already using this?)
I have also had the issue in the past where fastboot was available but attempting to push recovery failed. In some cases trying alternate versions of TWRP would work, and for me fastboot flashall will usually always work.
Another option is to push the images from the images folder individually. if one fails go to the next and then come back and retry the images that failed the first time. (Edit: I just reread Agimax post above, he mentioned this already.)
If you are in EDL mode you should be able to restore the stock images without receiving the error message You can enter EDL without opening the device, either by using a EDL deep flash cable or https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Another option ( requires a PC) is QPST, which I have used a lot in the past, its quick and easy to use. : https://miui.blog/any-devices/qualcomm-qpst-tool/

tsongming said:
Did you try as @Agimax suggested? You have shown that the device is seen in fastboot. If you can push recovery to the phone then the issue will be easily resolved.
You should also be able to use this modified MiFlash : https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847
( Maybe you are already using this?)
I have also had the issue in the past where fastboot was available but attempting to push recovery failed. In some cases trying alternate versions of TWRP would work, and for me fastboot flashall will usually always work.
Another option is to push the images from the images folder individually. if one fails go to the next and then come back and retry the images that failed the first time. (Edit: I just reread Agimax post above, he mentioned this already.)
If you are in EDL mode you should be able to restore the stock images without receiving the error message You can enter EDL without opening the device, either by using a EDL deep flash cable or https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Another option ( requires a PC) is QPST, which I have used a lot in the past, its quick and easy to use. : https://miui.blog/any-devices/qualcomm-qpst-tool/
Click to expand...
Click to collapse
Your solution worked with the phone in fastboot, but i had to try a usb hub, that's all, has for roms, experienced both of pixelrom3 and havoc and didn't conviced me enough, i find miui 11 of xiaomi.eu more good looking and doesn't have bugs, and thank you, you are a lifesafer, if it wasn't for that i would have never flashed stock rom back

tsongming said:
Did you try as @Agimax suggested? You have shown that the device is seen in fastboot. If you can push recovery to the phone then the issue will be easily resolved.
You should also be able to use this modified MiFlash : https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847
( Maybe you are already using this?)
I have also had the issue in the past where fastboot was available but attempting to push recovery failed. In some cases trying alternate versions of TWRP would work, and for me fastboot flashall will usually always work.
Another option is to push the images from the images folder individually. if one fails go to the next and then come back and retry the images that failed the first time. (Edit: I just reread Agimax post above, he mentioned this already.)
If you are in EDL mode you should be able to restore the stock images without receiving the error message You can enter EDL without opening the device, either by using a EDL deep flash cable or https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Another option ( requires a PC) is QPST, which I have used a lot in the past, its quick and easy to use. : https://miui.blog/any-devices/qualcomm-qpst-tool/
Click to expand...
Click to collapse
After i put the usb usb on laptop both solutions worked, and i was in windows and not linux, in linux works also

ClaudioG123 said:
After i put the usb usb on laptop both solutions worked, and i was in windows and not linux, in linux works also
Click to expand...
Click to collapse
That's great sorry for being late to respond, I haven't had time to check XDA for a couple of days. But I an really glad that you got everything sorted out.
BTW, I agree about Xiaomi.EU, and I also find it to be the most stable...by far. Plus, it's obviously the most up to date. No doubt that AOSP roms are fun, but also very unpredictable. I keep Xaiomi.EU on mi daily driver, ( the Mi8) and I tinker around with AOSP roms on my old phones.
Take care

tsongming said:
That's great sorry for being late to respond, I haven't had time to check XDA for a couple of days. But I an really glad that you got everything sorted out.
BTW, I agree about Xiaomi.EU, and I also find it to be the most stable...by far. Plus, it's obviously the most up to date. No doubt that AOSP roms are fun, but also very unpredictable. I keep Xaiomi.EU on mi daily driver, ( the Mi8) and I tinker around with AOSP roms on my old phones.
Take care
Click to expand...
Click to collapse
Currently on miui 11 on mine, and it's perfect, like the design vs miui 10 from official, it's fast and stable, only thing is that some apps that use gps are sometimes bugged, and does your mi8 drain battery a bit faster than in miui 10?

ClaudioG123 said:
Currently on miui 11 on mine, and it's perfect, like the design vs miui 10 from official, it's fast and stable, only thing is that some apps that use gps are sometimes bugged, and does your mi8 drain battery a bit faster than in miui 10?
Click to expand...
Click to collapse
Yeah, I don't think that they have that part completely sorted yet. I definitely had better battery life on the last Xiaomi.EU Pie rom. But its not too bad with this latest version. Checking Gsam battery manager just now my average is 7HR's 6 Min SOT Whereas with the Miui 11 Xiaomi EU Chinese Stable rom, I averages about 10 hrs SOT ( If I remember correctly)
Personally, I am not having any app issues.
Usually if I had a permissions issues after restoring apps, I would just uninstall and reinstall the app and that will usually take care of any issues. Another thing to check , is t make sure that any problem apps have the right permissions enabled.

tsongming said:
Yeah, I don't think that they have that part completely sorted yet. I definitely had better battery life on the last Xiaomi.EU Pie rom. But its not too bad with this latest version. Checking Gsam battery manager just now my average is 7HR's 6 Min SOT Whereas with the Miui 11 Xiaomi EU Chinese Stable rom, I averages about 10 hrs SOT ( If I remember correctly)
Personally, I am not having any app issues.
Usually if I had a permissions issues after restoring apps, I would just uninstall and reinstall the app and that will usually take care of any issues. Another thing to check , is t make sure that any problem apps have the right permissions enabled.
Click to expand...
Click to collapse
Im using Europe instead of china, does it change? Read changelog and didnt figured it out
This app works on android 9 but on 10 it bugs didn't had the issue back with miui 10 stock
Liked the fact that they boosted sound

ClaudioG123 said:
Im using Europe instead of china, does it change? Read changelog and didnt figured it out
This app works on android 9 but on 10 it bugs didn't had+ the issue back with miui 10 stock
Liked the fact that they boosted sound
Click to expand...
Click to collapse
I am also using the Xiaomi EU rom because I want to use Android 10, and as I mentioned for me the battery life is fine. So I wouldn't recommend changing.
If you having app issues, see if there is a beta version of that app.

tsongming said:
I am also using the Xiaomi EU rom because I want to use Android 10, and as I mentioned for me the battery life is fine. So I wouldn't recommend changing.
If you having app issues, see if there is a beta version of that app.
Click to expand...
Click to collapse
Mate, you are using MIUI 10 eu latest beta pie update or stable? I curiuous your rom coz you saying you are taking good battery life.
Sorry for my bad English.

harnkalkn said:
Mate, you are using MIUI 10 eu latest beta pie update or stable? I curiuous your rom coz you saying you are taking good battery life.
Sorry for my bad English.
Click to expand...
Click to collapse
I am using the weekly Xiaomi.Eu beta rom, averaging 7 hours and 15 minutes SOT and no real issues.

mi 8 bricked
i bricked mi 8 when i try to re-lock bootloader. now i only received a main menu and red massage "this miui version can't be installed on this device". anyone can help me?

Question How i got my CE 5G working after a soft brick. And the problems i came up against.

Before i start many thanks to Aman - thanks for being extremely patient and helping out no end.!!
So, first and foremost i followed the instructions in the rooting guide and for me it went wrong. I wasnt sure i was doing it correctly but like following a **** satnav i blindly carried on and soft bricked it.....not to worry im all good again - this was my 3 week journey. I thought it would be good to put down my experience as while ive rooted a lot of phones in my life at the same time i dont do them that often so i always find that im always... "learning again".
Followed the instructions on the other thread and downloaded the image, extracted it using the payload dumper - that itself was a pain in the arse as i couldnt get the linked one running - spent a good few afternoons, gave up and found one called "payload dumper 2021" which gave me a convenient exe to run and that worked fine (hurdle one over) - im trying to find the link to it so i can post it here but i cant...if i can ill update this thread...
I think this is where i started going wrong...i patched the boot.img from the downloaded os and flashed my phone. I got a black screen after booting (looking like it was dead) but if i held down the power button the reboot window showed up. Tried a wipe of cache etc etc but it didnt change.....not sure what i did after that as it was 3 weeks ago but ended up with a softbricked phone - all it would do on boot was crash dump. i had fastboot and recovery.
I tried the MSM tool on 3 different bits of hardware and none worked. Always hit the Firehose timeout error at 16seconds.
I also tried manually flashing the images but hit an error when i tried to reflash the product and system images....filesystem error.
Cue Enhanced Fastboot
Release v1.3.0 · libxzr/FastbootEnhance
New icon Add support for opening zips with payload.bin inside Add support for showing progress on taskbar
github.com
Put the phone into fastbootd and away you go. I actually had a couple of these phones to do so used the Oxygen updater to get the latest version of the os (i got 11.0.11.11EB13BA) - extracted that, patched it with magisk so it was ready to go.
Once i had reflashed the phone - using the enhanced fastboot Aman told me to delete the "cow" paritions first - this was where i was hitting the error manually flashing. Browse to the payload.bin file and it did the rest. Phone rebooted and it was alive again. Back into fastboot to install the patched boot,img (this was taken from 11.0.11.11EB13BA). Once rebooted i installed magisk by copying it over to the phone first and then a straight install.
Reboot the phone again, once booted with usb debugging on i then launched "adb shell" then type "su" - the request for root appeared on the phone and im done,
Not sure what the legalities of sharing the above OS image and the patched boot.img that goes with it are.
If anyone gets stuck ill try my best to help as others have helped me.

ComfySofa said:
Before i start many thanks to Aman - thanks for being extremely patient and helping out no end.!!
So, first and foremost i followed the instructions in the rooting guide and for me it went wrong. I wasnt sure i was doing it correctly but like following a **** satnav i blindly carried on and soft bricked it.....not to worry im all good again - this was my 3 week journey. I thought it would be good to put down my experience as while ive rooted a lot of phones in my life at the same time i dont do them that often so i always find that im always... "learning again".
Followed the instructions on the other thread and downloaded the image, extracted it using the payload dumper - that itself was a pain in the arse as i couldnt get the linked one running - spent a good few afternoons, gave up and found one called "payload dumper 2021" which gave me a convenient exe to run and that worked fine (hurdle one over) - im trying to find the link to it so i can post it here but i cant...if i can ill update this thread...
I think this is where i started going wrong...i patched the boot.img from the downloaded os and flashed my phone. I got a black screen after booting (looking like it was dead) but if i held down the power button the reboot window showed up. Tried a wipe of cache etc etc but it didnt change.....not sure what i did after that as it was 3 weeks ago but ended up with a softbricked phone - all it would do on boot was crash dump. i had fastboot and recovery.
I tried the MSM tool on 3 different bits of hardware and none worked. Always hit the Firehose timeout error at 16seconds.
I also tried manually flashing the images but hit an error when i tried to reflash the product and system images....filesystem error.
Cue Enhanced Fastboot
Release v1.3.0 · libxzr/FastbootEnhance
New icon Add support for opening zips with payload.bin inside Add support for showing progress on taskbar
github.com
Put the phone into fastbootd and away you go. I actually had a couple of these phones to do so used the Oxygen updater to get the latest version of the os (i got 11.0.11.11EB13BA) - extracted that, patched it with magisk so it was ready to go.
Once i had reflashed the phone - using the enhanced fastboot Aman told me to delete the "cow" paritions first - this was where i was hitting the error manually flashing. Browse to the payload.bin file and it did the rest. Phone rebooted and it was alive again. Back into fastboot to install the patched boot,img (this was taken from 11.0.11.11EB13BA). Once rebooted i installed magisk by copying it over to the phone first and then a straight install.
Reboot the phone again, once booted with usb debugging on i then launched "adb shell" then type "su" - the request for root appeared on the phone and im done,
Not sure what the legalities of sharing the above OS image and the patched boot.img that goes with it are.
If anyone gets stuck ill try my best to help as others have helped me.
Click to expand...
Click to collapse
Told ya, that the people in the telegram group could may help you out!
Happy to hear that everything is working again

Yep - many thanks - just trying to help spread the knowledge a bit.!

ComfySofa said:
Before i start many thanks to Aman - thanks for being extremely patient and helping out no end.!!
...
Click to expand...
Click to collapse
ComfySofa said:
..
If anyone gets stuck ill try my best to help as others have helped me.
Click to expand...
Click to collapse
Hi, seems like I have managed to brick my phone as well that was received this morning only and I proceeded to root it. Tried the MSM Tool, but that doesn't seem to be detecting the OnePlus Nord CE 5g, device manager showed my phone as QUSB_BULK_CID:... which wasn't correct so installed the QualComm USB Drivers from here after which the phone was detected as QDLoader9008..However, that doesn't seem to have helped as well as there was absolutely nothing happening in the MSM Tool
Am wondering what can be done to revive the phone?

sam_htc_touch said:
Hi, seems like I have managed to brick my phone as well that was received this morning only and I proceeded to root it. Tried the MSM Tool, but that doesn't seem to be detecting the OnePlus Nord CE 5g, device manager showed my phone as QUSB_BULK_CID:... which wasn't correct so installed the QualComm USB Drivers from here after which the phone was detected as QDLoader9008..However, that doesn't seem to have helped as well as there was absolutely nothing happening in the MSM Tool
Am wondering what can be done to revive the phone?
Click to expand...
Click to collapse
Well, lets try.....first and foremost you need a rom and you need the enhanced fastboot software.....ill see if i can find a link...

Try this version....
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
Then, get it into fastbootd mode....

Once youre in fastbootd mode - can be fiddly....get the latest plaform tools download and type in fastboot reboot fastboot while your in standard fastboot mode (with the green "start" at the top left)
youll know when your in fastbootd as it looks like recovery but says fastbootd in the middle of the screen....launch the fastboot enhanced and the click on the load payload.bin file from the extracted .zip file of the rom you downloaded - i got 11.0.11.11 using the oxygen downloader app but if youre phone is bricked im not sure than can be loaded up on another phone....

ComfySofa said:
Well, lets try.....first and foremost you need a rom and you need the enhanced fastboot software.....ill see if i can find a link...
Click to expand...
Click to collapse
Thanks for the super quick response
I had already tried the Fastboot Enhance v1.3.0, but that doesn't seem to detect my phone either. Wondering if I have lost ADB etc and hence the phone is not being detected anymore? And that is the first thing that needs to be fixed somehow?

Youre more than welcome....its needs to be in fastbootd mode for the enhanced fastboot to do its work....what have you got at the moment onscreen?

ComfySofa said:
Youre more than welcome....its needs to be in fastbootd mode for the enhanced fastboot to do its work....what have you got at the moment onscreen?
Click to expand...
Click to collapse
It's completely black, I was earlier able to get into Recovery Mode, but that's no longer happening as well - Did manage to somehow come into Safe Mode (shown at the bottom left corner) earlier but at the moment its completely black.

ok. if you hold the power and up volume down without the usb cable in to hard reset it then when it vibrates the once hold the down volume button down (hopefully that should get it into standard fastboot mode)

ComfySofa said:
ok. if you hold the power and up volume down without the usb cable in to hard reset it then when it vibrates the once hold the down volume button down (hopefully that should get it into standard fastboot mode)
Click to expand...
Click to collapse
somehow not able to get into fastboot mode anymore, it shows the standard warning about bootloader being unlocked and then proceeds to attempt to boot with red dot in between and smaller white circles revolving around it...this goes into an endless loop - the only way to come out of that is by long pressing the power button which brings up the option to either "power off" or "restart"
and the story repeats :-(

Well, if its any consolation yours is in better shape than mine was....youve still got a sort of working os.....! mine just went to crash dump mode....99% sure youve still got fastboot its just gonna be a bit of a faff getting into that mode....definately the way youre doing the key pressing/holding...