Related
[Evert] [Stock] Firmware - Return to Stock.Disclaimer
I can not be held responsible for any type of problem with your device. This information is for the sole purpose of reporting and is delivered "as is". Only the tests will confirm if everything works well or does not work at all, proceed with caution.
Recommendations.
Make sure to back up all information, device data, and (optional) persistence partitions of the device.
Always use common sense, and confirm that you do not have an error message in the console. Verify that things are done correctly.
Requirements
Make sure that the drivers and everything related to connectivity is working properly. The official Motorola drivers work fine, and the google fastboot drivers too. Look for tutorials on installing the fastboot driver if your computer is not detecting it properly, the tutorials of other moto models (eg moto g5 plus) on the drivers and others work just as well.
All this process spends time and of course the battery of your device, make sure you have a good battery (50+) and stay connected as much as possible.
Make sure you install the right firmware, in other devices from Oreo things are not so tight, in my case, my XT1926-7 device works perfect with a retailUS firmware, but it depends on each one...
All the commands and others are done from the fastboot utility, you can find it in https://developer.android.com/studio/releases/platform-tools.
Process
Download the correct firmware for your device.
Right now there are not many firmware available, as time passes the list will grow.
One of several sites is LOLINET.
https://mirrors.lolinet.com/firmware/moto/evert/official/RETAIL/
(If not already installed, make sure of ..) Install the drivers and download the fastboot utility. And of course, verify that the driver works properly. It will be done later.
Extract the fastboot utility, and the firmware within the same directory.
To verify the connection, enter the bootloader of your device, connect it with the PC. On the PC; run the console, go to the folder where you extracted the fastboot utility, and type fastboot.exe devices, you should see the listed device in the console.
If the connection works correctly and you notice nothing strange, you can start the process.
Open the console in the directory where the fastboot utility is on the firmware files, there should be no more folders inside. (In this case you should adjust the path of the files in the commands). And write the following commands, verify that you do not have errors.:
Warning,
The commands listed below as "optional" do not necessarily have to be executed, but to be completely safe, execute them all, as long as you have the right firmware.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img (optional)
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1 (Optional)
fastboot erase modemst2 (Optional)
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot erase carrier (Optional)
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
[I][/I]
Press the Power button, and wait a bit.. It will take a few minutes to start.
If you hear "Hello moto", congratulations you are in Stock (and everything "should work fine").
Notes
If your firmware has more or less sparsechunk files (eg, sparsechunk.3 or img_sparsechunk.7), run them all.
The bootloader will remain unlocked.
If all this was helpful, I hope your thanks.
With love by iGor.
And how remove verity Mode enabled?..and a black screen saying phone flashed with different software
IGorMcLven said:
Make sure you install the right firmware, in other devices from Oreo things are not so tight, in my case, my XT1926-7 device works perfect with a retailUS firmware
Click to expand...
Click to collapse
I am looking for an Oreo firmware for dual SIM XT1926-7.
Will all RETAIL version(s) support dual SIM ?
For example, does EVERT_RETAIL_8.0.0_OPWS27.113-92-5 support dual SIM?
rybshik said:
I am looking for an Oreo firmware for dual SIM XT1926-7.
Will all RETAIL version(s) support dual SIM ?
For example, does EVERT_RETAIL_8.0.0_OPWS27.113-92-5 support dual SIM?
Click to expand...
Click to collapse
I have the same phone.
First do this:
Go to settings: tap System, tap about phone and write down which software channel you are on.
It will say something like this:
RETLA
or
TEFCO
or
TEMX
or
TIGCO
Those are the only channels which offer stock roms for the XT1926-7
If your phone is factory unlocked you will probably have to use the RETLA versions.
the on your computer go to:
mirrors . lolinet . com /firmware /moto /evert /official/
You will find the original android 8 stock rom in there:
XT1926-7_EVERT_*YOUR_CHANNEL*_8.0.0_OPWS27.113-89-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Before you flash your phone make sure that you have a backup of :
EFS
and
Persist
partitions.
If those get corrupted or wiped you won´t have carrier signal or wifi once you reboot your phone. trust me it happened to me.
good luck.
Dual SIM XT1926-7: firmware and TWRP issue
lcmp said:
I have the same phone.
Before you flash your phone make sure that you have a backup of :
EFS and Persist partitions
Click to expand...
Click to collapse
Which TWRP version, what exact build file did you use to back up/restore partitions?
Was your TWRP capable of backing up /data partition?
In another tread, I posted that (after Magisk root) the latest twrp-3.3.1-0-evert.img failed to back up the /data partition, but twrp-3.2.3-42-evert.img worked well
rybshik said:
Which TWRP version, what exact build file did you use to back up/restore partitions?
Was your TWRP capable of backing up /data partition?
In another tread, I posted that (after Magisk root) the latest twrp-3.3.1-0-evert.img failed to back up the /data partition, but twrp-3.2.3-42-evert.img worked well
Click to expand...
Click to collapse
For me, it works exactly the opposite.
TWRP 3.2.3 was not able to decrypt the phone data.
But booting temporarily with TWRP 3.3.1-0 would successfully decrypt and backup everything.
TWRP decryption issue
lcmp said:
For me, it works exactly the opposite.
TWRP 3.2.3 was not able to decrypt the phone data.
But booting temporarily with TWRP 3.3.1-0 would successfully decrypt and backup everything.
Click to expand...
Click to collapse
for which firmware build? Pie or Oreo?
In my case, I was able to back up with twrp-3.3.1-0-evert.img before flashing Magisk. And I was able to Magisk-root with twrp-3.3.1-0-evert.img successfully as well.
But once rooted, was NOT able to back up \data partition with twrp-3.3.1-0-evert.img.
So I tried twrp-3.2.3-42-evert.img and it worked.
Is it possible to permanently remove encryption?
rybshik said:
for which firmware build? Pie or Oreo?
Click to expand...
Click to collapse
PIE
rybshik said:
But once rooted, was NOT able to back up \data partition with twrp-3.3.1-0-evert.img.
Click to expand...
Click to collapse
I´m not an expert, but from what i know, You need to have a pin or unlock pattern on your phone. TWRP asks you for it and uses it to decrypt the data partition. Then your backups will succeed.
rybshik said:
Is it possible to permanently remove encryption?
Click to expand...
Click to collapse
I read it´s possible but i´m no expert on the subject. Why would you want to remove encryption? I think its a good feature
lcmp said:
You need to have a pin or unlock pattern on your phone. TWRP asks you for it and uses it to decrypt the data partition.
Click to expand...
Click to collapse
Does TWRP ask for a PIN during back up?
I have not set up any PIN/unlock pattern at all. So TWRP did not ask for it during back up, but just failed to back up , showing an error related to data partition.
Could absence of PIN cause the backup to fail?
rybshik said:
Does TWRP ask for a PIN during back up?
Click to expand...
Click to collapse
What I noticed is that when TWRP 3.3 boots, it asks for your pin or unlock pattern in order to use that as the credential to get the decryption key and decrypt the data partition. TWRP 3.2 won't do this ( again, in my experience ) hence the back up fails because everything is encrypted.
This is how I noticed that force installing TWRP 3.2 was useless. it doesn´t ask for your pin or your unlock pattern so it doesn´t have a way of decrypting the data partition. Again this was my experience. A more advanced android / twrp user could give a definite answer.
rybshik said:
I have not set up any PIN/unlock pattern at all. So TWRP did not ask for it during back up, but just failed to back up , showing an error related to data partition.
Could absence of PIN cause the backup to fail?
Click to expand...
Click to collapse
I think so, yes. If you don´t have a pin or unlock pattern in your phone, TWRP doesn´t have a way to "authenticate" and get the decryption key and decrypt the data partition. Again, I´m assuming this out of my own experience.
Hello, can anyone share me the persist file from a xt1926-6 please?
I am having an issue with this file and I don't know what to do now
Thank you
lcmp said:
I have the same phone.
First do this:
Go to settings: tap System, tap about phone and write down which software channel you are on.
It will say something like this:
RETLA
or
TEFCO
or
TEMX
or
TIGCO
Those are the only channels which offer stock roms for the XT1926-7
If your phone is factory unlocked you will probably have to use the RETLA versions.
the on your computer go to:
mirrors . lolinet . com /firmware /moto /evert /official/
You will find the original android 8 stock rom in there:
XT1926-7_EVERT_*YOUR_CHANNEL*_8.0.0_OPWS27.113-89-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Before you flash your phone make sure that you have a backup of :
EFS
and
Persist
partitions.
If those get corrupted or wiped you won´t have carrier signal or wifi once you reboot your phone. trust me it happened to me.
good luck.
Click to expand...
Click to collapse
Hello, how did you solve the persist issue? I have it corrupt and I don't know what to do
Thanks
lcmp said:
Before you flash your phone make sure that you have a backup of :
EFS
and
Persist
partitions.
If those get corrupted or wiped you won´t have carrier signal or wifi once you reboot your phone. trust me it happened to me.
good luck.
Click to expand...
Click to collapse
This has happened to me, however I am dumb and did not make a back up... So, does this mean I can never get my carrier signal back? Internet works but sim card refuses to be read.
Toonka95 said:
This has happened to me, however I am dumb and did not make a back up... So, does this mean I can never get my carrier signal back? Internet works but sim card refuses to be read.
Click to expand...
Click to collapse
You can, recently I posted a solution for this issue (i believe it's the same as yours)
https://forum.xda-developers.com/g6-plus/how-to/guide-how-to-solve-wifi-mobile-data-t3994827
wow bro, just wow... for those who are reading this do not erase the modem and carrier my phone is now pretty much useless because I didnt know that erasing that would reset my imei. Now my phone has no wi-fi and no carrier connection. Now im running a damn reverse tethering to see if i can reverse this. Any ideas now? How the hell do i get this back?
By the way give people a warning to not do that wtf.... I can only imagine how many people you fcked with this.
Doxmey said:
wow bro, just wow... for those who are reading this do not erase the modem and carrier my phone is now pretty much useless because I didnt know that erasing that would reset my imei. Now my phone has no wi-fi and no carrier connection. Now im running a damn reverse tethering to see if i can reverse this. Any ideas now? How the hell do i get this back?
By the way give people a warning to not do that wtf.... I can only imagine how many people you fcked with this.
Click to expand...
Click to collapse
The following are the official firmware commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I don't know why there is a erase carrier command in the op
But the erase modem lines are standard
Sent from my mata using XDA Labs
---------- Post added at 04:25 AM ---------- Previous post was at 04:24 AM ----------
I would try flashing
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Again
Sent from my mata using XDA Labs
These lines are copied from the flashfile.xml inside the stock.zip:
Code:
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
The "erase carrier" command is as usual as the "erase modemst1/2" command. That's the default.
---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------
Doxmey said:
wow bro, just wow... for those who are reading this do not erase the modem and carrier my phone is now pretty much useless because I didnt know that erasing that would reset my imei. Now my phone has no wi-fi and no carrier connection. Now im running a damn reverse tethering to see if i can reverse this. Any ideas now? How the hell do i get this back?
By the way give people a warning to not do that wtf.... I can only imagine how many people you fcked with this.
Click to expand...
Click to collapse
Erase carrier + modem will not erase your IMEI as long as your /persist is not corrupted!!
sd_shadow said:
The following are the official firmware commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I don't know why there is a erase carrier command in the op
But the erase modem lines are standard
Sent from my mata using XDA Labs
---------- Post added at 04:25 AM ---------- Previous post was at 04:24 AM ----------
I would try flashing
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Again
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
WoKoschekk said:
These lines are copied from the flashfile.xml inside the stock.zip:
Code:
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
The "erase carrier" command is as usual as the "erase modemst1/2" command. That's the default.
---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------
Erase carrier + modem will not erase your IMEI as long as your /persist is not corrupted!!
Click to expand...
Click to collapse
Yeah man it took me all day to try to get it all working again, the fix was i downloaded an older stock rom and it restored my IMEI, it had to be the older version though because the newer one would recover it. Anyways now i'm never erasing that carrier or modem if it's not really necessary.
revert xt1926-3 to factory (2020)
IGorMcLven said:
[Evert] [Stock] Firmware - Return to Stock.
Code:
...
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
...
Click to expand...
Click to collapse
The latest factory image I downloaded from lolinet does not contain 2 files for system_b, only one, and it's named differently, so imho you have to replace the 2 above fastboot commands with the following (taken from flashfile.xml inside the download):
Code:
fastboot flash system_b system_other.img
I recommend to *always* compare flashfile.xml to zip contents before using a series of flash commands from somewhere else. Or someone could develop an XSLT file to convert flashfile.xml to a flashing script
I'm attaching a little verification shell script to check that all required files are in place.
tseeling said:
The latest factory image I downloaded from lolinet does not contain 2 files for system_b, only one, and it's named differently, so imho you have to replace the 2 above fastboot commands with the following (taken from flashfile.xml inside the download):
Code:
fastboot flash system_b system_other.img
I recommend to *always* compare flashfile.xml to zip contents before using a series of flash commands from somewhere else. Or someone could develop an XSLT file to convert flashfile.xml to a flashing script
I'm attaching a little verification shell script to check that all required files are in place.
Click to expand...
Click to collapse
Needs Termux and python.
Hello everyone !
I am a realme 7 user and I was trying to root my phone. But when i flashed vbmeta using the command "fastboot --disable-verity--disable-verfication flash vbmeta vbmeta.img " but it says unknown action
I have seen many users solving their problem by using the command fastboot flash vbmeta vbmeta.img
Can can I use the same command to root my device ?
Narayanxtry said:
Hello everyone !
I am a realme 7 user and I was trying to root my phone. But when i flashed vbmeta using the command "fastboot --disable-verity--disable-verfication flash vbmeta vbmeta.img " but it says unknown action
I have seen many users solving their problem by using the command fastboot flash vbmeta vbmeta.img
Can can I use the same command to root my device ?
Click to expand...
Click to collapse
I have also the same problem did you solve it bro?
vassiliszacharis said:
I have also the same problem did you solve it bro?
Click to expand...
Click to collapse
You mean at DELVIK etc? I think the first time I did it yes.
Also I was wondering if I am making a mistake, when I tried to install TWRP, I used this command:
fastboot flash boot path to patched boot img
instead of this
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
as it was not recognised by ADB...
hi everyone,
by mistake i didnt reload magisk after ota(RMX2202_11.C.15 GDPR), so i lost my root
now, the situaiton is:
bootloader is working
ive tried to instal twrp but something doesnt wanna work. i guess i installed but the screen is black
then i did manually:
adb.exe shell "twrp install /sbin/Magisk.zip"
Click to expand...
Click to collapse
didnt work.
for 2nd solution i tried
with my rom's vbmeta.img, vbmeta_system.img, vbmeta_vendor.img basicly
fastboot flash boot root.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification --disable-verity flash vbmeta_vendor vbmeta_vendor.img
Click to expand...
Click to collapse
didnt work either. and now when i try to open the phone, close itself and not always im able to open. now i can use just bootloader which is difficult to reach (need to press 3 buttons)
right now im waiting to finish unroot file.
well, (how) can i boot and root my phone without losing data?
Wow I'm in pretty much the exact same situation just made a thread lol
idk how but after some hours suddenly i saw that it started to work.
i think i changed the slot (like a>b) and flashed .img files on fastboot. at least now it works
Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Warning: I didn't test this procedure, I did backup the images from stock Chinese version before installing global version but I didn't flash it back. Please test at your own risks!
1. Make sure your bootloader is unlocked
2. Download the images provided in the link below
3. Boot your device to recovery (hold volume up and power until reboot)
4. Wipe data
5. Boot your device to bootloader (hold volume down and power until reboot)
6. Connect your device to PC (make sure you have installed fastboot on your PC)
7. From windows command prompt cd into the folder containing the images
8. Run the following commands to flash all images
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
When flashing super.img, if you get the message Invalid sparse file format at header magic, this is fine.
9. You should then be able to boot into system
Stock RMX3300 Chinese images: https://mega.nz/folder/Ilk2CBwb#VMlU6A8wcFJVU0twOD6vTA
All Stock RMX3300 Chinese images (slot B was the correct one when it was backed up): https://mega.nz/folder/d1dxEBTa#nzKU4KuhnDcHjK7MX_D2eA
myogui said:
免責聲明：我不對設備變磚、SD 卡死等負責！
警告：我沒有測試這個程序，我在安裝全球版本之前備份了庫存中文版本的圖像，但我沒有將其閃回。請您自擔風險進行測試！
1.確保您的引導加載程序已解鎖
2.下載以下鏈接中提供的圖片
3.引導您的設備進行恢復（保持音量和電源直到重新啟動）
4.擦除數據
5.將您的設備引導至引導加載程序（按住音量和電源直到重新啟動）
6.將您的設備連接到PC（確保您已在PC上安裝了fastboot）
7. 從 windows 命令提示符 cd 進入包含圖像的文件夾
8.運行以下命令刷寫所有鏡像
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash 元數據 metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
快速啟動 -w
刷新 super.img 時，如果您在 header magic 處收到 Invalid sparse file format 消息，這很好。
9.然後您應該能夠引導進入系統
庫存RMX3300中文圖片：https ://mega.nz/folder/Ilk2CBwb#VMlU6A8wcFJVU0twOD6vTA
All Stock RMX3300中文圖片（備份時槽B是正確的）：https ://mega.nz/folder/d1dxEBTa#nzKU4KuhnDcHjK7MX_D2eA
Click to expand...
Click to collapse
非常感謝你， 我會嘗試
wronkians said:
非常感謝你， 我會嘗試
Click to expand...
Click to collapse
Good luck mate!
myogui said:
Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Warning: I didn't test this procedure, I did backup the images from stock Chinese version before installing global version but I didn't flash it back. Please test at your own risks!
1. Make sure your bootloader is unlocked
2. Download the images provided in the link below
3. Boot your device to recovery (hold volume up and power until reboot)
4. Wipe data
5. Boot your device to bootloader (hold volume down and power until reboot)
6. Connect your device to PC (make sure you have installed fastboot on your PC)
7. From windows command prompt cd into the folder containing the images
8. Run the following commands to flash all images
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
When flashing super.img, if you get the message Invalid sparse file format at header magic, this is fine.
9. You should then be able to boot into system
Stock RMX3300 Chinese images: https://mega.nz/folder/Ilk2CBwb#VMlU6A8wcFJVU0twOD6vTA
All Stock RMX3300 Chinese images (slot B was the correct one when it was backed up): https://mega.nz/folder/d1dxEBTa#nzKU4KuhnDcHjK7MX_D2eA
Click to expand...
Click to collapse
I followed the steps to the letter. Still stuck in a bootloop
Moaz.Magdy said:
I followed the steps to the letter. Still stuck in a bootloop
Click to expand...
Click to collapse
I was stuck in bootloop too when I flashed the global version, try running the last 2 commands or wiping data from recovery then the last 2 commands again.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
myogui said:
I was stuck in bootloop too when I flashed the global version, try running the last 2 commands or wiping data from recovery then the last 2 commands again.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
Click to expand...
Click to collapse
Thanks! that did the trick. Finally running global version (from your other post) on chinese phone.
SirGustav said:
Thanks! that did the trick. Finally running global version (from your other post) on chinese phone.
Click to expand...
Click to collapse
Great to hear, congrats!
thanks mate
stuck on bootloop for me. i tried to run last 2 commands again, then it still stucks.
Addswes said:
stuck on bootloop for me. i tried to run last 2 commands again, then it still stucks.
Click to expand...
Click to collapse
I am so close tried the same and still bootlooping for me to
Well damn. Switching to the cable from the realme gt 2 pro box fixed it weirdly!
Ok so I now have a brick as it flashed global and tried to lock bootloader. Guess there is no way to fix? EDL mode?
wildlime said:
Ok so I now have a brick as it flashed global and tried to lock bootloader. Guess there is no way to fix? EDL mode?
Click to expand...
Click to collapse
Don't feel bad I made the same mistake. EDL mode is all you can do. In my case I had a person do it for me (unbrick device). Cost me 15 dollars.
robert3892 said:
Don't feel bad I made the same mistake. EDL mode is all you can do. In my case I had a person do it for me (unbrick device). Cost me 15 dollars.
Click to expand...
Click to collapse
What service did you use?
I used the person in post number 8 here:
MSM Downloaf Tool for realme GT 2 Pro
Does anyone know how to access this tool? This is ridiculous, realme has no useful tool to flash their phones and the one that is useful are impossible to access... The only one that I have access was one patched for some especific Oppo phone...
forum.xda-developers.com
wildlime said:
What service did you use?
Click to expand...
Click to collapse
PM me, I'll give you the cheapest one
thank you , any body help me reup to google drive or other
empty.cad said:
thank you , any body help me reup to google drive or other
Click to expand...
Click to collapse
Up, I need it too. @myogui can you reup to GDrive?
Use Mega , 50 GB for free
Can I use this to re-flash my global device? There are some bugs with my phone and a factory reset doesn't seem to fix it.
Download this Firmware -> https://mega.nz/file/JRFUwbpY#gsn5SmaPBpND5Vfredrm5sFJx6tWzegS67v2YDYvfjA
Put Firmware Files in your platform tools folder
CMD into the platform tools directory (if you don't know what that means,. then you are a NOOB LOL)
type
Fastboot devices
output: phone detected ? yes then proceed if no then you need to fix that
copy and paste all this in fastboot
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor vbmeta_vendor.img
fastboot flash metadata metadata.img
fastboot flash userdata userdata.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash bluetooth bluetooth.img
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash core_nhlos core_nhlos.bin
fastboot flash featenabler featenabler.mbn
fastboot flash vendor_boot vendor_boot.img
fastboot flash splash splash.img
fastboot flash oplus_sec oplus_sec.mbn
fastboot flash apdp apdp.mbn
fastboot flash toolsfv tools.fv
fastboot flash logfs logfs_ufs_8mb.bin
fastboot flash storsec storsec.mbn
fastboot flash oplusreserve2 oplusreserve2.img
then type fastboot reboot.
be patient
or if its bootlooping let me know.
i dont have a cph variant.
these commands above where tested in Gn2200
Theatrically it should still work for CPH
NOTES: I FIND IT Odd THAT THIS METHOD DEBRICKED my DEVICE to a success boot to HOMESCREEN without having too flash the critical PARTION NOR THE SUPER
I have the decrypted .ofp file. It doesn't give product.img, system.img, odm.img, and a couple others and everytime I unpack it, it corrupts some of the .img files. It also gives three supers. If you can get all of the raw files without corruption and post them, I'd be grateful.
TweakybirdsTheWord said:
I have the decrypted .ofp file. It doesn't give product.img, system.img, odm.img, and a couple others and everytime I unpack it, it corrupts some of the .img files. It also gives three supers. If you can get all of the raw files without corruption and post them, I'd be grateful.
Click to expand...
Click to collapse
Ya all those files are in the super.img . You gotta use simg2img to merge the parted supers then unpack that super
Well then. I'll, uh...I'll try that very simple sounding idea. My old college professor is laughing at me.
Decrypting the ofp takes like 20 minutes
Have you the merged super.img? I haven't had a chance to do it yet.
TweakybirdsTheWord said:
Have you the merged super.img? I haven't had a chance to do it yet.
Click to expand...
Click to collapse
redacted
How to use this
killerex said:
How to use this
Click to expand...
Click to collapse
redacted
I have one plus Nord n20 5g version is this compatible
killerex said:
I have one plus Nord n20 5g version is this compatible
Click to expand...
Click to collapse
Do you have the Gn2200 or the chp variant?
Chp
killerex said:
Chp
Click to expand...
Click to collapse
Then it should be compatible. . Is your device bricked and bootloader unlocked?
The guide wont be ready tonight maybe tomorrow.
Yes
redacted
bricklife4me said:
What was the lastest update you did to phone and how did you brick your phone.?
Click to expand...
Click to collapse
Latest update..I was trying to root it..I guess flashed wrong boot.img
killerex said:
Latest update..I was trying to root it..I guess flashed wrong boot.img
Click to expand...
Click to collapse
redacted
bricklife4me said:
here are the commands to flash in fast boot d
fastboot flash devcfg_a devcfg.mbn
fastboot flash devcfg_b devcfg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash dsp_b adspso.bin
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash pmic_a pmic.elf
fastboot flash pmic_b pmic.elf
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
fastboot flash splash splash.img
fastboot flash tz_a tz.mbn
fastboot flash tz_b tz.mbn
fastboot flash xbl_a xbl.elf
fastboot flash xbl_b xbl.elf
fastboot flash abl_a abl.elf
fastboot flash abl_b abl.elf
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash super super.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot erase userdata
to get to fastboot you have to adb the below command
adb reboot fastboot
Click to expand...
Click to collapse
How can I flash all this command in one flash?
bricklife4me said:
Did you pull your own boot image?
Click to expand...
Click to collapse
No I got from telegram.
killerex said:
No I got from telegram.
Click to expand...
Click to collapse
Lol probably from my Channel