Database Users

been working 2 days many hours to resolve PLEASE HELP!

"Power On This Pops Up As A Black Screen"
ap fastboot Flash Mode (s)
10.9B(*) (sha-61146a2, 2014-07-29 2:30:05)
eMMC Info: Size 8GB
Device is LOCKED, Status Code:0
Battery OK
Connect USB
Data Cable
Fastboot Reason: Sticky bit factory_fastboot
------------------------------------------------------------------------------------------------------------------
The Version Is 4.4.2 of the operating system
when i press the power button this happens, i can however hold the power button and both volume buttons to get into the operating system, by loading normally, I need to fix this issue so i can take another swing at trying to mod this razr-m xt907
the previous issue, before i made it to this issue was
Fastboot Reason: fastboot failure this happens if you mess up and try to towel root from your phone as in download the file onto your phone and then run the file from your phone, so any user out there trying to root their phone, that is not the way to go. Also I Am Dubbing This The Screen of Black Death!
As per Rooting the Phone, I tried Using "motofail2go" I press enter the App communicates with the phone then the dameon Starts, after that nothing at all happens i let it sit for 15-20 minutes and nothing happens
please help me figure this out, my goal is to put cmod on my phone, it is locked and unrooted at the moment, it has full charge and something has went wrong taking the above information walk me through it please, im on my knees begging. Ill even donate some money on the first of the month if we can get it working.

just_guy said:
"Power On This Pops Up As A Black Screen"
ap fastboot Flash Mode (s)
10.9B(*) (sha-61146a2, 2014-07-29 2:30:05)
eMMC Info: Size 8GB
Device is LOCKED, Status Code:0
Battery OK
Connect USB
Data Cable
Fastboot Reason: Sticky bit factory_fastboot
------------------------------------------------------------------------------------------------------------------
The Version Is 4.4.2 of the operating system
when i press the power button this happens, i can however hold the power button and both volume buttons to get into the operating system, by loading normally, I need to fix this issue so i can take another swing at trying to mod this razr-m xt907
the previous issue, before i made it to this issue was
Fastboot Reason: fastboot failure this happens if you mess up and try to towel root from your phone as in download the file onto your phone and then run the file from your phone, so any user out there trying to root their phone, that is not the way to go. Also I Am Dubbing This The Screen of Black Death!
As per Rooting the Phone, I tried Using "motofail2go" I press enter the App communicates with the phone then the dameon Starts, after that nothing at all happens i let it sit for 15-20 minutes and nothing happens
please help me figure this out, my goal is to put cmod on my phone, it is locked and unrooted at the moment, it has full charge and something has went wrong taking the above information walk me through it please, im on my knees begging. Ill even donate some money on the first of the month if we can get it working.
Click to expand...
Click to collapse
You can fix the sticky bit issue pretty easily through another fastboot command. The command is: fastboot oem fb_mode_clear - Check out this thread for all the details. http://forum.xda-developers.com/showpost.php?p=41706009&postcount=2
Alternatively, a full reflash of the firmware generally fixes the issue.
Sent from my Moto X 2014 Pure Edition using Tapatalk

xKroniK13x said:
You can fix the sticky bit issue pretty easily through another fastboot command. The command is: fastboot oem fb_mode_clear - Check out this thread for all the details. http://forum.xda-developers.com/showpost.php?p=41706009&postcount=2
Alternatively, a full reflash of the firmware generally fixes the issue.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Click to expand...
Click to collapse
I know its been a long time but um here is a belated thank you! I did in fact solve the issue thanks to xda and you, so truly thank you

How to boot LG Leon into recovery?

I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.

Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.

You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.

If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it

You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha

kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.

kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.

duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?

kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.

]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1

pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1

This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.

