Hi there!, i just bought a Huawei Maimang 5(MLA-AL10, Chinese Version) two weeks ago, then i noticed it had android 6.0 so i decided to upgrade it to 7.0..., since the Huawei Updater didn't find any update for my cellphone i downloaded FirmwareFinder App and use it instead, it worked but during the process the phone just rebooted and got bricked.
I tried to "save it" installing a new firmware via MicroSD, using Huawei eRecovery and Adb Tools, and nothing worked. Here my doubts:
1. Via MicroSD: i' m not sure the firmware i put on the card was the correct, i have found a lot of MLA-AL10 Roms and tried them all without any good results, the phone just start installation and at 5% reboot itself. Is there anyone out there who can help me finding the right one?
2. Via Huawei eRecovery: after i connect to a wifi network, my cellphone shows the next message: "There's no info for the package installed" and the only options i have left are: "Shutdown or Reboot", so i discarded this solution.
3. Via Adb Tools: using command "ADB DEVICES" shows empty list, i have no idea what i am doing wrong, my laptop recognize the phone and HiSuite too, but not Adb.
Hope someone can help me out.
Note: the phone has USB debugging disable.
Try recovery http://www.hardreset.info/devices/huawei/huawei-maimang-5/recovery-mode/
I forgot to mention i tried that too, and i cannot wipe data..., after 5% or 6% the EMUI logo dissapear and shows an exclamation mark.
Maybe this post will be help you https://forum.xda-developers.com/mate-8/help/boot-to-fastboot-mode-flashing-restore-t3550116
The solution is DC-Phoenix + 15 credits
Related
my huawei ascend y201pro is almost dead after i attempted to root. i know i may have made a mistake at one point but please forgive my ignorance. so this is exactly what happened before, during and now after rooting.:
I googled for the instrctions and got it. I downloaded the following files:
Root y201 pro.zip
UnlockBootloader.zip
recovery.zip
I extracted the files to a folder on desktop after which i was ready to start.
turned on usb debugging and disabled fast boot and then connected my phone to the pc. Installed drivers.
I clicked on the file unlockbootloader and ran as administrator and clicked on ROOT your phone. I guess here is where the problem was, after clicking on 'Root your phone" there was a command window running several commands automatically on my computer but before it alerted me of successful rooting, i checked my phone and saw a folder "superuser" clicked on it, and minimized the command window on computer screen and moved on to the next step; UNLOCKBOOTLOADER, clicked and worked out fine and closed itself, so i knew am through, i switched off the phone and removed the usb cable then tried to switch it on to no avail. could not charge , not being seen on the computer via the same cable. pulled out the battery and reinserted, tried to switch it on and what i see is the 3 buttons(menu,home and back keys) blinking exactly 10 times before they go off. The screen is completely black with no sign of life. I have searched for a solution to this online and in your forums but mostly are bricked phones which boot to recovery mode. nothing relates to exactly my problem.
any help please . i read the instructins here http://forum.xda-developers.com/showthread.php?t=2066887
Hello hope someone can help please have been trawling forums for a week now without getting anywhere.
I was running nxt-l29c636???? tried to upgrade via app firmware finder, first two I picked just failed then I picked older one thinking I might need to go from android 6 to 7 then to 8
Now it's stuck in a loop.
The firmware I picked looked like it was installing but failed early on 1 or 2 %
I can get to erecovery - does nothing and I've tried copying update.app to SD card and holding three button method but it does nothing.
When I fastboot it and rescue mode my phone status is locked.
Anyone know how I can recover please?
Ideally just want to flash it and if so it'd be great if it was android 8
Thanks for looking
So I fixed this by using the excellent DC-Phoenix, my problem was drivers
So for any noobs out there, got this work. My problem was the phone would never go into upgrade mode. The problem was in device manager (windows 7x64 but doesn't matter which version of windows), was when DC-Phoenix tried to put the phone in upgrade mode the command was sent and acted on but device manager showed warning triangles that it didn't have a driver or the driver was only partially loaded.
When I directed it to the downloaded Hi-Suite (which has all the drivers) it loaded the driver(s) there are TWO drivers on virtual COM ports. So if you phone is not going into upgrade mode best to check that Windows can actually see these TWO COM ports.
Hi hope someone can advise as I'm loosing the will to live
I've a mate 8 NXT-L29C636 which I believe is asia region although I've from the UK
I was running stock android 6 with EMUI 4.0
When I ask it to check for any update, it always came back with no updates.
I saw plenty of threads saying they had updated to android 7 and 8 and how they done it.
So I downloaded Firmware Finder from Google play and without too much difficulty managed to start installing firmware. That's when my problems started
This was two weeks ago and I've been spending 100+ hours trying to recover.
I think it failed a 5% or something and since then my phone will not boot properly.
I can only fastboot it and sometimes to erecovery and EMUI to wipe/factory reset
Searching forums it seems DC Phoenix was the only software that could help so I bought it.
So far I've tried flashing firmware from DC-Unlocker site in standard more but all goes ok with success for all the partitions but it requires the phone to put into upgrade mode, something my phone never does and I can't force it.
So that leaves me with advanced mode, again all successful but booting the phone just gives the huawei logo then reboots again
I've tried different stock roms NXT-L29C636 but they all claim successful but still can't boot my phone
I've followed the steps in DC-Phoenix instructions to no avail.
The last step today meant shorting a pin to ground to force the phone into a mode when it was seen as windows as Huawei USB COM device, which seemed to work.
The instructions claimed I can use any NXT board flash as they're all the same and again all successful i used
NXT-AL10_M00A102_Board Software_Global _Nonspecific_Android 6.0_EMUI 4.0_05021WLB_4.dtwork
but the log file now says build is;
Build number: HLNXTAL10BM00A102
Model: HUAWEI NXT-L29
Battery state: 3249mv
from
Build number: :NXT-L29C432B192
Model: HUAWEI NXT-L29
Battery state: 7035mv
So my question is am I using the wrong firmware? It is always successful so I don't think it's bricked but I can't work out what I'm doing wrong.
Other things to mention is pressing vol - and vol + and power with sd card and dload doesn't work either.
Sorry for long post and thanks for reading
Any help very much appreciated
No-one? I didn't expect a reply right away, but I can't be the only one with questions? Is there a better forum to post on?
Thank you
so for any noobs out there, got this work. My problem was the phone would never go into upgrade mode. The problem was in device manager (windows 7x64 but doesn't matter which version of windows), was when DC-Phoenix tried to put the phone in upgrade mode the command was sent and acted on but device manager showed warning triangles that it didn't have a driver or the driver was only partially loaded.
When I directed it to the downloaded Hi-Suite (which has all the drivers) it loaded the driver(s) there are TWO drivers on virtual COM ports. So if you phone is not going into upgrade mode best to check that Windows can actually see these TWO COM ports.
Hope this helps someone
Hi,
Could anyone help me with this one please? I have an ELE-L29 Phone and was prompted an OTA and clicked it but after restarting the phone got stucked with "Your device has loaded a different operating System" prompt. e-recovery doesn't seem to do something even the "download update and recover" option thru wifi.
**update. did a dload trick using a 431 EMUI 10 but still doesn't work. I can't seem to go to fastboot as well so i won't know what my previous build was.
johnvincent1 said:
Hi,
Could anyone help me with this one please? I have an ELE-L29 Phone and was prompted an OTA and clicked it but after restarting the phone got stucked with "Your device has loaded a different operating System" prompt. e-recovery doesn't seem to do something even the "download update and recover" option thru wifi.
**update. did a dload trick using a 431 EMUI 10 but still doesn't work. I can't seem to go to fastboot as well so i won't know what my previous build was.
Click to expand...
Click to collapse
Did you try Hicare on your computer?
The same problem here, I had install wrong firmware for huawei p30 lite. Is there anybody can help me solve this problem.
Hello, I am new here!
I have a problem with my P20. Yesterday I tried downgrading with HiSuite Proxy from Emui 9.1 to 8.1. The update went well, the emui loading circle with percentage appeared on the phone, then at 80 percent there appeared an error on the screen that the update has failed and I should either enter recovery or reboot. I clicked on reboot (I am dumb, I know) and since then the phone is showing a black screen and I cannot do anything. The phone is in Fastboot and it responds to fastboot commands from adb tools.
I think the problem is, that in Hisuite proxy I selected "normal update" instead of "rollback". That made Hisuite perform an update over a newer version of emui.
In the beginning, the phone was recognised by windows as "Andoid device" with a subname "HI3650". After switching drivers in device-manager, I got "ADB device" there.
What I tried so far:
- switching ADB drivers in device manager in windows
- system recovery in Hisuite. It fails, tried with several HiSuite versions so far.
- "fastboot flashing unlock" (most fastboot commands return errors like "FAILED (remote: check password failed!)" or "FAILED (remote: Command not allowed)"
I am not a pro with these things but understood that I could flash a recovery image with fastboot. Someone on this forum said something about .pac images which could be flashed even with a locked bootloader, mine is locked. Could somebody with good knowledge help me out? I did plenty of google searching before and also browsed through this forum, i did not find a solution, at least not with locked bootloader.
I would appreciate any help to save the phone before having to trash it!
Servus2403 said:
Hello, I am new here!
I have a problem with my P20. Yesterday I tried downgrading with HiSuite Proxy from Emui 9.1 to 8.1. The update went well, the emui loading circle with percentage appeared on the phone, then at 80 percent there appeared an error on the screen that the update has failed and I should either enter recovery or reboot. I clicked on reboot (I am dumb, I know) and since then the phone is showing a black screen and I cannot do anything. The phone is in Fastboot and it responds to fastboot commands from adb tools.
I think the problem is, that in Hisuite proxy I selected "normal update" instead of "rollback". That made Hisuite perform an update over a newer version of emui.
In the beginning, the phone was recognised by windows as "Andoid device" with a subname "HI3650". After switching drivers in device-manager, I got "ADB device" there.
What I tried so far:
- switching ADB drivers in device manager in windows
- system recovery in Hisuite. It fails, tried with several HiSuite versions so far.
- "fastboot flashing unlock" (most fastboot commands return errors like "FAILED (remote: check password failed!)" or "FAILED (remote: Command not allowed)"
I am not a pro with these things but understood that I could flash a recovery image with fastboot. Someone on this forum said something about .pac images which could be flashed even with a locked bootloader, mine is locked. Could somebody with good knowledge help me out? I did plenty of google searching before and also browsed through this forum, i did not find a solution, at least not with locked bootloader.
I would appreciate any help to save the phone before having to trash it!
Click to expand...
Click to collapse
Hello there! I can help you with this since I got exact same problem. Do you have any messaging app? add me on telegram t.me/dexxik or discord Dexxo#0295 if you want quicker response.
First of all, you f*cked up. I can help you recover your phone but you won't be able to use that phone for calling/messaging again.