Similar with many other soft brick problems, I updated my Mate20 Pro (C800E18R1P16, Softbank, Japan) to a mismatched version LYA-L09 10.0.0.154(C432E7R15) from post https://forum.xda-developers.com/mate-20-pro/help/lya-l09-emui-10-firmware-t4021495. However, without any luck, update failed. I got message "Your device has loaded a different operating system". I seems the emui10 rom still not ready in my region... :crying:
I have tried several solutions, but all failed.
1. tried other mismatched EMUI10 ROM (rename and w/o rename). Failed, of course.
2. tried matched EMUI9.1 ROM to rollback sys. Failed.
3. tried mismatched EMUI9.1 ROM. Failed. <- this is how i update from 9.0 to 9.1.
All this solutions are OTG style. Since my bootloader is locked, I cannot try fastboot.
I think I'm stucked here. Please help!
Thank you so much!
try dload ??
aureliolage said:
try dload ??
Click to expand...
Click to collapse
Yes, all tried OTG update used dload, but failed.
ChingRyu said:
Yes, all tried OTG update used dload, but failed.
Click to expand...
Click to collapse
So you are with
EMUI10 base
EMUI cust undetermined version
EMUI preload undetermined version
At first, cust&preload just need to be at emui10 version. DC-Phoenix could help force flash cust &/or preload both to some EMUI10 any vendorcountry which would succeed.
Then in a second time, once booting to normal mode just fine, you could fix them to proper vendorcountry hicloud's cust&preload by forced patched hisuite process (proxy/dns).
ChingRyu said:
Similar with many other soft brick problems, I updated my Mate20 Pro (C800E18R1P16, Softbank, Japan) to a mismatched version LYA-L09 10.0.0.154(C432E7R15) from post https://forum.xda-developers.com/mate-20-pro/help/lya-l09-emui-10-firmware-t4021495. However, without any luck, update failed. I got message "Your device has loaded a different operating system". I seems the emui10 rom still not ready in my region... :crying:
I have tried several solutions, but all failed.
1. tried other mismatched EMUI10 ROM (rename and w/o rename). Failed, of course.
2. tried matched EMUI9.1 ROM to rollback sys. Failed.
3. tried mismatched EMUI9.1 ROM. Failed. <- this is how i update from 9.0 to 9.1.
All this solutions are OTG style. Since my bootloader is locked, I cannot try fastboot.
I think I'm stucked here. Please help!
Thank you so much!
Click to expand...
Click to collapse
The problem arises for many who tried to update 10 android or go to 9.1. Errors are not correct. Need to use AOD. The issue is resolved,
You can find out information through fastboot
fastboot oem oeminforead-BASE_VERSION
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-PRELOAD_VERSION
I fixed OP's device 2 days ago.
Force updating its cust&preload to emui10 'unbricked' itS emui10.
Now his problem is about using a chinese simcard with calls working on a L29 device...
Similar issue
oslo83 said:
I fixed OP's device 2 days ago.
Force updating its cust&preload to emui10 'unbricked' itS emui10.
Now his problem is about using a chinese simcard with calls working on a L29 device...
Click to expand...
Click to collapse
Hello I'm having a similar issue with my mate 20 pro. can you help me?
Mismatched tried to upgrading it to EMUI 10 via dload mode, now phone is stuck in eRecovery.
Already tried flashing again firmware with correct info without any success.
This is the info I get now on fastboot:
Model: LYA-L09
vendor/region: tigo /la
get-build-number:
(bootloader) :STK-L03B 9.1.0.350(C605E7)
oeminforead-BASE_VERSION :LYA-LGRP2-OVS 9.1.0.350
oeminforead-CUSTOM_VERSION :STK-L03B-CUST 9.0.1.7(C605)
oeminforead-PRELOAD_VERSION:LYA-L09-PRELOAD 9.0.0.19(C45R1)
Can you please help me?
juanocastro813 said:
Hello I'm having a similar issue with my mate 20 pro. can you help me?
Mismatched tried to upgrading it to EMUI 10 via dload mode, now phone is stuck in eRecovery.
Already tried flashing again firmware with correct info without any success.
This is the info I get now on fastboot:
Model: LYA-L09
vendor/region: tigo /la
get-build-number:
(bootloader) :STK-L03B 9.1.0.350(C605E7)
oeminforead-BASE_VERSION :LYA-LGRP2-OVS 9.1.0.350
oeminforead-CUSTOM_VERSION :STK-L03B-CUST 9.0.1.7(C605)
oeminforead-PRELOAD_VERSION:LYA-L09-PRELOAD 9.0.0.19(C45R1)
Can you please help me?
Click to expand...
Click to collapse
I thikns you see
oeminforead-CUSTOM_VERSION :STK-L03B-CUST 9.0.1.7(C605)
its wrong
Related
Hello! Some day i want to downgrade my Marshmallow to Lollipop. I installed stock ROM to my Honor 5X but in older android - Lollipop 5.1. And I get bricked it. On start on screen i can see first-step logo honor after it i can see second-step honor's logo and here i wait 30 minutes and nothing 45 minutes and nothing. Worse is this I can't back to my stock Marshmallow, when I'm installing my previous ROM - MM i get the same brick on second-step logo. I installed a few more ROMs and nothing. My bootloader is unlocked but when i try to flash cust/system by fastboot appear an error. FAILED (remote: Command not allowed). I think i tried everything, thank for help me.
PS. Sorry for bad English :/
EDIT.1 I tried to use this method from Thread: http://forum.xda-developers.com/honor-5x/help/ive-bricked-honor-5x-t3324225. But the same problem at fastboot.
cust and system won't get flashed on 5X, try force updating it with an UPDATE.APP package for your device.
Put it inside dload folder in root of the Sdcard, and press all three buttons (Vol UP + Vol DOWN + Power) after switching off your phone, to start updating.
Sent from my PLK-L01 using Tapatalk
Thank you. But i tried to get ROM back by UPDATE.APP and when i want to go back to Marshmallow i get second-step honor logo and nothing after it. When i want to get Lollipop i have error "Software can't be installed" - something like that. I heard something about "Transition package" or "Downgrade Package" ? Maybe it can be work. But i can't find those packages for honor 5x KIW-L21.
Bayont said:
Thank you. But i tried to get ROM back by UPDATE.APP and when i want to go back to Marshmallow i get second-step honor logo and nothing after it. When i want to get Lollipop i have error "Software can't be installed" - something like that. I heard something about "Transition package" or "Downgrade Package" ? Maybe it can be work. But i can't find those packages for honor 5x KIW-L21.
Click to expand...
Click to collapse
If the Marshmallow update went through a bit, then you'll need transition package, so take on some pain to find it. It should be out there somewhere.
Sent from my PLK-L01 using Tapatalk
That's maybe becouse i don't remove ROOT and Xposed before installing ROM, how to unroot by TWRP?
Bayont said:
That's maybe becouse i don't remove ROOT and Xposed before installing ROM, how to unroot by TWRP?
Click to expand...
Click to collapse
If you use the this version of TWRP > https://www.androidfilehost.com/?fid=24588212152305793
you can flash system.img and cust.img extracted from your Update.APP with HuaweiUpdateExtractor
fastboot boot twrp.img
then copy the files to the phone
then choose Install / Install Image / system.img or cust.img or recovery.img boot.img ..you choose
Also just saying your have a L21 does not help
is it KIW-L21 C432 or KIW-L21 C185
Now i backed to B130 and i have loop with message Optimizing system... this process going to 100% and phone reboot. And it looping.
Bayont said:
Now i backed to B130 and i have loop with message Optimizing system... this process going to 100% and phone reboot. And it looping.
Click to expand...
Click to collapse
your post tells us nothing about what you did, are we suppose to guess ?
if you successfully flashed System.img - boot .img - cust.img and recovery.img you can now use the dload / Update.app
clsA said:
if you successfully flashed System.img - boot .img - cust.img and recovery.img you can now use the dload / Update.app
Click to expand...
Click to collapse
Done but without any effect, the same problem, stuck at second-step honor logo ;/
Any ideas?
Bayont said:
Any ideas?
Click to expand...
Click to collapse
Well considering I still don't know what you have done. Its hard to guess the next step
Sent from my SM-N920T using Tapatalk
Ok, one more time. When i'm installing any ROM B130 or B330, stock or official doesn't matter, the same problem. After installing rom by UPDATE.APP my phone booting and booting and booting and nothing. When i'm installing rom images by TWRP - boot, cust, system It's the same problem Booting, booting and nothing. When i tried to flash rom by fastboot i have error: FAILED (remote: Command not allowed). I would like to try this: http://forum.xda-developers.com/honor-5x/help/how-restore-cust-partition-t3356769 But i don't know how to access to adb shell: when i type "adb shell" in cmd where i have adb it say to me: error: device '(null)' not found. I don't know what to do more.
How much time honor 5x system is installing?
How i can check my honor is KIW-L21 C432 or KIW-L21 C185?
Bayont said:
How i can check my honor is KIW-L21 C432 or KIW-L21 C185?
Click to expand...
Click to collapse
If you tried to install the wrong Update.app the updater would get to 5% and stop and eventually just reboot. Did you actually watch the update go to 100% and reboot ?
I think i found source of my problem. When i want to downgrade my system was B340.
I read something about downgrade. Without Transition Package I can't downgrade my system I can install only the same (B340) or higher.
This making brick when i'm installing B330 or B140.
Now i'm trying to install OTA B340 and i have another problem,
when i have B330 and installing B340 by small OTA 124MB I have stuck on 5% of installing. It becouse:
EDIT 2 : If you come from B330, don't try to flash the small B340 update as local update has simply been disabled by theHuawei/Honor devs !
Worse, with B340 you won't be able to downgrade to any lower version : at least not easily... INFO FROM: HERE
Click to expand...
Click to collapse
But when i'm installing B130 by TWRP and upgrading to B340 by big upgrade (1,36GB) it's stucking on 0% and i get info: DO NOT UNPLUG....
I think that becouse my version isn't B130 only B140. I'm checking it by DC-UNLOCKER. Output from it:
Code:
Found Phone : KIW-L21
Model : Huawei phone in fastboot mode
Serial NR. : My Serial
Firmware : KIW-L21C432B140
FB LockState: LOCKED
widevine LockState: UNLOCKED
Bootloader Lock State: UNLOCKED
Root State: ROOT
Bootloader WidevineKey: WidevineKey_VALID
System State: Bootloader in UNLOCKED state
Bootloader Version: 001.001.000
Battery state: battery is present
Maybe I should Restore backup from diffrent KIW-L21 by TWRP?
Bayont said:
I think i found source of my problem. When i want to downgrade my system was B340.
I read something about downgrade. Without Transition Package I can't downgrade my system I can install only the same (B340) or higher.
This making brick when i'm installing B330 or B140.
Now i'm trying to install OTA B340 and i have another problem,
when i have B330 and installing B340 by small OTA 124MB I have stuck on 5% of installing. It becouse:
But when i'm installing B130 by TWRP and upgrading to B340 by big upgrade (1,36GB) it's stucking on 0% and i get info: DO NOT UNPLUG....
I think that becouse my version isn't B130 only B140. I'm checking it by DC-UNLOCKER. Output from it:
Code:
Found Phone : KIW-L21
Model : Huawei phone in fastboot mode
Serial NR. : My Serial
Firmware : KIW-L21C432B140
FB LockState: LOCKED
widevine LockState: UNLOCKED
Bootloader Lock State: UNLOCKED
Root State: ROOT
Bootloader WidevineKey: WidevineKey_VALID
System State: Bootloader in UNLOCKED state
Bootloader Version: 001.001.000
Battery state: battery is present
Maybe I should Restore backup from diffrent KIW-L21 by TWRP?
Click to expand...
Click to collapse
Normally restoring a TWRP backup is no different than flashing System.img and boot.img
your bootloop is firmware related ... you need the full B340 package
Yes, you written in Honor 5x Repo:
Waiting for full B340 to appear on Honor support site.
Click to expand...
Click to collapse
At the moment there isn't any full B340 ROM for download. And any OTA B340 doesn't work for me, yes? For example:
B140 -> B340
http://update.hicloud.com:8180/TDS/d...ull/update.zip
changelog
http://update.hicloud.com:8180/TDS/d.../changelog.xml
Click to expand...
Click to collapse
Bayont said:
Yes, you written in Honor 5x Repo:
At the moment there isn't any full B340 ROM for download. And any OTA B340 doesn't work for me, yes? For example:
Click to expand...
Click to collapse
Then you just have to wait
I don't publish the updates I just post them
Sent from my SM-N920T using Tapatalk
I can't back to Stock Lolipop by editing some files or install B340 from B140 by OTA
Hi,
As descripted in the title I can not restore my Honor 9 Anymore... I don't know what I did wrong but when I flash a new recovery or so in Fastboot I get the error "partion length error")
Any idea how I can fix this?
I have access to:
- TWRP Oreo (ADB not working)
- Fastboot Mode
- E-Recovery.
Do You used this command?:
fastboot flash recovery_ramdisk "name of your recovery"
4r44444 said:
Hi,
As descripted in the title I can not restore my Honor 9 Anymore... I don't know what I did wrong but when I flash a new recovery or so in Fastboot I get the error "partion length error")
Any idea how I can fix this?
I have access to:
- TWRP Oreo (ADB not working)
- Fastboot Mode
- E-Recovery.
Click to expand...
Click to collapse
Hello, I'm in Italy too I have the same problem are on oreo B360 C432 and 'I have only erecovery and bootloader flapped. IF you solved, please tell me how you did it. thank you
The same problem, with b 183 I was updating to b360, but after updating my phone just stands in Huawei eRecovery. I'm trying eRecovery and I can not find anything. 2 days I'm trying stock rom via sd card (dload) and nothing. I read the entire xda website and they do not help me. so please help me. my phone is locked and FRP locked. Essentially, I had this update through FF and after that the phone just stopped in eRecovery mode, and nothing has helped me for 2 days, my eyes are like the owl
comibumbar said:
The same problem, with b 183 I was updating to b360, but after updating my phone just stands in Huawei eRecovery. I'm trying eRecovery and I can not find anything. 2 days I'm trying stock rom via sd card (dload) and nothing. I read the entire xda website and they do not help me. so please help me. my phone is locked and FRP locked. Essentially, I had this update through FF and after that the phone just stopped in eRecovery mode, and nothing has helped me for 2 days, my eyes are like the owl
Click to expand...
Click to collapse
I've just solved with DC PHOENIX. What is fundamental is to put the same firmware before the brick. You can do it yourself using the appropriate section.
I got into this problem and fixed it.
I downloaded treble os and flashed it in fastboot then used adb commands to restore mine
superuser590 said:
I got into this problem and fixed it.
I downloaded treble os and flashed it in fastboot then used adb commands to restore mine
Click to expand...
Click to collapse
Can you explain it to me? I'm in the same situation right now.
themagicalmage22 said:
Can you explain it to me? I'm in the same situation right now.
Click to expand...
Click to collapse
Did you fix it or do you still need help?
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 tried to unroot my phone using SuperSU and failed so then I restarted my phone and now its doesn't continue to load. :crying: I also tried the eRecovery to restore and failed also to download latest version (Getting package info failed). I also tried to wipe/reformat and it doesn't work either. Now it just keep on loading and after a few minutes it will restart vice versa. Please help me :crying:
enderes05 said:
I tried to unroot my phone using SuperSU and failed so then I restarted my phone and now its doesn't continue to load. :crying: I also tried the eRecovery to restore and failed also to download latest version (Getting package info failed). I also tried to wipe/reformat and it doesn't work either. Now it just keep on loading and after a few minutes it will restart vice versa. Please help me :crying:
Click to expand...
Click to collapse
Use this guide to extract RAMDISK from your firmwares update.zip and flash using fastboot.
https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
Or tell me your firmware and I can do it, but you'll have to wait a couple of hours.
ante0 said:
Use this guide to extract RAMDISK from your firmwares update.zip and flash using fastboot.
https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
Or tell me your firmware and I can do it, but you'll have to wait a couple of hours.
Click to expand...
Click to collapse
I tried to use fastboot command to get the product model and phone build number but it doesn't detect my phone in PC that means I dont know what firmware to download.
enderes05 said:
I tried to use fastboot command to get the product model and phone build number but it doesn't detect my phone in PC that means I dont know what firmware to download.
Click to expand...
Click to collapse
I tried again and it works
BLA-L29 8.0.0.129(C185)
Same issue here
enderes05 said:
I tried again and it works
BLA-L29 8.0.0.129(C185)
Click to expand...
Click to collapse
Hi,
I am also facing same issue. Adb & fastboot tool is not able to identify my device.
Can you guide me, how did u resolve issue on your mobile?
enderes05 said:
I tried to use fastboot command to get the product model and phone build number but it doesn't detect my phone in PC that means I dont know what firmware to download.
Click to expand...
Click to collapse
Try Firmware Finder for Huawei, but it only in app recognizes the exact model example : My Phone RNE-L03 but for the correct firmware it adds an C178, if you have your exact model download the 3 files indicated in FFH
Good Luck!
Update : I now read the rest of the quote...i don't know what is the problem exactly, but FFH works fine for forced OTA updates and firmwares provider for me
problem
I have this problem too. I cant fix it
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