Phone dead after try to Reboot to Recovery from Power Menu - please help :(

Hello,
I got a Moto G4 with the LineageOS version 7.1.2 from the end of May.
I wanted to reboot to recovery, from the power menu options. Never thought that something like this may happen.
The only sign of life is the blinking LED while being connected to AC or USB port of PC (it goes fast on and off).
The key combinations don't do anything (even if I hold for 30 seconds). So no possibility to force restart? Access fastboot? Boot menu? Anything? :crying:
Never had a weird issue like that and don't find anything on google about it.
Any ideas? It is the only phone I got, would be soooo bad if it is somehow dead now.

Try holding the power button down for 2-3 minutes, this may invoke a hard restart which may break your device out of whatever state it's in. Then you may be able to reboot as normal.
What TWRP recovery do you have?

Thank you so much, after 2 minutes the phone restarted. I always thought the time needed was 20 seconds.
You saveed me <3
What might be interesting, my phone still consumed battery while it was off, went from 100 to 14%

I also had the same issue yesterday but I did a hell lot of things to flash bootloader again
I first searched xda Moto forums ,there I found 1 thread where in I had to blank flash some file using Qualcomm drivers installed in pc....
Then I was able to boot to bootloader...this was a different bootloader I had seen...but I cud see bootloader version B.***
In bootloader the recovery did not boot
'Your phone did not boot' was d msg
Then I tried flashing fastboot roms of Moto g4 plus
1st I tried mpj 6.0
2nd npj 14.11 7.0
In both above cases partition flash gpt.bin failed...preflash validation failed....!
So I tried fastboot flash recovery twrp.img
Then also it failed ......unable to initialize partition table...!
I loses hopes and worried that I need to go to service center
Then I saw that the same rom which was there was to be flashed
Then I fastboot flash latest rom npsj14.4...
This time I was able to flash partition gpt.bin
Then I successfully flashed bootloader.img ,
Then when flashed boot.img again I faced ' preflash validation failures...'!
Now I saw mobile bootloader was like official Moto bootloader
Finally I successfully flashed twrp.img
This time no error occurred because gpt.bin and bootloader of npsj14.4 worked
From twrp I restored the backup...and life of my phone came back
If I had seen this method earlier only it would have saved 2-3gb data for dwnlding all version fastboot roms and time,the worry I felt...so disgusting......so I feel that reading others problems in forum is very useful for us in future....
ty @ECHO u saved one Junior members problem otherwise had to suffer like me??

Mega Bricked 7X - Calling out all Senior/Pros for HELP!!

HI, I will get right to the point. My phone is Honor 7x (BND-AL10C675 INDIAN) I screwed it up.
Now, the fastboot or recovery or E recovery nothing works!!
There is only one screen which keeps coming in a loop rebooting with a vibration
It says " ERROR MODE"
ATTENTION!
PLEASE UPDATE SYSTEM AGAIN
ERROR! FUNC NO : 8 (HIFI IMAGE)
ERROR NO : 1 (SECURITY VERIFY FAILED)
It keeps rebooting and the phone doesn't even turn off. I tried the download mode (Volume UP & Down Power button, SAME SCREEN comes up)
Let me know if you want me to write a detailed version of how I got here or ask any specific questions.
Now, all I need is at least FASTBOOT so I can do something about it. Is there anyone who can help? I hope SOME PRO OR A GEEK is able to solve this issue magically. I just can't tell you what I'm going through.
UPDATE:
As Christo31 requested and maybe it's useful for other people to help me out. Here is what I did. It's a real long story!!
I have Honor 7x (BND-AL10C675 INDIAN) I had unlocked bootloader and twrp and I was on emui 8 beta which I flashed manually using one of the tutorials here on the forum. One day, I decided to get back to stock as I was stuck in emui 8 beta and no OTA updates so I downloaded the emui 8 stable rom from firmware finder and put it in sd card "dload" folder. Now, for this method to work, we need to relock bootloader and flash stock recovery which I did and it completely wiped everything out.
Now, the "dload" method fails at 5% every time. I tried different roms for this very model but no it doesn't work. (Also, my build no. was stuck at B141 for a long time no matter what rom I changed : Yes, this is stupid, I should have fixed it first) Maybe that's why the "dload" method doesn't work.
So, in this forum I saw some with similar issue but somewhat different " Frp locked & bootloader unlocked" and I was told that the DC phoenix software might fix this and I bought some credits and used the software. Here's what I discovered
My observations with the software:
* I put the phone in fastboot and downloaded the update.app full Ota (same one emui stable) and tried to flash. The software flash well ok as it says "the software is written" but the phone doesn't boot and goes directly into the recovery mode and again the bootloader and frp are locked.
*Here, I noticed that it shows something like "opening backdoor" and then the Bootloader status goes to red and says "UNLOCKED" it means it was definitely doing something so the next I repeated the same process but as soon as the phone was "UNLOCKED", I pulled the usb cable out and I kept my command ready and tried "fastboot flash recovery_ramdisk recovery.img" and guess what it flashed that twrp file and I could see in the command line that it went "okay" so I immediately booted to recovery but again the stock recovery comes up. Also, I tried system.img also it flashes fine but phone doesn't boot. Same recovery.
REMEMBER: THE ABOVE STEPS MAY WORK FOR PEOPLE WHO HAVE UNLOCKED BOOTLOADER BUT FRP LOCKED. IN MY CASE BOTH ARE LOCKED SO THAT'S THE DIFFERENCE.
* I tried another update.app I guess it's BNDL22.ZIP or something and this time the software was trying to flash in "upgrade mode" and somehow the recovery was broke. There was some "ERROR MODE" basically the recovery was broke. I didn't care much. Although flashing another update.app would have fixed it.
* The next step I tried after a lot of trial & error for about 1.5 days. This time I did the same when the bootloader was unlocked, I pulled the cable and tried the command "fastboot oem unlock unlock code" ( I should have got this idea before, I mean it's a mess guys, I didn't sleep for too long) and I was shocked to see that it showed the options "Unlocked bootloader yes or no" and I clicked "yes" and I jumped hoping that it's over but... I ended up with 'ERROR MODE' which I described above.
* I feel, because the recovery was broken, it ended up in error mode. Just imagine if my recovery was fine and then I tried this command then it would have erased everything and maybe I might have been presented with fastboot screen with both "frp & bootloader Unlcock" or at least 'bootloader unlock" in either way, I could have flashed a 'system.img' and get into settings and BEATH THE HELL OUT OF THAT "ENABLE OEM UNLOCK' in settings. The rest you know.
I wrote this not just because someone might help me but because a lot of posts on this forum really helped me a lot and posts like these can help a lot of people down the road.
Now, my phone is still in the same loop. Reboot, Honor logo, Error mode...REPEAT
I heard that once the phone drains down completely, we may get back fastboot. Fingers crossed. Sadly, I have Mac so I borrowed windows laptop for this purpose from a friend. This is the last day and I guess I'm going to put it on sale and sell it as a scrap or something for display and stuff.
How much does motherboard cost? anyone any ideas? if it's below 4K or about 80$ then I might go for the repair if nothing works!!
I'm going to update on this very soon. Le'ts hope for a miracle. Either way my HONOR 7X IS A LEGEND.
UPDATE :
After waiting for hours, my phone got discharged and I curiously plugged in the phone pressing "volume down" button OR power + volume and all other types of combinations but the phone just goes to the same "ERROR MODE' and keeps going in the same loop.
So, I really hate Huawei for not providing stock firmware or some type of recovery for people like me to get back to stock. For example : Xiaomi has that fastboot ROMS which you can easily flash in EDL mode no matter what happens to you and of course some other ways to recovery the bricked phones.
The Huawei E recovery?? What the **** is it? Does it ever work? It's some kind of a joke. The hisuite is again **** It says 'My model is not supported" and it only showed me two very older and ancient models that are supported for recovery.
I'm not expecting warranty but at least they should give the service for the customer. Did I tell you that this phone was in Service centre for three days when it had FASTBOOT, RECOVERY, E RECOVERY working. They could n't fix it in 3 days so I rushed them to get my phone back hoping that I would recover it with the above method.
Now, I got the Redmi Note 5 Pro and my 7X is a dead brick and I'll try selling it as scrap for display etc...
Finally, I really love the XDA forums and the friendly members who are very helping and so empathetic. Thanks guys, you are the best
I'm not leaving. I'll see you on the other side. I mean, the Redmi Note 5 pro development. Keep hustling

You need to tell us what you did exactly first for any help

Thetpcguy said:
ERROR! FUNC NO : 8 (HIFI IMAGE)
ERROR NO : 1 (SECURITY VERIFY FAILED)
Click to expand...
Click to collapse
when you are in this situation
- Keep press "volume down" + "power button" for about 10 seconds, the phone will reboot
- When the phone reboot, release the "power button" but keep "volume down" and in the same time plug the micro usb cable ( you have to be ready and quick )
the phone will boot in FASTBOOT&RESCUE MODE ( hope you have unlocked bootloader and frp unlocked )

azerty11 said:
when you are in this situation
- Keep press "volume down" + "power button" for about 10 seconds, the phone will reboot
- When the phone reboot, release the "power button" but keep "volume down" and in the same time plug the micro usb cable ( you have to be ready and quick )
the phone will boot in FASTBOOT&RESCUE MODE ( hope you have unlocked bootloader and frp unlocked )
Click to expand...
Click to collapse
Hi, thanks for your help but the phone doesn't turn off. it just keeps rebooting and there is honor logo and then error mode and then phone reboots and the same cycle. I tried what you said also with other possible things but I guess I need to let the battery drain out completely as some people said it worked for them. It's almost 9 hours and it's still not drained (it was on full charge) anyway Fingers Crossed!!

christo31 said:
You need to tell us what you did exactly first for any help
Click to expand...
Click to collapse
HI, I Updated the post in full details. I hope my phone is rescued.

Let the battery drain, and then try to get into fastboot using key combinations. Let me know if you can do this, from there on you can proceed normally.

vaasu_g_wills said:
Let the battery drain, and then try to get into fastboot using key combinations. Let me know if you can do this, from there on you can proceed normally.
Click to expand...
Click to collapse
It didn't work out. It only boots in error mode and keeps going in a loop.

Thetpcguy said:
It didn't work out. It only boots in error mode and keeps going in a loop.
Click to expand...
Click to collapse
Did you try huawie suite system recovery??

vaasu_g_wills said:
Did you try huawie suite system recovery??
Click to expand...
Click to collapse
I never heard of it I'm googling it now and please throw some light on this but strangely your message got my hopes up.
UPDATE: Oh, I guess you are talking about Huawei Hisuite. I did try that and it didn't work and I included that in my post above as well. I still have my phone with me completely discharged.

Thetpcguy said:
I never heard of it I'm googling it now and please throw some light on this but strangely your message got my hopes up.
UPDATE: Oh, I guess you are talking about Huawei Hisuite. I did try that and it didn't work and I included that in my post above as well. I still have my phone with me completely discharged.
Click to expand...
Click to collapse
and with phone , off, totaly discharged, holding volume down, and plugging in the usb cable , just gives you same error mode?

---------- Post added at 10:59 PM ---------- Previous post was at 10:27 PM ----------
[/COLOR]Follow this steps.
1. Just flash with Dc phoenix
3 extract two update. App with huwai firmware extractor.
4. Check the log of dc phoix. Check which files are not flashed. By comparing with extracted files You will observe some files are not flashed. (some files are not in log of dc phoinix) Like Vendor.img product.img cust.img etc.. Note down which imgs are not flashed..
5. Now use multitool and go to unbrick option. There will be option of flashing around 5 img. Flash the 5 imgs. You will get this 5 img from extracting Update.app
6.then your phone will be working but not perfectly. Flash TWRP with fastboot.
7. Aftee flashing TWRP flash all other imgs which were not flashed by dc phoenix.
Then boot. Your phone must be good.
And again if you want then re flash with HWOTA tool. Your phone will be running now.

mrmazak said:
and with phone , off, totaly discharged, holding volume down, and plugging in the usb cable , just gives you same error mode?
Click to expand...
Click to collapse
Yes, even after that it give the error mode and goes on the same loop. Honor log, Error Mode, Reboot...REPEATED LOOP
I Already gave up on this phone but only a miracle can save this phone now.

Thetpcguy said:
Yes, even after that it give the error mode and goes on the same loop. Honor log, Error Mode, Reboot...REPEATED LOOP
I Already gave up on this phone but only a miracle can save this phone now.
Click to expand...
Click to collapse
i more question for you. Please . Does the three button combo from power off attempt to show update screen. I know for everyone the dload method is failing at 5%, but still need to know if yours is attempting this or not even try.
There might be dload method that works, according to posts on 4pda.ru

mrmazak said:
i more question for you. Please . Does the three button combo from power off attempt to show update screen. I know for everyone the dload method is failing at 5%, but still need to know if yours is attempting this or not even try.
There might be dload method that works, according to posts on 4pda.ru
Click to expand...
Click to collapse
I tried that also. Power+Volume UP+Volume Down to get into download mode but it just goes into that "ERROR MODE'
Normally, it should but maybe because I broke my stock recovery also and then tried to unlock the bootloader when the frp was locked with the DC phoenix trick (Pulling out the plug) that it's really screwed up beyond all this. Let me know if you want me to post pics or maybe if the clips canoe uploaded here, I will make short clip with what's happening. I guess I need some factory or manufacturer level stuff or I need to replace the motherboard. BTW the local guy told me it costs 8K INR which is around 125-130 USD which I'm not willing to spend. I got Redmi Note 5 Pro and I'll probably never ever buy Huawei phones ever.
ANYONE HERE WHO CAN DONATE THE MOTHERBOARD, PLEASE PM ME:laugh:

bootlooped mate 9 lineageOS at booting

Hi all,
I've installed LineageOS on my mate 9, using their own tutorial, and with a stock recovery.
Everything ran smoothly for a couple of weeks. Today however my phone would not turn the screen on, just minutes after it worked fine. So, I rebooted manually by holding the power button.
Did not work, but instead: my phone is stuck on the 'your device has been unlocked and can't be trusted' + your device is booting now... screen. But it does not boot.
I can't go into the stock recovery mode, using power + volume up.
I can get into fastboot mode, but my pc (which I used to root my phone) does not recognise it using adb, while it did earlier. sometimes a fastboot command (fastboot devices) works and lists a code.
But if I try fastboot flash system and the filename for the lineageOS img, it sends the first package but does not seem to write, writing system 1/4 lasts for ever without anything happening. The phone also stays in the white fastboot screen during this event.
Can someone help me solve this? Is there a solution?

Mate 9
dekraan said:
Hi all,
I've installed LineageOS on my mate 9, using their own tutorial, and with a stock recovery.
Everything ran smoothly for a couple of weeks. Today however my phone would not turn the screen on, just minutes after it worked fine. So, I rebooted manually by holding the power button.
Did not work, but instead: my phone is stuck on the 'your device has been unlocked and can't be trusted' + your device is booting now... screen. But it does not boot.
I can't go into the stock recovery mode, using power + volume up.
I can get into fastboot mode, but my pc (which I used to root my phone) does not recognise it using adb, while it did earlier. sometimes a fastboot command (fastboot devices) works and lists a code.
But if I try fastboot flash system and the filename for the lineageOS img, it sends the first package but does not seem to write, writing system 1/4 lasts for ever without anything happening. The phone also stays in the white fastboot screen during this event.
Can someone help me solve this? Is there a solution?
Click to expand...
Click to collapse
In fastboot mode does it tell you the phone is still unlocked and frp is unlocked?

Newrooter22 said:
In fastboot mode does it tell you the phone is still unlocked and frp is unlocked?
Click to expand...
Click to collapse
Did not try that! It is at a repairshop at the moment, they feel it is a software problem, but I guess mainly because I dropped the word 'custom rom'.
I've got a couple clues that suggest it might be a fried chip: I get Command not allowed errors when trying several fastboot commands, and I also get a remote:flash write failure when I try to flash a ramdisk.img or system.img.
Hope to hear from the shop today or tomorrow, and will update afterwards!

I have this exact issue on my huawei y6 2018, i can access to the emui recovery mode, and have bootloader unlocked.