Hello,
After the step 15 in
android.modaco.com/topic/345950-02-oct-3414051-installing-honeycomb-on-your-flyer-the-complete-guide
"Flash your device's recovery with the patched-to-work-with-new-hboot revolutionary recovery - 'fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.hboot0010.img"
The flyer doesn´t boot anymore in recovery. I can go to Bootloader or Fastboot. No adb possible. When I try normal boot, Fyler stucks in White Htc logo.
To run ruu for going back to GB is not possible because I get an Error "Battery less than 30%" after charging the fyer all night
please I need help guys.
thanks a lot
Elfuente said:
Hello,
After the step 15 in
android.modaco.com/topic/345950-02-oct-3414051-installing-honeycomb-on-your-flyer-the-complete-guide
"Flash your device's recovery with the patched-to-work-with-new-hboot revolutionary recovery - 'fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.hboot0010.img"
The flyer doesn´t boot anymore in recovery. I can go to Bootloader or Fastboot. No adb possible. When I try normal boot, Fyler stucks in White Htc logo.
To run ruu for going back to GB is not possible because I get an Error "Battery less than 30%" after charging the fyer all night
please I need help guys.
thanks a lot
Click to expand...
Click to collapse
if you can turn on bootloader, under fastboot selectable power-down, then you can continue to charge. it takes several hours
that´s exactely what I did
viera77 said:
if you can turn on bootloader, under fastboot selectable power-down, then you can continue to charge. it takes several hours
Click to expand...
Click to collapse
I charged the whole night, It´s not working.
Elfuente said:
I charged the whole night, It´s not working.
Click to expand...
Click to collapse
when you turned off your charger was plugged in? flashes the power button? if so, let flyer until it is completely off
Charger
viera77 said:
when you turned off your charger was plugged in? flashes the power button? if so, let flyer until it is completely off
Click to expand...
Click to collapse
Yes charger was on when i turned off.
Now I turned off without the charger and replugged the charger when the flyer was off. I will charge it for two hours and give it a new try.
I hope it will work, I am little bit desperated.
thanks so far
download the file for the recovery image again and make sure you have that file in the directory you are running fastboot from.
redo step 15
If that does not work, boot into bootloader and tell us exactly what it says at the top of the screen
FAILED (status malformed (1 bytes))
DigitalMD said:
download the file for the recovery image again and make sure you have that file in the directory you are running fastboot from.
redo step 15
If that does not work, boot into bootloader and tell us exactly what it says at the top of the screen
Click to expand...
Click to collapse
Now when I try to do step 15 again I get; sending 'recovery' (4746 KB)... FAILED (status malformed (1 bytes))
Content of Bootloader
***UNLOCKED***
#FLYER PVT SHIP S-ON RL
HBOOT-1.11.0010
MICROP-0850
RADIO-3809.07.04.06_M
eMMc-boot
Oct 12 2011,16:50:58
HBOOT USB PLUG
wow, I've seen this before. There's another thread with that same issue.
What PC are you using? Windows? Mac?
Windows XP
DigitalMD said:
wow, I've seen this before. There's another thread with that same issue.
What PC are you using? Windows? Mac?
Click to expand...
Click to collapse
Windows XP.
If needed I can also use a Mac. I am just not familiar with using the flyer, sdk and so on with Mac.
Actually Windows is easier. I've seen this exact problem in a thread before but I don;t remember the solution. I suggest you contact GlobalTron directly and ask him, he's worked on a lot of install and restore issues. You will see him as the OP in the first thread in development.
Elfuente said:
Now when I try to do step 15 again I get; sending 'recovery' (4746 KB)... FAILED (status malformed (1 bytes))
Content of Bootloader
***UNLOCKED***
#FLYER PVT SHIP S-ON RL
HBOOT-1.11.0010
MICROP-0850
RADIO-3809.07.04.06_M
eMMc-boot
Oct 12 2011,16:50:58
HBOOT USB PLUG
Click to expand...
Click to collapse
I had same problem
You have different Hboot und Radio version.
I solved this problem with Gold Card
Ok, you're officaily a dumbass ( I am joking in case that isn't clear )
You can't flash becasue you're in the wrong mode (hboot). Nothing can be flashed from hboot mode. Select fastboot from the menu and then run the flash command.
officaily a dumbass
globatron said:
Ok, you're officaily a dumbass ( I am joking in case that isn't clear )
You can't flash becasue you're in the wrong mode (hboot). Nothing can be flashed from hboot mode. Select fastboot from the menu and then run the flash command.
Click to expand...
Click to collapse
Which flahs command
the recovery one.
Now I can not test it I get; sending 'recovery' (4746 KB)... OKAY [ 1.047s]
writing 'recovery'... FAILED (remote: battery low)
I will try after one hour charging:
Still the same problem.
Ruu after 5 hours charging stopped with; Error "Battery less than 30%"
When I try to flash the stock-hc-flyer-radio-3.41.405.1.img again I get;
sending 'radio' (25728 KB)... OKAY [ 4.250s]
writing 'radio'... INFOsignature che
FAILED (remote: signature verify fail)
finished. total time: 6.703s
no adb possible.
HEEEEEEEELPPPPPP
desperate
any chance of support with this problem?
i have the same problem , i need help to ? unlocked but s-on , fast boot works but a d b doesn't ??? how can i made a gold card without even opening my htc flyer ? please help ????
mimdrj said:
i have the same problem , i need help to ? unlocked but s-on , fast boot works but a d b doesn't ??? how can i made a gold card without even opening my htc flyer ? please help ????
Click to expand...
Click to collapse
Fastboot oem lock
Run stock ruu
If you can not proceed from current state
right
mcord11758 said:
Fastboot oem lock
Run stock ruu
If you can not proceed from current state
Click to expand...
Click to collapse
exactly, all I had to do was 1. "Fastboot oem lock", 2. Run stock ruu.
It took me 2 days to figure that out by myself and now I see here the answer. Why could nobody told me that when I was desperately looking for help.
Anyway HC is now running and I am very content with.
Related
My almost two-year-old Hero froze this morning, so I had to take out the battery, but after this I've been unable to boot, it's stuck on the HeRO screen. I can't start recovery either, the only thing working is hboot / fastboot. Erasing user data using fastboot doesn't do anything.
Also, plugging the phone into charger doesn't signalize charging – the LED doesn't light up, and the PC doesn't recognize the phone either. Only fastboot does connect the phone to the PC, but adb doesn't work and all attempts to flash a new recovery or do anything else via fastboot end with "FAILED (remote: not allowed)":
Code:
c:\adb>fastboot devices
HT97JL903267 fastboot
c:\adb>fastboot boot recovery-RA-hero-v1.7.0.1.img
downloading 'boot.img'... FAILED (remote: not allow)
c:\adb>fastboot flash boot recovery-RA-hero-v1.7.0.1.img
sending 'boot' (3972 KB)... FAILED (remote: not allow)
I tried installing the official RUU updates (2.73.405.66, 2.73.405.5 and 1.76.405.1 too) but none of them could connect to the phone, Error [170]: USB Connection error.
I was using Elelinux-Hero-2.1-update1-Reloaded with radio 63.18.55.06SU_6.35.17.03 and recovery was Amon RA 1.6.2 I guess.
The phone did a similar thing 3 weeks ago but I was able to boot into recovery and erase data and cache and it worked fine afterwards. Now only fastboot is accessible.
Is there anything else I can do at this point or is the phone dead for good?
Disregard my previous post.
I left the phone booting for 30 minutes, the battery got uncomfortably hot, but the phone booted up eventually. Then I managed to install the official RUU from here.
It didn't solve anything though – it still takes around 20 minutes to boot, the touch screen doesn't work and I get an "android.process.acore" error all the time – but since the phone seems untouched (thanks to the RUU install) I can lodge a claim and get a replacement phone hopefully.
You could try putting HEROIMG.NBH on the sdcard and booting into hboot. If you go into fastboot and press vol-down it quickly scans for files on the SD, of which heroimg is one, and if it finds them, installs them.
Can't really help more than that. My phone did that last year, took it to the shop and ended up getting a new motherboard, cause the ROM chip was knackered.
One thing I would recommend though when you get it fixed is to flash an engineering bootloader, do if it breaks again you've got none of this "remote not allow" rubbish.
Of all the times to say disregard my last post.........
Sorry about that, thanks a lot though!
I suppose some hardware is broken in my Hero as well, I will take it back to the shop tomorrow.
Thanks again!
Unlocked phone by following steps on HTC site. Phone got unlocked without any issues now upon reboot phone is stuck on htc one boot screen What are my options do I have to flash another rom ??
Using HTC RUU to repair the phone and I am getting ERROR [130]: MODEL ID ERROR ERROR [131]: . Any ideas what does this error means
sguy156 said:
Unlocked phone by following steps on HTC site. Phone got unlocked without any issues now upon reboot phone is stuck on htc one boot screen What are my options do I have to flash another rom ??
Click to expand...
Click to collapse
Hold vol down as it goes through the next loop, and it will put you in bootloader. From there, you can go to fastboot mode and flash custom recovery. Then adb sideload, adb push a ROM, or load a ROM to the removable SD if you have a card reader you can connect to your computer. Then boot custom recovery and flash the ROM.
sguy156 said:
Using HTC RUU to repair the phone and I am getting ERROR [130]: MODEL ID ERROR ERROR [131]: . Any ideas what does this error means
Click to expand...
Click to collapse
It means you are trying to run the RUU for another carrier version. What version do you have (this section is for AT&T) and what RUU are you trying to run?
How can I flash another recovery when the PC doesn't see it as phone. Tried two different cables . Once I get the PC to see the phone it should be ok . See the screen when the phone boots up.
Any other suggestions on getting the PC see the phone. I installed HTC sync also that didn't helped also ..
Will putting the recovery in sd card and then booting the phone work and dont I have o turn S-OFF before I can flash any ROMS ??
sguy156 said:
Will putting the recovery in sd card and then booting the phone work and dont I have o turn S-OFF before I can flash any ROMS ??
Click to expand...
Click to collapse
Yes if your S-OFF you can put recovery on your sdcard
http://forum.xda-developers.com/showthread.php?t=2951030
I am S-ON and bootloader is relocked . Can I still flash custom recovery with S-ON and then flash ROMS ?? Rebooting the phone it says wrong img . What can I put on the sd card to flash the img for the phone to boot..
sguy156 said:
I am S-ON and bootloader is relocked . Can I still flash custom recovery with S-ON and then flash ROMS ?? Rebooting the phone it says wrong img . What can I put on the sd card to flash the img for the phone to boot..
Click to expand...
Click to collapse
I thought you had S-OFF so no you can't load a custom recovery to your sdcard.
---------- Post added at 08:45 AM ---------- Previous post was at 08:36 AM ----------
sguy156 said:
I am S-ON and bootloader is relocked . Can I still flash custom recovery with S-ON and then flash ROMS ?? Rebooting the phone it says wrong img . What can I put on the sd card to flash the img for the phone to boot..
Click to expand...
Click to collapse
Try the universal drivers from the link below.
http://dottech.org/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/#asus
I will try universal drivers and see what happens. What commands
I need to try on the phone if these drivers work ??
sguy156 said:
How can I flash another recovery when the PC doesn't see it as phone. Tried two different cables . Once I get the PC to see the phone it should be ok . See the screen when the phone boots up.
Any other suggestions on getting the PC see the phone. I installed HTC sync also that didn't helped also ..
Click to expand...
Click to collapse
The PC can see the phone, otherwise you wouldn't get the Model ID error message you indicated in the first post.
So no response if you type the following in command prompt?: fastboot devices
Fastboot and/or adb connectivity issues are rather common.
Another trick you can try, is to uninstall all HTC software (Sync and drivers) from your PC. Then connect the phone. DO NOT accept any prompts to automatically install drivers or Sync. Go to Device Manager, find the device, and pick the option to manually select the drivers, and pick the generic Android MTP device drivers.
Also try different USB ports. IN particular, if the ports are USB 3.0, that is known to cause issues (you may be able to disable the 3.0 drivers).
And if your PC is Win8.1, that is also known to be problematic.
---------- Post added at 09:39 AM ---------- Previous post was at 09:36 AM ----------
sguy156 said:
I will try universal drivers and see what happens. What commands
I need to try on the phone if these drivers work ??
Click to expand...
Click to collapse
fastboot erase cache
fastboot flash recovery filename.img
(where filename.img above is replaced with the actual name of the desired recovery file)
Yes trying fastboot doesn't show the phone. Is this something HTC can fix under warranty
sguy156 said:
Yes trying fastboot doesn't show the phone. Is this something HTC can fix under warranty
Click to expand...
Click to collapse
Fastboot and adb connectivity issues are almost always a problem on the PC's side (ports, Win version, drivers, USB 3.0). Warranty replacement isn't going to help you.
I've given you a few suggestions on addressing the connectivity issues. You haven't indicated whether you have tried them yet, or not.
i tried your sugestions phone is showing up as HTC andriod device and running adb devices doesn't show anything. Not sure what else I can try , I am trying this on a windows 7 PC as windows 8 gave me so many issues .
@sguy156
So your running adb commands from c:\user .
I think your not navigating to adb properly.
I go to where adb and fastboot lives and Shift+right-click so I can open the cmd there
Thats what i did ran it from the location where adb and fastboot are installed same issues .
I hate to ask but do you have usb debugging on wile trying to use adb ?
Please keep an open mind as I'm trying to help ?
---------- Post added at 08:57 AM ---------- Previous post was at 08:30 AM ----------
Try this out if you can't get anything going.order the cable and use a second rooted Android device (no drivers needed at a all)
http://forum.xda-developers.com/att...c-fastboot-t2965030/post57315448#post57315448
USB debugging was on when phone was rooted not sure if its on ss I
Cannt check it now ..
Ok I finally got fastboot to work . Tried this on windows 7 PC with different cable and it worked . Now what ROMS I can use to flash the zip with SON and get this phone working.. but flashing the recovery gave me this error
C:\adb>fastboot flash recovery openrecovery-twrp-2.8.1.0
target reported max download size of 1826414592 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.813s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.408s looks like verification of signature failed . Is this anything to be concerned about ..
Did these command also .................
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.013s
Phone didn't reboot into twrp recovery got stuck at htc one boot screen is it because bootloader is locked ??
sguy156 said:
Ok I finally got fastboot to work . Tried this on windows 7 PC with different cable and it worked . Now what ROMS I can use to flash the zip with SON and get this phone working.. but flashing the recovery gave me this error
C:\adb>fastboot flash recovery openrecovery-twrp-2.8.1.0
target reported max download size of 1826414592 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.813s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.408s looks like verification of signature failed . Is this anything to be concerned about ..
Did these command also .................
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.013s
Phone didn't reboot into twrp recovery got stuck at htc one boot screen is it because bootloader is locked ??
Click to expand...
Click to collapse
I'm not trying to be rude but now that you have fastboot figured out I suggest you put the phone down in another room and start reading on what procedures to take next.
You learn the hard way by not looking in the "General section" where all the information is posted.
Yes you need the bootloader unlocked to push a custom recovery.
Thanks for your help , I found the other steps on other section . Hit post too quickly ..... Learning experience ..
sguy156 said:
Thanks for your help , I found the other steps on other section . Hit post too quickly .....
Click to expand...
Click to collapse
I like shortcuts when I drive ,I just don't advise taking them with the hacking of my devices.
If you use the "Tapatalk app" or the "XDA app" the forum is easier to read through
----------------EDIT --- GOT IT FIXED--- READ FIRST 4 PAGES OF THE THREAD----------------------- BACK TO STOCK <3 XDA
Hello, I used relock bootloader command in fastboot.... now the phone only restarts to "ERROR MODE"
It looks like that
"ERROR MODE"
Attention!
Please Update system again.
[Green Android]
Error!
Func NO : 11 (reovery image)
Error NO : 2 (load failed!)
--------------------------------------
Anybody can help me? When I restart phone this mode appears again and again, can't enter fastboot mode or recovery.. when pressing any key it restarts to this error mode...
Also phone can't be tunred off, when hard pressing POWER it will instantly reboot to this mode.
Phone doesn't show up in device manager... when doing anything via fastboot command only waiting for device...
-----------------
Can you boot into fastboot mode? is bootloader and frp unlocked?
RobertHarkness said:
Can you boot into fastboot mode? is bootloader and frp unlocked?
Click to expand...
Click to collapse
no
... it was unlocked.. than i used relock command in fastboot mode and endet here....
If you can't boot into fastboot mode then your going to have to contact huawei. Without fastboot your phones hard bricked mate
RobertHarkness said:
If you can't boot into fastboot mode then your going to have to contact huawei. Without fastboot your phones hard bricked mate
Click to expand...
Click to collapse
Ok... that sucks...
Rommco05 said:
Probably if u see this are u already in fastboot try when shows this screen plug cable to pc and write in adb >>>> fastboot devices
Attention!
Please Update system again.
[Green Android]
Error!
Func NO : 11 (reovery image)
Error NO : 2 (load failed!)
edit: ok now I see... waiting for device
---------- Post added at 07:49 ---------- Previous post was at 07:26 ----------
How happend this situation, what u do before relock bootloader?
Click to expand...
Click to collapse
The smartphone doesn't show up in adb-devices... Also dodn't see it in USB... before I did this it worked without problems.
The situation before... everything worked normal and I restarted to fastboot and tried to relock bootloader with oem relock bootloader command... after that command phone turned off and the looping error appeared... tried various button combinations also vol down + usb plugin ... but only this mode appears... also I cant turn smartphone off it restarts and restarts and restarts to this mode...
Rommco05 said:
Probably this phone need service. When u relock bootloader u have twrp or stock recovery and which system was in phone?
Click to expand...
Click to collapse
Before I did this command I had the chinese TWRP installed and Stock Rom... since the relock command doesn't delete anything of these things I think it is still here I think.... but I can't access it ...thats the problem and since the error mode doesn't start an usb-connection to Computer I can't use adb/fastboot... Thx for help guys
Rommco05 said:
Isn't good idea relock bootloader with twrp, if u want do relock always with stock recovery... :/
Click to expand...
Click to collapse
Yes was stupid idea... help would be still appreciated... Anybody know where I must send the smartphone to to repair it? (Europe/Germany)
UPDATE!!!
----I UNLOADED THE BATTERY TO 0 % NOW SO SMARTPHONE TURNED OFF----
------>CONNECTED AND RESTARTED MULTIPLE TIMES WITH USB CABLE AND BUTTON PRESSING------
------------------------>>>>AFTER 50 TRYS I AM IN FASTBOOT MODE<<<<------------------------------
WHAT DO NOW?
fastbootmessages:
PHONE Relocked
FRP Lock
When try to flash boot img via adb I get Error
target reported max download size of 471859200 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.717s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.728s
Rommco05 said:
I think you need to unlock booloader and after flash all imgs
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
im not sure if is this right order
Click to expand...
Click to collapse
Great!
But now next problem... when I unlock Bootloader I will need my Unlock code from Huawei Site... but can only access if if I have Model Nr (Which can be obtained only in Android) and Serial Number (Also only viewable in Android).... I have both IMEIS on the Back of my phone.... any ideas how to obtain without boot to android?
4r44444 said:
Great!
But now next problem... when I unlock Bootloader I will need my Unlock code from Huawei Site... but can only access if if I have Model Nr (Which can be obtained only in Android) and Serial Number (Also only viewable in Android).... I have both IMEIS on the Back of my phone.... any ideas how to obtain without boot to android?
Click to expand...
Click to collapse
You won't be able to unlock bootloader even if you have unlock code because of FRP. The only option is to use the DC Phoenix which uses some kind of backdoor - belive me, been there done that.
OK but maybe I can try... obtained my Serial via DC Phoenix... now only need the Product Idea when Dialing *#*#1357946#*#*. .... anybody can tell me please? :3
4r44444 said:
OK but maybe I can try... obtained my Serial via DC Phoenix... now only need the Product Idea when Dialing *#*#1357946#*#*. .... anybody can tell me please? :3
Click to expand...
Click to collapse
Not possible, you'll again need some program to directly read the bootloader code. What happened to your old one, it's always the same ?
Rommco05 said:
check here first post https://forum.xda-developers.com/p9/help/how-to-product-id-bricked-p9-t3561156
Click to expand...
Click to collapse
This is an old program, doesn't support Honor 9...
Rommco05 said:
He use it for Huawei P9, isnt id and serial on box?
Click to expand...
Click to collapse
Isn't this thread about bricked Honor 9? On the box of Honor 9 is everything except ID. Anyway, I found a newer version of the program, he can give it a try.
Ok got everything... but all time I try this Error appears in fastboot:
FAILED (remote: Command not allowed)
----------------------------------------------------
I tried to Unlock via DCPhoenix (Bought for 20 €)... it sayed it got unlocked but FRP is still locked..
"Phone Relocked"
"FRP Lock"
In Fastboot..
Rommco05 said:
Have you installed drivers (HiSuite)?
Click to expand...
Click to collapse
Yes... restore via it doesn't work.. "Your device is not supported" Error when using rescue mode.
So I think the main problem is now I can't do anything on fastboot because Bootloader is relocked (Also OEM-Unlock isnt activated in [email protected]).... So I think the only thing I can restore my 400€ Phone is to backdoor unlock it.... DC-Phoenix without success. any ideas from the real pros? Would pay 50€ if your method would work to restore my phone :/
Rommco05 said:
No no, just for drivers for communicating phone and pc. I think is some way how push imgs without unlocked bootloader
I'm not sure if is for this topic https://forum.xda-developers.com/an...stion-mounting-recover-partition-adb-t3591261
edit: I don't want money anyway...
Click to expand...
Click to collapse
Ok... I have to go to work now... will try later... I will read other posts later thank you all for help!!!!!!!!
4r44444 said:
Ok... I have to go to work now... will try later... I will read other posts later thank you all for help!!!!!!!!
Click to expand...
Click to collapse
Use this tutorial, it should work. Does it show you any error ?
https://www.dc-unlocker.com/repair-bricked-huawei-honor-7
Greetings…
W̶i̶l̶l̶ ̶d̶o̶n̶a̶t̶e̶ ̶2̶0̶ ̶U̶S̶D̶ ̶t̶o̶ ̶w̶h̶o̶e̶v̶e̶r̶ ̶c̶a̶n̶ ̶f̶i̶x̶ ̶m̶y̶ ̶p̶h̶o̶n̶e̶ Fixed and contacted both Bordo_Bereli51 and Ante0.
My Huawei Mate 10 got in a bootloop after installing Xposed Framework
It was on Android Oreo 8.0 rooted and bootloader unlocked
Lock state info:
FB LockState: LOCKED
USER LockState: UNLOCKED
Leaving the device to boot normally: HUAWEI logo then reboots.
Vol up+power: eRecovery mode … doesn’t work (wiped data and cache .. tried to download firmware through wifi .. nothing works). ... then tried this method it worked while downloading the firmware .. but after verifying the firmware then installing it when it gets from 0% to 1% it fails and a red exclamation mark appears. :crying:
Vol down + power: fastboot: always get: FAILED (remote: Command not allowed) ). even though the bootloader is supposed to be unlocked. :crying:
Vol up and down: download mode .. on USB: stuck at 5% … without USB connection to computer: nothing happens (a red exclamation mark appears).
The device has an SD card slot: I tried placing the UPDATE.APP in dload folder and pressed both volume buttons but nothing appeared .. did I do something incorrectly?
Here are more info:
product-model: ALP-L29
vendorcountry: hw/meafnaf
build-number: System 8.0.0.38(0310)
fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ALP-L29 8.0.0.128(C185)
Please help.
thanks in advance
====================
FIXED: Thanks to Bordo_Bereli51 who wrote this post and thanks for Ante0 for recommending DC Pheonix and for taking a lot of his time explaining a lot of things to me privately. contacted both as promised.
How I fixed it (credits to Bordo_Bereli51 for the guide .. I only modified it a bit and added some info from my experience):
1- I purchased a 19 euro -3 days pass for DC Pheonix.
2- Download Firmware Finder and click the "Common Base" tab, then download a FullOTA-MF firmware (all 3 files) which is approved for installation ( I copied the "changelog" link and pasted it in the 6th icon at the top "Firmware Checker" and it returned "Firmware approved for install" I' was not able to repack other non approved firmwares).
3- extract UPDATE.APP from update.zip
4- run DC Phoenix program .. tap the "Standard" button in Update mode .. select "update" and choose the UPDATE.APP you just extracted.
5- let it flash everything successfully then redo step 4 again.
6- Here's the trick before it flashes anything ... as soon as you see "utilizing backdoor" (or something like that) open Task Manager and force close DC Phoenix (it has to be BEFORE flashing anything, otherwise you might get errors like:
"error: exec '/system/bin/sh' failed: No such file or directory"
and AFTER utilizing backdoor (so you can use fastboot commands)
7-Download HWOTA8_Mate10 , place the 3 files you downloaded in step 2 in the "repack" folder, and rename "update_data_full_public.zip" to "update_data_public.zip" and "update_full_*ALP-L29*_hw_*meafnaf*.zip" to "update_all_hw.zip". Then run "repack.bat" and wait for it to finish.
8- run "ota.bat" in "ota" folder.
9- When it flashes the recovery_ramdisk and kernel plug your usb cable out and Reboot to recovery by pressing volume up + power button
10- When the phone is in recovery now ADB works (in case you need to do things manually).
11- When this process also finishes, the command center will tell you to press enter, so it boots to erecovery, which will flash the files.
12- Now your phone is unbricked after the flash.
Do not forget to do factory reset by pressing again at boot: (power + volume up) and selecting (factory reset).
After boot allow (OEM Unlock) under (developer settings) or otherwise the FRP will still be locked but the phone will work.
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Dolev234786 said:
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Click to expand...
Click to collapse
I have the same problem.
Dolev234786 said:
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Click to expand...
Click to collapse
No, I don’t have TWRP.
hero3210 said:
No, I don’t have TWRP.
Click to expand...
Click to collapse
What does fastboot mode say, unlocked on both phone and frp?
ante0 said:
What does fastboot mode say, unlocked on both phone and frp?
Click to expand...
Click to collapse
yes both are unlocked
Dolev234786 said:
yes both are unlocked
Click to expand...
Click to collapse
Post input & output when you try to flash using fastboot
ante0 said:
Post input & output when you try to flash using fastboot
Click to expand...
Click to collapse
My device used to be bootloader unlocked
But I always get "FAILED (remote: Command not allowed)" for any fastboot command
I searched here and a lot of people had the same issue and they fixed it by relocking then re-unlocking the bootloader
I tried that .. relocked successfully but now I cannot unlock it again.
This is the current info from info.bat:
Lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
in fastboot mode it says:
PHONE Relocked
FRP Lock
=====
Input and output of fastboot:
fastboot flash recovery_ramdisk SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'recovery_ramdisk' 1/7 (460797 KB)...
OKAY [ 3.650s]
writing 'recovery_ramdisk' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 3.661s
Thanks for taking time to reply
hero3210 said:
My device used to be bootloader unlocked
But I always get "FAILED (remote: Command not allowed)" for any fastboot command
I searched here and a lot of people had the same issue and they fixed it by relocking then re-unlocking the bootloader
I tried that .. relocked successfully but now I cannot unlock it again.
This is the current info from info.bat:
Lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
in fastboot mode it says:
PHONE Relocked
FRP Lock
=====
Input and output of fastboot:
fastboot flash recovery_ramdisk SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'recovery_ramdisk' 1/7 (460797 KB)...
OKAY [ 3.650s]
writing 'recovery_ramdisk' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 3.661s
Thanks for taking time to reply
Click to expand...
Click to collapse
You need to enable OEM unlock in Settings-developer options. At least frp needs to say unlock else you won't be able to unlock or flash, at least not for free.
But since you can't boot you're pretty much limited to use dc unlocker/dc phoenix
ante0 said:
You need to enable OEM unlock in Settings-developer options. At least frp needs to say unlock else you won't be able to unlock or flash, at least not for free.
But since you can't boot you're pretty much limited to use dc unlocker/dc phoenix
Click to expand...
Click to collapse
Thanks for the reply
Do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
hero3210 said:
Thanks for the reply
Do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
Click to expand...
Click to collapse
Dc phoenix is what you'll need, Mate 10 is not supported in DC Unlocker. (Though DC Unlocker made DC Phoenix)
You'd just want it to flash stock anyway.
And it's cheaper than FunkyHuawei... FH "only" cost 1 credit to flash, but minimum to buy is 5 credits which is $41.
FH is easier though as you'd only need to setup DNS, but it's up to you
HCU/DC Phoenix pass for 3 days is €19, and then you have unlimited usage.
If you need further help you can find me at the telegram group https://t.me/HuaweiMate
as it's easier to do it live than through messages.
There is a "DC Phoenix repair tutorial" if you google it, use Method 1. Basically you just download the firmware update zip you're on now (and hw data zip) from http://pro-teammt.ru/firmware-database/ then extract update.app from it and select it in Phoenix, then extract update.app from hw data zip and select it as customization.
Alternatively you can downgrade to factory build using images from DC Phoenix (the build your phone came with) then update from there when you have a booting phone.
Thank you sooo much man. I really appreciate your help.
What version of Xposed frameworks did you install I have beta 4 working fine on my mate 10 pro.
tokoam said:
What version of Xposed frameworks did you install I have beta 4 working fine on my mate 10 pro.
Click to expand...
Click to collapse
yeah the bootloop was fixed in beta4 (original comment by dev) which wasn't officially released to the channel when I installed it, so I didn't know about it until I got the bootloop.
Anyways, I just managed to fix my issue. I'll post about it now.
ante0 said:
What does fastboot mode say, unlocked on both phone and frp?
Click to expand...
Click to collapse
what would happens if it says unlock on frp? i cant load twrp i have flashed many times but i does not take it.
I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
Spamming every thread won't help you fix your issue.
Pretoriano80 said:
Spamming every thread won't help you fix your issue.
Click to expand...
Click to collapse
I apologize. I panicked since I don't know what to do. I will continue on the thread which I received a response.
Hello guys,
I've recently got my hands on a not-working P20 Lite, which was stuck on boot with the well-known "your device has failed verification and may not work properly" error message. Since I got stuck on a HUAWEI logo when trying to enter the recovery, ended up in a bootloop trying to enter the download mode, the only way to get the phone working was fastboot. And since I am writing this post, yeah, y'all guessing correctly, it has not been successful. (Error message 'Command not allowed')
After giving up on it and leaving it stuck on the HUAWEI logo for a while, I have noticed that it has turned off. After turning on the device, it shows a green screen with 2, red and blue squares (see attached image), still not being able to boot in recovery mode, however fastboot still somehow manages to fire up.
Any suggestions? Is this phone dead (which I honestly believe), or is there something that would possibly be able to change its state?
Thanks!
EnterPaulini said:
your device has failed verification and may not work properly"
Click to expand...
Click to collapse
EnterPaulini said:
it shows a green screen with 2, red and blue squares
Click to expand...
Click to collapse
Wrong region (oeminfo).
EnterPaulini said:
Is this phone dead?
Click to expand...
Click to collapse
No, not dead yet
Need more information about your phone . Install on your PC "Minimal ADB and fastboot" tool .
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
fastboot oem battery_present_check
and post the results please.
(First try to charge the phone).
(bootloader) :ANE-LX1 9.1.0.372(C432E7R1P7)
(bootloader) ANE-LX1
vendorcountry: hw/eu
(bootloader) :ANE-LX1-CUST 9.1.0.7(C432)
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
(bootloader) 3426mv
Thanks!
Okay, try this way out...
1. in fastboot mode run command
fastboot erase userdata
and try restart the device.
2. download and use a Service ROM
https://androidhost.ru/2AVi
with an sd/card or an USB-OTG flashdrive in dload mode. Unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it! (instruction can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo .(Power+Vol.Up+VolDown).
-Alf- said:
Okay, try this way out...
Click to expand...
Click to collapse
Still hanging in there! Entering the dload mode does not work, I always land on the same green screen and it shuts down.
EDIT:
Back to the "Your device has failed verification and may not work properly" screen. It actually shows the HUAWEI logo again and shows that the device is charging, when turned off. Trying to enter the dload mode results in a bootloop.
EDIT2:
After few times of trying to enter the dload mode I am stuck with the green screen again. From what I have observed, the green screen does not come up when I am connected with the USB cable. When not, everything except fastboot leads to the green screen with a small LED diode blinking red (not so familiar with this phone, no idea what's this for, it's located on the notch). On the other hand, everything except fastboot with cable connected leads to a bootloop. But at least I can see the HUAWEI logo, eh?
Paid service
But if it's a hardware problem (e.g. dead memory), it won't help you.
-Alf- said:
Paid service
But if it's a hardware problem (e.g. dead memory), it won't help you.
Click to expand...
Click to collapse
And if I tried this solution @kikson112 suggested? Doing something with that test point, could this end up working?
I can't help you, that's Greek to me... I have never used this method, nor dc-phoenix (thank goodness).
This happened to my ANE-LX1 a while ago, bootloader never unlocked and device was fully stock...
Device was still under warranty and huawei repaired it for free
Probably a hardware issue
Hey! I have the same problem now. From todays morning it has been stuck on the loading Huawei logo. I haven't got any messages about that warning, you have got, but I have tried to enter the recovery mode and sometimes, it just flashes that green screen with the two squares. Now I think is without power. Have you somehow started the phone?
AmaliaRepova said:
Hey! I have the same problem now. From todays morning it has been stuck on the loading Huawei logo. I haven't got any messages about that warning, you have got, but I have tried to enter the recovery mode and sometimes, it just flashes that green screen with the two squares. Now I think is without power. Have you somehow started the phone?
Click to expand...
Click to collapse
Hello,
some related links:
https://forum.xda-developers.com/t/...-blue-red-flag-fastboot.4339931/post-85697163