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!
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
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
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
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?
HELP...
So I tried to install a new OS Lineage and it everything just went wrong...LOL
I'm stuck in a bootloop and new OS didnt install correctly
But I know there is still some hope... I can boot into TWRP 3.2.1.0 and fastboot and have adb connection.
Just need a little guidance and what my options are from this point.
Huawei Mate 10 Pro BLA-A09C567B127
ha !! os lineage exists for mate 10 pro ? link please
AgentNerull said:
HELP...
So I tried to install a new OS Lineage and it everything just went wrong...LOL
I'm stuck in a bootloop and new OS didnt install correctly
But I know there is still some hope... I can boot into TWRP 3.2.1.0 and fastboot and have adb connection.
Just need a little guidance and what my options are from this point.
Huawei Mate 10 Pro BLA-A09C567B127
Click to expand...
Click to collapse
Download BLA-A09C567B127 firmware and extract UPDATE.APP file from it.
Use Huawei Firmware Extractor (get it from XDA) to open the UPDATE.APP file and extract the system.img and recovery_ramdis.img
Boot your device in fastboot and flash the two images with the following commands :
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash system system.img
Reboot to recovery and do a factory reset. Done!
ericcostes said:
ha !! os lineage exists for mate 10 pro ? link please
Click to expand...
Click to collapse
https://www.xda-developers.com/lineageos-honor-view-10-huawei-mate-10-pro-project-treble/
Pretoriano80 said:
Download BLA-A09C567B127 firmware and extract UPDATE.APP file from it.
Use Huawei Firmware Extractor (get it from XDA) to open the UPDATE.APP file and extract the system.img and recovery_ramdis.img
Boot your device in fastboot and flash the two images with the following commands :
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash system system.img
Reboot to recovery and do a factory reset. Done!
Click to expand...
Click to collapse
THANKS Pretoriano80
flashed both files and factory reset in recovery
but after about 10%, I get a big red Exclamation
any ideas?
Used this firmware. Maybe thats the error
https://forum.xda-developers.com/mate-10/how-to/huawei-mate-10-pro-bla-a09-c567-usa-t3775258
AgentNerull said:
THANKS Pretoriano80
flashed both files and factory reset in recovery
but after about 10%, I get a big red Exclamation
any ideas?
Used this firmware. Maybe thats the error
https://forum.xda-developers.com/mate-10/how-to/huawei-mate-10-pro-bla-a09-c567-usa-t3775258
Click to expand...
Click to collapse
i would use the files from the firmware you were on, in your case it should be B127
That B127 version does not seem as a valid one.At least not on EMUI 9,maybe EMUI 8
P. S. In fastboot mode, use this command to check the current version : fastboot oem get-build-number
Pretoriano80 said:
i would use the files from the firmware you were on, in your case it should be B127
That B127 version does not seem as a valid one.At least not on EMUI 9,maybe EMUI 8
P. S. In fastboot mode, use this command to check the current version : fastboot oem get-build-number
Click to expand...
Click to collapse
BLA-A09 8.0.0.127(C567)
Well... thats what I was afraid of... I still haven't been able to find the original firmware. And the backup I had was years ago and can't seem to find those files.
So is my phone just a paper weight? LOL
not even funkyhuawei has those files
AgentNerull said:
BLA-A09 8.0.0.127(C567)
Well... thats what I was afraid of... I still haven't been able to find the original firmware. And the backup I had was years ago and can't seem to find those files.
So is my phone just a paper weight? LOL
not even funkyhuawei has those files
Click to expand...
Click to collapse
Let me check if i can get those files for you. Eventually hit me on Telegram, it's easier to chat.