Mate 10 Lite Oreo RNE-L22 C636
Ran on Morfuz 3.4 Oreo
I tried to change SuperSU to Magisk and I think I didn't do some steps and now it's just soft bricked. It can go to fastboot mode and eRecovery. It has the Func NO : 10 (Boot Image) and Error NO : 2 (load failed).
How do I fix this please
themagicalmage22 said:
Mate 10 Lite Oreo RNE-L22 C636
Ran on Morfuz 3.4 Oreo
I tried to change SuperSU to Magisk and I think I didn't do some steps and now it's just soft bricked. It can go to fastboot mode and eRecovery. It has the Func NO : 10 (Boot Image) and Error NO : 2 (load failed).
How do I fix this please
Click to expand...
Click to collapse
, do you have twrp?
I have same problem and have TWRP. Can you help me ?
Go to this link: https://forum.xda-developers.com/ho...ash-official-firmware-recovery-t3769279/page1
Maybe it will help you guys ???
i have same problem , and no twrp
when i want to acces to twrp i have NO : 11 (recovery Image) and Error NO : 2 (load failed).
Yeah. Just got the same after trying to install Magisk 16.0 after realizing that 16.6 must be somehow corrupted cause not installing and changing layout of Magisk Manager to arabic-like. Can't get to TWRP, can't boot to the system. Need a clue how to fix it. Ehh... Never expected that this phone will be THAT bad to mod.
Oh, and I'm using stock Oreo, C432.
Related
Hi,
My phone : Redme Note 4 Global Edition 3/32 unlocked and rom developper.
My problem : I wanted to put TWRP and I did a MEGA bull****.
To install TWRP I did:
Fastboot flash boot recovery.img
instead of :
Fastboot flash recovery recovery.img
My phone starts systematically on TWRP... (It boots no more normally)
I have shot tempted one:
Fastboot flash boot boot.img
With the boot.img retrieved from the MIUI 9 archive 7.8.10 (mido_global_images_7.8.10_20170810.0000.00_7.0_global_239182c21e.tgz)
Now the phone shows me the logo miui indefinitely.
I still have access to Fastboot
Is it necessary to try with the boot.img of version MIUI 9 7.8.18 (installed version)? Can someone provide it to me?
If not, can anyone help me restore the boot without losing any facilities made?
Thank you in advance.
Regards
Hi,
Well I finally made a MiFlash with the option "flash_all_except_storage.bat" on the same flashboot ROM that was previously installed in my phone before my error. (MIUI 9 7.8.18).
The phone is OK.
I did not clean it : I hope it will not bug.
Regards.
When you've flashed TWRP when MIUI is installed you need to install lazyflasher with recovery. Without it MIUI will not boot with TWRP
Sent from my Redmi Note 4 using Tapatalk
Hi,i have tried to update my ALP-L29 to 9.0 with flashy_0.2 .It failed after %80.Then i have flashed TWRP to install 8.0 again but it did not boot to TWRP.Now i can only boot to fastboot Phone Unlocked FRP locked.I tried to flash stok recovery again but it gives FAILED (remote: Command not allowed).How can i get to 8.0 agian?Pls help.
aydink1979 said:
Hi,i have tried to update my ALP-L29 to 9.0 with flashy_0.2 .It failed after %80.Then i have flashed TWRP to install 8.0 again but it did not boot to TWRP.Now i can only boot to fastboot Phone Unlocked FRP locked.I tried to flash stok recovery again but it gives FAILED (remote: Command not allowed).How can i get to 8.0 agian?Pls help.
Click to expand...
Click to collapse
Searching in Google downgrade pie 9
Enviado desde mi ALP-L09 mediante Tapatalk
I bricked my Huawei Mate 10 too
Removed to avoid spamming
Carnage! said:
Mine is kind of different though, update to Android 9.0 was successful but the problem started after trying to downgrade my device.
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
No with hwota is another programa
Enviado desde mi ALP-L09 mediante Tapatalk
---------- Post added at 11:57 PM ---------- Previous post was at 11:55 PM ----------
Carnage! said:
Mine is kind of different though, update to Android 9.0 was successful but the problem started after trying to downgrade my device.
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
http://www.mediafire.com/file/...zb/BLA_beta-downy_0.4.zip/file
Enviado desde mi ALP-L09 mediante Tapatalk
Hello! I have a model plk-l01, with emui 3.1,, b140 version. I had rooted with kingroot app. Then I had installed flashify app, and tried to flash twrp recovery. Bad decision. Now when I want to reboot in recovery mode, on the screen appears that : rescue mode. Please update system again. Error Func no 11(recovery image) func no 2 (load failed).
I tried to reflash stock recovery through fastboot, but no chance. (it says ok, but after :command not allow). I tried with dlload method, but returned into that error. I tried to flash twrp with fastboot, but same error. So, my phone works well, but no recovery. I have no possibility to update to marshmallow... Please help if you can. Cheers!
I've tried patching the stock recovery but when I boot into it it just stays on the loading. Do I have to downgrade from 9.1 to root my p20 Lite?
Moocow93 said:
I've tried patching the stock recovery but when I boot into it it just stays on the loading. Do I have to downgrade from 9.1 to root my p20 Lite?
Click to expand...
Click to collapse
download magisk manager , extract your stock recovery_ramdisk image and patch it with magsk manager. then flash this patched magisk recovery_ramdisk with fastboot: fastboot flash recovery_ramdisk patched magisk ramdisk.img dont unplug the usb cable, then fastboot reboot, let the usb on the phone, dont unplug it, when emui is started, then use adb command: adb reboot recovery ,..still have the usb cable on the phone, when it reboots into "recovery" magisk gets installed to recovery, phone gets rebooted into emui, then open magisk manager and u install advanced stuff, reboots itselve, and then u have root but only works with emui 9.1 version 132 above 132 version this methode doesnt work, and no working methode is known by now for emui 9.1 above 132 version
nofx161 said:
download magisk manager , extract your stock recovery_ramdisk image and patch it with magsk manager. then flash this patched magisk recovery_ramdisk with fastboot: fastboot flash recovery_ramdisk patched magisk ramdisk.img dont unplug the usb cable, then fastboot reboot, let the usb on the phone, dont unplug it, when emui is started, then use adb command: adb reboot recovery ,..still have the usb cable on the phone, when it reboots into "recovery" magisk gets installed to recovery, phone gets rebooted into emui, then open magisk manager and u install advanced stuff, reboots itselve, and then u have root but only works with emui 9.1 version 132 above 132 version this methode doesnt work, and no working methode is known by now for emui 9.1 above 132 version
Click to expand...
Click to collapse
Strange, working for me with 146 and 151.
Ofcorse, if you don't use clear system, then there are chance that it don't work, but on clear system works like 99% , so, best way how to root any emui 9.1 is , dload latest version, unlock , and flash magiskpatched.img
Arnys said:
Strange, working for me with 146 and 151.
Ofcorse, if you don't use clear system, then there are chance that it don't work, but on clear system works like 99% , so, best way how to root any emui 9.1 is , dload latest version, unlock , and flash magiskpatched.img
Click to expand...
Click to collapse
i always do that,.. the problem above 132 (as it seems to me) is that u patch ramdisk_recovery but erecovery doesnt get patched,.. as stated above had no problem with magisk with 132 version, with 151 it doesnt work
How do I downgrade from 9.1.0.140 to 132.? I tried flashing by fastboot but in settings it still said I was on 140
How to root realme 7 a.89....i have a.87 vbmeta img file.but my device is a.89.is this vbmeta file work on my a.89. please help
I think you can flash a.87 vbmeta in a.89 because if any version of vbmeta is in a10 or you are in a10 then you can flash it there no problem because i tested it tell me if you have problems with
hello guys, i'm having a problem here, I just installed a pixel plus ui and then installed the magisk app, then I renamed it to a zip file as mentioned in the website and went to flash it on my phone (Realme 7) after flashing successfully completed I pressed the reboot to system option, now it's stuck on the realme logo and doesn't budge anymore... I'm really worried please help me.
qeb said:
How to root realme 7 a.89....i have a.87 vbmeta img file.but my device is a.89.is this vbmeta file work on my a.89. please help
Click to expand...
Click to collapse
That vbmeta ( if it's patched ) can be used for all A10 builds. Which means u can use it with not only A87, A89. but all others RUI 1 available builds ( A83, A75....etc)
nabarun12 said:
hello guys, i'm having a problem here, I just installed a pixel plus ui and then installed the magisk app, then I renamed it to a zip file as mentioned in the website and went to flash it on my phone (Realme 7) after flashing successfully completed I pressed the reboot to system option, now it's stuck on the realme logo and doesn't budge anymore... I'm really worried please help me.
Click to expand...
Click to collapse
You can only do that with Permissive ROM builds, for Enforcing, you will need to patch boot.img manually with Magisk, then flash it into boot partition using fastboot command or custom recovery.