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.
Related
Hi,
After much read of guides, I post here my SIMPLE guide for OTA upgrades when your Moto G is unlocked and you use systemless root and TWRP.
This guide is safe and works!
For example, with this guide you can upgrade from STOCK MPJ24.139-23.4 to MPJ24.139-63:
Warning: I assume you know the concepts "fastboot", "systemless root" and TWRP.
For the original stock firmware search here for your exact MODEL and VERSION: http://mirrors.lolinet.com/firmware/moto/athene/official/
1) Reboot to TWRP and make a FULL BACKUP of your current firmware. Use the SD-Card and not the internal memory.
2) To Apply the OTA you need to restore BOOT.IMG and SYSTEM.IMG.
2a) If you rooted your device, for sure your BOOT.IMG isn't the original one. You can:
- Option 1: Restore it from an original backup of your firmware (if you backup it prior to root).
- Option 2: Download the STOCK and ORIGINAL firmware for your device, extract "boot.img" and flash it in the fastboot mode using "fastboot flash boot boot.img".
2b) If you use Systemless SuperSU then your system partition can be untouched. In case of doubt, or if the patch shows an error, you can restore it...
- Option 1: Restore it from one backup of your firmware (only if you backup it prior to root).
- Option 2: Download the STOCK and ORIGINAL firmware for your device, extract "system.img_sparsechunk.0-7" and flash them in the fastboot mode using these 8 commands (execute one, wait until completes, then execute the next one):
Code:
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
3) Boot to the TWRP Custom Recovery (you don't need to restore the original Recovery partition).
4) Download the OTA (Blur_Version.24.24.4.athene.retail.en.US.zip) or copy it from the downloaded directory. Copy the ZIP file to a computer, extract the file "/META-INF/com/google/android/updater-script" and edit it... Remove these three lines (this only removes the check of the running build, because you like to execute it inside TWRP):
Code:
getprop("ro.build.thumbprint") == "6.0.1/MPJ24.139-63/64:user/release-keys" ||
getprop("ro.build.thumbprint") == "6.0.1/MPJ24.139-23.4/4:user/release-keys" ||
abort("Package expects build thumbprint of 6.0.1/MPJ24.139-63/64:user/release-keys or 6.0.1/MPJ24.139-23.4/4:user/release-keys; this device has " + getprop("ro.build.thumbprint") + ".");
After that, copy (repack) this edited file to the ZIP file of the OTA. I suggest to change the name of the ZIP, for example to "Blur_Version.24.24.4.athene.retail.en.US-TWRP.zip". Now, you can run this patch file running TWRP.
5) Copy the patch OTA file to the SD-CARD, boot to the TWRP and apply the OTA... After several minutes the task completes. Reboot and check if the update is done and all works well. Your data needs to be already there...
6) Reboot into the fastboot mode and reflash the TWRP Custom Recovery using "fastboot flash recovery twrp-3.0.2-0-athene.img". Then boot in the recovery mode and do another Backup (for save untouched "system.img" and "boot.img" partitions).
7) Now you can re-root using the TWRP mode and SuperSU 2.78 in Systemless mode (remember to execute "echo SYSTEMLESS=true>>/data/.supersu" prior to install the SuperSU.zip)
I hope this helps you!
This guide only uses the minimum and required steps.
:good:
If you like to download one already patched OTA, then download it from here (join the two files first!):
Part 1: http://www.sendspace.com/file/dkws7p
Part 2: http://www.sendspace.com/file/xaompg
Part 1: http://www.sendspace.com/file/e3of46
Part 2: https://www.sendspace.com/file/a3tl4r
CRC:
filename=Blur_Version.24.24.4.athene.retail.en.US-TWRP.zip
size=508332365
crc32=AFEC5752
Thank you, I was wondering about just this. Will come In handy.
Do you need to resign the zip with signapk?
Thanks for you guide!
I used it to update my Lenovo P2 to Nougat.
I would love to unlock my phone, alas, I am on an amazon variant of the G4, so it cannot be done. I would love to try out the OS listed here.
Indianvixen9 said:
I would love to unlock my phone, alas, I am on an amazon variant of the G4, so it cannot be done. I would love to try out the OS listed here.
Click to expand...
Click to collapse
I've heard this from a few people. I got the Amazon variant little more than a week ago. Unlocked BL and rooted lickety splits, no issues.
I consider myself pretty tech savvy, but the post might as well have been in Swahili. Can it be dumbed down any further?
The links at the end of your post for the two patched ota downloads aren't any good, would you please upload them again? Thanks
t0mm13b said:
Do you need to resign the zip with signapk?
Click to expand...
Click to collapse
No, just re-zip! :victory:
Dbush72 said:
The links at the end of your post for the two patched ota downloads aren't any good, would you please upload them again? Thanks
Click to expand...
Click to collapse
Done! :highfive:
Thank you for the reply and refreshing the download links
As far as I can tell you are flashing this via TWRP which is why the zips dont need signed is that correct?
I have an xt1625 non-amazon version that im working with.
I tried flashing Blur_Version.25.11.12.athene.retail.en.US on top of ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml which didnt work with this error:
E3005: "EMMC:/dev/block/bootdevice/by-name/boot:
has unexpected contents
I also tried flashing Blur_Version.25.11.12.athene.retail.en.US on top of ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml
Failed with the same error as last time
I also tried flashing Blur_Version.24.31.48.athene.retail.en.US on top of ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml which does seem to pass the version checks but gives this error:
"eom/app/BRApps2/oat/arm/BRApps.odex" has unexpected contents.
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?
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void... Well, probably not.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* A lot.
*
* Tl;dr: if your device crashes and burns, I'm sorry, but I'm not to be blamed.
*/
Hey guys.
This is a guide on how to install official Android 8.1.0 "Oreo" on our beloved, forgotten, poor Moto G5s (montana). As you all may know, Lenovorola still hasn't released Oreo for everyone worldwide. Only a few Latin American countries are receiving the update, with Brazil due to receive it Soon™, since we've already received the August security patch (still Nougat though :/).
Update 2018.09.29: Brazil and India have also started receiving Oreo, but with a different build (OPP28.65-37-2).
However, this is Lenovorola we're dealing with, so I went ahead, captured the OTA and created a TWRP flashable zip, by patching the June firmware (NPPS26.102-49-11) with said OTA. And also, there's the standard .xml.zip to be used with fastboot, directly from Moto.
For those of you who want to keep everything stock, locked bootloader and all, I recommend going with the fastboot zip. For those who already have unlocked their phone's bootloaders and have TWRP installed, or are coming from a custom ROM but don't want to fiddle around with fastboot, you should use the TWRP flashable zip.
I can't stress this enough. ALWAYS BACK UP YOUR STUFF!!!! Do a TWRP backup (data, system, boot). I recommend backing up the contents of your internal storage as well. And for those willing to downgrade at some point, back up your persist and efs partitions, otherwise you'll lose IMEI!
Oh, and I assume you already have adb, fastboot and the Motorola USB drivers installed. In case you don't...
Motorola USB Drivers
Android SDK Platform Tools (includes adb & fastboot)
If you use Linux, you don't need to install any drivers, but you may have to configure udev to allow fastboot to detect your device. But that, along with telling how to configure adb and fastboot, is beyond the scope of this thread.
I don't know how things work in the Apple side, so kindly don't ask me how to do that on macOS.
This firmware should work on all Moto G5s models (XT1791/2/3/4/5/7). I can't tell if it works on model XT1799-2 (aka Green Pomelo / Qingyou).
A few warnings:
1. Forced encryption has not been disabled. So, if your phone is not encrypted, it will be encrypted again upon the very first boot. Don't interrupt the process, otherwise you'll lose ALL of your data! (You can flash @Zackptg5's dm-verity / forced encryption disabler if you want to)
2. Xposed doesn't work, whether it's installed to /system or via Magisk (systemless). I've already opened an issue on GitHub and am awaiting a reply.
3. (Fastboot only) Updating to this firmware will also update your bootloader and partition table. If you're unsure about that and/or afraid of a possible hard brick, skip the gpt and bootloader lines.
4. Please install the proper build for your software channel. For retbr and retin, use OPP28.65-37-2. For the other channels, go with OPP28.65-37.
5. If your phone's software channel is retbr or retin and you have already flashed the -37 build, you can simply dirty flash the -37-2 build over it. No need to factory reset / fastboot erase userdata.
With that out of the way, let's get to what matters most.
Downloads:
Build OPP28.65-37 (retla):
Fastboot ZIP (Android File Host | MEGA)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Build OPP28.65-37-2 (retbr & retin):
Fastboot ZIP (Android File Host)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Installation Guide:
Fastboot ZIP:
1. Download (obviously)
2. Extract the contents to a folder of your choice
3. Go to the folder which you extracted the files to
3. Inside the folder, open a command prompt, PowerShell, terminal or whatever you use as a command line interface
4. Put your device into fastboot mode if you haven't already done that (just hold Vol Down + Power for a while) and connect it to your PC
5. Execute the following commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
reboot
6. Have fun
Click to expand...
Click to collapse
TWRP Flashable ZIP:
1. Download (duh)
2. Put the file at the root of your internal storage (/sdcard)
3. Reboot to TWRP
4. Do a factory reset (optional if coming from stock Nougat) and then format /system
(If your device is encrypted and you want to remove encryption, you will have to format /data and then flash the forceencrypt disabler I mentioned above after flashing the ROM)
5. Flash the zip
6. Reboot
7. Have fun
Click to expand...
Click to collapse
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
@Cesarcami53 for telling us that the update was out for retla
@erfanoabdi for his Motorola OTA Link Generator and IMG Patch Tools
@lohanbarth for mirroring the fastboot zips to AFH / Mega
In case I forgot someone, please do let me know.
F.A.Q. (Read this before crying!!!!)
Q: Why did you come up with this?
A: Because Lenovorola is pulling a Samsung, taking forever to officially deliver the Oreo update to everyone.
Q: ERMAHGERD DIS ROM SUCKZ, MAH BATTERY IS DEAD IN 30 MINS, PLZ HALP!
A: Please do blame Motorola, or yourself, or your apps' developers, but not me. I haven't got anything to do with that. I haven't changed anything.
Q: What works and what doesn't?
In theory, everything should work, and nothing should be broken, since this is a stock ROM.
Q: Will you add feature xyz?
A: No.
Q: Why no inbuilt root/Magisk/xyz/abc?
A: Because not. 1. There's something called freedom of choice, and that must be respected. / 2. I want to keep everything as bit-perfect as possible, and as close as possible to what you would get by flashing a real OTA.
Q: How do I report bugs?
A: If you wanna report a bug, send me a logcat. In case of a kernel panic, /proc/last_kmsg will help.
Q: How do I flash this?
A: I suggest you scroll up and read the OP. The instructions are there.
Q: How do I tweak this ROM?
A: For theming, there's full OMS/Substratum support. Xposed doesn't work, so no extra tweaks for now.
Q: This kid is such a n00b!
A: Oh well then, why don't you go do something like this yourself, instead of criticizing my work and wasting your time?
Reserved again
Oh look! Another reserved post!
And as a bonus, have this nice little dark boot logo from me, which hides that dreaded "N/A" and also "bad key" things. Extract the zip file and flash the logo3.bin file inside using fastboot:
Code:
fastboot flash logo logo3.bin
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Which security pet
Official or Soak test?
Kamin4ri said:
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
[/SIZE]
Click to expand...
Click to collapse
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
I can tell you that this build work very well in european distribution (reteu).
Basicly everything work including sim and nfc(paying not tested yet)
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Also not able to download, please offer another download Location!
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
ilovepanda said:
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Click to expand...
Click to collapse
No. Your bootloader will be updated if, and only if, you install via fastboot and actually execute the respective command.
[email protected] said:
Official or Soak test?
Click to expand...
Click to collapse
This is the official firmware released for retla (Latin America). However, the soak tests in Brazil haven't finished yet. I'll update the OP with the link for the Brazilian firmware as soon as it's available.
NZedPred said:
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
Click to expand...
Click to collapse
Thank you, friend! I'll be definitely using that guide again.
7opex0 said:
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
Click to expand...
Click to collapse
Only if you're flashing via TWRP. If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
giugiura said:
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Click to expand...
Click to collapse
dau999 said:
Also not able to download, please offer another download Location!
Click to expand...
Click to collapse
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Kamin4ri said:
If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
Click to expand...
Click to collapse
Okay then! Thanks for information.
7opex0 said:
Okay then! Thanks for information.
Click to expand...
Click to collapse
Not at all!
Kamin4ri said:
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Click to expand...
Click to collapse
Please upload it on some other cloud so that we can download it thanks for help sir
In advance
Devices that started to be received today have Oxygen OS 10.5 out of the box.
No flashable zip for that software release is publicly available, meaning its stock boot.img cannot be extracted.
You then need to update to a newer build first. You can do so from my OxygenOS builds repo thread.
Once done, enable developers options and enable OEM unlock.
Reboot to fastboot (enable USB debugging in dev options and use adb reboot bootloader)
Type fastboot oem unlock and accept to unlock bootloader (warning: as a safety measure Android will wipe your userdata)
Go through OxygenOS setup
Install Magisk Manager from https://github.com/topjohnwu/Magisk/releases/download/manager-v7.5.1/MagiskManager-v7.5.1.apk
Move stock boot.img to your phone internal storage (please open spoiler)
For your convenience, 10.5.2 stock boot.img for EU and India have been extracted
EU download: https://drive.google.com/file/d/18aPqErEMbRqmN4BpdvHE4OKgizDcEbou/view?usp=sharing
India download: https://drive.google.com/file/d/1ZIEYWH2PYkKyojq_S_i_onBstejHKDTJ/view?usp=sharing
For future builds, you can use payload dumper (Windows) , (Linux ) to extract stock boot.img
Click on Install
Choose "Select and patch a file"
Select your stock boot.img
Wait until Magisk patches your boot.img, and once patched it can be found in the Downloads folder
Copy that patched boot.img (which should be named magisk_patched.img) to your computer
Boot into fastboot again
Type fastboot getvar current-slot into your terminal window and press Enter.
If the output is a , type fastboot flash boot_a magisk_patched.img into your terminal window and press Enter.
If the output is b , type fastboot flash boot_b magisk_patched.img into your terminal window and press Enter.
Reboot to OxygenOS
Open Magisk Manager and your device should now be rooted.
TIPS:
- Ensure you got latest platform tools installed from https://developer.android.com/studio/releases/platform-tools
- Backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.
Credits:
@topjohnwu for making Magisk
/u/Jisifus for testing on his device and for screenshots
Some_Random_Username said:
TIPS:
- Ensure you got latest platform tools installed from https://developer.android.com/studio/releases/platform-tools
- Backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.
Click to expand...
Click to collapse
Great to see it works this way and thanks for the tip.:good:
do u lose all data while rooting?
#edit1
nevermind, cannot read right
OK, will give this a try asap,have the device here now...
I gave it a try, works like a charm! Thanks for this! Small tip, unlock bootload before u copy your files
now my phone is a bit laggy. with magisk on it.. i will test it later if its getting better
Some_Random_Username said:
Type fastboot getvar current-slot into your terminal window and press Enter.
If the output is a , type fastboot flash boot_a magisk_patched.img into your terminal window and press Enter.
If the output is b , type fastboot flash boot_b magisk_patched.img into your terminal window and press Enter.
Click to expand...
Click to collapse
You can simply type "fastboot flash boot magisk_patched.img" - it flash boot to current active slot. Just for note.
Can confirm that it works, just tried it myself
If WiFi/data does not work (usually happens when you flash wrong version, but can also happen if you flash correct one), fastboot boot the image, then do a direct install in Magisk Manager.
Also, big thumbs up for adding tips for persist backup, I see too many people needing to send their device back because they messed it up somehow.
Failed for me
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
jmwengineering said:
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
Click to expand...
Click to collapse
The size is normal.
When patching your image you have to select "Preserve Force Encryption" and "Preserve AVB 2.0/dm-verity" under advanced settings in the main screen where you patch the image.
jmwengineering said:
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
Click to expand...
Click to collapse
And that's why it's recommended to boot the patched image first.
Thanks
Lossyx said:
The size is normal.
When patching your image you have to select "Preserve Force Encryption" and "Preserve AVB 2.0/dm-verity" under advanced settings in the main screen where you patch the image.
Click to expand...
Click to collapse
Thanks for confirming file size - Preserve Force Encryption and Preserve AVB 2.0/dm-verity were ticked during the patching process. Guess I'll have to wait until TWRP is verified as Nord compatible.
---------- Post added at 07:06 PM ---------- Previous post was at 06:59 PM ----------
Kollachi said:
And that's why it's recommended to boot the patched image first.
Click to expand...
Click to collapse
Thanks for the reply. Not sure what you mean by booting the patched image first. You have to create the patched image on the phone first before you can flash and then boot it. Step 7 in my post above details the flashing of the patched image and subsequent attempt to reboot Oxygen OS. I can't boot the patched image until I've created and flashed it!
jmwengineering said:
Thanks for the reply. Not sure what you mean by booting the patched image first. You have to create the patched image on the phone first before you can flash and then boot it. Step 7 in my post above details the flashing of the patched image and subsequent attempt to reboot Oxygen OS. I can't boot the patched image until I've created and flashed it!
Click to expand...
Click to collapse
Nah, instead of flash the patched boot image you can boot it only. Not sure why it's not working for you. But usually it should work.
Command: fastboot boot "patched boot image"
Edit: that's also what lossyx said. Boot image and than install it with magisk manager.
And if you boot the image and something went wrong you aren't bricked or anything. It's a safe way to test something.
Thanks for the advice - will boot the image file on my PC rather than flashing first.
Sent from my AC2003 using Tapatalk
Does unlocking the bootloader break widewine L1 on this device like it did with 7/7T/7P/7TP/8/8P
..
CryllicBuster273 said:
Does unlocking the bootloader break widewine L1 on this device like it did with 7/7T/7P/7TP/8/8P
Click to expand...
Click to collapse
Yeah I guess when you unlock your phone it will break L1 as always.
---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------
DIR49DNOR0N said:
I will try this unless twrp is cooked on release. Where did you get the OTA zips from actually?
I want to, extract boot.img, save it, patch boot.img, boot it, use some apps that require root and remove some packages, uninstall magisk, power down, use normal image, relock bootloader. Does this work how i expect it to work ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-nord/how-to/oneplus-nord-repo-oxygen-os-builds-t4138085
DIR49DNOR0N said:
I will try this unless twrp is cooked on release. Where did you get the OTA zips from actually?
I want to, extract boot.img, save it, patch boot.img, boot it, use some apps that require root and remove some packages, uninstall magisk, power down, use normal image, relock bootloader. Does this work how i expect it to work ?
Click to expand...
Click to collapse
No, keep the bootloader unlocked if your phone is modified, else it can cause some issues.
Btw when you lock/unlock the bootloader, data will be wiped. apps will be reinstated again so that's useless
The guide worked perfectly and I'm up and running with Root!
One thing I have noticed is that the Google Play store is no longer Play Protect Certified.
I've tried registering my device with Google using this XDA guide but I haven't found any change to the Play Store certification.
I should probably wait for a while to see if the registration takes some time. I also couldn't use the adb commands that Google recommends and I had to use the Device ID app to get the Google Service Framework (GSF).
I've read in a few places that it may be because the Bootloader is unlocked and I'm wondering if I should re-lock it now that I have root. Not sure how/if that will affect my ability to keep root when future updates come out though.
Anyone have any thoughts/experience with this?
Possible TWRP without waiting?
Can anyone use this and try? Might be used as an alternate Method for Rooting via TWRP
https://forum.xda-developers.com/an...g/guide-how-to-port-twrp-to-qualcomm-t3420013
I tried installing fastboot images extracted from ozip files but vendor and system images gave partision not found error and I didn't have a windows device I had ubuntu
I installed .ofp by this way
I had bootloader unlocked, please report if it works without bootloader unlocked
1.Download .ofp file of your device
https://c.realme.com/in/post-details/1271381271037083648 this is link for Indian version from realme's website
2.extract .ofp file, I did it using https://github.com/bkerler/oppo_decrypt (This took awfully long time for me)
3.Go to fastboot and flash all the files through fastboot commands
( 1. fastboot flash boot boot.img 2.fastboot flash super super.img 3.fastboot flash vbmeta vbmeta.img 4. fastboot flash vbmeta_system vbmeta_system.img 5.fastboot flash vbmeta_vendor vbmeta_vendor.img 6.fastboot flash userdata userdata.img)
in this order
4.go to stock recovery and format and wipe data
5.Now you should be able to boot
(If anyone wants stock recovery tell me I'll give link)
thank you very much this have save me a lot of times.
my windows computer have problem with fastboot driver. i installed realme adb-fastboot driver again and again but it doesnt work, device manager still have ''question mark'' android driver, maybe windows need to be reinstall or something... i use the same pc to unlock bootloader before,
i unpack the ozip on raspbian (using raspberry pi 3 with microsd) , fastboot flash realme x 3 that i messed up before and now it work.
Shreeram02 said:
I tried installing fastboot images extracted from ozip files but vendor and system images gave partision not found error and I didn't have a windows device I had ubuntu
I installed .ofp by this way
I had bootloader unlocked, please report if it works without bootloader unlocked
1.Download .ofp file of your device
https://c.realme.com/in/post-details/1271381271037083648 this is link for Indian version from realme's website
2.extract .ofp file, I did it using https://github.com/bkerler/oppo_decrypt (This took awfully long time for me)
3.Go to fastboot and flash all the files through fastboot commands
( 1. fastboot flash boot boot.img 2.fastboot flash super super.img 3.fastboot flash vbmeta vbmeta.img 4. fastboot flash vbmeta_system vbmeta_system.img 5.fastboot flash vbmeta_vendor vbmeta_vendor.img 6.fastboot flash userdata userdata.img)
in this order
4.go to stock recovery and format and wipe data
5.Now you should be able to boot
(If anyone wants stock recovery tell me I'll give link)
Click to expand...
Click to collapse
I followed the same steps, but no luck. later i checked in twrp and it says no os installed.
ash1337x said:
I followed the same steps, but no luck. later i checked in twrp and it says no os installed.
Click to expand...
Click to collapse
ignore twrp thing and u didn't follow everything as u have twrp u should install stock recovery
everything is cool but i have multiple super imgs what do i do?
Shreeram02 said:
I tried installing fastboot images extracted from ozip files but vendor and system images gave partision not found error and I didn't have a windows device I had ubuntu
I installed .ofp by this way
I had bootloader unlocked, please report if it works without bootloader unlocked
1.Download .ofp file of your device
https://c.realme.com/in/post-details/1271381271037083648 this is link for Indian version from realme's website
2.extract .ofp file, I did it using https://github.com/bkerler/oppo_decrypt (This took awfully long time for me)
3.Go to fastboot and flash all the files through fastboot commands
( 1. fastboot flash boot boot.img 2.fastboot flash super super.img 3.fastboot flash vbmeta vbmeta.img 4. fastboot flash vbmeta_system vbmeta_system.img 5.fastboot flash vbmeta_vendor vbmeta_vendor.img 6.fastboot flash userdata userdata.img)
in this order
4.go to stock recovery and format and wipe data
5.Now you should be able to boot
(If anyone wants stock recovery tell me I'll give link)
Click to expand...
Click to collapse
Send me stock recovery please
prabal_2004 said:
everything is cool but i have multiple super imgs what do i do?
Click to expand...
Click to collapse
Yes, 4 or 5 super img files how to flash
4 or more super img files, with defrent name
Sajeevkaif said:
4 or more super img files, with defrent name
Click to expand...
Click to collapse
If all of them have the same size, then they're duplicated, rename one of them to super.img, and delete the others.
SubwayChamp said:
If all of them have the same size, then they're duplicated, rename one of them to super.img, and delete the others.
Click to expand...
Click to collapse
for me, i have 1 super.0 file with 2.86gb
1 super.1 file 1.95gb
and 12 super.2 files ranging 800mb to 1.8gb
what should i get for the super.img?
i opened the super_map.csv and saw this(the picture below)
the super0 and super1 for all country is the same, and in the super2 is different
should i get my super.img from the super2 with my country?
CloudChase said:
i opened the super_map.csv and saw this(the picture below)
the super0 and super1 for all country is the same, and in the super2 is different
should i get my super.img from the super2 with my country?
Click to expand...
Click to collapse
Sometimes the tool split the super images, and sometimes it unpacks it in a one single file, but I guess the size can't be less than 5 or even 6 GB.
SubwayChamp said:
Sometimes the tool split the super images, and sometimes it unpacks it in a one single file, but I guess the size can't be less than 5 or even 6 GB.
Click to expand...
Click to collapse
the overall size of the ofp file for the global version of realme c25s is 21gb, do you need authorization when using the Realme Flash Tool?
SubwayChamp said:
Sometimes the tool split the super images, and sometimes it unpacks it in a one single file, but I guess the size can't be less than 5 or even 6 GB.
Click to expand...
Click to collapse
what should i do? i need to fix my phone
CloudChase said:
the overall size of the ofp file for the global version of realme c25s is 21gb, do you need authorization when using the Realme Flash Tool?
Click to expand...
Click to collapse
CloudChase said:
what should i do? i need to fix my phone
Click to expand...
Click to collapse
I referred to the super image size, it's unlikely that the image has just this size, anyway it doesn't hurt to try it, flash some of them and see, you can try using fastboot too.
SubwayChamp said:
If all of them have the same size, then they're duplicated, rename one of them to super.img, and delete the others.
Click to expand...
Click to collapse
No, all of threm have Difrent name and size (more than a gb file)
Sajeevkaif said:
No, all of threm have Difrent name and size (more than a gb file)
Click to expand...
Click to collapse
Did you try flashing one of them?
SubwayChamp said:
Did you try flashing one of them?
Click to expand...
Click to collapse
No,
There is a tool to merge Super Image if they are split into multiple files.
Follow this tutorial to merge it. Find the exact tool from Google search and ensure it has the orange logo as seen in the video.
my bad I didn't open xda for a long time as this device doesn't have much support on xda
yea only a10 has 1 super img other ones have multiple super imgs
if ur in still in stock u can use partition backup app(needs root) from playstore to backup required img files
I'll try to upload separate img files from a11 and a12 backed up here soon