Related
hello everyone so i messed up bad. need rsd lite firmware to flash if anyone can share. all i have now is the abiliy to get into bootloader mode. Any help would be appreciated.
mikelikesbikes said:
hello everyone so i messed up bad. need rsd lite firmware to flash if anyone can share. all i have now is the abiliy to get into bootloader mode. Any help would be appreciated.
Click to expand...
Click to collapse
All factory images can be found here: http://motofirmware.center/files/category/23-droid-turbo/
having trouble getting rsd to recognize my device in bootloader, anyone recommend some drivers i can try? windows 8.1
mikelikesbikes said:
having trouble getting rsd to recognize my device in bootloader, anyone recommend some drivers i can try? windows 8.1
Click to expand...
Click to collapse
Install Motorola Device Manager from Moto's website. That will give you the drivers you need.
My advice is don't use RSDlite. To get it to work, you have to edit the xml file in the firmware that you're trying to flash to remove all the other devices that it inexplicably also includes. All RSDlite does is automate the fastboot flashing process. A better way to do it, in my opinion, is to edit the .bat file that comes with the factory images and manually input the fastboot commands that you see there. If you want more detailed directions, see my post here: http://forum.xda-developers.com/droid-turbo/help/turbo-firmware-t3254185
tried your tutorial. now for some reason i cant get fastboot to recognize my device. device manager now says "fastboot quark S" with the little triangle beside it. fastboot devices isnt showing my device is connected,but it did before i tried manually flashing like in the post you linked me to. i dont get it
TheSt33v said:
Install Motorola Device Manager from Moto's website. That will give you the drivers you need.
My advice is don't use RSDlite. To get it to work, you have to edit the xml file in the firmware that you're trying to flash to remove all the other devices that it inexplicably also includes. All RSDlite does is automate the fastboot flashing process. A better way to do it, in my opinion, is to edit the .bat file that comes with the factory images and manually input the fastboot commands that you see there. If you want more detailed directions, see my post here: http://forum.xda-developers.com/droid-turbo/help/turbo-firmware-t3254185
Click to expand...
Click to collapse
what do you mean by editing the .bat file that comes with factory images?
mikelikesbikes said:
what do you mean by editing the .bat file that comes with factory images?
Click to expand...
Click to collapse
I mean right click on the .bat file that is included in the .zip file of the firmware that you're trying to flash and select "edit." This allows you to see the commands that the .bat file does when you double click on it.
But you don't have to worry about that, because I already outlined the necessary commands in the post that I gave you a link to.
TheSt33v said:
I mean right click on the .bat file that is included in the .zip file of the firmware that you're trying to flash and select "edit." This allows you to see the commands that the .bat file does when you double click on it.
But you don't have to worry about that, because I already outlined the necessary commands in the post that I gave you a link to.
Click to expand...
Click to collapse
any idea why fastboot doesnt see my device now? it did before, but I get the yellow triangle in device manager. I have installed every driver i can find... including motorola device manager and ran it several times. Was on mofo'd 4.4.4. and for some dumb reason thought i could flash the lollipop bootloader so now i am stuck with bootloader, recovery, but no os. any advice would be great.
OK, so i finally got fastboot to recognize my device again. Trying to download stock firmware from Rootjunky. Am i correct that I extract the zip into the fastboot folder then issue the commands? I am about to pull my hair out...
mikelikesbikes said:
any idea why fastboot doesnt see my device now? it did before, but I get the yellow triangle in device manager. I have installed every driver i can find... including motorola device manager and ran it several times. Was on mofo'd 4.4.4. and for some dumb reason thought i could flash the lollipop bootloader so now i am stuck with bootloader, recovery, but no os. any advice would be great.
OK, so i finally got fastboot to recognize my device again. Trying to download stock firmware from Rootjunky. Am i correct that I extract the zip into the fastboot folder then issue the commands? I am about to pull my hair out...
Click to expand...
Click to collapse
Yep. That should be all you have to do.
As stated above, I am trying to unbrick my Axon M with the firehose provided by Unjustified Dev. and firmware from deadman96385. When I tried using QFIL, even placing everything in its own directory on the root of the PC with no spaces in file names, it would get stuck when flashing. And whenever I tried to use MiFlash, I would get the error:"couldn't find flash script" when I selected the firmware folder. Any help is much appreciated.
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
ff7cloudsnobody said:
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
Click to expand...
Click to collapse
I'm confused, I am using Deadmans b37 firmware, and Unjustified's firehose. I removed the entire userdata line from rawprogram0, and used that with the accompanying patch xml file with QFIL. I don't know how to alter boot.img, and where would I place the edited "recovery.img" file? I am using a good USB cable as well.
ehsan96696 said:
I'm confused, I am using Deadmans b37 firmware, and Unjustified's firehose. I removed the entire userdata line from rawprogram0, and used that with the accompanying patch xml file with QFIL. I don't know how to alter boot.img, and where would I place the edited "recovery.img" file? I am using a good USB cable as well.
Click to expand...
Click to collapse
Ignore the img edits, that's what I did but its not necessary. Are you running qfil as admin? Is the directory simple, no spaces or symbols? What is the latest error you are getting?
boot
ff7cloudsnobody said:
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
Click to expand...
Click to collapse
Hello.
Can you share your patched boot image, please? Perhaps, after the removal of secure boot, it will be possible to patch the boot image with Magisk (in working Android), and then flash it with TWRP or QFIL, thus obtaining root?
WBR, Draco.
ff7cloudsnobody said:
Ignore the img edits, that's what I did but its not necessary. Are you running qfil as admin? Is the directory simple, no spaces or symbols? What is the latest error you are getting?
Click to expand...
Click to collapse
I did run qfil as admin. These pictures will show the directory: https://imgur.com/M2TdriT https://imgur.com/BmwyeMa
I did not encounter error, it just gets stuck as shown above.
Drakosha said:
Hello.
Can you share your patched boot image, please? Perhaps, after the removal of secure boot, it will be possible to patch the boot image with Magisk (in working Android), and then flash it with TWRP or QFIL, thus obtaining root?
WBR, Draco.
Click to expand...
Click to collapse
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
ehsan96696 said:
I did run qfil as admin. These pictures will show the directory: https://imgur.com/M2TdriT https://imgur.com/BmwyeMa
I did not encounter error, it just gets stuck as shown above.
Click to expand...
Click to collapse
rename that folder, that name is way too long. Name it z999update37 or something short and sweat like I did and see if that helps, you can also see if it was a bad download by trying a new one. it just seems to be getting stuck on the emmc portion. Like someone else said in the other thread, make sure the config of qfil is for emmc and that not really anything is selected.
edit: I attached my emmc file, try using it in your folder to see if thats the issue
ff7cloudsnobody said:
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
rename that folder, that name is way too long. Name it z999update37 or something short and sweat like I did and see if that helps, you can also see if it was a bad download by trying a new one. it just seems to be getting stuck on the emmc portion. Like someone else said in the other thread, make sure the config of qfil is for emmc and that not really anything is selected.
edit: I attached my emmc file, try using it in your folder to see if thats the issue
Click to expand...
Click to collapse
So, few things. After following all of Undead's installation steps (minus using QFIL), and the steps that I listed at the start of this post, I used the miflash from the axon 7 tutorial page here:https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
For some reason any other Miflash would give the previously stated error. I then installed the ZTE Android drivers provided. And using deadman's B37, Miflash worked like a charm!
ff7cloudsnobody said:
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
Click to expand...
Click to collapse
Hello.
I flashed B37 with your boot image & TWRP successfully (using MiFlash; QFIL stopped at the same emmc_appsboot file). Except for "TV Mode setup" that was blocking the normal startup, everything went smooth. However, when I attempted to flash Magisk-patched boot image using TWRP, the phone refused to boot, so I had to re-flash an original boot.img. I guess, root access will be a bit more complicated since the bootloader appears to be locked indeed...
Can you sign the rooted boot image with the same keys as the rest of the b37 firmware? Perhaps, then it will work?
Best regards,
Draco.
ehsan96696 said:
So, few things. After following all of Undead's installation steps (minus using QFIL), and the steps that I listed at the start of this post, I used the miflash from the axon 7 tutorial page here:https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
For some reason any other Miflash would give the previously stated error. I then installed the ZTE Android drivers provided. And using deadman's B37, Miflash worked like a charm!
Click to expand...
Click to collapse
Weird but awesome that it worked
Drakosha said:
Hello.
I flashed B37 with your boot image & TWRP successfully (using MiFlash; QFIL stopped at the same emmc_appsboot file). Except for "TV Mode setup" that was blocking the normal startup, everything went smooth. However, when I attempted to flash Magisk-patched boot image using TWRP, the phone refused to boot, so I had to re-flash an original boot.img. I guess, root access will be a bit more complicated since the bootloader appears to be locked indeed...
Can you sign the rooted boot image with the same keys as the rest of the b37 firmware? Perhaps, then it will work?
Best regards,
Draco.
Click to expand...
Click to collapse
Right now I'm focused on building the aosp instead of editing the current setup more than have. You can use the android image kitchen to unpack the imgs and edit them. I just used notepad to do my edits.
Root
ff7cloudsnobody said:
Right now I'm focused on building the aosp instead of editing the current setup more than have. You can use the android image kitchen to unpack the imgs and edit them. I just used notepad to do my edits.
Click to expand...
Click to collapse
Can you, please, look into this problem and help us obtain root? It is absolutely necessary for this phone outside of US, right now it's just a small tablet Building AOSP is great, but until it's ready, until it supports dualscreen & e.t.c. - there could be weeks or even months... You edited boot image, and this edited boot worked with locked bootloader - witch means, that it is still signed with OEM keys. Please, do this once more with Magisk-patched rooted image.
Thanks in advance,
WBR - Draco
Drakosha said:
Can you, please, look into this problem and help us obtain root? It is absolutely necessary for this phone outside of US, right now it's just a small tablet Building AOSP is great, but until it's ready, until it supports dualscreen & e.t.c. - there could be weeks or even months... You edited boot image, and this edited boot worked with locked bootloader - witch means, that it is still signed with OEM keys. Please, do this once more with Magisk-patched rooted image.
Thanks in advance,
WBR - Draco
Click to expand...
Click to collapse
Ok, so the boot img I had previously sent did not have all secure options disabled, try this one (already magisk patched)
ff7cloudsnobody said:
Ok, so the boot img I had previously sent did not have all secure options disabled, try this one (already magisk patched)
Click to expand...
Click to collapse
Thanks! Unfortunately, this boot does't work, the phone repeatedly boots into recovery (just like a regular boot image after being patched with Magisk). But thank you for your time anyway, with respect - Draco.
Drakosha said:
Thanks! Unfortunately, this boot does't work, the phone repeatedly boots into recovery (just like a regular boot image after being patched with Magisk). But thank you for your time anyway, with respect - Draco.
Click to expand...
Click to collapse
Doing the unpatched boot with security removed works, so this must be something that is in a subsection of boot.img other than build.prop. I'll have to look at what magisk changes, see what other locks ZTE has inside the image, and go from there.
edit: at this point, this conversation is not related to the post. If I make a breakthrough then I will make a new thread.
Hello, thanks for all people, who have written this thread! I bought an Axon M which was bricked. I tried QFIL with the B30 ATT firmware, but it didn't worked. Than, as already mentioned, i have to remove the userdata line from rawprogram , use the firehose from Unjustified Dev from and with MiFlash it worked without any problems. I had problems with getting into the qdloader mode, but i tried several combinations with Power and Volume Buttons, until i got into the qdloader mode.
Hi all
I need Loader please for this AT&T Z999 model
the one I found in this publication did not work for me : https : // forum.xda-developers.com/axon-m/how-to/rom-zte-axon-m-stock-firmware-firehose-t3909847
I just wish this method would work to update the AT&T Axon M from B30 to B37.
tj65 said:
Hello, thanks for all people, who have written this thread! I bought an Axon M which was bricked. I tried QFIL with the B30 ATT firmware, but it didn't worked. Than, as already mentioned, i have to remove the userdata line from rawprogram , use the firehose from Unjustified Dev from and with MiFlash it worked without any problems. I had problems with getting into the qdloader mode, but i tried several combinations with Power and Volume Buttons, until i got into the qdloader mode.
Click to expand...
Click to collapse
Are you able to provide the firehose that you used?
I tried the B37 and the firehost from this link https://forum.xda-developers.com/t/rom-zte-axon-m-stock-firmware-firehose.3909847/
along with the miflash from this link https://forum.xda-developers.com/t/edl-a2017-a2017u-emergency-dl-mode-twrp-unlock-upgrade.3553514/
But it always fails.
It will simply give an error of "Cannot receive hello packet"
then it will eventually go to the error of
"Object reference not set to an instance of an object."
I am using an AT&T Z999 that is on B30, and I am trying to get it updated to B37 (currently not looking to root or anything else, just want to update without having to have active AT&T service.
Edit: I think I found the right one. https://forum.xda-developers.com/t/...-unofficial-twrp-recovery-for-axon-m.3959314/
So far, copying that firehose file into the B37 folder seems to be allowing it to flash.
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 messed up my v40 405ebw, itry to cross flash it to korean version 409n using lgup partition dl but now it is not usable, an error always pop up and I can't access about phone, i try to flash it via refurbish but it includes error not support for cross flash please help me to restore my v40..
you may download and install the below LGUP, then replace the files in the lgup forlder in your program files with the one in "LGUP_to be copied into LGUP folder", then run LGUP you'll be able to crossflash to your European kdz again.
drive.google .com/file/d/1mmap7NZAdNXXz1TIZTDv7XEuqEqyR9JA/view?usp=sharing
ps. remove spaces in the link
hope it helps.
V2056A | PD2056 | 5G China variant
- PD2056B_A_1.11.13 HERE Android 11
thats good!
and how can i flash it?
My device is last week broken . is the rom flashable with fastboot? thx mike
How did you broken the device?
You can simply upload zip on device with adb command and flash by using stock recovery mode
adb push .....
I tried to flash my patched boot.img (via_magisk) with the MTKROOT V2.5.5 tool. -https://www.ayudaroot.com/root/vivo/como-rotear-los-telefonos-vivo-x60-pro-plus . The first problem was unlocking the bootloader. That did not make the tool. The tool failed .. I unlocked that manually in fastboot mode. After the bootloader was open, I tried the tool for the second time.
That was probably the serious mistake! The tool has transferred the patched boot img. So far everything was o. K. Then I booted to the Recovery Menu to clean the data and cache partition. (Factory Reset). Then restart system. Since then I have a bootloop and it was not possible to boot into recovery mode.
Then I flashed from the Indian Rom the boot and the recovery image.
Now the device booted again in Indian Recovery Mode (English). Then I tried to execute the recovery WLAN update. Unfortunately, the system has found no access points when searched.
!! F *** K !!
The next day I tried to flash the original CN-ROM with the QPST flashtool from https://www.needrom.com/download/vivo-x60-pro-plus/ ..
Here I had problems installing the Qualcomm driver for the EDL download mode or to boot the device in the EDL mode.
Without success!
Finally, I tried to flash all the items of the CN-ROM from Needrom via Fastboot. The Flash order of the items I had from the partition.xml file on the CN-ROM.
But I still have a bootloop ..
No access to the recovery WLAN Update-No networks are displayed ..
Do you have an idea for the EDL download mode?
88user88 said:
I tried to flash my patched boot.img (via_magisk) with the MTKROOT V2.5.5 tool. -https://www.ayudaroot.com/root/vivo/como-rotear-los-telefonos-vivo-x60-pro-plus . The first problem was unlocking the bootloader. That did not make the tool. The tool failed .. I unlocked that manually in fastboot mode. After the bootloader was open, I tried the tool for the second time.
That was probably the serious mistake! The tool has transferred the patched boot img. So far everything was o. K. Then I booted to the Recovery Menu to clean the data and cache partition. (Factory Reset). Then restart system. Since then I have a bootloop and it was not possible to boot into recovery mode.
Then I flashed from the Indian Rom the boot and the recovery image.
Now the device booted again in Indian Recovery Mode (English). Then I tried to execute the recovery WLAN update. Unfortunately, the system has found no access points when searched.
!! F *** K !!
The next day I tried to flash the original CN-ROM with the QPST flashtool from https://www.needrom.com/download/vivo-x60-pro-plus/ ..
Here I had problems installing the Qualcomm driver for the EDL download mode or to boot the device in the EDL mode.
Without success!
Finally, I tried to flash all the items of the CN-ROM from Needrom via Fastboot. The Flash order of the items I had from the partition.xml file on the CN-ROM.
But I still have a bootloop ..
No access to the recovery WLAN Update-No networks are displayed ..
Do you have an idea for the EDL download mode?
Click to expand...
Click to collapse
My PC is over adb unautorized, after the Factory reset...
I managed to get this full rom from Recovery, there is a option to download the full last rom and burn. I use another phone with photo google translator to navegate in the menu.
I know this option with the update from the WLAN - but this option is no longer available to me - after the search for a network is completed, no further networks are displayed. He doesn't find any networks.
And the second problem was - I cannot import this Update.zip into the main directory because the PC is unauthorized.
It wasn't just the MTK tool that was wrong.
I think our mistake was you mixed recovery and boot of another Rom. I did that many years ago with Huawei but for me it was a hard brick. Better not mix!
yes i think thatat too. first step now- i try to put the phone in EDL download mode. Then I could try the Qualcomm Flash Tool -. .. But thank you anyway.
with which command did you unlocked the bootloader? I can't find a way.
@88user88 : i wish you the best.
Do you see a way to flash the indian ROM?
Question was not for me but:
I think i have a way that works. But for that I need the command to unlock the bootloader. Because none of the normal ones works.
DPMDP said:
with which command did you unlocked the bootloader? I can't find a way.
Click to expand...
Click to collapse
+1
wolfgart said:
V2056A | PĐ2056 | Biến thể 5G Trung Quốc
- PD2056B_A_1.11.13 TẠI ĐÂY Android 11
Click to expand...
Click to collapse
hello i am a new user in vietnam, can you guide me in detail how to install . Thank you very much
I spent almost 5 hrs yesterday tried to flash from CN ROM, Origin OS to Global ROM, FunTouch OS. I used several methods including AFTool, QFIL, and QPST tool. None of them succeed.
AFTool - failed to flash because missing Fastboot batch file in the global firmware.
QFIL - failed to flash because, Qualcomm Driver 9808 not detected.
QPTS - failed to flash because, Qualcomm Driver 9808 not detected.
I like Origin OS but the reason I want to change to FunTouch OS is because Origin OS didn't come with Google Mobile Seevice package. In fact, 'Hey Google' also didn't worked out.
DPMDP said:
Question was not for me but:
I think i have a way that works. But for that I need the command to unlock the bootloader. Because none of the normal ones works.
Click to expand...
Click to collapse
OK, if we manage to restore my device, I'll give you instructions on how you can unlock your bootloader. then at least I know that in an emergency you also have the option to restore your device.
otherwise it would be too unsafe for me ...
ok?-now you come!
astrofahim said:
I spent almost 5 hrs yesterday tried to flash from CN ROM, Origin OS to Global ROM, FunTouch OS. I used several methods including AFTool, QFIL, and QPST tool. None of them succeed.
AFTool - failed to flash because missing Fastboot batch file in the global firmware.
QFIL - failed to flash because, Qualcomm Driver 9808 not detected.
QPTS - failed to flash because, Qualcomm Driver 9808 not detected.
I like Origin OS but the reason I want to change to FunTouch OS is because Origin OS didn't come with Google Mobile Seevice package. In fact, 'Hey Google' also didn't worked out. YouTube Vanced also always failed to open.
Click to expand...
Click to collapse
same here, my device is iqoo 7 cn origin os i downloaded from android 12 website, failed to upgrade in recovery mode when in hardware check.
both on funtouch os and android 12
Hi, does anyone know where it is I can find this PD2056C_A_1.14.1 firmware
the command menu of the recovery mode of the Chinese version and in Chinese or English