Related
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Meranico said:
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Click to expand...
Click to collapse
If you can boot to "downloader" use rebranding SW, it will fix everything
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
Thank you so much! My mobile phone is working again! :victory:
Edit: Small problem persists: I cannot use the buttons left and right of the scanner. They do not react.
Edit2: Could fix this. I flashed B120 and the buttons worked again.
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
whats rebranding sw and hoe do i do it as i have the smae problem please help
corey568brown said:
whats rebranding sw and hoe do i do it as i have the smae problem please help
Click to expand...
Click to collapse
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Meranico said:
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Click to expand...
Click to collapse
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
corey568brown said:
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
Click to expand...
Click to collapse
Good to know!
As I had the same problem as you do know: I flashed B120, which does not seem to have the bug with the buttons and upgraded via Firmware Finder to B130 and then to B150.
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
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!
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
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.