Mate 10. So, I tried to install the latest EMUI version using HuRUpdater - bad idea. Now, my phone will not boot. I can enter EMUI Recovery Mode but when I try to receive download package, it says it can't be retrieved. I can also enter Fastboot Mode but the problem with that is that under Device Manager, it only gets recognized as, "Android Bootloader Interface."
Please, any help would be greatly appreciated.
edit: So, fastboot DOES work. What files from what version do I flash to return to stock recovery? I don't even know if Pie was actually written to the device or not before the device rebooted and wouldn't boot.
edit again: I have just successfully installed TWRP via fastboot but it hangs at startup screen - is this because it's not compatible with Pi?
So I've tried flashing ramdisk_recovery.img, kernel.img and system.img from the Pi version but I still can't factory reset the phone. It boots back to the white screen with the android dude and says, "Please update system again."
Any help would be appreciated...
Using Multi-Tool, it detects my device in Fastboot mode as still 8.0.0.143. So, I'm trying to flash System, Ramdisk, Cust, Recovery_Ramdisk and Userdata......all succeed, except one - Ramdisk.img. When I manually try to flash Ramdisk.img in command prompt, it also fails, "FAILED (remote: partition length get error)". In Multi-tool, the error is, "the size or path does not match the file system markup."
Please, does anyone have any other suggestions? I've been at this for nearly 12 hours straight.
I assume u have unlocked bootloader and frb unlocked too if both yes u can search in xda for zip file beta downy 0.4
It will help you to downgrade emui 9 to. Emui 8
If u have unlocked bootloader only I guess u need funky huawei to restore ur devise
I hope I did helped u
Thanks for the reply.
My bootloader is unlocked but how do I know if I have unlocked FRP?
And downy tool requires ADB but I can only access Fastboot.
edit: I just checked and my FRP is also unlocked. What now?
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
essen212 said:
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
Click to expand...
Click to collapse
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Pretoriano80 said:
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Click to expand...
Click to collapse
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
essen212 said:
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
Click to expand...
Click to collapse
Try with EMUI 9 first, then, if it fails, try Oreo. The most important part is finding a DLOAD firmware for your cust/region.
I've fixed it!
Funky emailed me back and I ended up using a different method on their site which worked like a charm. I couldn't recommend them enough.
Hi, good to hear you got it sorted! Would you mind sharing the details on what you had to do differently with FHC? I'm in the same boat here with a mate 10 pro that died on emui9 and I'm not sure if I should go the FHC way or not...
Thx - David
Related
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Meranico said:
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Click to expand...
Click to collapse
If you can boot to "downloader" use rebranding SW, it will fix everything
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
Thank you so much! My mobile phone is working again! :victory:
Edit: Small problem persists: I cannot use the buttons left and right of the scanner. They do not react.
Edit2: Could fix this. I flashed B120 and the buttons worked again.
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
whats rebranding sw and hoe do i do it as i have the smae problem please help
corey568brown said:
whats rebranding sw and hoe do i do it as i have the smae problem please help
Click to expand...
Click to collapse
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Meranico said:
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Click to expand...
Click to collapse
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
corey568brown said:
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
Click to expand...
Click to collapse
Good to know!
As I had the same problem as you do know: I flashed B120, which does not seem to have the bug with the buttons and upgraded via Firmware Finder to B130 and then to B150.
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
So I was on honor 9 stf-l09c432b182 with openkirins twrp and had sideloaded Supersu and everything was working fine.
My plan was to uninstall root, flash stock recovery and upgrade to B183.
So I uninstalled supersu, flashed the recovery.img and recovery2.img in fastboot.
Then I tried to install B183 with the system updater of emui. Failed in the middle of the process.
So then I tried to manually flash system.img, cust.img, recovery.img, recovery2.img, boot.img(basically everything that doesn't give the error: remote command not allowed)
from B183 and when I rebooted i had a really weird version number( similar to this: https://forum.xda-developers.com/honor-9/help/strange-version-t3699280).
Now heres the part where I probably bricked some stuff: I was really concerned and tried to flash my old B180 firmware and then my device is stuck at the screen: Your device can't be trusted...
(http://s1.postimg.org/yilteiv0f/bab3a651_1dcc_4073_88ec_8172118b7227.jpg)
Your device is booting now.
I tried to relock and unlock the bootloader, but does not work.
Tried: fastboot oem lock, fastboot oem relock, fastboot flashing lock
Now current status:
I can boot into bootloader via volume down+ plug in.
Oem and frp are unlocked.
I can hold down volume up and go into erecovery but trying to install something from there didn't work.
I can charge my phone.
Something similar happened to this guy here: https://forum.xda-developers.com/honor-8/help/stuck-device-booting-t3650016 but he was lucky to find someone who repaired it for him.
I would thank you all soo much if you could help me, or just give me a tip what I can do.
Thanks for all replies
You should try to full restore to service repair stock working firmware with sdcard :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Alternatively, you could try to downgrade to stock firmware without rebrandind (no sdcard needed) :
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
I think that Rebrand method is the best way for this situation.
Dload with B130 dont help , its happen to me.
If boot after Rebrand method , let it restart several times.
Erecovery will appear then made wipe data/ factory reset.
If dont work again , Erecovery , wipe cache partition.
We can not rollback and upgrade as we want with Huawei..
All done step by step . But work for B120.
k1ks said:
I think that Rebrand method is the best way for this situation.
Dload with B130 dont help , its happen to me.
If boot after Rebrand method , let it restart several times.
Erecovery will appear then made wipe data/ factory reset.
If dont work again , Erecovery , wipe cache partition.
We can not rollback and upgrade as we want with Huawei..
All done step by step . But work for B120.
Click to expand...
Click to collapse
Which version should I use for rebrand ? B120 ?
If yes, I cant find any download links for B120 zips.
Thanks for your reply.
https://yadi.sk/d/Y2yuM--73Lb9Kk
This link
k1ks said:
https://yadi.sk/d/Y2yuM--73Lb9Kk
This link
Click to expand...
Click to collapse
Ok thank you so much my phone is now working again on B120, what a trip!
Lukalion said:
Ok thank you so much my phone is now working again on B120, what a trip!
Click to expand...
Click to collapse
Youre welcome , , a little spicy huawei.
I had the same mishap.
I think we have to wait for a possible fix of the twrp , nothing is stable at the moment.
Too much random behavior.
Lukalion said:
Ok thank you so much my phone is now working again on B120, what a trip!
Click to expand...
Click to collapse
So which file you used for that? I downloaded all three files from that yandex link. What to do now? I tried many different things up to now and everytime the update failed via that installer at 5%.
Freakeee93 said:
So which file you used for that? I downloaded all three files from that yandex link. What to do now? I tried many different things up to now and everytime the update failed via that installer at 5%.
Click to expand...
Click to collapse
These B120 are unaproved, so to install them you need a no-check recovery.
Follow this guide while skipping step 7 :
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
oslo83 said:
These B120 are unaproved, so to install them you need a no-check recovery.
Follow this guide while skipping step 7 :
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
Click to expand...
Click to collapse
But that HWOTA.zip is not available anymore. So I did't knew what to do.
Edit: Found it... It's edited from the mod. Am trying if the download is ready.
It works again!!!! Great and thank you for your help!:good::good::good:
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Arseon said:
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Click to expand...
Click to collapse
Go to TWRP and restore your system backup.
kilroystyx said:
Go to TWRP and restore your system backup.
Click to expand...
Click to collapse
But I didn't install a custom recovery. So no TWRP
Arseon said:
But I didn't install a custom recovery. So no TWRP
Click to expand...
Click to collapse
So, then try flash same system partition via fastboot.
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
What your build ?
If this phone with OREO or with NOUGAT / Android 8.x or 7.x ?
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Arseon said:
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Click to expand...
Click to collapse
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
kilroystyx said:
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
Click to expand...
Click to collapse
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Arseon said:
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Click to expand...
Click to collapse
It seems like you are doing well, but have you read the instructions carefully? They recommend when something fail.
https://www.dc-unlocker.com/huawei-phone-flashing-in-fastboot
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
AND very important : do not relock the bootloader !
ONLY if bootloader 'unlockt' you can self-repair !
JamesBott said:
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
Click to expand...
Click to collapse
Mine is ANE-AL00 8.0.0.131(C675). I used ANE-AL00C00B131 (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2370/g1789/v138744/f1/full/filelist.xml ) to flash
JamesBott said:
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
Click to expand...
Click to collapse
Sadly no. Both bootloader and frp are locked.
JamesBott said:
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
Click to expand...
Click to collapse
Since bootloader and frp locked, adb commands are not working. Hence I'm using DCPheonix to flash the file. But without luck. It's still botting to eRecovery only
your phone is C675, you flash C00 : no correct
now is inside your phone a 'mix'
i think, you can no self-repair - sorry
@Arseon, my opinion your system partition is a mess due to xposed installation fail.
The solution for this case is restore system partition, it worked for me in the past.
In some cases we can get lucky install a clean system partition even if it is from other region code, because the main differences between regions are located in the other partitions
But what I learning is that system from C00 region don’t follow this standard because at least is missing google apps.
With DCPheonix did with get lucky and flash all files or just the first 4 and stop in the PACKAGE_TYPE?
same situation
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Edit: I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
alvavaca said:
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Click to expand...
Click to collapse
This thread can help you a lot => HuRUpdater
kilroystyx said:
This thread can help you a lot => HuRUpdater
Click to expand...
Click to collapse
Thks for your help, I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Arseon said:
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
Click to expand...
Click to collapse
In pretty sure you are flashing the wrong firmware, try to push your version with dc-unlocker in fastboot and download the excatly matching firmware. Good luck
well, i have all of this+one more tougher stuff..
Well, I tried to install a custom ROM on my P20 Lite (ane-lx1) via TWRP aand when I failed I ended up into a bootloop, but the thing that got me a headache after a full day of forum research is that when I attempted to install the custom ROM the TWRP wanted a .img file, not a .zip file, so I rebooted after I alreday wiped out everything, I made a backup into the phone, BUT I cant access it because.. the TWRP freezes every time at the TeamWin logo.....the only thing that is accessible now its the fastboot&rescue mode and I'm out of juice and desperated...the bootloader is enabled...i think i preety much killed my phoen and my brain trying to get an android stock experience...i really have to get some sleep,well..thank you for your attention, if you have any suggestions that would pick me up from this mess I would be very greatfull, i'll see what i had left to do as soon as i'm able to...for now, have a good night/day/afternoon, whatever side of the world you're from
Edit:
I left the phone all night into bootloobing and after it got FULLY discharged, I dont know exactly how but the TWRP hasn't popped out, instead after this I was able to get into eRecovery and now it is downloading the 146(C432) version. I guess that I got lucky
I bricked my huawei mate 10. Please help. TIA
me 2
You have to give more information if you want us to provide a viable (if there are any) solution. What firmware were you on, what firmware were you trying to install?
i was trying to install xposed
bootloop
me too please help
I'd really appreciate your help
I have a Huawei Mate 10 on Android Oreo 8.0 rooted and bootloader unlocked
Lock state info:
FB LockState: LOCKED
USER LockState: UNLOCKED
Current build number:
System 8.0.0.38(0310)
Product model:
ALP-L29
I tried installing Xposed Framework ... after installation got in a bootloop
eRecovery doesn't work
I don't have TWRP
can only enter fastboot
the device has an SD card slot but I'm confused because some say upgrading or formatting it works and some say it doesn't .
I just want the device to boot ... I don't care about the data
please kindly help
thanks in advance
hero3210 said:
me too please help
I'd really appreciate your help
I have a Huawei Mate 10 on Android Oreo 8.0 rooted and bootloader unlocked
Lock state info:
FB LockState: LOCKED
USER LockState: UNLOCKED
Current build number:
System 8.0.0.38(0310)
Product model:
ALP-L29
I tried installing Xposed Framework ... after installation got in a bootloop
eRecovery doesn't work
I don't have TWRP
can only enter fastboot
the device has an SD card slot but I'm confused because some say upgrading or formatting it works and some say it doesn't .
I just want the device to boot ... I don't care about the data
please kindly help
thanks in advance
Click to expand...
Click to collapse
More info:
fastboot oem get-product-model
...
(bootloader) ALP-L29
fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
fastboot oem get-build-number
...
(bootloader) :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 inform me of how to flash update.zip because I get an error
or place in in SD card because UPDATE.APP is more than 4GB ..
I think for the experienced, my problems are fairly easy to fix so please help ... I appreciate any suggestion. Thank you.
royhanks3 said:
You have to give more information if you want us to provide a viable (if there are any) solution. What firmware were you on, what firmware were you trying to install?
Click to expand...
Click to collapse
ALP-L29 bootloader unlocked.
Rooted
I am just struck in bootloop.
Erecovery doest help. I have the firmware(update.app) just tell me how to flash the stock rom i.e (update.app)
Thanks in advance.
Please help
Karthik1898 said:
ALP-L29 bootloader unlocked.
Rooted
I am just struck in bootloop.
Erecovery doest help. I have the firmware(update.app) just tell me how to flash the stock rom i.e (update.app)
Thanks in advance.
Please help
Click to expand...
Click to collapse
You need to unpack the update.app with Huawei Update Extractor and get the system.img.Then flash it with fastboot and check if it boots.
Pretoriano80 said:
You need to unpack the update.app with Huawei Update Extractor and get the system.img.Then flash it with fastboot and check if it boots.
Click to expand...
Click to collapse
How can this be done?
Tumpster said:
How can this be done?
Click to expand...
Click to collapse
I've just told you in my previous post, lol.
Use this guide - > https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733 <- to extract the system.img and then flash the image with this command : fastboot flash system system.img
Then reboot the with "fastboot reboot" command and hope that your system boots.
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
As i know you cannot downgrade from pie to oreo try to flash back the pie files as u did before with HWOTA8 and see if the devise boot
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
Flash back stock pie kernel. Hwota flashes recovery and kernel (and ramdisk which fails because there is no ramdisk partition in pie). If kernel doesn't work because its corrupt or wrong (pie kernel is 4.9 while Oreo use 4.4) your device can't boot recovery or boot to system.
You can downgrade using TWRP but you'd have to do it manually.
Antidote03 said:
As i know you cannot downgrade from pie to oreo try to flash back the pie files as u did before with HWOTA8 and see if the devise boot
Click to expand...
Click to collapse
Thanks for the suggestion. I tried flashing back the pie files using HWOTA8 but the software requires you to boot to recovery in order for the installation to continue but the device won't boot to recovery, it's just stuck on device is booting now screen.
---------- Post added at 11:42 AM ---------- Previous post was at 11:39 AM ----------
ante0 said:
Flash back stock pie kernel. Hwota flashes recovery and kernel (and ramdisk which fails because there is no ramdisk partition in pie). If kernel doesn't work because its corrupt or wrong (pie kernel is 4.9 while Oreo use 4.4) your device can't boot recovery or boot to system.
You can downgrade using TWRP but you'd have to do it manually.
Click to expand...
Click to collapse
Thanks for the explanation. At least I have an idea now what caused the issue . If it's fine do you have the steps or link which provides steps how to downgrade using TWRP?
Carnage! said:
Thanks for the explanation. At least I have an idea now what caused the issue . If it's fine do you have the steps or link which provides steps how to downgrade using TWRP?
Click to expand...
Click to collapse
Look here - > https://forum.xda-developers.com/mate-10/how-to/how-people-bricked-phone-rebranding-ota-t3797555 <- use the Huawei Update Extractor tool to get the image files than flash with fastboot.
kernel = fastboot flash kernel kernel.img
system = fastboot flash system system.img
recovery = fastboot flash recovery_ramdisk recovery.img
Obviously, replace image name with the ones you are using.
For downgrading, download this tool - > https://mega.nz/#!oxkQWApD!-PtLtrekX3DS-iglnr7xpdB1285dF1nZSiOSHyZsqKA <- unpack it on your PC, launch Flash.bat and follow the On Screen instructions .
Now you got it why you shouldn't spam threads? You get answers all over the forum, which is not nice.
Pretoriano80 said:
Look here - > https://forum.xda-developers.com/mate-10/how-to/how-people-bricked-phone-rebranding-ota-t3797555 <- use the Huawei Update Extractor tool to get the image files than flash with fastboot.
kernel = fastboot flash kernel kernel.img
system = fastboot flash system system.img
recovery = fastboot flash recovery_ramdisk recovery.img
Obviously, replace image name with the ones you are using.
For downgrading, download this tool - > https://mega.nz/#!oxkQWApD!-PtLtrekX3DS-iglnr7xpdB1285dF1nZSiOSHyZsqKA <- unpack it on your PC, launch Flash.bat and follow the On Screen instructions .
Now you got it why you shouldn't spam threads? You get answers all over the forum, which is not nice.
Click to expand...
Click to collapse
Thanks for the steps. I will try it later and will let you know. I really apologize for spamming since I panicked and I don't know where to get help. I will continue and reply to this thread only moving forward.
Carnage! said:
Thanks for the steps. I will try it later and will let you know. I really apologize for spamming since I panicked and I don't know where to get help. I will continue and reply to this thread only moving forward.
Click to expand...
Click to collapse
I would start with just flashing kernel. Flashing system can disable Oem unlock, which will result in frp lock in fastboot.
@Pretoriano80
Thx this has Fixed my Phone
In Huawei Service Center they are not able to fix the Firmwarefail *rofl*
ante0 said:
I would start with just flashing kernel. Flashing system can disable Oem unlock, which will result in frp lock in fastboot.
Click to expand...
Click to collapse
I think he already flashed system once! ?
ante0 said:
I would start with just flashing kernel. Flashing system can disable Oem unlock, which will result in frp lock in fastboot.
Click to expand...
Click to collapse
Got it. Thanks again for all the help!
I will try to be brief, I've tried to root my Y6- L22 (2018) Huawei, but I think I flash a bad ROM or got mixup with the TWRP command.
I am now trying to flash the original firmware to have a functional phone. I've tried the method with Huawei Update Extractor and flashing the following:
fastboot flash system SYSTEM.img
fastboot flash ramdisk ramdisk.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
All the process is running smoothly with OKAY everywhere but when I reboot my phone goes to ‘Huawei’(with the lovely and annoying Huawei ring) then it reboot again. I tried different Firmware as I do not have the Built version/regional Number, but none are working.
I've also tried the dload method with the Update.app in the microSD... but getting Software install failed after 5%.
In the meantime I’ve also erase system, and erase cache and install firmware without any success
I would appreciate to have some suggestion or advice from any of you that have faced this issue or know how to get out of this.
Many thanks,
MrKMr said:
I will try to be brief, I've tried to root my Y6- L22 (2018) Huawei, but I think I flash a bad ROM or got mixup with the TWRP command.
I am now trying to flash the original firmware to have a functional phone. I've tried the method with Huawei Update Extractor and flashing the following:
fastboot flash system SYSTEM.img
fastboot flash ramdisk ramdisk.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
All the process is running smoothly with OKAY everywhere but when I reboot my phone goes to ‘Huawei’(with the lovely and annoying Huawei ring) then it reboot again. I tried different Firmware as I do not have the Built version/regional Number, but none are working.
I've also tried the dload method with the Update.app in the microSD... but getting Software install failed after 5%.
In the meantime I’ve also erase system, and erase cache and install firmware without any success
I would appreciate to have some suggestion or advice from any of you that have faced this issue or know how to get out of this.
Many thanks,
Click to expand...
Click to collapse
07/06/19
Hi All, so I've not had any reply, but I keep trying to fix this Y6 phone.
Just answering to myself in case this can help someone; if you happen to lose the Built Number and phone is not working, you can check if retailer are still selling this phone. If yes, it is likely that they have the same built number and regional code. For mine it is ATU-L22 - 8.0.0.140 (C185).
MrKMr said:
07/06/19
Hi All, so I've not had any reply, but I keep trying to fix this Y6 phone.
Just answering to myself in case this can help someone; if you happen to lose the Built Number and phone is not working, you can check if retailer are still selling this phone. If yes, it is likely that they have the same built number and regional code. For mine it is ATU-L22 - 8.0.0.140 (C185).
Click to expand...
Click to collapse
hi. how did you fixed the bootloop?