Related
Hello!
As title says i bricked my Axon :crying:
I followed http://forum.xda-developers.com/showpost.php?p=68738854&postcount=100 (and the german one that linked to this one) but couldnt do the fastboot unlock.
So i couldnt finish this and my phone required a pin number to start android: bootet and started up but wanted a pin code to start/enter system.
Wasnt able to fix that with googling for answers so i went back to edl mode and rewrote my backup boot/recovery images with axon7backup.
Had no errors with that but it wont start now:
After the ZTE Logo the display goes black but it connects as "handset diagnostic interface (DFU) (ComX)" to my computer.
I fiddled around with driver installing etc and forced the HS-USB QDLoader 9008 on it but no luck, axon7backup/root can not connect.
When i did the actual flashing yesterday it never connected with the hold both vol-keys and connect usb way either, always had to reboot into edl via adb.
I cant boot anything else (no twrp/recovery) it just goes to the diagnostic interface mode.
Thanks in advance
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Starvirus said:
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Click to expand...
Click to collapse
Thanks. I tried it but it wont go to FTM. Only goes to diagnostic com port.
It seems i cant even turn it off. The little red light on the front is on the whole time .
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
adb don't show your device?
Starvirus said:
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
Click to expand...
Click to collapse
Oh ok. I expected ftm to work from vol-down and power-button till restart.
@adb: sadly no connection possible since it goes straight to Comport Connection.
Edit:
Couldnt make that work. It was off and i connected the usb. So it showed me the loading battery picture where i cant do anything. held the vol-down the whole time. But as soon as it had some battery it went straight to comport-connection again
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
nsabir said:
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
Click to expand...
Click to collapse
Hi,
couldnt fix it myself so i had to send it in.
Unless some tool/rom was released in the last few months to fix it yourself i would guess your device is bricked.
Hi I have almost the same problem, I tried to unlock bootloader and now I don't have the recovery, I can boot and use my mobile but I can't restore it or update it because I don't have the recovery
I try whit axon7tool to restore the recovery but I got a error.
MaxRink said:
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
Click to expand...
Click to collapse
Hi, do you have any idea, if there will be such a flashtool to work with DFU mode? I'm thinking that there are a lot of guys have bricked their devices (including me).
((
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
GloryNation said:
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
Click to expand...
Click to collapse
tried to enter recovery, still not work. can't go to developer options because phone is stuck on logo, can't power off. couldn't find any solution that works anywhere, been searching for more than 6 hours, still no use. phone model is VNS-L21 forgot to mention earlier
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
GloryNation said:
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
Click to expand...
Click to collapse
I tried to install nougat update, computer recognizes it only in fastboot. holding volume buttons haven't changed anything still no progress. the thing is i had installed nougat a moth or so ago and it worked fine, then rolled back to marshmallow and now this. i'm pretty sure i tried to install correct package, because it was the same i had installed earlier
Did you download a adb tool on your computer that have the 'fastboot.exe' file? If so open that folder,
Have the mouse curser hover in that folder, hold down shift & right click the mouse
Open command prompt
Connect phone as is in fastboot mode
Type adb devices & press enter
Type adb continue & press enter
Hi,
I have the same issue as ellanyx.
my phone can only be stucked while booting or if I connect my phone to a computer, I'm able to boot it in fastboot.
as ellanyx, I didn't enable usb-debug nor OEM unlock option...
so when I'm in fastboot, I type the command "fastboot oem unlock xxxxxx" (hopefully the different data needed are the correct ones mentioned on the box of the phone) I get this error message:
C:\Users\Dieu\Downloads\SRKToolHuawei-STABLE-V1.3-20160619>fastboot oem unlock xxxxx
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
and off course the other options like "fastboot flash recovery recovery.img "... doesn't work.
I can't use the adb commands neither.
when I type the commande, as mentioned above, "adb devices" or "adb continue", nothing works.
So I'm a bit desesperate
do you have any solution for this kind of issue?
thanks
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
pyromana said:
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
Click to expand...
Click to collapse
Probably you didnt have correct Oeminfo for MM if dload method didnt work....Try to conect phone with Toolkit and follow procedure for flashing oeminfo and custombin, after that flash stock recovrry and b161 via dload metod. You will find it on forum here.
Regards
the procedure from SRK toolkit?
would it be possible to provide it? because I can't unlock the OEM and I didn't tick the USB debug think.
Maybe problem with the ps not phone so u can not connect with adb
Try with different pc you must have flash oem with fast boot without enable adb from phone if u in fastboot
I can only boot my phone in fastboot (vol- + power) and not in recovery (vol+ + power).
also when using the SRK toolkit, the first screen tells me to be sure that the usb debugging is enable, which I haven't done...
if I'm not mistaken, fastboot is to use the fastboot command and recovery the adb commands
the connection with fastboot works on my computer, the link is made. however when I type the command to unlock the OEM, I get an error stating that the command is not allowed.
when I use the SRK toolkit, with the different questions, he tries to connect the phone with adb and waiting.... waiting...
is there a command to reboot in recovery but from fastboot? in the otherway around it exists but it doesn't seem that from fastboot to recovery it exists.
thanks.
Alexxxx1 said:
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Click to expand...
Click to collapse
dload method works on N. I downgraded my phone from unofficial N update back to official MM update using this method yesterday. You just have to enable OEM at developer options on settings.
It looks like people can't be bothered to read the 1st post properly before they reply.
HE CAN NOT BOOT TO ANDROID SO HE CAN NOT ENABLE OEM OR ACTIVATE USB DEBUGGING!!!!
What he CAN do, is go into eRecovery and Fastboot.
With that in mind, I would suggest using the dload method through fastboot.
Also, make sure it is Huawei SRK Tools 2.0 that is used, as it actually asks if you are in debug mode or fastboot.
Note that there is a few bugs in SRK 2.0:
The TWRP recovery file has the wrong filename in the package, so it WILL fail unless you name it correctly.
Also, when trying to root, do NOT use the "P9 Lite" method as that WILL fail too. Use the "P9/P9 Plus" method.
I am trying to set up a complete guide that can restore the phone when it is stuck in fastboot, however I apparently went a step too far...
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken[/QUOTE
Do you have TWRP recovery ?
---------- Post added at 09:55 AM ---------- Previous post was at 09:50 AM ----------
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
Click to expand...
Click to collapse
Boot into fastboot mode and flash a custom recovery by meticulus. Link : meticulus.co.vu
Then whenyou get stuck hold power and vol down button for 2 minutes the phone will reboot and then when it says that your device has been unlocked and cant be trusted then only press vol up key ( dont press power button then). The u get into huawei recovery. From that u should power off the phone. Now get a custom rom by meticulus into your device sd card ( Cyanogenmod 13 is recommended ). Then insert sd card in a powered off phone. Now press vol up and power key and flash gapps and custom rom and you are good to go.
Click to expand...
Click to collapse
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
SnowmanDK said:
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
Click to expand...
Click to collapse
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Arsaam said:
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Click to expand...
Click to collapse
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
SnowmanDK said:
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
Click to expand...
Click to collapse
Go to fast boot mode and from their try to flash meticulus recovery.
You can also try the adb method as well.
Visit meticulus.co.vu
Hello, I turned on my phone this morning as usual however was instead presented into a Factory Test Mode, has happened for the first time. I then long pressed the power button but still no luck, after trying every combination possible I gave up. I charged the phone last night at 100% and turned it off as usual. (On stock rom, Oreo 8.0 not rooted or anything. - A2017GV1.3.0B03 ) Also, don't really want to disassemble or reset my phone. Any help would be much appreiated. Thanks!
owerevoke said:
Hello, I turned on my phone this morning as usual however was instead presented into a Factory Test Mode, has happened for the first time. I then long pressed the power button but still no luck, after trying every combination possible I gave up. I charged the phone last night at 100% and turned it off as usual. (On stock rom, Oreo 8.0 not rooted or anything. - A2017GV1.3.0B03 ) Also, don't really want to disassemble or reset my phone. Any help would be much appreiated. Thanks!
Click to expand...
Click to collapse
what is "long pressed"? You have to hold it for about a minute or so, did you?
If it doesn't work, FTM mode has ADB, so you should be able to hook it up to a PC and issue "adb reboot" from the terminal. If you end up in FTM again then your phone is just borked or something, you can attempt to fix it by using "adb reboot recovery" instead and reflash stuff
Choose an username... said:
what is "long pressed"? You have to hold it for about a minute or so, did you?
If it doesn't work, FTM mode has ADB, so you should be able to hook it up to a PC and issue "adb reboot" from the terminal. If you end up in FTM again then your phone is just borked or something, you can attempt to fix it by using "adb reboot recovery" instead and reflash stuff
Click to expand...
Click to collapse
Thanks, adb reboot solved it! Can't thank you enough!
Same case to me on OreoB03. Power button long pressed didn't respond. I used "minimal_adb_fastboot_1.4.1_portable" and command reboot.
svsavic said:
Same case to me on OreoB03. Power button long pressed didn't respond. I used "minimal_adb_fastboot_1.4.1_portable" and command reboot.
Click to expand...
Click to collapse
Same problem here.
But i do not know how to use ADB tool.
I dowloaded minimal adb fastboot tool and i have now 3 executable (adb, fastboot, MAF32) in a directory but I do not know how to use them in order to reboot my Axon 7.
I would appreciate a step by step guide, made for a very beginner.
Note also that I may not have already the device drivers on my computer.
Find cmd.exe in syistem32, run as administrator, drag adb.exe in cmd window. Write command adb reboot.
Impossible for me.
I am not even able to have the phone recognized since the drivers are not correctly installed and Zadig tools wont help.
I'm really stuck.
Would any Belgian Guys be able to help me having a computer with adb WinUSB drivers correctly installed so that we can reboot my phone with his PC with any adb tool ? Please PM me is so.
Phone is recognized as adb device (w/o driver). Just try this and write command adb reboot or reboot (i don't remember).
It is said that no devices is found.
?
Also had the same FTM problem and can confirm that power button did not work in stock Oreo.
If can't get adb reboot work, one simple way is to discharge the phone - USB type C connection is fully working in FTM mode (u can simply check that). Connect one or few (use simple usb spliter) USB devices (the best way is to connect devices, for example power bank, some bluetooth speaker, which actually suck energy etc.) to your phone in order to charge them and it will fully discharge the phone in a few hours. Then on phone turned off connect power charger, wait about 15-20 minutes to charge and turn on the phone as usual (using only power button for a few seconds).
Hello, i actually thought about this option of waiting for the battery to be discharged but did not dare to take the risk. I finally found someone that will "adb reboot" my phone tomorrow, fingers crossed.
Hi,
OK, let's hope that "adb reboot" option will succeed.
However, personally I see no risks in discharging the battery - when the phone discharges it just safely automatically turns off - no data loss, no need to reflash the ROM etc. I went through this route myself.
I think it could be another bigger risk to keep the screen on (not moving screen) for a longer time - possible burn in of screen etc. But not sure about this risk and don't want to frighten, maybe others have more knowledge on possible screen burn in issues. In my case after discharging the battery no burn in or other screen problems.
I ordered a OTG cable that should arrive tomorrow to discharge the phone if adb reboot does not work. Thank you for ur feedback.
Have you tried this tool to get to EDL and then you can use Miflash to flash back to stock https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
billjim24 said:
Have you tried this tool to get to EDL and then you can use Miflash to flash back to stock https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
Click to expand...
Click to collapse
that's not remotely useful to the situation
please read up before posting lmao
Mine Axon 7 did just that, couldn't turn it off in any way, also on b03 Oreo rom. So I let it discharge completely, and just did a normal power on, and it worked again.
I think that the Oreo Rom is in an awfully bad beta Rom rushed out from a sinking mobile company, that don't give a s... about their customers.
Will never buy ZTE again.
A friend could reboot mine with adb reboot. Problem solved.
I guess adb drivers did not worked well on m'y computer.
Next thing to do : downgrade to Nougat in order to get Daydream. What a shame.
Chinesur said:
A friend could reboot mine with adb reboot. Problem solved.
I guess adb drivers did not worked well on m'y computer.
Next thing to do : downgrade to Nougat in order to get Daydream. What a shame.
Click to expand...
Click to collapse
G B03 has daydream, hasn't it?
No, it doesn't have
Boot in FTM,open axon7toolkit,connect phone to laptop and follow instructions in axon7toolkit.It will reboot in edl and you can flash a firmware
Not sure how to title this forum post, but this is the best I got. Forgive my ignorance and lack of knowledge on these topics.
I was trying to root my Axon 7 mini. After some searching to find out how to unlock the bootloader (like needing JDK, older Android SDK version to run android.bat, etc.), I finally got it to work. Ran Recovery to "apply update from SD Card" (can not remember the file right now) and was then ready to load TWRP Recovery. When I rebooted to the recovery TWRP image, it told me something failed and the phone had to be factory reset. I took my SD card out in fear of my data being deleted and "accidentally" clicked the power button. It then reloaded with a password prompt where I typed some random password (1234 because I never set a pin password nor knew what to do here), clicked submit, and then gave me some error; now my phone doesn't work.
The Problem:
- I can enter bootloader, sometimes, but can only run fastboot commands; adb device does not detect phone so can't run adb commands (always says the server is old or something and reloads daemon successfully but never finds my device regardless). Also, I don't think I can get it to run in EDL mode; MiFlash gives out errors too when trying to flash recovery images.
- Recovery mode doesn't appear or work; not sure if the MiFavor command prompts on the phone is recovery or not, but it's safe to say this no longer appears. This is also where I believe the phone bootloops. I can get the fastboot commands to flash a TWRP recovery, but it never actually enters the TWRP dashboard.
- Can not turn off the phone... I think. None of the command options that appear on-phone shut it off; however, when the screen does stay black, I'm not sure if it's in EDL mode or plainly off.
- Device Manager shows the phone as different stuff (namely Kedacom USB Device and Portable Devices/MTB USB Device). Sometimes Qualcomm appears, but it depends. More often than not, when my device does appear, there's either an error code (like Code 10, Code 43) and/or the device is grayed out.
Conclusion:
I just want to get my phone to work normally again, if possible. Currently, I locked the oem to see if fastboot commands could still work and now I'm stuck at the ZTE logo, so can't try to unlock it right now. What are the proper tools, drivers, programs, etc I need to get this phone back to normal? I've scoured the web and these forums for 2 days now with no luck and lots of either missing info or obscure info.
I bought this at Best Buy, so I'm assuming it's US Axon7 Mini version in terms of drivers (not sure if the box specifies any info that could be useful here).
Un-brick Axon 7 Mini
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
mariegalante55 said:
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
Click to expand...
Click to collapse
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Kuma21 said:
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Click to expand...
Click to collapse
K, I can get tuliptool to work and run command, but i keep getting a "Failed: Unkown Error" response everytime i run a command. Can't unlock my bootloader, nor write a recovery disk due to this error. does anyone have any idea why this happens?
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.