Database Develop

[Q] Can't boot to recovery or download mode, Bootloader seems to be locked as well.

I have a Samsung SIII mini, Latin version (i8190L) and use it with the Virginity Rom, since the version 8, updating everytime a new one comes out.
Never had a problem whatsoever. I flashed the recently out Virginity V12 with aroma installer just to update. I backed up everything so I could make all of the wipes and then flashed it as new. The thing is that I chose the Honami Xperia Keyboard and I didn't like it because it was working somewhat buggy. So I tried (after just a couple of days) to reboot to recovery, to reflash the rom, just using the traditional S4 keyboard. To my surprise. I couldn't.
I can't boot to recovery, I can't boot to download and the bootloader seems to be locked as well. When finishing the installation and rebooting the device just after v12 was installed, the recovery gave me as a final option if I wanted to disable recovery boot, to which I chose no.
I tried rebooting using the button combination, but everytime I do, it just boots normally, as if I only had held down the power button. I tried also to use the built in reboot menu, which has an option to reboot to recovery or download, and either of them had success.
I don't know what to do, I don't want to be without recovery or download mode, in case i need them. Is this some kind of brick? the device is working perfectly, all of the apps work, and the ROM works fine, so I can fully use my device.
Also, I read on a previous post of a person who couldn't get into recovery but could get into download, he was told to delete the system file "install-recovery.sh" and then flash romracer's recovery via fastboot. I did delete the file, but fastboot did not work for me, it just kept saying "waiting for device" however my phone was connected and USB debbugging active.
Can you please help me?
Also, sorry if my english is bad, not a native speaker, and sorry if I'm too "noobbish" i'm relatively new to this stuff.

Failed downgrade from Nougat to MM bricked my EVA-L09

Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.

i2ectcf said:
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
Click to expand...
Click to collapse
did you wiped data, cache, dalvik?

