Related
Is it specific for each device? Or does it depend only on finding the correct partition/block to be extracted?
Could you point me to further readings about that?
Thanks.
It is at least device specific, for extracting the bootimage, check this http://forum.xda-developers.com/showthread.php?t=1951426
Sent from my Acer Cloudmobile S500
IF YOU THINK I MADE SOME SENSE, PLEASE HIT THE THANK BUTTON !!!
What if everything is an illusion, and nothing exists?
In that case, I definitely overpaid my carpet....!
DopeyTheOne said:
It is at least device specific, for extracting the bootimage, check this http://forum.xda-developers.com/showthread.php?t=1951426
Sent from my Acer Cloudmobile S500
IF YOU THINK I MADE SOME SENSE, PLEASE HIT THE THANK BUTTON !!!
What if everything is an illusion, and nothing exists?
In that case, I definitely overpaid my carpet....!
Click to expand...
Click to collapse
Well, that link is to proceed AFTER you have boot.img at hand. I want to find a way to extract it from my phone (assuming default.prop can be changed in there).
Thanks.
When you make a back up with CWM, you have a copy of your bootimage in the clockworkmod map, not?
That's the thing ... I am trying to figure out how to get that backup in hand at first.
Currently, following the method in http://droidcore.blogspot.com.br/2012/12/how-to-edit-initrc-in-android.html
It seems to use the same scripts as cited in your link.
Will post results afterwards.
Don't make things more complicated as they are. If you just install CMW recovery (or TWRP for that matter) for your device, you have your full backup in minutes, including one of your bootimage, then use the script from my first post.
I managed to find boot.img, made the necessary changes, sent it back to device (used MPK Rom Studio and SP Flash Tool).
The problem is, the reason I want to change boot.img is to root my device. I thought that disabling ro.secure, I would be able to do so. But I couldn't.
I believe cmw recovery, or twrp, both need my phone to be rooted, no?
MrCabana said:
I managed to find boot.img, made the necessary changes, sent it back to device (used MPK Rom Studio and SP Flash Tool).
The problem is, the reason I want to change boot.img is to root my device. I thought that disabling ro.secure, I would be able to do so. But I couldn't.
I believe cmw recovery, or twrp, both need my phone to be rooted, no?
Click to expand...
Click to collapse
I used a CWM image to root my device. Booted up with that image, and flashed SU....after that you can use su, and apparantly, with the changes you made with your bootimage...you'll be like God on your phone
Sent from my S500 using xda app-developers app
I have the same problem, I need the boot image of my device to root it using magisk manager, but I can't find it.
Help!!!!!
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
I think this only possible when you have root..
It is also not possible with adb without root...so
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Edit:- If your device is Mediatek, using SP Flash Tool you can readback. If you have Snapdragon, then bkerler's edl tool can readback. (No need of root)
HemanthJabalpuri said:
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Click to expand...
Click to collapse
Do you mean the stock firmware on the device, where is this located? or do you mean from the vendors web page?
bromeara said:
Do you mean the stock firmware on the device, where is this located? or do you mean from the vendors web page?
Click to expand...
Click to collapse
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
Alright thank you. I'm fairly new to the android ecosystem and to boot I'm working on a Fire tablet so its running fireos and amazon doesn't really make it easy to touch their code
think he is facing the same situation as mine, for hk version of htc u12+, its hard to find the proper RUU or firmware from internet. Just wanna know the method of ...pulling the boot.img directly from device. Thanks in advance for any assistance.
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
Vita.T said:
Just wanna know the method of ...pulling the boot.img directly from device. Thanks in advance for any assistance.
Click to expand...
Click to collapse
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
I think this only possible when you have root..
It is also not possible with adb without root...so
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Edit:- If your device is Mediatek, using SP Flash Tool you can readback. If you have Snapdragon, then bkerler's edl tool can readback. (No need of root)
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
It's not that simple though, firmware comes in KDZ extension..have to extract using Extraction tool & even then extracted files are in .BIN extension..Boot.img is not available immediately after DZ extraction
dano.556 said:
It's not that simple though, firmware comes in KDZ extension..have to extract using Extraction tool & even then extracted files are in .BIN extension..Boot.img is not available immediately after DZ extraction
Click to expand...
Click to collapse
Ok....
I am assuming that the op has a samsung device....
Same Problem
Loku_kika said:
I have the same problem, I need the boot image of my device to root it using magisk manager, but I can't find it.
Help!!!!!
Click to expand...
Click to collapse
The Boot Image for oppo ax7 isn't available so i am trying to find aswell, OR i need help: taking the boot.img off my unrooted, non bootloader unlocked phone. Or extracting it from the stock ROM, unfortunately i'm not ble to open oppo's OFP file.
Lloydster said:
The Boot Image for oppo ax7 isn't available so i am trying to find aswell, OR i need help: taking the boot.img off my unrooted, non bootloader unlocked phone. Or extracting it from the stock ROM, unfortunately i'm not ble to open oppo's OFP file.
Click to expand...
Click to collapse
just google "Latest Software Version for OPPO OPPO AX7" and go to the Software Updates page on oppo-uk.custhelp.com. Download 2.4GB ozip file (like CPH1903EX_11_OTA_0210_all_oStq7F7jxqfF.ozip) and unpackit with 7zip program. You'll find boot.img inside .ozip file.
I do not have root, there is no recovery or rom for my phone, Can I extract the boot.img from my phone storage, to patch it with Magisk?
My Indian version Honor 7 with Android 6, PLKUL00 C675 B341, Bootloader unlocked, Rooted and Xposed installed.
today I received an update for B351, How should I proceed with the update.
Please someone help.
So if you reseaved the update then you should Just go to settings go down and update then click check for update
Timanttikuutio said:
So if you reseaved the update then you should Just go to settings go down and update then click check for update
Click to expand...
Click to collapse
Thats quite right, But my phone is rooted with xposed installed. So can I go and just click update?
Sent from my PLK-UL00 using XDA-Developers mobile app
no you cant
you need to remove root
first you should backup your and all important using hisuite then flash twrp and flash original honor 7 paggage from huawei website but you need to extract that huawei update file then flash system, boot, recovery and reboot
also you phone needs to be unlocked bootloader
ganeshindeed said:
My Indian version Honor 7 with Android 6, PLKUL00 C675 B341, Bootloader unlocked, Rooted and Xposed installed.
today I received an update for B351, How should I proceed with the update.
Please someone help.
Click to expand...
Click to collapse
First Unroot your device by flashing this UnSu script using TWRP recovery, then go to updater, update your device, if its still doesn't work then lock your bootloader and try again.
ganeshindeed said:
My Indian version Honor 7 with Android 6, PLKUL00 C675 B341, Bootloader unlocked, Rooted and Xposed installed.
today I received an update for B351, How should I proceed with the update.
Please someone help.
Click to expand...
Click to collapse
Remove root, it will not let the phone to be updated
If iam right...
1. Unroot from su
2. Flash FULL original B341 ROM by extracting the update file
3. Then update by Extracting the B351 update file.
4. ROOT again.
by the way before updating someone was saying i have to flash stock recovery.
How do i do that...
I extracted the B341 rom and found two recovery 1&2..how do i flash it.
Sent from my SM-T715 using XDA-Developers mobile app
PalakMi said:
Remove root, it will not let the phone to be updated
Click to expand...
Click to collapse
If iam right...
1. Unroot from su
2. Flash FULL original B341 ROM by extracting the update file
3. Then update by Extracting the B351 update file.
4. ROOT again.
by the way before updating someone was saying i have to flash stock recovery.
How do i do that...
I extracted the B341 rom and found two recovery 1&2..how do i flash it.
Sent from my SM-T715 using XDA-Developers mobile app
Ask @DigiGoon
@ganeshindeed
Follow these steps:
Unroot from UnSu script.
Flash system.img, cust.img, boot.img, recovery.img from B341 ROM by extracting the UPDATE.APP(B341) file.
Then put UPDATE.APP(B341) file in dload folder of your External SDCARD, and do the three button update.
Once the system successfully boots up.
Then put UPDATE.APP(B351) file in dload folder of your External SDCARD, and do the three button update again.
Thanks for the detailed help...appreciate it.
The problem is
1. Iam having two recovery after extracting B341. Which to use?
2. Also flash means how to do it...these are .img
Thanks
Sent from my SM-T715 using XDA-Developers mobile app
DigiGoon said:
@ganeshindeed
Follow these steps:
Unroot from UnSu script.
Flash system.img, cust.img, boot.img, recovery.img from B341 ROM by extracting the UPDATE.APP(B341) file.
Then put UPDATE.APP(B341) file in dload folder of your External SDCARD, and do the three button update.
Once the system successfully boots up.
Then put UPDATE.APP(B351) file in dload folder of your External SDCARD, and do the three button update again.
Click to expand...
Click to collapse
Thanks for the detailed help...appreciate it.
The problem is
1. Iam having two recovery after extracting B341. Which to use?
2. Also flash means how to do it...these are .img
Thanks
Sent from my SM-T715 using XDA-Developers mobile app
@ganeshindeed
I said recovery.img there is second one named as recovery2.img but you just have to extract recovery.img.
And by flash I meant to flash via fastboot commands, like these:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
and to boot into fastboot/bootloader mode switch off your device and press and hold Vol DOWN + Power Button.
DigiGoon said:
@ganeshindeed
I said recovery.img there is second one named as recovery2.img but you just have to extract recovery.img.
And by flash I meant to flash via fastboot commands, like these:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
and to boot into fastboot/bootloader mode switch off your device and press and hold Vol DOWN + Power Button.
Click to expand...
Click to collapse
Thanks man..
Sent from my SM-T715 using XDA-Developers mobile app
Always here to help.
DigiGoon said:
@ganeshindeed
Follow these steps:
Unroot from UnSu script.
Flash system.img, cust.img, boot.img, recovery.img from B341 ROM by extracting the UPDATE.APP(B341) file.
Then put UPDATE.APP(B341) file in dload folder of your External SDCARD, and do the three button update.
Once the system successfully boots up.
Then put UPDATE.APP(B351) file in dload folder of your External SDCARD, and do the three button update again.
Click to expand...
Click to collapse
Am always getting struck at 3rd step, three button update at 5%.
What shall i do
Sent from my SM-T715 using XDA-Developers mobile app
ganeshindeed said:
Am always getting struck at 3rd step, three button update at 5%.
What shall i do
Click to expand...
Click to collapse
If you are using the three button method then don't.
Just flash the four images and let Android boot normally.
Use your dialer to dial *#*#2846579#*#*
And choose software upgrade and then SD card upgrade and now it should run till 100%
Tried it friend but install failed at 30%
Sent from my SM-T715 using XDA-Developers mobile app
ganeshindeed said:
Tried it friend but install failed at 30%
Click to expand...
Click to collapse
ganeshindeed said:
Tried it friend but install failed at 30%
Click to expand...
Click to collapse
How long did you let it run when it got stuck at 30%.
When I got stuck at 5%, I used the method I mentioned and it worked for me.
Give it another try or two. Sorry, I don't know of any other way.
Maybe 5 to 10minutes...
Sent from my SM-T715 using XDA-Developers mobile app
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
fargonaz said:
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
Click to expand...
Click to collapse
Thanks for taking the time to the reply mate, sorry to hear about your M3.
I tried fastboot flash ramdisk ramdisk.img and it said flashed successfully but the device is still not booting. Nothing else seems to have changed either.
Let me know if I misunderstood what you wanted to try or if you have any other ideas.
Cheers
etheberge said:
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Click to expand...
Click to collapse
I think I am in a similar spot. I went from a custom ROM back to stock, but now all attempts at installing full OTAs fail. Did you ever figure this out how to fix it?
Thanks
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Edit: I can flash system, I did flash kernel, I can flash recovery too, but when I try to flash anything else, it gives me that error
Edit2: can someone tell me which files do I need to extract via huawei update extractor to flash? I know that system.img is one of them
konopla4 said:
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Click to expand...
Click to collapse
Check if you're still FRP unlock in Fastboot.
ante0 said:
Check if you're still FRP unlock in Fastboot.
Click to expand...
Click to collapse
Both bootloader and from are unlocked
konopla4 said:
Both bootloader and from are unlocked
Click to expand...
Click to collapse
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
You could use HWOTA for Mate 10 Lite if you can get into stock recovery, as it will flash the full update.app rather than the limited partitions fastboot can flash.
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
Click to expand...
Click to collapse
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
konopla4 said:
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
Click to expand...
Click to collapse
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
Click to expand...
Click to collapse
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
konopla4 said:
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
Click to expand...
Click to collapse
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
ante0 said:
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
Click to expand...
Click to collapse
Waaaait it, I can update from TWRP?
Or is it a specialized one?
konopla4 said:
Waaaait it, I can update from TWRP?
Or is it a specialized one?
Click to expand...
Click to collapse
It's a script, but it needs a TWRP that's compatible. The one by Catuva21 is (or so I've heard).
Before rooting, you'll need an unlocked bootloader. Check my previous guide here: https://forum.xda-developers.com/x3...ck-bootloader-realme-x3-t4136325/post83109505.
After unlocking, we can get started with rooting.
First, you'll want to install Magisk Manager. You can find the latest APK here: https://github.com/topjohnwu/magisk/releases.
Next, you'll need to download the latest OTA OZIP. There's a link at the end of the post for this.
While that's downloading, you'll also need to grab a copy of an OZIP extractor. Follow the link below, download the repository as a ZIP, and unzip it.
For this program to work, you'll need Python 3 installed. On Linux systems, it should already be installed. On Windows 10, you can install Python from the Store.
Open a terminal or CMD window and cd to where you extracted the OZIP extractor files.
Use pip to install the docopt module: "pip3 install docopt".
Once the OZIP has finished downloading, move it to the same folder as the extractor program.
Run the following command: "python3 ozipdecrypt.py NAME_OF_OZIP_FILE". This will take a while!
Once it's done extracting, there will be a ZIP file with the same name as the OZIP. We only need two files from here: boot.img and vbmeta.img.
Extract those two files to the same folder as the extractor program.
Copy the boot.img file to your device.
Open Magisk Manager and choose the "INSTALL" option next to the Magisk status. Tap "INSTALL" in the dialog that appears and then choose "Select and Patch a File."
Browse to where you copied your boot.img to and select it. Magisk will now patch it and create a file named magisk_patched.img in your Download folder. Copy magisk_patched.img back to your computer.
Reboot your phone into fastboot: "adb reboot bootloader". If you don't have ADB or fastboot installed (which you should, since you needed them for the previous guide), you can find the link in the bootloader unlocking guide.
Before you flash the patched boot image, you need to disable image verification, which is where the vbmeta.img comes in.
Run "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (remember, you'll probably need to unplug and replug the device after hitting Enter). This will disable boot verification and allow the patched image to actually work.
Finally, run "fastboot flash boot magisk_patched.img". This will flash the rooted boot image to your device.
Run "fastboot reboot" and let the phone boot back into the system. Check Magisk Manager and you should now be rooted!
Troubleshooting:
If you get an error that the boot image was "destroyed," don't worry. You'll just need to flash the stock boot.img and try again. Unplug your phone from your computer and wait for it to turn off. Once the screen is black, hold down VOL-DWN and PWR to enter fastboot mode. You can then run "fastboot flash boot boot.img" (where boot.img is the stock image) to restore. Reboot, then try the vbmeta and patched image flashing again.
You can get the OTA OZIPs from Realme EU's site: https://www.realme.com/eu/support/software-update.
You can get an OZIP extractor from here: https://github.com/bkerler/oppo_ozip_decrypt. (NOTE: you'll need to install the "docopt" Python module.)
OZIPs contain a boot.img, which you can extract and patch with Magisk for root. If someone else has an idea for patching Magisk into the boot.img, this is where to start.
Here's my patched boot.img for A.32. I don't recommend using this on other versions: https://www.androidfilehost.com/?w=files&flid=315334
Could you share your patched boot.img for the latest OS version? And could you check if the aux magisk module from X2 pro works to activate all aux cameras in Gcam? Thanks
Patched boot image
Thanks Zacharee1....Could someone upload the patched boot image for the latest one? Also do we have a generic version of twrp that can be installed on x3 ?? If yes, then we could try installing havoc gsi...
I've added a link to a patched A.32 boot.img.
also needed pip install pycryptodome win10
Zacharee1 said:
I've added a link to a patched A.32 boot.img.
Click to expand...
Click to collapse
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
cheth20 said:
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
Click to expand...
Click to collapse
It's pretty simple to patch it yourself. Download the OZIP, use the Python tool to unencrypt it, take the boot.img file out of the created ZIP, copy it to your device, and then patch with with Magisk Manager.
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Firmware for RMX2085
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
The firmware is the same for them all.
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
phonedroid said:
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
Click to expand...
Click to collapse
Yes, and that's why. It might be possible to pull the boot image directly from your device, but I'm not sure.
Can someone tell me if I can use realme 6 pro vbmeta.img?
realme x3 super zoom twrp recovery bro give me
Hi Sukhad,
I updated the system to the latest OTA (39), but I do not have the latest magisk patched file. Could you kindly help me with latest version patched boot for x3 superzoom?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
Thanks Zacharee1!
Finally did it (15/20 year old windows machines... Win7 was dificult and finally use a win8). Worth big as root gives me a new smartphone
Had all sorts of problems (installing python... But once installed was pretty quick) mainly adb conneting...
Anyway I will share vbmeta.img attached for a38 rom.
Also link to boot img, again a38.
For A38 rom
http://www.mediafire.com/file/i9jvl1al95k40vv/magisk_patched_a38.img/file
bro please could u tell me.. help
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
bro please could u tell me.. after unlocking the bootloader of realme X3 superzoom , does it breaks the fingerprint sensor?
ota update after root
Someone have experiencing ota update failed on rooted device with this procedure? I m on RMX2081EU_11.A.40 but ota update to RMX2081EU_11.A.42 fails. how to update now?
Good afternoon. I want to get a root for my X3 super zoom, but I literally do not understand all the manipulations so that your description is attached with an image (screenshots). I think it will be useful for everyone who can't.
Anyone have working patched boot.img for a46?? I'm trying and always boot destroyed. Magisk 21.4
It's really weird on official en site there is a42 soft from September but on pl site there is a46 from December.