Related
I have a rare phone running Android 6.0 on a MT6750 with an unlocked bootloader (might be MT6750T since it is 1920x1080, but the only things I have found say MT6750)
I have been unable to get TWRP working on this phone after trying several porting guides and TWRP images. Almost all port attempts result in the boot image (logo.bin - android logo), followed by a black screen for a few seconds, then it reboots into Android.
Is it possible to manually patch the boot.img to gain root? If so, can someone point me to a guide for it? I found https://forum.xda-developers.com/android/software-hacking/systemless-root-mediatek-t3309909 but PATH doesnt seem to be set anywhere in my boot image (grep -nrw 'boot.img-ramdisk' -e "PATH"). I tried adding "export PATH $PATH:/data/bin" or "export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin::/data/bin" to init.environ.rc with other exports, but I get a boot loop
try recompile the decompiled boot.img without doing any changes and flash the compiled boot.img to see that there is no problem with respect to compilation of boot.img
shankar_vl said:
try recompile the decompiled boot.img without doing any changes and flash the compiled boot.img to see that there is no problem with respect to compilation of boot.img
Click to expand...
Click to collapse
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also
btw im using oppo f3 mt6750t
rajeshca911 said:
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also
btw im using oppo f3 mt6750t
Click to expand...
Click to collapse
Then its a compilation error. Its not being compiled correctly.
Btw, systemless root by supersu and magisk do a lot things like starting sudaemon, injecting supolicy changes, mounting su.img, etc. Its better to port a custom recovery and let supersu or magisk zip do all the required things to root your device.
Or if you want to be ambitious, dirty your hands with hackings, unzip these zip files and try to implement manually what is programmed there.
My suggestion is go for porting recovery from devices matching your device specs ( need not be 100%). There are several threads on this forum helping you out on this. I think chances of porting a workable custom recovery are brighter than manually compiling su compatible boot.img.
There's the problem..
I did port custom recovery.
But when I flash it back to device it's showin error.
I understand that I need to dirt my hands more to get root my device
So I decided to compile revovery.. But oppO f3 source files r not available. I tried with omni Tom source. But it failed
rajeshca911 said:
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also
btw im using oppo f3 mt6750t
Click to expand...
Click to collapse
rajeshca911 said:
There's the problem..
I did port custom recovery.
But when I flash it back to device it's showin error.
I understand that I need to dirt my hands more to get root my device
So I decided to compile revovery.. But oppO f3 source files r not available. I tried with omni Tom source. But it failed
Click to expand...
Click to collapse
You said that even the imgs just compiled without any changes made to decompiled files are not able to boot. Then there must be something wrong with compiling. Your tools for compiling may not be correctly working.
There are carlive image kitchen tools. get them here https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658. They are known for flawless working.
What is more important now is that you have right tools for compiling imgs. Then you can think of further.
shankar_vl said:
You said that even the imgs just compiled without any changes made to decompiled files are not able to boot. Then there must be something wrong with compiling. Your tools for compiling may not be correctly working.
There are carlive image kitchen tools. get them here https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658. They are known for flawless working.
What is more important now is that you have right tools for compiling imgs. Then you can think of further.
Click to expand...
Click to collapse
Thanks bro. But im using carliv kitchen tools only.
I didn't tried with other kitchen tools yet.. So i give a try other tools
rajeshca911 said:
Thanks bro. But im using carliv kitchen tools only.
I didn't tried with other kitchen tools yet.. So i give a try other tools
Click to expand...
Click to collapse
no need. carliv tools are perfect. stick with them.
are you able to successfully flash imgs with sp flash tools? no matter whether you are able to boot with them.
as for porting, use twrp or any other custom recovery of SoC as yours, mt6750t and of OS version similar to yours as well.
shankar_vl said:
no need. carliv tools are perfect. stick with them.
are you able to successfully flash imgs with sp flash tools? no matter whether you are able to boot with them.
as for porting, use twrp or any other custom recovery of SoC as yours, mt6750t.
Click to expand...
Click to collapse
Ok.. I stick with carliv as u suggested. And... Yes... Im able to flash img files to phone but not with sp flash tools. Im using professional tools ( uni tools from volcano) and also flashing using a cracked download tool meant for oppo devices. ( the download tool was created on base of sp flash tools only)
Then...
I just tried twrp porting only ( same soc mt6750t quitel k6000 plus i think.. Which chipset is mt6750t)
Also tried with oppo f1s twrp which chipset is mt6750.. ( not 6750t.. ) both went wrong..
seniors and xda developrs ( zackie& a guy from Indonesia unfortunately i forgot his name) also tried to. Port twrp for me. I also tried flashing their img files ..everything went not well.. There i have understood that either compiling or flashing causing error in my device
Thats y im trying to find other wayz.. There i found ur thread .& fetching useful checklist:good:
rajeshca911 said:
Ok.. I stick with carliv as u suggested. And... Yes... Im able to flash img files to phone but not with sp flash tools. Im using professional tools ( uni tools from volcano) and also flashing using a cracked download tool meant for oppo devices. ( the download tool was created on base of sp flash tools only)
Then...
I just tried twrp porting only ( same soc mt6750t quitel k6000 plus i think.. Which chipset is mt6750t)
Also tried with oppo f1s twrp which chipset is mt6750.. ( not 6750t.. ) both went wrong..
seniors and xda developrs ( zackie& a guy from Indonesia unfortunately i forgot his name) also tried to. Port twrp for me. I also tried flashing their img files ..everything went not well.. There i have understood that either compiling or flashing causing error in my device
Thats y im trying to find other wayz.. There i found ur thread .& fetching useful checklist:good:
Click to expand...
Click to collapse
As you tried various flashing methods, you might have already known all the related intricasies of flashing. still I just want to mention that I presume you might have then known vcom drivers, creating scatter file with mtkdroid tools, loading scatter file and, most importantly switching off phone and plugging phone to PC just after clicking on flash button in sp flash tool.
And about the other tools of flashing you mentioned, sorry I will not be helpful.
A thing to mention regarding porting is taking care of mount points in fstab file and a similar file if any at /etc folder in ramdisk of decompiled port recovery. mount points should be same as fstab of your boot.img.
Besides, ensure kernel (Imaze) of port recovery is replaced with that of boot.img.
shankar_vl said:
As you tried various flashing methods, you might have already known all the related intricasies of flashing. still I just want to mention that I presume you might have then known vcom drivers, creating scatter file with mtkdroid tools, loading scatter file and, most importantly switching off phone and plugging phone to PC just after clicking on flash button in sp flash tool.
And about the other tools of flashing you mentioned, sorry I will not be helpful.
A thing to mention regarding porting is taking care of mount points in fstab file and a similar file if any at /etc folder in ramdisk of decompiled port recovery. mount points should be same as fstab of your boot.img.
Besides, ensure kernel (Imaze) of port recovery is replaced with that of boot.img.
Click to expand...
Click to collapse
Your not helpfull??.. I don't agree with that. May be im Not in the position to catch your mind.
However.. Im not going to miss single chance to upgrade myself ( yes ofcourse from devs n seniors like u)
As you said
1) i have installed vcom drivers & fetched scatter file. ( again not from mtk droid tools) . I heard mtkdroid tools nOt fully supporting mt67xx Series. Even i tried modified mtkdroid tools developed by dev havoc.. And droid tool showed some info like cpu info.. Etc. But right hand side there was an error which saying that its usable to fetch info. . I presume the error may b causing by oppo. Own OS ( Color OS based on android 6.0).. And my last try was 2 months ago. So i dont know if there is any improvements in droid tools or not. Please privide me links if they updated/ supported 67xx series
2)yes i agree with mount points you mentioned. I was just replacing fstab file from stock to. Port. I didnt edit any. . I will check again and update u.
3) Actually im in dilemma to blame on cimpiling or flashing.. The device is not booting even i didn't modify any item after repack. I need solution for that. If that resolved... Automatically everything will b set up by themselves.. Pls share any views regarding this..
I know its difficult to u to guide until u have hands on it or personally seen d procedures & results
I may upload videos / pictures/ share Team viewer etc.. if u want to see it personally.. So.. U can better understand my problem , my flaws where i need to b improved ( onlynif u wish) however i need a mentor to guide n judge methods im following
rajeshca911 said:
Your not helpfull??.. I don't agree with that. May be im Not in the position to catch your mind.
However.. Im not going to miss single chance to upgrade myself ( yes ofcourse from devs n seniors like u)
As you said
1) i have installed vcom drivers & fetched scatter file. ( again not from mtk droid tools) . I heard mtkdroid tools nOt fully supporting mt67xx Series. Even i tried modified mtkdroid tools developed by dev havoc.. And droid tool showed some info like cpu info.. Etc. But right hand side there was an error which saying that its usable to fetch info. . I presume the error may b causing by oppo. Own OS ( Color OS based on android 6.0).. And my last try was 2 months ago. So i dont know if there is any improvements in droid tools or not. Please privide me links if they updated/ supported 67xx series
2)yes i agree with mount points you mentioned. I was just replacing fstab file from stock to. Port. I didnt edit any. . I will check again and update u.
3) Actually im in dilemma to blame on cimpiling or flashing.. The device is not booting even i didn't modify any item after repack. I need solution for that. If that resolved... Automatically everything will b set up by themselves.. Pls share any views regarding this..
I know its difficult to u to guide until u have hands on it or personally seen d procedures & results
I may upload videos / pictures/ share Team viewer etc.. if u want to see it personally.. So.. U can better understand my problem , my flaws where i need to b improved ( onlynif u wish) however i need a mentor to guide n judge methods im following
Click to expand...
Click to collapse
I empathize with your frustration.
Truth is that with the devices which have not caught the fancy of developers, not having proven root methods, custom recovery, etc only, we take initiatives ourselves and learn the things the hard way which is essentially a true way learning. With popular devices having already so many developments, there is no scope for adventurism and fun as well.
Just see back what are all you gained in doing the things you did with your device for gaining root. Could it have been possible with the so called popular devices?
Now let's come to the issue. In all times of failed booting on compiled imgs, how did you restore them? flashing again stock boot and recovery imgs? and with tools you mentioned?
If you could flash stock boot and recovery with the tools you mentioned, then there is no problem with those flashing tools. Then it comes to the decompiling and recompiling of imgs.
If it could be possible, can you share here stock boot.img, and custom recovery you have selected for porting (also mention the device name, recovery pertained). Let me try.
Yup.. Bro.
What have you said all true.. during this journey i have learned so manythings like porting custom recovery , read back firmware etc and i cant forget what i have learned.. so many trail and errors
below link is the stock and custom recovery i tried to port
https://drive.google.com/file/d/0B6wWbhnrRZ_-V2RZQXByYjc4QVU/view?usp=drive_web
and a developer also tried to to port recovery for me .. below is the link which he modified for me
https://www.androidfilehost.com/?fid=745425885120760137
Im also enclosing stock boot.img
https://mega.nz/#!MF1ySQ4D!ku6RWfOP8QTkm75sNq_1_n-_Af0y843J0I0tiCHRa8k
My Device Details are
Manufacture : Oppo
Device name : Oppo f3
Model No : CPH1609
chipset : MT6750T , 4gb Ram , 64 Gb storage
[ I Really praying Inside ....:angel: god may give result for our endless efforts }
@rajeshca911 can you give details for the custom recovery you have given links, like name of the device, its os ( lollipop, marshmallow, like), and chipset if possible, it pertained to.
shankar_vl said:
@rajeshca911 can you give details for the custom recovery you have given links, like name of the device, its os ( lollipop, marshmallow, like), and chipset if possible, it pertained to.
Click to expand...
Click to collapse
Aquired custom recovery from
Device : qukitel K6000 plus, chipset MT6750T
android version 6.0 (from below)
https://www.google.co.in/amp/s/foru...al/oukitel-k6000-plus-twrp-root-t3620241/amp/
rajeshca911 said:
Aquired custom recovery from
Device : qukitel K6000 plus, chipset MT6750T
android version 6.0 (from below)
https://www.google.co.in/amp/s/foru...al/oukitel-k6000-plus-twrp-root-t3620241/amp/
Click to expand...
Click to collapse
I think the signature of the boot.img gets changed. Try to sign it after decompiling and recompiling by AVB patcher from here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
anandverma458 said:
I think the signature of the boot.img gets changed. Try to sign it after decompiling and recompiling by AVB patcher from here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Shall i sign both boot.img and recovery.img as well?? or is it enough to sign compiled recovery.img ?
---------- Post added at 07:57 AM ---------- Previous post was at 07:44 AM ----------
i generated public and private keys also signed and generated
boot_signed.img
recovery_signed.img
first i flashed both the images... result was soft brick and i had to flash original boot.img
second i flashed only signed recovery.img and same was repeated.
rajeshca911 said:
Shall i sign both boot.img and recovery.img as well?? or is it enough to sign compiled recovery.img ?
---------- Post added at 07:57 AM ---------- Previous post was at 07:44 AM ----------
i generated public and private keys also signed and generated
boot_signed.img
recovery_signed.img
first i flashed both the images... result was soft brick and i had to flash original boot.img
second i flashed only signed recovery.img and same was repeated.
Click to expand...
Click to collapse
Actually, I had the same problem (I have vivo 1603). When I flashed boot.img after decompiling and recompiling,it bootlooped. I had twrp installed, so I first restored the backup of stock boot.img, and then installed the recompiled boot.img without rebooting. That worked for me
As you don't have custom recovery, I suggest that you first flash stock boot.img, and after the process completes, flash the recompiled boot.img without rebooting your device.
Hey bro, I decompiled the stock boot.img to see that if 'verify' flag was preventing booting the system with other than stock recovery. Dm-verity is a recent security control for preventing booting with changed/modified kernel/system. But I could not find any such flags, but found verity_key, so I just deleted it and decompiled the boot.img. I am not sure whether it can solve your booting problem. Let's see will this now allow to boot with custom kernel. Here is the modified stock boot.img. http://www.mediafire.com/file/tc1k1ghmy76nfqd/modified_oppo_boot.img
Flash first this boot.img and then flash the custom recovery.imgs (you can try your recoveries also)
I have also ported two recovery.imgs. Both are ported from the twrps for the same device, K6000 plus. However, what I found for this k6000 plus was different in size. So I ported two twrp recovery imgs. Here are two twrp ported recoveries, one is from you have given links to and another is from what I found on this forum.
http://www.mediafire.com/file/4als7qmpwdz1iv4/oppo_port_twrpv1.img
http://www.mediafire.com/file/5xz7387at6rr0dy/oppo_port_twrpv2.img
Once again, I reiterate that first flash the modified boot.img and then try flashing the recoveries.
Best of luck
anandverma458 said:
Actually, I had the same problem (I have vivo 1603). When I flashed boot.img after decompiling and recompiling,it bootlooped. I had twrp installed, so I first restored the backup of stock boot.img, and then installed the recompiled boot.img without rebooting. That worked for me
As you don't have custom recovery, I suggest that you first flash stock boot.img, and after the process completes, flash the recompiled boot.img without rebooting your device.
Click to expand...
Click to collapse
Bro thanks for your advice.. and i did same what you have said.. i flashed stock boot.img with out rebooting flashed recompiled boot.img the device didnt boot up.. i think culprit is something else .. that prevets booting custom images
Hello people. Recently i got my first qualcomm device redmi-4x (v8.2.12.0) global (previously i used/worked-for mtk devices), and from past few days i have been reading/learning about this qualcomm device.
I have checked almost all redmi-4x forums (miui, xda, 4pda etc) and still have some questions in my mind.
Q1:
I want to backup my redmi-4x before unlocking/rooting/FlashingTWRP. I know in mtk devices, even if the device is unrooted/untouched we can easily backup firmware/complete-emmc (each and every partition) by readback methods using SP-FlashTool/Miracle-Box etc...
i read somewhere, we can do same thing, i.e readback qualcomm device's emmc in edl-mode but unfortunately, xiaomi has disabled fastboot edl mode in new devices and the only way left to open edl mode is test point method which requires disassembly. though i can but i don't want to disassemble it (warranty will be void). Another solution i saw was Deep Flash Cable, which isn't working either, personally tested... Now, having no other option, i decided to unlock it to make stock rom backup using TWRP. Actually i wanted to make backup with minimum changes to original firmware, so if anyone here knows any other solution to make backup without unlocking bootloader, (or unlocked_bootloader + no_other_changes, i.e without TWRP) please share... Thanks!
Q2:
From what i have learned so far, i think MiUI bootloader unlock tool doesn't work with non-miui firmwares, right? so the question is, if we manually relock our redmi 4x using fasboot when there is some non-miui rom installed in the device. what can be the possible solution to unlock it again? (except reflashing miui by test point method and then unlocking bootloader). Thanks!
EnerJon said:
i wanted to make backup with minimum changes to original firmware, so if anyone here knows any other solution to make backup without unlocking bootloader, (or unlocked_bootloader + no_other_changes, i.e without TWRP) please share... Thanks!
Click to expand...
Click to collapse
Hi, I do it this way:
- unlocked bootloader
- copy http://www.mediafire.com/file/pj0qh1ccj4h2a2a/p0.zip to FAT32 flash drive
- fastboot boot twrp.img (TWRP is not flashed, boots from RAM, not eMMC, so no_other_changes)
- attach the flash drive to R4X on OTG adapter
- in TWRP "install" p0.zip
- entire eMMC will be compressed and saved on the flash drive
My new R4X 32GB was compressed down to 2GB within around half an hour. Later I mounted the disk image on a PC and erased OS/data partitions: system, cache, userdata, cust, recovery, boot, and now the entire 32GB with bootloader, support and firmware is 80MB compressed.
Have you tried QPST backup in EDL mode?
k23m said:
- unlocked bootloader
- copy http://www.mediafire.com/file/pj0qh1ccj4h2a2a/p0.zip to FAT32 flash drive
- fastboot boot twrp.img (TWRP is not flashed, boots from RAM, not eMMC, so no_other_changes)
- attach the flash drive to R4X on OTG adapter
- in TWRP "install" p0.zip
- entire eMMC will be compressed and saved on the flash drive
My new R4X 32GB was compressed down to 2GB within around half an hour. Later I mounted the disk image on a PC and erased OS/data partitions: system, cache, userdata, cust, recovery, boot, and now the entire 32GB with bootloader, support and firmware is 80MB compressed.
Click to expand...
Click to collapse
Thanks for The Guide, it Will Surely be Helpful for New R4X Users :good: Just Wondering Why No One Made Such a Guide For R4X Earlier... Or Did i Missed it Somewhere?
k23m said:
Have you tried QPST backup in EDL mode?
Click to expand...
Click to collapse
No, But i Used another Tool Which i Think Uses Same Technique as QPST in EDL Mode. i Unlocked My R4X and Then Booted into EDL Mode, Used This Tool (With "prog_emmc_firehose_8937_ddr.mbn" From R4X Fastboot Firmware) To Take Complete EMMC Backup, it Also Converted The Backup into Fastboot ROM...
EnerJon said:
Thanks for The Guide, it Will Surely be Helpful for New R4X Users :good: Just Wondering Why No One Made Such a Guide For R4X Earlier... Or Did i Missed it Somewhere?
Click to expand...
Click to collapse
I made the guide and script for Nexus 7'13 but it works well on R4X too. There is no known method of QPST backup on the Nexus but Xiaomi always had more options thanks to freely available "firehose" files. Thank you for the emmcdl link, it is a very simple and convenient tool.
We could use emmcdl for unlocking. I found some pre-patched "persist" partitions here http://blog.regenerationmm.com/2017/03/emmc-dl-အသုံးျပဳျပီး-mi-account-bypass-ျပဳလုပ္/
:highfive:
k23m said:
I made the guide and script for Nexus 7'13 but it works well on R4X too. There is no known method of QPST backup on the Nexus but Xiaomi always had more options thanks to freely available "firehose" files. Thank you for the emmcdl link, it is a very simple and convenient tool.
We could use emmcdl for unlocking. I found some pre-patched "persist" partitions here http://blog.regenerationmm.com/2017/03/emmc-dl-အသုံးျပဳျပီး-mi-account-bypass-ျပဳလုပ္/
:highfive:
Click to expand...
Click to collapse
Hello. Do you have more information on this? I have a Redmi 4x that I really want to unlock the bootloader, but the official method doesn't work for me.
I found this site showing a method for the redmi 4a that uses the emmcdl tool:
Rolex Instant UBL (Unofficial Unlock Bootloader for Redmi 4A) Tested! - OmBob Opreker
Complete Tutorial how to bypass your Redmi 4A (rolex) lock bootloader, the unofficial way. tested And Work for all rolex version
ombob.my.id
Is this what you mentioned?
unluckyuser said:
Hello. Do you have more information on this? I have a Redmi 4x that I really want to unlock the bootloader, but the official method doesn't work for me.
I found this site showing a method for the redmi 4a that uses the emmcdl tool:
Rolex Instant UBL (Unofficial Unlock Bootloader for Redmi 4A) Tested! - OmBob Opreker
Complete Tutorial how to bypass your Redmi 4A (rolex) lock bootloader, the unofficial way. tested And Work for all rolex version
ombob.my.id
Is this what you mentioned?
Click to expand...
Click to collapse
Hi, I have files from the defunct link, but never tested them as my R4X is unlocked officially.
The R4A is indeed using the unlock method I speculated about.
k23m said:
Hi, I have files from the defunct link, but never tested them as my R4X is unlocked officially.
The R4A is indeed using the unlock method I speculated about.
Click to expand...
Click to collapse
I would like to have the files and experiment, thank you.
I already messed up my phone and I'm trying to flash the stock rom via edl first.
Hi there,
I'm facing a huge problem and I can not find the solution Googling and reading in randon forums.
Basically after unlocking the bootloader I wanted to relocked it again to avoid fingerprints issues, so that's the problem. I did something wrong and everytime I press Power button it appears a message saying
"The current image(boot/recovery) have been destroyed and cannot boot..."
The thing is that I can not even access to fastboot pressing Power button + Vol-, just pressing Power button + Vol+ and it access to EDL, but my question is related to EDL thing.
I have downloaded the .ozip file which contains the ROM files, but I don't find the "rawprogram0.xml" or related files to flash the phone properly with Qualcomm Flashing tools.
I have also tried with "Msm download tool" but the program gives me and advert which says that the .ofp file is not correct blablabla.
Do you guys know where to get the proper ROM with rawprogram0.xml and patch files?
I would really appreciate your help because I'm getting crazy with this issue and I don't know how to fix it.
Thanks so much.
guide CN Version
How to Install Stock ROM on Realme X2 Pro (RMX1931)
Before doing anything, we need to have the ROM file for the designated device ie Realme X2 Pro. Here is the download link for the same.
Download Stock ROM File
RMX1931_11_0110: Download
Installation Guide
Before beginning with the installation remember a few pointers we have mentioned below.
Pre-Requisites
This ROM is exclusively for the Realme X2 Pro (RMX1931). Don’t use it on other devices.
Charge your phone completely before installing the ROM.
A Windows PC/Laptop
Download and install Realme USB drivers on your Windows PC.
Download QFil Tool or QPST Flash tool and install on your PC.
It is always recommended to take a backup of your Android Device.
Backup Android Phone Without Root on any device
If you have TWRP Recovery, Create and Restore Nandroid Backup using TWRP Recovery
GetDroidTips will not be responsible for any hardware or software issue happening to your phone upon installing this firmware or following this guide. Perform this installation at your own risk..!
Method 1: Instructions to Install via QFIL Tool:
Download Qualcomm Flash image loader tool and USB Drivers on your PC. Follow the below link to install the firmware using QFIL tool
Guide to Install Stock ROM using QFIL Tool
Method 2: Instructions to Install via MSM Download tool:
Download the MSM Download tool, firmware, and drivers on your PC.
Now install the USB drivers
Place the MSM download tool and firmware in the same folder
Open the MSM download tool and connect your device to PC/Laptop
Once you connect, it will automatically load the firmware, if not select it manually.
Click on start button and wait patiently to complete the installation process.
Once it is done! remove your device from PC. That’s it!
Method 3: Instructions to Install via QPST Tool:
Here are the instructions you need to follow in order to install Stock ROM on the Realme X2 Pro :
First of all, do all the PREREQUISITE STEPS and Now Open the Extracted QPST Folder
You will find two files with the name: Qualcomm_USB_Drivers_For_Windows.rar and QPST.WIN.2.7 Installer-00429.zip QPST folder
Open the QPST Win folder and Install the QPST.exe file on your PC/Laptop QPST install
After Installation, Go to the Installed Location in the C Drive
Open the QPST Configuration QPST Configuration exe open
Now in the QPST Configuration, Click on Add new port -> Select the com port of your device -> and close it QPST Configuration
Now Open the EMMC Software Downloader in the same folder located all the QPST Files EMMC Software download
In EMMC Software Downloader, Check program boot loaders -> Browse for the device com portEMMC Software download Browse
Now Click Load XML Def and browse for rawprogram0.xml in folder ROM in EMMC Software Downloader (If you didn’t extract please extract the ROM and then browse the file rawprogram0.xml)click and load xml
Now tap on Load Patch def and browse for patch0.xml in folder ROM load patch
Check the search path 2 and browse for the folder ROM search path QPST
Now click download, wait for the download to finish (it never finish but it also detects for a new driver, and that’s important) and it will search for the new hardware found, install the driver
That’s it! Once your installation is done! Reboot the phone! Congrats, you successfully installed Stock ROM on Realme X2 Pro.
So, that’s it, guys. Now you know how to install stock ROM on Realme X2 Pro (RMX1931). We hope this tutorial was helpful to you. In case you have any queries do let us know in the comments.
Check out this guide CN Version
Thanks for the reply, but it does not help. I have followed all the guides found in Google, but none has the correct ROM to get rawprogram0.xml and patch.xml files.
Btw, I have European Global ROM (RMX1931EX)
yj_206 said:
Thanks for the reply, but it does not help. I have followed all the guides found in Google, but none has the correct ROM to get rawprogram0.xml and patch.xml files.
Btw, I have European Global ROM (RMX1931EX)
Click to expand...
Click to collapse
did you try via fastboot to fix it ? it might work with the official global rom
natedogg20050 said:
did you try via fastboot to fix it ? it might work with the official global rom
Click to expand...
Click to collapse
any solition?, i have de same case
I think I almost have it, but I need the scatter file, any of you have it generated?
natedogg20050 said:
did you try via fastboot to fix it ? it might work with the official global rom
Click to expand...
Click to collapse
"The thing is that I can not even access to fastboot pressing Power button + Vol-, just pressing Power button + Vol+ and it access to EDL, but my question is related to EDL thing."
Isavar said:
any solition?, i have de same case
Click to expand...
Click to collapse
I sent it back to the shop and they gave me a new one. I said it was "updating issue"
There should be a fix hopefully soon, maybe check the thread how to lock the bootloader maybe it helps
What are people using to extract from ozip?
yj_206 said:
Hi there,
I'm facing a huge problem and I can not find the solution Googling and reading in randon forums.
Basically after unlocking the bootloader I wanted to relocked it again to avoid fingerprints issues, so that's the problem. I did something wrong and everytime I press Power button it appears a message saying
"The current image(boot/recovery) have been destroyed and cannot boot..."
The thing is that I can not even access to fastboot pressing Power button + Vol-, just pressing Power button + Vol+ and it access to EDL, but my question is related to EDL thing.
I have downloaded the .ozip file which contains the ROM files, but I don't find the "rawprogram0.xml" or related files to flash the phone properly with Qualcomm Flashing tools.
I have also tried with "Msm download tool" but the program gives me and advert which says that the .ofp file is not correct blablabla.
Do you guys know where to get the proper ROM with rawprogram0.xml and patch files?
I would really appreciate your help because I'm getting crazy with this issue and I don't know how to fix it.
Thanks so much.
Click to expand...
Click to collapse
Did you find a fix?
i have one now with "The current image(boot/recovery) have been destryed and can not boot"
any ideea? the client bring to me in that mode. I think i nned test point because the phone its in the bootloop, i cant make nothing with taste combination. I will open the phone first to remove battery... will see after... Thx in advance!
---------- Post added at 04:24 PM ---------- Previous post was at 04:12 PM ----------
good, the phone enter in HS mode without battery with vol+ and vol - pressed... will see next step. I'll try with QFil first...
xchris said:
i have one now with "The current image(boot/recovery) have been destryed and can not boot"
any ideea? the client bring to me in that mode. I think i nned test point because the phone its in the bootloop, i cant make nothing with taste combination. I will open the phone first to remove battery... will see after... Thx in advance!
---------- Post added at 04:24 PM ---------- Previous post was at 04:12 PM ----------
good, the phone enter in HS mode without battery with vol+ and vol - pressed... will see next step. I'll try with QFil first...
Click to expand...
Click to collapse
did you made to unbrick the device?
any update guys.....i have the same problem and i can't seem to find any solution
I have extracted the firmware and I got patch0.xml , rawprogram0.xml , prog_firehose_ddr.elf and bunch of other files .
I upload a picture of the files .
The firmware is RMX1931_11_A.11 .
I do not have this device yet and I am not 100% sure how to use it but as I understand there is an option to flash though QPST tool on EDL mode.
Update - I also extracted RMX1931EX_11_A.06 global firmware .
how did u extract the ozip file ??
---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------
or965 said:
I have extracted the firmware and I got patch0.xml , rawprogram0.xml , prog_firehose_ddr.elf and bunch of other files .
I upload a picture of the files .
The firmware is RMX1931_11_A.11 .
I do not have this device yet and I am not 100% sure how to use it but as I understand there is an option to flash though QPST tool on EDL mode.
Update - I also extracted RMX1931EX_11_A.06 global firmware .
Click to expand...
Click to collapse
how did u extract the file ??
uv.007 said:
how did u extract the ozip file ??
---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------
how did u extract the file ??
Click to expand...
Click to collapse
The OZIP file does not have any of the files that are needed to flash on QFIL tool. I extracted the ofp file .
I currently uploading the extracted files of the Global and CN versions and will post a partial guide of how to flash it through QFIL .I do not 100% sure that it will work as I have not tested it and the guide will be very dangerous and only recommended for people with hard bricked devices that have locked bootloader . I bought this device and waiting to receive it .I was planing to unlock the bootloader of the device and then I read that many people have hard bricked their device and decided to search a way to unbrick this phone in case that I will hard brick the phone in the future.
or965 said:
The OZIP file does not have any of the files that are needed to flash on QFIL tool. I extracted the ofp file .
I currently uploading the extracted files of the Global and CN versions and will post a partial guide of how to flash it through QFIL .I do not 100% sure that it will work as I have not tested it and the guide will be very dangerous and only recommended for people with hard bricked devices that have locked bootloader . I bought this device and waiting to receive it .I was planing to unlock the bootloader of the device and then I read that many people have hard bricked their device and decided to search a way to unbrick this phone in case that I will hard brick the phone in the future.
Click to expand...
Click to collapse
do u have any link for ofp file for realme X2 (RMX1992)
[/COLOR]
uv.007 said:
do u have any link for ofp file for realme X2 (RMX1992)
Click to expand...
Click to collapse
I just search on Google and found one, RMX1992EX_11_A.15_191029_ea418f8c.ofp - https://drive.google.com/file/d/1quux10IHGy6T_dbHljbdxaqWPY-ZBeg_/view
This is an ofp firmware, you can not extract it with winrar or 7 zip,you need special software . If you need I can upload an extracted version . The guide that i will post should be also good for the realme x2 as it has a snapdragon CPU .
or965 said:
[/COLOR]
I just search on Google and found one, RMX1992EX_11_A.15_191029_ea418f8c.ofp - https://drive.google.com/file/d/1quux10IHGy6T_dbHljbdxaqWPY-ZBeg_/view
This is an ofp firmware, you can not extract it with winrar or 7 zip,you need special software . If you need I can upload an extracted version . The guide that i will post should be also good for the realme x2 as it has a snapdragon CPU .
Click to expand...
Click to collapse
downloaded this zip and it's mirror too both are corrupted some crc issue
I have a Mi 9t pro that has TeamWin on it. I have no idea how to root or what i am doing. it came with it. I accidently wiped the OS and now it just reboots over and over again and I just dont know to do. any advice or steps would help me. thanks.
P.S it still has the TeamWin on it. i dont know how factory reset it.
Willdabeast37 said:
I have a Mi 9t pro that has TeamWin on it. I have no idea how to root or what i am doing. it came with it. I accidently wiped the OS and now it just reboots over and over again and I just dont know to do. any advice or steps would help me. thanks.
P.S it still has the TeamWin on it. i dont know how factory reset it.
Click to expand...
Click to collapse
Wrong place to post your question. It should have been posted under Q&A section. I am requesting the mod to move your post to the right section.
no questions in development
Willdabeast37 said:
I have a Mi 9t pro that has TeamWin on it. I have no idea how to root or what i am doing. it came with it. I accidently wiped the OS and now it just reboots over and over again and I just dont know to do. any advice or steps would help me. thanks.
P.S it still has the TeamWin on it. i dont know how factory reset it.
Click to expand...
Click to collapse
I am assuming your device is soft bricked and you have access to some good internet and twrp is still working and partitions have not been corrupted and unlocked bootloader and very important your device is Redmi K20 pro aka MI 9T PRO(as you have posted in wrong section. i have to assume xD)...
By following these steps you will reset your device to stock miui.
You will require a PC/laptop and type c data cable
1: Download miui fastboot rom from the official site
2: reboot your device in fastboot mode
3: install mi flash tool
4: open mi flash tool
5: hopefully it automatically installs the drivers (if not search google for Qualcomm drivers and download/install the same)
6: connect the device to pc via cable
7: your device should detect in the flash tool
8: extract the downloaded fastboot rom.
9: select the folder containing the rom in the flash tool
10: *(VVI)at the bottom of the tool click on "clear all wipe"(very important step else you may hardbrick your device)
11: click start and wait until your device reboots itself
12: unplug the cable and enjoy
ps: some mi flash tool may not work try with different versions if newer doesn't works try older.
Thank you hope this helps....Do press thanks if this helps you.
This is the official guide to flashing MIUI
https://c.mi.com/oc/miuidownload/detail?guide=2
You will need to view the page in desktop mode if using a mobile browser.
It basically gives you the procedure given in the previous post, with the benefit of pictures.
It also has a link to the latest official version of the Mi Flash Tool, which should work with no problems.
Get the fastboot ROM from here https://xiaomifirmwareupdater.com/miui/raphael/
Choose the correct region for the phone. Mi 9T Pro will be either European or global. Also make sure you download the fastboot ROM.
This site does not host the files, but provides links to the official versions on the official Xiaomi servers, so you can be sure what you flash is safe and untouched.
Saswata Chakraborty said:
Wrong place to post your question. It should have been posted under Q&A section. I am requesting the mod to move your post to the right section.
Click to expand...
Click to collapse
sorry im new here and not sure what places to post to.
Hello,
I have a problem.
I tried to install a custom ROM on my Zuk Z2 Pro, but I managed to erase the original one, so now I have no ROM on it. I can only turn it on in recovery or fastboot mode, but I can't connect it to my PC because it is not recognize by it.
I just have TWRP on it, but that's it. I don't have any os img to install in my Zuk's internal storage so I can't install another one using TWRP.
I really don't know what to do now. I just want my phone back :'(
Please help me
Look in this forum for a stock rom or aosp one and follow the instructions to flash a rom, it should be easy, i no more have the device to advise you which rom but search and you'll find
Nickthegr8 said:
Look in this forum for a stock rom or aosp one and follow the instructions to flash a rom, it should be easy, i no more have the device to advise you which rom but search and you'll find
Click to expand...
Click to collapse
I tried following these instructions https://forum.xda-developers.com/t/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.3928699/ but I'm stuck at step 1.1.4 (method 2). QFIL does not find any available port
alexiosAuditore said:
I tried following these instructions https://forum.xda-developers.com/t/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.3928699/ but I'm stuck at step 1.1.4 (method 2). QFIL does not find any available port
Click to expand...
Click to collapse
ALL STOCK - Zui 4.0.247ST + Gapps Sync + GBoard 100% (NO ROOT + LOCKED BOOTLOADER)
Requirements - Your are on stock Rom How to install Oreo - Download 2.5.243/ST stock rom .zip package from here https://mega.nz/#!kUIHhRzY!iaE7-orVxznqXlz59r7QnQiSOYnrGBEUDsIonGmx_G4 - Rename it as update.zip - Put it in principal root of your...
forum.xda-developers.com
Search bro...
alexiosAuditore said:
I tried following these instructions https://forum.xda-developers.com/t/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.3928699/ but I'm stuck at step 1.1.4 (method 2). QFIL does not find any available port
Click to expand...
Click to collapse
Disable digital driver signature on windows and reinstall drivers
alexiosAuditore said:
I tried following these instructions https://forum.xda-developers.com/t/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.3928699/ but I'm stuck at step 1.1.4 (method 2). QFIL does not find any available port
Click to expand...
Click to collapse
Use twrp and reboot to EDL mode