Does anyone have boot image for RMX3300 A.19 or fireware download link for rmx3300_11_a.19?
thanks
I'm looking too. Only found it at Halab Tech Support. It's not free, unfortunately I can't cope with the payment methods via PayPal. Otherwise I would have already tried to extract the boot.img
here is the magisk patched boot image for RMX3300 chinese firmware C.19
i only have this version
backup the stock boot.img before flashing
and dont forget to flash vbmeta.img before magisk.img
Very nice thank you.
However, my question is how do I backup my boot.img without root?
I have version A.19. If I can make a backup without root, I could patch the boot.img from the backup and install it via Magisk.
Or am I wrong?
Just how to backup without root.....?
shyzj666666 said:
here is the magisk patched boot image for RMX3300 chinese firmware C.19
i only have this version
backup the stock boot.img before flashing
and dont forget to flash vbmeta.img before magisk.img
Click to expand...
Click to collapse
How can I do a backup of boot.img?
Related
Hi
I have put TWRP n my phone but when i flash a new rom i need patch the boot.img.
I want to know what i need make to reverse this?
I try the cofface twrp and work good for flash a zip rom, no need modify the boot.img.
In OTA dont work
I want reverse for original form. Without twrp.
Is possible?
Thanks a lot!
Download your version of ROM, extract the recovery.img and flash in using fastboot
Hi, I'm having trouble with Magisk re-installation.
First I installed Magisk using the flashing boot.img method, it was working correctly but I tried to remove the youtube vanced module, when it asked for a reboot it went straight to the bootloader, I just re-flashed the original boot.img to the phone and got it working again. the issue came when I tried to reinstall Magisk from scratch again. Whenever I tried to install it the process would go without any issue but when I tried to start the system it is going to the bootloader again.
I tried installing twrp using this guide and got the custom recovery working on both slots, then I tried to flash magisk using the zip file, the installer ran without throwing any issues but when I tried to reboot again to the system it still goes to fastboot, this time not only corrupting the system start but also the twrp recovery. I haded to reflash the stock boot.img image on slot A and the twrp image on slot B to re install twrp on both slots.
Also using the TWRP tried running the uninstall magisk zip but whenever I try to run it it just fails because it cannot find the magisk.img file and exits by telling that I have not installed magisk.
Tried erasing the folders inside of /data/adb but its the same issue all over again.
Does anyone has any idea or suggestion on what could I try to fix the issue?
Thanks
Try flashing patched boot image (the same version as your system) and boot into the system, go into magisk manager and do complete uninstall. Or download the latest Magisk uninstaller and try from TWRP again. Recent versions of Magisk ditched magisk.img, so you might be using old version of the uninstaller.
_mysiak_ said:
Try flashing patched boot image (the same version as your system) and boot into the system, go into magisk manager and do complete uninstall. Or download the latest Magisk uninstaller and try from TWRP again. Recent versions of Magisk ditched magisk.img, so you might be using old version of the uninstaller.
Click to expand...
Click to collapse
Tried using the lastest uninstaller found on the topjohnwu/Magisk repository, which did not show any error but after installing magisk the phone still goes to bootloader, then tried to run the uninstaller again but it only works on the b slot and to run it on the a slot I have to reflash boot.img and then install twrp on both slots.
But thanks for the sugestion.
jtcp2703 said:
Tried using the lastest uninstaller found on the topjohnwu/Magisk repository, which did not show any error but after installing magisk the phone still goes to bootloader, then tried to run the uninstaller again but it only works on the b slot and to run it on the a slot I have to reflash boot.img and then install twrp on both slots.
But thanks for the sugestion.
Click to expand...
Click to collapse
I would restore stock ROM, skip TWRP installation and flash just correct patched boot image.
_mysiak_ said:
I would restore stock ROM, skip TWRP installation and flash just correct patched boot image.
Click to expand...
Click to collapse
Do you know where can I find the lastest stock rom? Right now I'm on 10.3.9.0 PFQEUXM, or if the lastest is not possible, could I flash a older version of the rom without any trouble?
jtcp2703 said:
Do you know where can I find the lastest stock rom? Right now I'm on 10.3.9.0 PFQEUXM, or if the lastest is not possible, could I flash a older version of the rom without any trouble?
Click to expand...
Click to collapse
Try to find the full OTA zip for the latest version (or at least the same you have) and extract it with this tool https://github.com/cyxx/extract_android_ota_payload
Xiaomi hasn't released the fastboot rom for the recent updates yet.
So far I was able to find only global links here (they should work too, but rather backup your data first). http://4pda.ru/forum/index.php?showtopic=962154
You might have luck installing older fastboot EU ROM, but again, backup your data first.
If you did not enable "allow system modifications" in TWRP, it should be enough to flash only stock boot image (there are links to them somewhere on this forum).
Also I would avoid installing TWRP.
Sapper Morton said:
The complete firmware images, can only be found in .tgz archives, payload.bin OTAs only contains incremental firmware updates; thus you won't be able to successfully restore, system, vendor, boot, critical partitions and etc; the recommended method is to restore to either 10.3.4.0 PFQMIXM or 10.3.7.0 PFQEUXM, both .tgz archives, complete firmware inside. @_mysiak_
Click to expand...
Click to collapse
There are usually two types of OTA zip files, small incremental ones (which you described) - for monthly updates and full OTA (1-2gb in size) - for direct update across several versions. You can create all needed fastboot images from the full OTA payload.bin with before mentioned python extractor script.
Sapper Morton said:
You can try for yourself, I wasn't able to restore using this images (assuming of course you have a corrupt, system, vendor, boot, ... partition): https://bigota.d.miui.com/V10.3.6.0...UTGlobal_V10.3.6.0.PFQMIXM_00713c5a1d_9.0.zip
I was only able to return to global channel, by using 10.3.4.0 PFQMIXM firmware, .tgz archive.
Click to expand...
Click to collapse
By wasn't able to restore you mean that you couldn't convert payload.bin to fastboot images, or that converted fastboot images were not working?
I've just extracted these files from payload.bin from the link you provided (with this app). I don't have a phone to test them though (I did the same thing a few times on Mi A1 and flashing, phone and OTA worked afterwards).
Code:
abl.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dtbo.img
hyp.img
imagefv.img
keymaster.img
modem.img
product.img
qupfw.img
rpm.img
storsec.img
system.img
tz.img
uefisecapp.img
vbmeta.img
vendor.img
xbl.img
xbl_config.img
So I currently have USA Hawaii mate 10 pro on 9.0.0264 BL unlocked and magisk patched ramdisk and I keep getting notification to install the .267 update but it will not install due to the patched ramdisk so I just want to flash back to stock, I have downloaded the full ota through Hawaii hisuite application and its in zip format, so how do i flash this zip to go back to stock, thank you.
lingarajug said:
So I currently have USA Hawaii mate 10 pro on 9.0.0264 BL unlocked and magisk patched ramdisk and I keep getting notification to install the .267 update but it will not install due to the patched ramdisk so I just want to flash back to stock, I have downloaded the full ota through Hawaii hisuite application and its in zip format, so how do i flash this zip to go back to stock, thank you.
Click to expand...
Click to collapse
You don't have to flash the whole update, just extract the recovery_ramdisk from 9.0.0.264 firmware (use Huawei Extractor to do that) and flash it with fastboot.
Another way to get the stock recovery it's to use Partitions Backup by Wanam (from Playstore), in its options enable the "raw partition image" and backup "erecovery_ramdisk".
Copy the backup on PC and flash it with this fastboot command :
fastboot flash recovery_ramdisk erecovery_ramdisk.img
Note: replace "erecovery_ramdisk.img" with the filename of the image that you backed up previously.
After flashing the stock recovery_ramdisk, you can install the official OTA.
I am confused, there is recovery_ramdis and erecovery_ramdisk and which one is it.
Update- i just flashed recovery_ramdis and then system from ota and i am updated now. Thank you.
Hi! Ive just installed los 17.1 from this guide : https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
I have also installed twrp
But now Im confused on how to install magisk
Do I use the ramdisk from emui stock firmware and patch it and fastboot flash it?
Is there a way to get a ramdisk from the los image ?
Or is it possible to just flash the normal magisk zip in twrp ?
Any help would be appreciated thank you!
(Ane-lx1
Was running emui 9.0.0.133(c185))
DonnyRedZone1 said:
Hi! Ive just installed los 17.1 from this guide : https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
I have also installed twrp
But now Im confused on how to install magisk
Do I use the ramdisk from emui stock firmware and patch it and fastboot flash it?
Is there a way to get a ramdisk from the los image ?
Or is it possible to just flash the normal magisk zip in twrp ?
Any help would be appreciated thank you!
(Ane-lx1
Was running emui 9.0.0.133(c185))
Click to expand...
Click to collapse
Simply download and flash patched recovery_ramdisk
-Alf- said:
and also copy to the SD card patched Recovery_ramdisk:
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
Click to expand...
Click to collapse
Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ).
-Alf- said:
Simply download and flash patched recovery_ramdisk
Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ).
Click to expand...
Click to collapse
Thank you so much for helping me over the past few days man ur a legend !
(realised i was being stupid nvm)
hi guys i'm trying to unlock the bootloader and install a custom recovery and custom rom i've never done it if anyone can help me and all the necessary files thanks a lot
Well first downgrade to rui 2.0 and then using deep testing apk unlock the bootlorder and then flash custom recovery (ofox better) . Install your custom rom of your choice then ur good to go
Pranav060 said:
Bene, prima eseguire il downgrade a rui 2.0 e quindi utilizzare l'apk di deep testing per sbloccare il bootlorder e quindi eseguire il flashing del ripristino personalizzato (ofox migliore). Installa la tua rom personalizzata di tua scelta, quindi sei a posto
Click to expand...
Click to collapse
unfortunately I can't find the realme ui 2.0 downgrade file when I install what is written in the guides it tells me verification failed and I can't downgrade
andrea34334343 said:
unfortunately I can't find the realme ui 2.0 downgrade file when I install what is written in the guides it tells me verification failed and I can't downgrade
Click to expand...
Click to collapse
I have this version of realme ui 3
Hi, maybe my experience will be useful to you. I have Realme 7 pro with android 12 rmx2170_11_f.24. I was doing root to my device. What I was doing? First I downloaded deeptest rui3.apk. When I get confirmation from manufacturer I start deep test in app. Then I use ADB to send command for unlock bootloader. I completed this task. Then I downloaded and flash TWRP 3.6.2_12 (because it's can work with android 12. I tried 3.5.2_10 it's not worked). Also you need vbmeta file from rmx2170_11_f.24 to don't make your phone brick. First flash vbmeta then recovery. After recovery you need to install Magisk from TWRP to keep TWRP working after reboot. But, when I tryed install Magisk I was getting TWRP error 1: cannot write /system. How I fix it? I reboot device and install Magisk 25.2 via Android. Then you need patch boot.img from rmx2170_11_f.24 via Magisk and you get Magisk patched boot.img. Then you need flash TWRP again and reboot to recovery. In TWRP you need chose flash img button and flash Magisk patched boot.img to boot partition. Doing this you keep TWRP working and then you can flash custom ROM's to your phone.
Mod edit: 4pda link removed.
here you can get f24 ROM ( you need vbmeta and boot.img from this ROM). ROM is ~2 Gb size. Maybe you need registration on website to download. Also get TWRP 3.6.2. I'll pin deep test rui3.apk and Magisk 25.2 for you here. You can rename Magisk.zip to Magisk.apk and install via Android. I gaved you roadmap how to make this. Hope you can do it. By the way, hello from Ukraine)
s_svyrydenko said:
Hi, maybe my experience will be useful to you. I have Realme 7 pro with android 12 rmx2170_11_f.24. I was doing root to my device. What I was doing? First I downloaded deeptest rui3.apk. When I get confirmation from manufacturer I start deep test in app. Then I use ADB to send command for unlock bootloader. I completed this task. Then I downloaded and flash TWRP 3.6.2_12 (because it's can work with android 12. I tried 3.5.2_10 it's not worked). Also you need vbmeta file from rmx2170_11_f.24 to don't make your phone brick. First flash vbmeta then recovery. After recovery you need to install Magisk from TWRP to keep TWRP working after reboot. But, when I tryed install Magisk I was getting TWRP error 1: cannot write /system. How I fix it? I reboot device and install Magisk 25.2 via Android. Then you need patch boot.img from rmx2170_11_f.24 via Magisk and you get Magisk patched boot.img. Then you need flash TWRP again and reboot to recovery. In TWRP you need chose flash img button and flash Magisk patched boot.img to boot partition. Doing this you keep TWRP working and then you can flash custom ROM's to your phone.
Mod edit: 4pda link removed.
here you can get f24 ROM ( you need vbmeta and boot.img from this ROM). ROM is ~2 Gb size. Maybe you need registration on website to download. Also get TWRP 3.6.2. I'll pin deep test rui3.apk and Magisk 25.2 for you here. You can rename Magisk.zip to Magisk.apk and install via Android. I gaved you roadmap how to make this. Hope you can do it. By the way, hello from Ukraine)
View attachment 5867277 View attachment 5867279
Click to expand...
Click to collapse
Thanks for helping me out and passing me the necessary files
{Mod edit: Quoted post has been deleted. Oswald Boelcke, Senior Moderator}
You wrote in the wrong trend write in a new post
s_svyrydenko said:
Hi, maybe my experience will be useful to you. I have Realme 7 pro with android 12 rmx2170_11_f.24. I was doing root to my device. What I was doing? First I downloaded deeptest rui3.apk. When I get confirmation from manufacturer I start deep test in app. Then I use ADB to send command for unlock bootloader. I completed this task. Then I downloaded and flash TWRP 3.6.2_12 (because it's can work with android 12. I tried 3.5.2_10 it's not worked). Also you need vbmeta file from rmx2170_11_f.24 to don't make your phone brick. First flash vbmeta then recovery. After recovery you need to install Magisk from TWRP to keep TWRP working after reboot. But, when I tryed install Magisk I was getting TWRP error 1: cannot write /system. How I fix it? I reboot device and install Magisk 25.2 via Android. Then you need patch boot.img from rmx2170_11_f.24 via Magisk and you get Magisk patched boot.img. Then you need flash TWRP again and reboot to recovery. In TWRP you need chose flash img button and flash Magisk patched boot.img to boot partition. Doing this you keep TWRP working and then you can flash custom ROM's to your phone.
Mod edit: 4pda link removed.
here you can get f24 ROM ( you need vbmeta and boot.img from this ROM). ROM is ~2 Gb size. Maybe you need registration on website to download. Also get TWRP 3.6.2. I'll pin deep test rui3.apk and Magisk 25.2 for you here. You can rename Magisk.zip to Magisk.apk and install via Android. I gaved you roadmap how to make this. Hope you can do it. By the way, hello from Ukraine)
View attachment 5867277 View attachment 5867279
Click to expand...
Click to collapse
Please provide twrp link.
UNOFFICIAL TWRP RMX2170 TRIAL FOR ANDROID 12
give me
boot img .vbmeta and .persist img