Related
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!
All new update from (pro-teammt.ru) after 9.0.231 failed to flash by EMUI 1.1 Flasher, or by fastboot, giving error during last step (Huawei erecovery). My phone is unlocked mate 10 pro C185. Is the recent firmwares are different. or error in my phone?
BSAKotb said:
All new update from (pro-teammt.ru) after 9.0.231 failed to flash by EMUI 1.1 Flasher, or by fastboot, giving error during last step (Huawei erecovery). My phone is unlocked mate 10 pro C185. Is the recent firmwares are different. or error in my phone?
Click to expand...
Click to collapse
What kind of error?
Edit: Maybe you meant B271?In that case, try B274!
verification error at 5% in Huawei erecovery
In internet search some suggest flash of service firmware to resolve this type of error.
Is safe to flash older pie firmware (9.0.0.177) my current is 9.0.0.231 (model BLA-L29C185)?
Can any one help?
BSAKotb said:
In internet search some suggest flash of service firmware to resolve this type of error.
Is safe to flash older pie firmware (9.0.0.177) my current is 9.0.0.231 (model BLA-L29C185)?
Can any one help?
Click to expand...
Click to collapse
That's not the issue! You should try to flash B258 or B259, i don't recall which one was released as OTA for C185.
The problem with these new firmwares is that even if are looking as "unified" for all customs, they are not.
Edit : Found it! B258 was released for C185, so your best shot is to try flashing that one from FF.
@Pretoriano80
Thank you for your reply, I will try and report the result
I tried to flash firmware 258 but gives same error
Then I flashed 177 (2 files) success, and phone download and update small file automatically
I tried to flash firmware from 258 (pro-teammt.ru) failed with same error
I left the phone to download and update itself and successfully updated to 258
Are the files different , or Huawei modified erecovery to check before update?
Regards magisk, how to extract installed boot image (unlocked without root)
BSAKotb said:
I tried to flash firmware 258 but gives same error
Then I flashed 177 (2 files) success, and phone download and update small file automatically
I tried to flash firmware from 258 (pro-teammt.ru) failed with same error
I left the phone to download and update itself and successfully updated to 258
Are the files different , or Huawei modified erecovery to check before update?
Regards magisk, how to extract installed boot image (unlocked without root)
Click to expand...
Click to collapse
Hmm! That's odd, if EmuiFlasher works on C432, it should work on C185 too, at least if there's nothing wrong with the update file.
As for root, extract the recovery_ramdisk.img with Huawei Extractor, patch it with Magisk Manager and then flash the patched ramdisk in fastboot mode.
@Pretoriano80
I extracted the recovery_ramdisk.img with Huawei Extractor, patch it with recent Magisk Manager and then flash the patched ramdisk in fastboot mode. I followed all steps exactly, but stuck at booting after pressing the phone boot in safe mode with safe mode window (the system has detected an app launch anomaly and has entered safe mode and it is recommended that you install any recently pr updated third party apps to resume normal launch) and gives lists of recently installed with first item is magisk manager. After uninstall magisk manager, the phone boot normally but without root and magisk
Any help to root?
https://drive.google.com/open?id=11_-f_nY-mLZirU03TYHdaAgGELoykli1
BSAKotb said:
@Pretoriano80
I extracted the recovery_ramdisk.img with Huawei Extractor, patch it with recent Magisk Manager and then flash the patched ramdisk in fastboot mode. I followed all steps exactly, but stuck at booting after pressing the phone boot in safe mode with safe mode window (the system has detected an app launch anomaly and has entered safe mode and it is recommended that you install any recently pr updated third party apps to resume normal launch) and gives lists of recently installed with first item is magisk manager. After uninstall magisk manager, the phone boot normally but without root and magisk
Any help to root?
Click to expand...
Click to collapse
Did you enabled the 2 advanced options in Magisk Manager(preserve encryption and avb) , before patching?
In magisk manager 7.2.0 there no advanced setting to preserve encryption and avb
BSAKotb said:
Yes of course
Click to expand...
Click to collapse
Can you try this image - > https://mega.nz/#!UgUThaTC!QZceeV1squ-sTsaeKmkchUQww_9_iu5gRLERp9f9VMs
Make sure latest Magisk Manager is installed!
BSAKotb said:
In magisk manager 7.2.0 there no advanced setting to preserve encryption and avb
Click to expand...
Click to collapse
There is!
[email protected] I download your magisk.img and flashed with fastboot and reboot phone after finish with power + vol up then released power after your device is booting now appear and phone stuck at that stage till now
BSAKotb said:
[email protected] I download your magisk.img and flashed with fastboot and reboot phone after finish with power + vol up then released power after your device is booting now appear and phone stuck at that stage till now
Click to expand...
Click to collapse
Then i don't know what's wrong, just flash back your original recovery_ramdisk and the device will boot.
@Pretoriano80
advanced option not shown , but showing paypal and Patreon instead with magisk manager 7.2.0 (213))up to date and magisk latest 19.3 not installed
@Pretoriano80 Thanks for your help. I flashed service firmware 177 , then wipe all data from erecovery followed by letting phone to update to 258. After the phone boot normally I flashed patched 258 boot image Finally rooted and operate normally.
Again thanks
BSAKotb said:
In internet search some suggest flash of service firmware to resolve this type of error.
Is safe to flash older pie firmware (9.0.0.177) my current is 9.0.0.231 (model BLA-L29C185)?
Can any one help?
Click to expand...
Click to collapse
From Firmware finder only latest full-ota is 9.0.0177. after that if the firmware is not full-ota u will not be able to flash. And Currently I am on Openkirin omnipie and I do flash 9.0.0.177 when ever i need Emui.
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.
Hi
I recently bought a p20 lite from Facebook and i think the previous owner must have flashed the wrong firmware. In developer options there is no oem unlock button, and i tried eRecovery and it didn't work. The phone is dual sim, some apps see as if the phone is rooted and when i check with root checker, there's no root. I'm from South Africa and i hope i provided the necessary information. I would like to downgrade the phone to the firmware I'll be able to get the bootloader code from.
Looneychoons said:
Hi
I recently bought a p20 lite from Facebook and i think the previous owner must have flashed the wrong firmware. In developer options there is no oem unlock button, and i tried eRecovery and it didn't work. The phone is dual sim, some apps see as if the phone is rooted and when i check with root checker, there's no root. I'm from South Africa and i hope i provided the necessary information. I would like to downgrade the phone to the firmware I'll be able to get the bootloader code from.
Click to expand...
Click to collapse
Hi, just to be sure -
A) enter Project Menu (*#*#2846579#*#*) > 'Network info ... ' > 'Vendor country info'
B) In fastboot mode run command
fastboot oem oemimforead-CUSTOM_VERSION
and post the results.
Edit.: what was the reason for the failure with erecovery?
-Alf- said:
Hi, just to be sure -
A) enter Project Menu (*#*#2846579#*#*) > 'Network info ... ' > 'Vendor country info'
B) In fastboot mode run command
fastboot oem oemimforead-CUSTOM_VERSION
and post the results.
Edit.: what was the reason for the failure with erecovery?
Click to expand...
Click to collapse
Thanks for the reply man.
Vendor country is hw/meafnaf. Secondly, I get oeminforead-CUSTOM_VERSION failed. When i did erecovery i got 'Getting package info failed' i did factory reset and tried again but same error.
Looneychoons said:
Thanks for the reply man.
Vendor country is hw/meafnaf. Secondly, I get oeminforead-CUSTOM_VERSION failed. When i did erecovery i got 'Getting package info failed' i did factory reset and tried again but same error.
Click to expand...
Click to collapse
Okay, try this way out:
1. Download Oreo Service ROM
2. Unpack it and copy dload folder (can be found in 'Software') to the SD Card (without unpacking it!)
3. Turn of your phone and use three button combo (dload method) .
The process will erase all your data!
-Alf- said:
Okay, try this way out:
1. Download Oreo Service ROM
2. Unpack it and copy dload folder (can be found in 'Software') to the SD Card (without unpacking it!)
3. Turn of your phone and use three button combo (dload method) .
The process will erase all your data!
Click to expand...
Click to collapse
Thank you bro I'll let you know how it goes. After dload do i setup the device or wipe and factory reset, also do i check for updates or just buy credits for dc unlocker to get my bootloader code?
Looneychoons said:
buy credits for dc unlocker to get my bootloader code?
Click to expand...
Click to collapse
First check if ANE-LX2 is supported, I'm not sure...
Looneychoons said:
wipe and factory reset,
Click to expand...
Click to collapse
not necessary now
-Alf- said:
First check if ANE-LX2 is supported, I'm not sure...
not necessary now
Click to expand...
Click to collapse
Thanks man I'll kepl you posted.
-Alf- said:
First check if ANE-LX2 is supported, I'm not sure...
not necessary now
Click to expand...
Click to collapse
Hey bro I can't thank you enough. All went well after dload, I got my oem unlock button working, all that's left is to get my bootloader code. After I get it I want to root my phone, so can you please help me with a tutorial, from installing the correct twrp for my device and flashing magisk?
Looneychoons said:
Hey bro I can't thank you enough. All went well after dload, I got my oem unlock button working, all that's left is to get my bootloader code. After I get it I want to root my phone, so can you please help me with a tutorial, from installing the correct twrp for my device and flashing magisk?
View attachment 5372567View attachment 5372569
Click to expand...
Click to collapse
For Oreo only!
Download TWRP
Magisk.zip
Magisk manager apk
- download Magisk.zip and copy it to SD
- install Magisk manager apk
- install TWRP in fastboot mode, use command:
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot
- flash magisk.zip in TWRP
- reboot
- open M.manager apk
Update Manager & Magisk , if you want.
-Alf- said:
For Oreo only!
Download TWRP
Magisk.zip
Magisk manager apk
- download Magisk.zip and copy it to SD
- install Magisk manager apk
- install TWRP in fastboot mode, use command:
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot
- flash magisk.zip in TWRP
- reboot
- open M.manager apk
Update Manager & Magisk , if you want.
Click to expand...
Click to collapse
Really bro thank you. You're the best.