snapdesign said:
did you wiped data, cache, dalvik?
Click to expand...
Click to collapse
Hi! I'm not sure how to wipe data, cache or dalvik, because when I upgraded to Nougat this apparently removed TWRP.
Also I'm wondering if trying to use srktool to reinstall TWRP for 6.0 might have corrupted my 7.0 phone?
Is there any way to wipe data, cache, and/or dalvik now? Or are there other things I could try to unbrick?

Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow. Here's an outline:
1. Google "Huawei Bricked phone repair guide with DC Phoenix", go to the first result and look at the instructions (I can't post URLs yet).
I used Method 1. But note! The newer versions of DC Phoenix are missing a feature that the instructions make clear you have to use. To get the original version used in their guide, you have to download the latest version of DC Phoenix, open it on your PC, then click "Enter Support Area" which logs you in to a download section. Find "DC Unlocker Softwares", "DC_Phoenix", then download DC_Phoenix_v14.rar and run that instead. Whether it's Method 1 or 2 make sure you complete it - i.e. the fastboot flash step AND a step they call "flashing in upgrade mode."
(Also note that for DC Phoenix you want to feed it the oldest version of firmware available for your phone, in my case b152. This is because themes and icons won't be fixed until it receives the next version of firmware as an update.)
2. Once I did the fastboot and upgrade flash, I did a system reset from the Settings app trying to get themes and current icons again. (This didn't work but doesn't do any harm or might have helped somehow further down the line).
3. I used hajuuk's Firmware Updater and HiSuite to upgrade to the next version of firmware available (in my case b168).
3. All fine and your phone is back to stock - icons look nice again and local themes are back. To get the original icons layout, go to Recents, hold down on the Trash Icon, show system apps, and Clear Data for Huawei Home.

i2ectcf said:
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow.
Click to expand...
Click to collapse
Thanks for sharing! You saved me!

P9-L09/19 touch screen doesn't work in eRecovery or TWRP

Hi,
I must admit that I am panicking now because looks like i have bricked my phone and no matter what i try to do i am stuck between erecovery fastboot and TWRP.
To give you some light as to what actually happen... I've replaced oeminfo in originally EVA-AL-10 with EVA-l09. I have installed full system EVA-L09C432B136 and everything was fine at that point.
I thought to myself that it would be nice before putting any data to the phone to actually rebrand it to L19 so i do get a dual sim support.
In another thread I've found oem info for L19-C432. I've replaced it and decided to reflash full image EVAL19-C432B161 which i've also found on this forum due to huawei servers being down? (for some reason I couldn't download anything from the manufacture sources) This is when i got a first error message that updated failed due to incompatibility with the device.
I have been looking for some other full packages but whichever one I've put on a SD card, i couldn't get to work. for some stupid reason i thought about updating B136 hoping that during update process incompatibility issue will get fixed. Unfortunately this wasn't the case and even though the update completed "successfully" on the screen, after the reboot, i ended up in eRecovery.
Having oeminfo in SRK tools which worked for me previously i unlocked bootloader again and installed TWRP so i can root my phone and use srk to update OEM info back to 09.
This is where serious problems started to happen. in TWRP I am unable to use touch screen, only volume buttons and power button to confirm. As its a first launch of the TWRK I cannot even swipe to confirm read/write mode hence I can't go any further to install supersu etc...
Do you have any suggestions what can I do to unbrick it? Is there any workaround to get root via sd card? or maybe forcing somehow stock rom L09C432B136 to install regardless? Maybe there is a way to repack update.app so i doesn't look at the oeminfo?
I have tried replacing images (CUST, BOOT, RECOVERY and SYSTEM) in fastboot mode but I am not having any luck whatsoever.
Please throw me any ideas...
Thanks.

Hi azgooon,
I'm having the same problem, even it's a different huawei phone, did you get your problem fixed? How? Thanks for sharing.
douyi

Boot problems

Hello everyone!
I have just recently installed TWRP recovery on my L-09 and attempted to install OpenKirin's RROS from around here. Although the installation seemed to work fine at first, the device was stuck on the roms bootanimation. As such, I did what I would always do in this case, and try to recover my backup that I made through TWRP. Unfortunately though, that dos not boot up either.
Since then I have spent literal hours trying to find a way to make the phone boot , including trying to flash Moonlight and Magic Rainbow to no avail. I tried everything, flashing back to stock recovery, or the inbuilt erecovery or however it is call, nothing works. I have also tried to flash with the dload method, the installation fails with the file I found.
TWRP still seems to work, as does Fastboot mode and everything, so I have a feeling the situation should be salvagable.
Anyone with any better ideas? I have spent sooo long on this and I am on the end of my sanity
Thanks in advance!
Ok, Update: I have found an image that seemed to work with the dload method, but it is still stuck on the "Your device is booting now" screen..

Mi A2 Bricked, Solved

Hi, I need some help with my Mi A2.
I tried to install the RR Rom and was already struggeling in the beginning to get twrp up and running, after I got twrp running Ive got, while trying to install the RR rom (yes I did wipe everything that needed to be btw) error code 1 . So I tried to just shut my phone off and retried the installation after being back in twrp. and it did sort of install, I wasnt getting any error this time but after rebooting or atleast trying to I was stuck in a bootloop. soooo, I went back into twrp and tried wiping everything except internal storage and did an factory reset. but now fastboot mode wont let me use any commands for example "fastboot boot twrp.img" it just responds with "command write failed" or something like that. and when trying to boot into the "system" I get an blackscreen with a smal text in the top left corner saying "press any key to shutdown".
I hope someone can help me I tried now for hours to get anything running.
as a side-note I am not that new to flashing roms but, I have no idea what I screwed up this time.
Thanks for anyone that tries to help!
Edit: Using MiFlash and downloading the stock room from Xiaomi worked.

Minxxe said:
Hi, I need some help with my Mi A2.
I tried to install the RR Rom and was already struggeling in the beginning to get twrp up and running, after I got twrp running Ive got, while trying to install the RR rom (yes I did wipe everything that needed to be btw) error code 1 . So I tried to just shut my phone off and retried the installation after being back in twrp. and it did sort of install, I wasnt getting any error this time but after rebooting or atleast trying to I was stuck in a bootloop. soooo, I went back into twrp and tried wiping everything except internal storage and did an factory reset. but now fastboot mode wont let me use any commands for example "fastboot boot twrp.img" it just responds with "command write failed" or something like that. and when trying to boot into the "system" I get an blackscreen with a smal text in the top left corner saying "press any key to shutdown".
I hope someone can help me I tried now for hours to get anything running.
as a side-note I am not that new to flashing roms but, I have no idea what I screwed up this time.
Thanks for anyone that tries to help!
Click to expand...
Click to collapse
Try installing Stock Rom using MiFlash

gmoura5010 said:
Try installing Stock Rom using MiFlash
Click to expand...
Click to collapse
Yea, did that yesterday and that recovered my device. Still thanks for the advice.