I'm searching for the P20 Lite ANE-LX1-C432 Stock Firmware update.app or the stock/matching system.img file.
I cannot find it on google maybe huawei did not release it yet so i wonder if one of you guys did dump it
Thank you.
EDIT:
I found a full firmware here for ANE-LX1 :
Stock Firmware C185 (Middle East) [url]https://www.allrom.ir/2018/04/01/رام-فارسی-اندروید-8-0-هوآوی-پی-20-لایت-ane-l21-l01/[/URL]
I extracted the stock system.img ANE-LX1 from the update.app
I just flashed it everything works. system.img :
https://drive.google.com/open?id=1cbfdA9GaOQAKMWM0sFBPZh28q-Klmyvc
Without root we can't dump anything, still working on it. For now, there's nothing
RogerXIII said:
Without root we can't dump anything, still working on it. For now, there's nothing
Click to expand...
Click to collapse
Yes i tried to dump files with adb or fastboot but was not successful and now my device is too modified to try again.
Gonna wait for Huawei to post the firmware...
EDIT:
Look at the first post for links ! thx.
I found a full firmware here:
https://www.allrom.ir/2018/04/01/رام-فارسی-اندروید-8-0-هوآوی-پی-20-لایت-ane-l21-l01/
This one is C185 (Middle East)
Edit: Now i need to create a P20 Lite Profile for the Huawei Extractor. :crying:
Edit 2: i was able to extract the system.img from the update.app, now trying it.
Edit 3: I now have a Stock system.img ANE-LX1
I just flashed it everything works.
I will post it if you need it like me after trying some treble roms :angel:
Thanks, got system.img from this with no problem, but it looks like there's no boot.img in here, so still no chance for root
RogerXIII said:
Thanks, got system.img from this with no problem, but it looks like there's no boot.img in here, so still no chance for root
Click to expand...
Click to collapse
In the OREO boot & recovery partitions got a different names.
RECOVERY is now split in several partitions:
RECOVERY_RAMDISK
RECOVERY_VENDOR
RECOVERY_VBMETA
In the Oreo the command to flash a TWRP (that is not available yet) in the fastboot mode is:
fastboot flash recovery_ramdisk twrp.img
___
BOOT is now split in two partitions:
KERNEL
RAMDISK
In the Oreo the command to flash "KERNEL" in the fastboot mode is:
fastboot flash kernel kernel.img
kilroystyx said:
In the OREO boot & recovery partitions got a different names.
RECOVERY is now split in several partitions:
RECOVERY_KERNEL
RECOVERY_RAMDISK
RECOVERY_VENDOR
RECOVERY_VBMETA
In the Oreo the command to flash a TWRP (that is not available yet) in the fastboot mode is:
fastboot flash recovery_ramdisk twrp.img
___
BOOT is now split in two partitions:
KERNEL
RAMDISK
In the Oreo the command to flash "KERNEL" in the fastboot mode is:
fastboot flash kernel kernel.img
Click to expand...
Click to collapse
Thanks for this information! Patching boot.img to get root that way is not possible then I assume?
By flashing the Mate 10 Pro recovery, you can dump your boot.img with adb in recovery using dd command. I just tried dumping some partitions of my P20 Lite, everything works fine, but I already flashed a wrong boot partition so I cant provide the stock boot.img file.
EDIT : the recovery doesn't work at all, please do nothing else except dumping partitions, or you may brick your phone
Never mind! I managed to root by patching the ramdisk.img
RogerXIII said:
Never mind! I managed to root by patching the ramdisk.img
Click to expand...
Click to collapse
Can you pleeease give me a dump of your boot partition? I failed flashing the partition and without any boot.img file I'm totally lost :')
Jb-kun said:
Can you pleeease give me a dump of your boot partition? I failed flashing the partition and without any boot.img file I'm totally lost :')
Click to expand...
Click to collapse
I made a thread here, you can root or go back to stock there
Boas kilroystyx comprei um ANE-LX1 P20 Lite da vdf. Isto está com apenas single SIM. Sabes se mudar a ROM liberta a segunda SLOT? ainda não há firmware para isto pois não?
Obrigado,
MC
GV
kilroystyx said:
In the OREO boot & recovery partitions got a different names.
RECOVERY is now split in several partitions:
RECOVERY_KERNEL
RECOVERY_RAMDISK
RECOVERY_VENDOR
RECOVERY_VBMETA
In the Oreo the command to flash a TWRP (that is not available yet) in the fastboot mode is:
fastboot flash recovery_ramdisk twrp.img
___
BOOT is now split in two partitions:
KERNEL
RAMDISK
In the Oreo the command to flash "KERNEL" in the fastboot mode is:
fastboot flash kernel kernel.img
Click to expand...
Click to collapse
@ggviegas, xda is an international forum, so please write in English, or PM me.
RogerXIII said:
Thanks, got system.img from this with no problem, but it looks like there's no boot.img in here, so still no chance for root
Click to expand...
Click to collapse
I was too lazy to dump the other partitions because had to create a huawei extractor profile for the device, and there is a lot of partitions on the P20 Lite.
I am a complete noob. Brought the Chinese version with HiApp and all - don't know how to get it to the Middle East version. Can someone share the instruction that a 3-year-old can understand???
Thanks
I flashed system in fastboot. My device is Huawei Nova 3e (P20 Lite in china) everything works kinda nicely but notch settings in the display settings are disappeared. Notch is not working properly. Other than that, everything is alright. I need help to fix that notch settings. Can somebody help me?
Is the Android Auto working properly on this version? I see its the 105 and not the 108.
thelonelyman said:
I flashed system in fastboot. My device is Huawei Nova 3e (P20 Lite in china) everything works kinda nicely but notch settings in the display settings are disappeared. Notch is not working properly. Other than that, everything is alright. I need help to fix that notch settings. Can somebody help me?
Click to expand...
Click to collapse
Try to update the software as the notch options were added recently.
Hi there. I downloaded the Firmware and flashed the system.img but still my phone shows the 112 version. How is this possible?
When i flashed all img (all recovery, ramdisk, kernel, system) i got into a bootloop.
So i replaced them with the old ones. But still the system img was from the downloaded package.
What am i doing wrong? i can flash every system.img file but my version wont change.
I did a Full wipe aswell.
kilroystyx said:
In the OREO boot & recovery partitions got a different names.
RECOVERY is now split in several partitions:
RECOVERY_RAMDISK
RECOVERY_VENDOR
RECOVERY_VBMETA
In the Oreo the command to flash a TWRP (that is not available yet) in the fastboot mode is:
fastboot flash recovery_ramdisk twrp.img
___
Click to expand...
Click to collapse
so, using fastboot flash recovery_ramdisk recovery_ramdisk.img would be the proper way to go back to stock recovery?
Related
I flashed wrong baseband/modem files on oxygen os 3.1.4 and now i am stuck at oneplus logo.I can only boot into fastboot mode not even custom recovery.
Please help!!!!!!
saagr_2800 said:
I flashed wrong baseband/modem files on oxygen os 3.1.4 and now i am stuck at oneplus logo.I can only boot into fastboot mode not even custom recovery.
Please help!!!!!!
Click to expand...
Click to collapse
Was on 3.1.4 around 7 months ago. Do you have EFS backup? If don't, that was a big mistake flashing new baseband without backup.
But here some advices to do:
→Boot to fastboot and re-check if bootloader still unlocked (if yes then proceed ↓ )
→Flash the stock MM recovery for OOS within fastboot
→Directly boot to recovery (using fastboot command or manually)
→Reflash the full ROM 3.1.4 zip. It should bring back everything
*Or try to flash compatible TWRP for 3.1.4 and just restore the EFS partition or full Nand Backup (if you have one)
*If not, then you'll need to follow mega unbrick guide.
oneplus x fastboot images of rom
seacowx said:
Was on 3.1.4 around 7 months ago. Do you have EFS backup? If don't, that was a big mistake flashing new baseband without backup.
But here some advices to do:
→Boot to fastboot and re-check if bootloader still unlocked (if yes then proceed ↓ )
→Flash the stock MM recovery for OOS within fastboot
→Directly boot to recovery (using fastboot command or manually)
→Reflash the full ROM 3.1.4 zip. It should bring back everything
*Or try to flash compatible TWRP for 3.1.4 and just restore the EFS partition or full Nand Backup (if you have one)
*If not, then you'll need to follow mega unbrick guide.
Click to expand...
Click to collapse
Bro i have messed with oneplus x,I have deleted all the data inside now i can only boot to fastboot mode,can u please help me finding fastboot images of any rom for oneplus x?
saagr_2800 said:
Bro i have messed with oneplus x,I have deleted all the data inside now i can only boot to fastboot mode,can u please help me finding fastboot images of any rom for oneplus x?
Click to expand...
Click to collapse
Thats disaster. Have you tried any steps i suggested earlier?
Re-check unlocked bootloader? and try flashing compatible TWRP within fastboot? hows the results?
• Download full ROM 3.1.4 zip and place in your computer (ADB folder)
• Directly boot to TWRP and use "ADB sideload" of full ROM zip (using ADB command)
Use search button (or just google it) how to use ADB sideload.
→Worst case scenario, follow the mega unbrick guide that should help you. OK. goodluck.
Note: Easiest way, contact oneplus support team for remote session. They will help you
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
try that
can't flash factory oneplus rom from recovery
saagr_2800 said:
Bro i have messed with oneplus x,I have deleted all the data inside now i can only boot to fastboot mode,can u please help me finding fastboot images of any rom for oneplus x?
Click to expand...
Click to collapse
Bro i somehow fastboot firmware and radio files now i can access recovery ,i tried to install factory oneplus oos 3.1.4 but i get these red lines saying
could not find META-INF/com/google/android/update-binary
error installing .zip
failed to mount '/firmware' (invalid argument)
failed to mount '/system' (invalid argument)
saagr_2800 said:
Bro i somehow fastboot firmware and radio files now i can access recovery ,i tried to install factory oneplus oos 3.1.4 but i get these red lines saying
could not find META-INF/com/google/android/update-binary
error installing .zip
failed to mount '/firmware' (invalid argument)
failed to mount '/system' (invalid argument)
Click to expand...
Click to collapse
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
These commands helped me
saagr_2800 said:
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
These commands helped me
Click to expand...
Click to collapse
What twrp version are you on?
You need a stock MM recovery for opx to flash full 3.1.4.
and make sure you ain't got corrupted zip file. Download full 3.1.4 ROM zip from onplus website.
seacowx said:
What twrp version are you on?
You need a stock MM recovery for opx to flash full 3.1.4.
and make sure you ain't got corrupted zip file. Download full 3.1.4 ROM zip from onplus website.
Click to expand...
Click to collapse
I tried from mm recovery as well it says installation failed
saagr_2800 said:
I tried from mm recovery as well it says installation failed
Click to expand...
Click to collapse
If you're already on stock MM recovery. then just reflash the OOS full ROM 3.1.4 zip. (The zip you tried was corrupted one, i guess). re-download and try again.
Note: make sure to checked box mount (system, data, cache) only, before flashing full ROM.
dchrono said:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
try that
Click to expand...
Click to collapse
sorry, does it make any difference?
his situation was having a bootloop/softbrick and couldnt boot into system nor recovery at all,, all partition has been wiped,,the only thing that working is fastboot (now he has recovery).
as i know "fastboot erase modemst1/2" is for fixing network/gps/wifi issue on booted state device. Cmiiw
The only way is, he could try reflash full ROM zip using stock recovery or custom ROM using TWRP with proper way
Part.0 said:
sorry, does it make any difference?
his situation was having a bootloop/softbrick and couldnt boot into system nor recovery at all,, all partition has been wiped,,the only thing that working is fastboot (now he has recovery).
as i know "fastboot erase modemst1/2" is for fixing network/gps/wifi issue on booted state device. Cmiiw
The only way is, he could try reflash full ROM zip using stock recovery or custom ROM using TWRP with proper way
Click to expand...
Click to collapse
You know what, It's a bit old and hectic dealing with stock MM things.. Plus messing up with modem with no backup preparation. It's more like complicated hell
IF only he wanna try flash any N custom ROM for opx,
(At least to get or to make sure your device get booted back first)
I could suggest him the proper procedure IF he want to.
seacowx said:
You know what, It's a bit old and hectic dealing with stock MM things.. Plus messing up with modem with no backup preparation. It's more like complicated hell
IF only he wanna try flash any N custom ROM for opx,
(At least to get or to make sure your device get booted back first)
I could suggest him the proper procedure IF he want to.
Click to expand...
Click to collapse
lmao, yeah that was terrible gambling without having a backup!
anyway how to backup modem/baseband? do u have link refers to that? thanks
Part.0 said:
lmao, yeah that was terrible gambling without having a backup!
anyway how to backup modem/baseband? do u have link refers to that? thanks
Click to expand...
Click to collapse
Here you go, in case someone try messing up with the modem make sure to backup modemst1 & modemst2 first:
Just open terminal emulator on device and types:
su (to grant root access)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
*It will copy the 2 files into sdcard/internal storage. Save those 2 files to safety place. like a Bank
To restore (using fastboot) types:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
seacowx said:
Here you go, in case someone try messing up with the modem make sure to backup modemst1 & modemst2 first:
Just open terminal emulator on device and types:
su (to grant root access)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
*It will copy the 2 files into sdcard/internal storage. Save those 2 files to safety place. like a Bank
To restore (using fastboot) types:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
Click to expand...
Click to collapse
lol, nice thanks a lot man! im not intend to messing up with my modem either lol
Part.0 said:
sorry, does it make any difference?
his situation was having a bootloop/softbrick and couldnt boot into system nor recovery at all,, all partition has been wiped,,the only thing that working is fastboot (now he has recovery).
as i know "fastboot erase modemst1/2" is for fixing network/gps/wifi issue on booted state device. Cmiiw
The only way is, he could try reflash full ROM zip using stock recovery or custom ROM using TWRP with proper way
Click to expand...
Click to collapse
To repair EFS issues when fastboot only available. There are other ways as well however OP mentioned fastboot available only.
Edit: @Part.0 if you would have read OP correctly, you would have noticed he mentioned that he flashed the wrong modem files and my solution along with a fastboot reboot which I didn't mention would have solved his problem. fastboot erase modemst1/2 although you only know it for solving modem/GPS issues are also partitions. Remember our job here is not to convince @Part.0 of our solutions, next time a thank you would do well for teaching you something.
seacowx said:
If you're already on stock MM recovery. then just reflash the OOS full ROM 3.1.4 zip. (The zip you tried was corrupted one, i guess). re-download and try again.
Note: make sure to checked box mount (system, data, cache) only, before flashing full ROM.
Click to expand...
Click to collapse
I tried oneplus rom with oneplus recovery,before installing i also did wipe and cache,it failed.
I also tried installing lineage os using twrp but there it says
could find meta-inf/com/google/android/update-script not found
and failed to mount './firmware' (invalid argument)
saagr_2800 said:
I tried oneplus rom with oneplus recovery,before installing i also did wipe and cache,it failed.
I also tried installing lineage os using twrp but there it says
could find meta-inf/com/google/android/update-script not found
and failed to mount './firmware' (invalid argument)
Click to expand...
Click to collapse
Ok since i can't reproduce your issue on this one, so i can't find the right solutions for your case.
• Unlocked bootloader + Working Recovery + Fastboot + Full ROM zip file
Those should enough fixing your issue.
Perhaps i missed something, like corrupted partitions (firmware). Maybe another user experienced with the issue can help you out.
Best luck for you.
Note: Maybe our friend here can help you out @dchrono or willing to help you. Thank you.
Ps: Try mountng of "Firmware" in mount section before flashing full ROM. So it will mounted (Firmware, System, data, cache) But wait, ask out before you do. Finger crossed
Download these files
https://www.androidfilehost.com/?fid=24269982087019810
http://www.mediafire.com/file/8g9v5fsslnbf1r6/Qualcomm+Driver+Setup.zip
1 switch off Oneplus x forced
2 install Qulacomm usb driver
3 press volume up button n connect with PC
4 extract Oneplus x unbrick tool
5 run msm downloder and click on start
6 if complete flashing flash stock ROM via memory card
Contact me on. WhatsApp if not success
+917756968834
seacowx said:
Here you go, in case someone try messing up with the modem make sure to backup modemst1 & modemst2 first:
Just open terminal emulator on device and types:
su (to grant root access)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
*It will copy the 2 files into sdcard/internal storage. Save those 2 files to safety place. like a Bank
To restore (using fastboot) types:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
Click to expand...
Click to collapse
can it be done with TWRP recovery?
Hi there
I think my phone is briked. I wantet to downgrade my phone to the 108 version becaus there was android auto working.
So i tried to flash the System.img from the 108 Software. I tried 2 different:
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-lx1&firmware_page=0
and the Middle east from the thread here.
Id did flash over fastboot, but after every start the Build number was still on the 112 Firmware.
So i tried the Trebel ASOP, RR and LOS. ASOP Booted but had only forceclose on every service. RR and LOS did not work.
Then i tried to flash the ramdisk, recovery, vendor kernel etc from the update.app from the 108 Firmware. No my phone is briked.
I tried to flash eveyrthing from the .112 updateapp from the Official thread but nothing happend.
Then i tried to flash every possible .img file from the .112 app but most of them gave "Error Command not allowed"
So here i Am. Bootlooping phone and i dont know what else to do.
Since the beginning i could flash every system.img but it still was on the 112 Build and suddenly it bricked. I cant get to the 112 Version back with flashing system.img because it bootloops. Same for Treble and the newest 126 Version or the old 108 Build.
The only thing booting is ASOP Treble but i cant navigate coz of the 1000 of forceclosed errors.
I formated the userpartition as i was asked from Huawei, and bevore i did those installations i did a fullwipe with EMUI.
The Recovery cant connect to the server, and yeah.. i dont know what to do next. ofc i have unlocked bootloader. I bought the Phone in Switzerland with Dual Sim. ANE-LX1.
Does anyone have another idea?
Cheers
EDIT:
After 10000 billions klicks i managed to get through the treble wizzard, even when the com.android.phone has stopped is comming every second.
At the Moment im in the About Phone Screen and i see this: (I am in the newest ASOP Treble SU with gapps)
Model: ANE-LX1
Android Version 8.1
Baseband: unknown
Kernel Version 4.4.23+ (gcc version 4.9x 20150123 (prerelease) (GCC))
Fri Mar 9 09:51:47 CST 2018
Build Number ANE-LX1 8.0.0.112(c432) <------- WTF ?!?
I hope this informations is something to work with.
SIM CARD is not readable.
Edit2:
I connected it to HI SUit. It says my device running properly on the .112 Version (WTF i got Treble installed)
I cant connect anything. How the hell can i get rid of this ****ing wong Build number??
Same for Checking Updates. .112 should be newest (its not its 126) Any ideas?
Edit3:
Can only Flash with fastboot. Twrp cant mount the partitions. Trying to installing the zip or adb sideload gives me an error code or command not allowed :\
i think the best way is
download a FULL-Update for your build
https://forum.xda-developers.com/9-lite/help/huawei-honor-firmware-download-t3790327
read this https://forum.xda-developers.com/hon...flash-t3778085
if you understand and have the know how : good luck
with this way i have my Ho9L reflash to stock-rom
you have to know what you're doing
use Magisk (search inside xda the thread)
this work by me better as SuperSU (with less problem's)
use this twrp, it's work WITH encryption
ttps://forum.xda-developers.com/huawei-p20-lite/development/recovery-testing-t3783587
if you understand what i am write - you can reset your phone to "delivered-state" and beginning by zero (initial-setting's) and
what ever you flash - you have a chance to reset your phone
first look on bootloader-screen if
- bootloader unlocked
- FRP unlock
THIS is essential !
last tip: let the fingers from custom-rom if this not expressly build for OREO
OREO is other as NOUGAT ! very different !
Relock your bootloader before trying an Erecovery...
please try this :
- download full update rom for your device, extract the .APP files using HuaweiUpdateExtractor
- boot into fastboot by press and hold Volume Down and plug in usb cable into your pc and your phone, hold it until it boot into fastboot
- do this :
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- reboot your device and hold Volume Up and Volume Down to get it boot into eRecovery and do Wipe Cache Partitions and then do Factory Data Reset, and reboot again
- let it boot normally, and see what happen next, i can't remember for sure because it's been so long i unbricked my Nova 2s with this method. there are 2 possibility, you'll boot into system normally, or it will boot into eRecovery again and there is an option Download Latest Version And Recovery and you can choose that, of course you should have connection to internet via wifi.
please report back if you have difficulties.
heindrix said:
please try this :
- download full update rom for your device, extract the .APP files using HuaweiUpdateExtractor
- boot into fastboot by press and hold Volume Down and plug in usb cable into your pc and your phone, hold it until it boot into fastboot
- do this :
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- reboot your device and hold Volume Up and Volume Down to get it boot into eRecovery and do Wipe Cache Partitions and then do Factory Data Reset, and reboot again
- let it boot normally, and see what happen next, i can't remember for sure because it's been so long i unbricked my Nova 2s with this method. there are 2 possibility, you'll boot into system normally, or it will boot into eRecovery again and there is an option Download Latest Version And Recovery and you can choose that, of course you should have connection to internet via wifi.
please report back if you have difficulties.
Click to expand...
Click to collapse
I'm getting this error when I'm trying to extract UPdate.app of anE-LX1 8.0.0.108(C185)
https://ibb.co/k0HmGy
haidermiz said:
I'm getting this error when I'm trying to extract UPdate.app of anE-LX1 8.0.0.108(C185)
https://ibb.co/k0HmGy
Click to expand...
Click to collapse
go to settings, untick all options that have "verify" in it, and try extract again.
heindrix said:
go to settings, untick all options that have "verify" in it, and try extract again.
Click to expand...
Click to collapse
thanks it worked
heindrix said:
please try this :
- download full update rom for your device, extract the .APP files using HuaweiUpdateExtractor
- boot into fastboot by press and hold Volume Down and plug in usb cable into your pc and your phone, hold it until it boot into fastboot
- do this :
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- reboot your device and hold Volume Up and Volume Down to get it boot into eRecovery and do Wipe Cache Partitions and then do Factory Data Reset, and reboot again
- let it boot normally, and see what happen next, i can't remember for sure because it's been so long i unbricked my Nova 2s with this method. there are 2 possibility, you'll boot into system normally, or it will boot into eRecovery again and there is an option Download Latest Version And Recovery and you can choose that, of course you should have connection to internet via wifi.
please report back if you have difficulties.
Click to expand...
Click to collapse
When i did fastboot flash vendor vendor.img it says
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460706 KB)...
OKAY [ 18.084s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
haidermiz said:
When i did fastboot flash vendor vendor.img it says
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460706 KB)...
OKAY [ 18.084s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Hi there, if you have TWRP, you could flash system and vendor using TWRP. boot into TWRP, choose install, choose use image file, and flash system.img to system, and vendor.img to vendor.
heindrix said:
Hi there, if you have TWRP, you could flash system and vendor using TWRP. boot into TWRP, choose install, choose use image file, and flash system.img to system, and vendor.img to vendor.
Click to expand...
Click to collapse
Tried then phone was stuck at installing update 5% after 5 mins there was a screen android written on it then again it booted to erecovery i factory reset data, wiped cache then again it rebooted and it's finally open now thanks
heindrix said:
Hi there, if you have TWRP, you could flash system and vendor using TWRP. boot into TWRP, choose install, choose use image file, and flash system.img to system, and vendor.img to vendor.
Click to expand...
Click to collapse
I did that a installed stock rom after that I tired to reset data it said failed, it failed at 20% then I WIPED CHAHE and now when It opened I sign in and downloaded snapchat but it's noy opening and in settings about phone there's no model number mentioned it says unknown I don't know what to do
haidermiz said:
I did that a installed stock rom after that I tired to reset data it said failed, it failed at 20% then I WIPED CHAHE and now when It opened I sign in and downloaded snapchat but it's noy opening and in settings about phone there's no model number mentioned it says unknown I don't know what to do
Click to expand...
Click to collapse
if you could, please provide screenshot so i can see it more clearly.
after you flashing the rom, one thing you must do is to format the data and cache through emui erecovery, as long as you're not format the data and cache successfully, the rom will not works properly.
for another reference, please refer to my other post here : https://forum.xda-developers.com/ma...0-pro-help-t3776050/post76916307#post76916307
heindrix said:
if you could, please provide screenshot so i can see it more clearly.
after you flashing the rom, one thing you must do is to format the data and cache through emui erecovery, as long as you're not format the data and cache successfully, the rom will not works properly.
for another reference, please refer to my other post here : https://forum.xda-developers.com/ma...0-pro-help-t3776050/post76916307#post76916307
Click to expand...
Click to collapse
Greetings, I downloaded the rom of my Huawei p20 EML-L09 and it has two Update.app
How and in what order should I install them?
Udpate.app that weighs 4.62gb and
update_EML-L09_hw_la.app which weighs 1.5gb
Thanks a lot.
ajbn7 said:
Greetings, I downloaded the rom of my Huawei p20 EML-L09 and it has two Update.app
How and in what order should I install them?
Udpate.app that weighs 4.62gb and
update_EML-L09_hw_la.app which weighs 1.5gb
Thanks a lot.
Click to expand...
Click to collapse
Hi,
this guide is two years old, if you want to recover your phone, download Service ROM from androidhost.ru website, and flash it using dload method .
Which EMUI version are you running? Your region is C605 ?
-Alf- said:
Hi,
this guide is two years old, if you want to recover your phone, download Service ROM from androidhost.ru website, and flash it using dload method .
Which EMUI version are you running? Your region is C605 ?
Click to expand...
Click to collapse
Correct, my region is 605. I already downloaded the latest version available for download on that page which is 8.1.
Before my phone went into brick, it had version 9.1
And bring those two update.app
ajbn7 said:
Before my phone went into brick, it had version 9.1
Click to expand...
Click to collapse
For 9.1 you can download
https://androidhost.ru/2bCG
Unpack .zip archive , find dload file and simply transfer it to the SD card, without unpacking it! (instructions can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo.
Note: Service ROM L-29 contains both version - L-29 & L-09 .
-Alf- said:
For 9.1 you can download
https://androidhost.ru/2bCG
Unpack .zip archive , find dload file and simply transfer it to the SD card, without unpacking it! (instructions can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo.
Note: Service ROM L-29 contains both version - L-29 & L-09 .
Click to expand...
Click to collapse
I struggled so hard to download the file, and to my surprise it does not include the software version for the L-09, only for the L-29
Are there any risks if I try to install version 8.1?
Another thing, the Huawei p20 does not have a micro sd slot, I guess I should do it through a USB OTG?
ajbn7 said:
I struggled so hard to download the file, and to my surprise it does not include the software version for the L-09, only for the L-29
Click to expand...
Click to collapse
Are you sure?
I'm really sorry, but most of the packages are universal.
ajbn7 said:
Are there any risks if I try to install version 8.1?
Click to expand...
Click to collapse
It may brick your phone definitively.
ajbn7 said:
Another thing, the Huawei p20 does not have a micro sd slot, I guess I should do it through a USB OTG?
Click to expand...
Click to collapse
Yes, you can.
ajbn7 said:
I struggled so hard to download the file, and to my surprise it does not include the software version for the L-09, only for the L-29
Are there any risks if I try to install version 8.1?
Another thing, the Huawei p20 does not have a micro sd slot, I guess I should do it through a USB OTG?
Click to expand...
Click to collapse
Okay, I definitely don't get the 9.1 for Eml-09 for free.
So last query (I hope), what is less risky, install Rom 8.1 which is for my region and exact model, or install Rom 9.1 with my region but for model L-29 or install a Rom 9.1 for my model but with a different region?
Thank you for your support.
ajbn7 said:
what is less risky?
Click to expand...
Click to collapse
L29 EMUI 9.1 C605. Even if it succeeds the phone will not work correctly.
Most probably you will get the wrong model or in build number "system_0.46 (xxxx)" . HiSuite will not recognize your device (and no OTA update).
I installed EMUI 9 on my p20 lite and didn't like it, so I tried one of the openkirin 9.0 beta roms. There was some features that didn't work so I decided I wanted to go back. I followed the guide on openkirin's website about going back to stock by flashing system.img, ramdisk.img, kernel.img and recovery_ramdisk.img however trying to flash ramdisk.img gives "partition length get error". Now, the phone only is able to boot into fastboot and eRecovery mode. In eRecovery the options to backup and to factory reset are grayed out however, and the "update to latest version" doesn't work. When I plug the charger in from being turned off it shows the white error screen with error 10 (boot image) and error 2 (load failed). I have a suspicion that flashing kernel.img is what causing the problem, but I don't really know enough to be sure and I don't want to do anything to make it worse since it seems like this should be fixable.
This is the only phone I have which properly worked so any help is greatly appreciated.
Hi there
Don't worry, it's fixable
There's way bigger mess than that, so the best solution for you and the easiest one is to flash a signed dload package, which you can find for your model and build number in this website:
https://androidhost.ru/search.html
Search in this format "ANE-LX1C66".
Then extract it and copy the "dload" folder to the root of your sd card.
Then power off your device if it isn't and then press POWER + Volume Plus + Volume Minus at the same time until a circle with EMUI appears.
That will erase all data and lock your bootloader.
Cheers!
AS
ars_chelsea said:
Hi there
Don't worry, it's fixable
There's way bigger mess than that, so the best solution for you and the easiest one is to flash a signed dload package, which you can find for your model and build number in this website:
https://androidhost.ru/search.html
Search in this format "ANE-LX1C66".
Then extract it and copy the "dload" folder to the root of your sd card.
Then power off your device if it isn't and then press POWER + Volume Plus + Volume Minus at the same time until a circle with EMUI appears.
That will erase all data and lock your bootloader.
Cheers!
AS
Click to expand...
Click to collapse
Ah, yeah, forgot to mention I already tried that. Unfortunately it doesn't work. It just says "software install failed". I'm genuinely about to throw this f***ing thing into orbit
Thanks for your help though.
Afifus said:
Ah, yeah, forgot to mention I already tried that. Unfortunately it doesn't work. It just says "software install failed". I'm genuinely about to throw this f***ing thing into orbit
Thanks for your help though.
Click to expand...
Click to collapse
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
ars_chelsea said:
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
Click to expand...
Click to collapse
Tried Oreo build 150 for ane-lx1c432 and ane-lx1c782 since those are the only models my phone could be.
Although, when I do the get-build-number command in fastboot it still says I'm on a Pie build. I'm gonna try doing a Pie build and I'll get back to you.
ars_chelsea said:
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
Click to expand...
Click to collapse
Yeah, pie didn't work either.
Afifus said:
Yeah, pie didn't work either.
Click to expand...
Click to collapse
But there is no signed package for those models yet, what dload files did you use?
Cheers,
AS
ars_chelsea said:
But there is no signed package for those models yet, what dload files did you use?
Cheers,
AS
Click to expand...
Click to collapse
I got it off of firmware finder. Are those not signed?
Afifus said:
I got it off of firmware finder. Are those not signed?
Click to expand...
Click to collapse
No, those are not signed, you need the dload files from Androidhost.ru since it's the only place you can get them for free, here's a link for both the versions you showed:
Single SIM ANE-LX1C432: https://androidhost.ru/Utm
Dual SIM ANE-LX1C432: https://androidhost.ru/Utn
Single SIM ANE-LX1C782: https://androidhost.ru/29Zn
Dual SIM ANE-LX1C782: https://androidhost.ru/1jzD
Choose the right one, and follow the procedure I sent you in a reply above.
ars_chelsea said:
No, those are not signed, you need the dload files from Androidhost.ru since it's the only place you can get them for free, here's a link for both the versions you showed:
Single SIM ANE-LX1C432: https://androidhost.ru/Utm
Dual SIM ANE-LX1C432: https://androidhost.ru/Utn
Single SIM ANE-LX1C782: https://androidhost.ru/29Zn
Dual SIM ANE-LX1C782: https://androidhost.ru/1jzD
Choose the right one, and follow the procedure I sent you in a reply above.
Click to expand...
Click to collapse
Cheers, but unfortunately neither of those worked. I'm at a loss on what else I could try.
Afifus said:
Cheers, but unfortunately neither of those worked. I'm at a loss on what else I could try.
Click to expand...
Click to collapse
at less you back to emui 9.1 only to save your phone
first download the firmware from tm team database search the right firmware for your phone
after that unzip the two files then use huawei extractor to extract files from update.app
and follow this instructions
Copy to the following partitions to the adb fastboot folder:
recovery_ramdisk
recovery_vbmeta
recovery_vendor
cust
kernel
system
userdata
product
vendor
Then boot your device in fastboot mode.
note if you dont found recovery ramdisk then rename recovery ramdis to previous name
The commands for fastboot:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash system system.img
aftet that make a wipe / factory reset
what happen to you happen to me the same thing if this work after that then be patience until we get official emui, the last news that i read that huawei postpone release until july
Thanks to kilroystyx
Try this and tell me
yassine2217 said:
at less you back to emui 9.1 only to save your phone
first download the firmware from tm team database search the right firmware for your phone
after that unzip the two files then use huawei extractor to extract files from update.app
and follow this instructions
Copy to the following partitions to the adb fastboot folder:
recovery_ramdisk
recovery_vbmeta
recovery_vendor
cust
kernel
system
userdata
product
vendor
Then boot your device in fastboot mode.
note if you dont found recovery ramdisk then rename recovery ramdis to previous name
The commands for fastboot:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash system system.img
aftet that make a wipe / factory reset
what happen to you happen to me the same thing if this work after that then be patience until we get official emui, the last news that i read that huawei postpone release until july
Thanks to kilroystyx
Try this and tell me
Click to expand...
Click to collapse
Holy f*** thank you. That seems to have worked. It also seems to have fixed the sms problem I had with 9.1.
Afifus said:
Holy f*** thank you. That seems to have worked. It also seems to have fixed the sms problem I had with 9.1.
Click to expand...
Click to collapse
great happy for you
root: for A.87 stock rom
Unlock bootloader and place the mentioned two files to Platform tools folder on your pc.
Download "vbmeta.img" and "Magisk_patched.img"
• adb devices
• adb reboot bootloader
•fastboot devices
• fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
• fastboot flash boot magisk_patched.img
• fastboot reboot
+++±+++++++
Guide to flash Recovery
- Connect your phone to PC, Allow USB Debugging. Now Type These Commands.
adb reboot bootloader
fastboot devices
fastboot reboot bootloader
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery recoveryname.img
fastboot reboot recovery
To keep custom recovery flash twrpkeep.zip when's booted to recovery :
Bro my device is a.89 ..is this vbmeta working...?
qeb said:
Bro my device is a.89 ..is this vbmeta working...?
Click to expand...
Click to collapse
Yes it work on all a10 update
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
misiek998 said:
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
Click to expand...
Click to collapse
oh, thank's men. edited.
Hello, Can I use the VBMeta on android 11 or no? thanks!
Ryeeeeel said:
Hello, Can I use the VBMeta on android 11 or no? thanks!
Click to expand...
Click to collapse
Can't root rui 2.0 (Android 11), and can't install custom recovery except "los recovery" but can't do any thing with it just wiping cache and data partition.
do not try to flash custom recovery on realme ui 2.0 , it will brick your device
I need to ask, this guide will work with A88/A89 update?
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
adamuadamu said:
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
Click to expand...
Click to collapse
Yes. Just flash the original firmware using SP Flash-Tools. However, youmust make sure it is the full 7-8 GB ROM, and not an OTA file. Also, ensure that you are flashing the correct ROM for your model. If your model is an RMX2155, you'll need to follow this guide steps 1-through-to-10 (inclusive):
[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK
WELCOME, ALL. After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an...
forum.xda-developers.com
If it is any other model, just do what is said to work. Unfortunately, I don't know much about the other versions.
thanks the explanation.
I've found a 2155 ROM or at least a file that's said to be - ie. I've found a file 'RMX2155export_11_C.09_2021070809260000', extracted that, there was a huge file 'RMX2155export_11_C.09_2021070809260000.ofp' inside; using oppo-decrypt from github I've got bunch of files with names that seem to be SPFlashTool ROM.
Assuming it's a proper ROM: if I have already unlocked the bootloader, do I have to flash the rom and do the 10 steps from the tutorial or could I replace recovery.img and magisk-patched boot.img and flash rooted rom immediately? Sorry if it sound noobish, but I don't want to brick the phone.
I'm curious to try to go back to stock ROM for a while, because of call quality (I believe changing it to Vietnam needed for unlock made the call quality worse) and to check the camera and it's libraries - I'm running crdroid, photo quality is disappointing no matter what GCam/settings/tweaks I use and there are only imx682/imx471 libs on the phone there are samsung libs, but diagnose apps like aida show the main sensor is imx682, but the EU version of realme 7 is said to have different back camera sensor (GM1). Not sure if RMX2151 ROMs would include proper GM1 libs if that's true about sensor differences between RMX2151 and 2155.
I would be grateful if someone could upload the new A18 boot.img global , from the latest update patched with magic or original.
where is the firmware? you can extract the boot.img and patch it yourself. It is easy.
I know it can be done easily, but I don't have the firmware. The phone downloaded the update and I didn't think about it and restarted the phone.
I think that after the update the phone deletes the file that was used for the update.
By the way, it's the boot image, not the bootloader.
Thank you.
Rapper_skull said:
By the way, it's the boot image, not the bootloader.
Rapper_skull said:
By the way, it's the boot image, not the bootloader.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Rapper_skull said:
If I were not Italian: I flashed your modified boot, now the phone is in bootloop, I don't know how to recover it since I can't find the link to download the firmware anywhere. Could you please pass me the original boot? help me please
Click to expand...
Click to collapse
Rapper_skull said:
Ciao sei italiano? ho visto la località di napoli! Io ho flashato la boot, ora ho bootloop!! Puoi passarmi la boot originale? per favore sono disperato non so come recuperarlo
non riesco a trovare da nessuna parte il firmware.zip da scaricare per prelevare la boot. In caso hai telegram? su telegram mi trovi x91xmarcox91x
Click to expand...
Click to collapse
marco.chinagliaxx91 said:
If I were not Italian: I flashed your modified boot, now the phone is in bootloop, I don't know how to recover it since I can't find the link to download the firmware anywhere. Could you please pass me the original boot? help me please
Click to expand...
Click to collapse
EU or global, the boot.img is the same. You probably bootlooped because you have to do
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Attached you can find the original boot.img
Rapper_skull said:
EU or global, the boot.img is the same. You probably bootlooped because you have to do
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Attached you can find the original boot.img
Click to expand...
Click to collapse
this comand
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
first or later the flash boot?
marco.chinagliaxx91 said:
this comand
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
first or later the flash boot?
Click to expand...
Click to collapse
After the flash, but of course you have to get the vbmeta.img file.
Rapper_skull said:
EU or global, the boot.img is the same. You probably bootlooped because you have to do
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Attached you can find the original boot.img
Click to expand...
Click to collapse
it doesn't work, I thought it was the same eu or global as in the oneplus. How can I do now?
Rapper_skull said:
After the flash, but of course you have to get the vbmeta.img file.
Click to expand...
Click to collapse
i can't find the entire firmware online.
marco.chinagliaxx91 said:
i can't find the entire firmware online.
Click to expand...
Click to collapse
I am writing a post with all the firmware links right now. Please wait.
Rapper_skull said:
I am writing a post with all the firmware links right now. Please wait.
Click to expand...
Click to collapse
tnk
Rapper_skull said:
I am writing a post with all the firmware links right now. Please wait.
Click to expand...
Click to collapse
let me know here then when you finished the post, thanks man
marco.chinagliaxx91 said:
let me know here then when you finished the post, thanks man
Click to expand...
Click to collapse
[Global/EU] Collection of firmware files
Since a lot of people is asking for firmware files, OTAs, boot.img, I decided to collect all the resources here, so that it would be easier to get what you need. First of all, you have to identify your ROM version. It is not the scope of this...
forum.xda-developers.com
What procedure did you use to flash.
I recommend this one:
Quake94 said:
EDIT: Uploaded A.16 Global ROM.
Ok so for anyone struggling, here is what I did to flash 3300 to 3301 Global & root w/safety net. I hope myogui can update original post because many of us are puzzling pieces of information from different sources. Credits to @myogui, @hacls and Shato from 4pda.to forum
Myogui Google Drive has A.10 version. As of now, the newest official version is A.17.
EDIT1: A.16 Global ROM with A.16 patched boot.img is available here.
super.img is a compressed 7zip archive, extract to the same directory as other files.
https://drive.google.com/drive/folders/1Y5mZtZchLytYqDqs0sOYTqCmaZeURrJ5?usp=sharing
EDIT2: Magisk A.17 patched boot.img added to Google drive credit @themagicalImage22
https://drive.google.com/file/d/1k6-K8vRlEnZJXPH6z_t5QHy5Kiud2sGX/view?usp=sharing
If you unlock bootloader the Widevine will be L3. Netflix will not stream in HD.
As of now, there is no official method to restore L1
Locking bootloader does not fix it. Root or stock does not fix it.
OTA update does not fix it.
To check Widevine level, you can use app DRMInfo
1. Download platform-tools for fastboot:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2. Download the Global ROM files (*.img) and put them in the same folder as the platform-tools where your fastboot is. Sometimes the super.img gets renamed to super-001.img, so change name back to super.img
3. Connect phone in fastboot. If drivers are not installed or working, fix it via Windows Update -> Check Updates -> Optional Updates -> Drivers -> Google + FTDI
4. Run the deep testing apk, and after it's approved let it go into bootloader mode.
5. Connect phone to PC. If fastboot shows "waiting for devices", exit, go into Windows Update and check for updates. Then go to Optional Updates and select & install Android Google driver. (Windows 10-11)
6. Complete the unlocking of bootloader with fastboot flashing unlock
7. Follow flashing like below credit @hacls
NOTE 1: You can also run fastboot getvar current-slot to check which partition is active before running fastboot --set-active=a
NOTE 2: You can flash stock nonroot boot.img first and root later with 1 command. Otherwise, flash a patched boot.img that matches the ROM version.
NOTE 3: When flashing super.img, error message will display "Invalid sparse file format in header", it will look frozen but this is OK, leave it running.
Locking bootloader:
If you don't care about root and don't plan to root in future, follow @sanya_rnd guide:
NOTE: CAREFUL - High risk of hard brick if the data was not wiped in step 4. All partitions must be stock, no root.
For unlocked bootloader:
Rooting with Magisk:
The newest Global version as of now is A.17.
NOTE: Patched boot.img has to match the version of the ROM.
7. After flashing global rom check what is most up to date version available via the software update.
You will have to disable automatic system updates to keep the root if Realme releases newer ROM.
7a. Reboot back to bootloader (if you have ADB debugging enabled in Developer Options, run adb reboot bootloader, otherwise you can do the Power + volume down method)
Download appropriate patched boot.img
bootA10magisk.img for A.10
https://drive.google.com/file/d/1hBxqFe7XzO7hub-jgZjsFfAHo4XIdjlm/view?usp=sharing
bootA16magisk.img for A.16
https://drive.google.com/file/d/1pyz7VFkiPjnkzizWfSJjOe836yinQR1w/view?usp=sharing
bootA17magisk.img for A.17
https://drive.google.com/file/d/1k6-K8vRlEnZJXPH6z_t5QHy5Kiud2sGX/view?usp=sharing
7b. Run fastboot getvar current-slot .
Replace the "bootXXXmagisk" with a correct filename for patched magisk file
- If it shows boot B partition, run fastboot flash boot_b bootXXXmagisk.img
- If it shows boot A partition, run fastboot flash boot_a bootXXXmagisk.img
7.c Reboot device with fastboot reboot
7.d Complete Magisk app install
Install Magisk modules (you have to copy .zip files):
SafetyNetFix : https://github.com/kdrag0n/safetynet-fix/releases
Shamiko : https://github.com/LSPosed/LSPosed.github.io/releases
7.e Activate Zygisk in Magisk
7.f Go to configure DenyList and add in any apps you want to hide Magisk from like banking apps.
However - Don't enable the "Activate DenyList" option! This is required by Shamiko hide Magisk module
Just adjust the DenyList.
7.g Restart phone and enjoy root
Safety Net passes with BASIC evaluation type
Additional notes:
Magisk updates can be installed with "Direct Install (recommended)"
Manual extracting of boot.img and other files from original ROM OFP file:
Flash files can be extracted using Oppo Decrypt from:
https://github.com/bkerler/oppo_decrypt
I advise against using MCT OFP Extractor Tool as it contains a ransomware Trojan:Win32/Trickbot!ml
Untested OTA-update preserving root method (proceed at your own risk!)
- Copy current ROM version stock boot.img to storage
- Open Magisk and select install -> Patch file -> Select the stock boot.img
- Restart phone.
This will generate Magisk "backup image" folder
- Go to Magisk -> Restore Images
- Go to OTA update and select to download update. Once it finishes the "Extracting" process, do not click "Install" in the updater!
- Go back to Magisk app and select Install -> Install to Inactive Slot (After OTA)
- After Magisk is done, select reboot
The above method is untested, so make sure you have stock and patched boot.img files for the newest ROM version. Theoretically in the worst case scenario if something goes wrong, all that needs to be done is reflash boot.img via fastboot.
A.17 ROM .ofp file:
RMX3301export_11_A.17_2022062222270183: https://rms01.realme.net/SW/realme service/realme GT2 Pro/216AC/RMX3301export_11_A.17_2022062222270183.7z
Click to expand...
Click to collapse
The most important part is
7b. Run fastboot getvar current-slot .
Replace the "bootXXXmagisk" with a correct filename for patched magisk file
- If it shows boot B partition, run fastboot flash boot_b bootXXXmagisk.img
- If it shows boot A partition, run fastboot flash boot_a bootXXXmagisk.img
Rapper_skull said:
By the way, it's the boot image, not the bootloader.
Click to expand...
Click to collapse
Are you sure this is the real boot.img? All the previous ones were about 190 MB and this one is only 50 MB?
dejop said:
Are you sure this is the real boot.img? All the previous ones were about 190 MB and this one is only 50 MB?
Click to expand...
Click to collapse
The boot partition is not filled to the max of course, so the boot.img extracted from the firmware files is smaller than the partition size (192 MB). In the OTA firmware, the partitions are not filled with empty space like in full firmware files. That's why Full OTA packages are only 5 GB.