This is for realme xt, but I believe that it is similar to a lot other devices based on qualcomm MSM chipsets.
In my specific case, I have a brand new realme xt phone with a locked bootloader (default from factory). I've upgraded it to latest stock realme Adnroid 10 from realme only to notice that the official unlock tool didn't work anymore. So I've tried to downgrade it from Android 10 to Android 9 stock ROM. It seemed to go ok, but it failed. Now system, recovery and fastboot are unaccessible. When turned on, it only stays at the logo screen.
So, after searching a lot, I've found out that there is a hidden EDL (Emergency Download Mode) from Qualcomm that it is used in situations like this. I've found the stock firmware (official ROMs in a .ofp file format). Since I can't reach recovery or fastboot mode, EDL seems to be the only option.
Again I've serched a lot, including what people would use for other phones, but I can't get any of those EDL tools to work: sometimes either you must have some secret credentials or the software have viruses (and I don't know if it still requires credentials). Other options require the firmware in other file formats: XML, MTN, etc, which I haven't figured out how to extract or acquire. Finally, there are many texts that says that QFIL, etc tools can't be used for realme xt, because they wouldn't be able to write the filesystems.
In my region there is no realme service center, so that's not an option. I've bought the phone from a registered importer, which is also clueless. The phone has all the invoices and related paperwork correct.
So, in a nutshell:
1) The phone is softbricked (hopefully), but requires EDL mode to be recovered. Sending it to a service center is not possible (because of import/export procedures);
2) Where can I find a tool to enable me to revive it to stock ROM (I already have ofp and ozip files)?
3) How can I acquire the required credentials (if necessary) for it to work?
4) Failing 2 and 3, does anybody know of someone who can provide remote services to fix it? (I'm thinking of setting up my computer and someone remotely using their credentials and procedures)
Thank you all in advance for any help. This would be my mother's Christmas gift, It is very expensive for us and right now it is only a very expensive paper weight.
Related
Hi,
I bought a Huawei Mediapad M3 Lite 10 tablet last week. Its model number is BAH-L09. I am in desperate need of rooting this device. I have searched in google for quite a time. But no success. Please help me get this device rooted. I can provide further details of the tablet if required. Please help...
+1
maybe I will never ever buy Huawei Android devices again. There are no Devs - not even AOSP support.
Gesendet von meinem MHA-L29 mit Tapatalk
liveondead said:
Hi,
I bought a Huawei Mediapad M3 Lite 10 tablet last week. Its model number is BAH-L09. I am in desperate need of rooting this device. I have searched in google for quite a time. But no success. Please help me get this device rooted. I can provide further details of the tablet if required. Please help...
Click to expand...
Click to collapse
Any Progress on this I am in a similar situation with M3 Lite 8
liveondead said:
Hi,
I bought a Huawei Mediapad M3 Lite 10 tablet last week. Its model number is BAH-L09. I am in desperate need of rooting this device. I have searched in google for quite a time. But no success. Please help me get this device rooted. I can provide further details of the tablet if required. Please help...
Click to expand...
Click to collapse
This is a Qualcomm Nougat device. You can root using Magisk or a custom recovery. I'll be happy to help.
Do you have the firmware for this model? If not search for it and download first
Hovatek said:
This is a Qualcomm Nougat device. You can root using Magisk or a custom recovery. I'll be happy to help.
Do you have the firmware for this model? If not search for it and download first
Click to expand...
Click to collapse
I do not have the firmware, I looked for a full OTA update on MT and everywhere I could think of but I could not find it. Does Magisk require FW as a starting point? I'm not familiar with Magisk but will now look it up...
jkindem said:
I do not have the firmware, I looked for a full OTA update on MT and everywhere I could think of but I could not find it. Does Magisk require FW as a starting point? I'm not familiar with Magisk but will now look it up...
Click to expand...
Click to collapse
The reason you'll need the firmware is that you'll need either tock boot.img or recovery.img to root. You obtain them either from the firmware or by dumping your phone's firmware
Hovatek said:
The reason you'll need the firmware is that you'll need either tock boot.img or recovery.img to root. You obtain them either from the firmware or by dumping your phone's firmware
Click to expand...
Click to collapse
I ordered an NCKpro box thinking that as advertised I would be able to read the stock firmware from the tablet since it has a QUALCOMM chipset. however after unlocking my device (success), and trying to put it in EDL mode it does not enumerate as a QUALCOMM device, so the NCK module looking for it doesn't work. It seems to enumerate as "android adapter PCUI (COM5)". I have sent multiple messages to the NCK forum but have gotten no response....seems like there is no support from that group and the documentation comes mostly from Hovetec. Amazing that there is no support for the product.
Have you had success trying to read stock ROM off of Huawei with NCK box?
jkindem said:
I ordered an NCKpro box thinking that as advertised I would be able to read the stock firmware from the tablet since it has a QUALCOMM chipset. however after unlocking my device (success), and trying to put it in EDL mode it does not enumerate as a QUALCOMM device, so the NCK module looking for it doesn't work. It seems to enumerate as "android adapter PCUI (COM5)". I have sent multiple messages to the NCK forum but have gotten no response....seems like there is no support from that group and the documentation comes mostly from Hovetec. Amazing that there is no support for the product.
Have you had success trying to read stock ROM off of Huawei with NCK box?
Click to expand...
Click to collapse
I share your frustration with the limited info and support for the box, that's why we're trying to fill that void with our tutorials and videos.
I've been able to backup Qualcomm using NCK Pro Box as explained at https://forum.hovatek.com/thread-22362.html but not yet tried a Huawei Qualcomm . Ensure to see the video and install drivers as instructed (very important).
In EDL Mode, you should have something like Qualcomm HS-USB QDLoader 9008 in device manager not android adapter PCUI (COM5) so its either you've not installed drivers correctly or are not in EDL mode.
Yours is MSM8940 , I believe NCK Pro box should support.
How are you booting in EDL? Using button combo or ADB / Fatboot?
Hovatek said:
I share your frustration with the limited info and support for the box, that's why we're trying to fill that void with our tutorials and videos.
I've been able to backup Qualcomm using NCK Pro Box as explained at https://forum.hovatek.com/thread-22362.html but not yet tried a Huawei Qualcomm . Ensure to see the video and install drivers as instructed (very important).
In EDL Mode, you should have something like Qualcomm HS-USB QDLoader 9008 in device manager not android adapter PCUI (COM5) so its either you've not installed drivers correctly or are not in EDL mode.
Yours is MSM8940 , I believe NCK Pro box should support.
How are you booting in EDL? Using button combo or ADB / Fatboot?
Click to expand...
Click to collapse
Booting in EDL mode using ADB or button presses get me to the same Huawei screen. its orange type that says press the volume up button for 3 seconds to enter recovery mode, otherwise it does a normal boot. When pressing this button it goes into a recovery mode in which I saw in the device manager what I reported previously.... no QUALCOMM. Perhaps this newer tablet has some layer over the base QUALCOMM or it is something new altogether. Oddly the Huawei ultimate module wants to connect in service mode which is set by doing the keypad with the ()()xxx()() code, etc. The Huawei module seems to be able to communicate with the device, but there is no functionality there to download stuff. I can't believe that no one has figured this out or there is no stock images out there for this tablet, but I also found that Huawei pulled all the stock images and updates off the web for their products last September....
I am an expert at installing usb drivers, but perhaps the ones that are in the default enumeration need to be overridden? I tried that but there are 4 different device enumerations of which none are QUALCOMM what was shown in the thread.
Can you think of any other way of getting a stock rom for this?
jkindem said:
Booting in EDL mode using ADB or button presses get me to the same Huawei screen. its orange type that says press the volume up button for 3 seconds to enter recovery mode, otherwise it does a normal boot. When pressing this button it goes into a recovery mode in which I saw in the device manager what I reported previously.... no QUALCOMM. Perhaps this newer tablet has some layer over the base QUALCOMM or it is something new altogether. Oddly the Huawei ultimate module wants to connect in service mode which is set by doing the keypad with the ()()xxx()() code, etc. The Huawei module seems to be able to communicate with the device, but there is no functionality there to download stuff. I can't believe that no one has figured this out or there is no stock images out there for this tablet, but I also found that Huawei pulled all the stock images and updates off the web for their products last September....
I am an expert at installing usb drivers, but perhaps the ones that are in the default enumeration need to be overridden? I tried that but there are 4 different device enumerations of which none are QUALCOMM what was shown in the thread.
Can you think of any other way of getting a stock rom for this?
Click to expand...
Click to collapse
Check the thread at https://forum.xda-developers.com/general/help/how-to-enter-qualcomm-mmc-storage-diag-t3253478
It talks about other backup options using QFIL (HDDRaw) or emmc raw tool. Also look at the Enter Qualcomm HS-USB QDLoader 9008 part which talk of entering edl using eMMC software download (QPST) > Switch device to DLoad; or using EFS Pro - Qualcomm NV Tools > Change mode since adb, fastboot and button combo don't work.
liveondead said:
Hi,
I bought a Huawei Mediapad M3 Lite 10 tablet last week. Its model number is BAH-L09. I am in desperate need of rooting this device. I have searched in google for quite a time. But no success. Please help me get this device rooted. I can provide further details of the tablet if required. Please help...
Click to expand...
Click to collapse
Untill TWRP for this device developed, u can get this device rooted by flashing magisk-patched boot.img.
check here "https://forum.xda-developers.com/general/help/huawei-mediapad-m3-lite-10-custom-rom-t3621619/page7"
Hi,
I hope this is the right forum, otherwise mods please move this thread to right one.
Problem
Stock Nougat ROM on Infinix Note 4 Pro (x571) was upgraded to Oreo 8.1 via OTA. Device was purely stock, no rooting or custom recovery of any sort. After a few weeks from day of upgrade, device became sluggish and restarted randomly until it reached to a level were it would start and after reaching home screen, it will restart again (a boot-loop kind of thing). I factory resetted the device using stock recovery which was the starting of disaster. I ended up being stuck in "Setup Wizard" where it would go 2 steps forward then come back to "restore device or start a refresh".
Searches on Google revealed that this setup wizard problem is not device specific and only solution is to flash stock ROM. I was unable to find stock Oreo ROM but found Nougat hence using SP Flash Tool, I manage to flash it back correctly. Device finish setup smoothly and worked flawlessly until I realized I am unable to make/receive calls. I checked and re-inserted SIM, operator signals were shown correctly, rebooted many times, cleared cache, etc. but nothing worked until another set of search at Google shows that it could be because of IMEI hence I used *#06# only to find that IMEI was null (blank).
I tried to restore IMEI from the box using:
* MTK Engineering Mode tools > Connectivity > CDS as per various forums and blogs. Unfortunately, my device was did not show CDS options like many screenshots at Internet.
* After failing with MTK Engg. Mode tools, I resorted to MobileUncle Tool. Generated IMEI.bak with genuine IMEI numbers using a software file but as soon as I touched "Restore IMEI" in MobileUncle Tool, it showed error "No Support".
Only method left for trying is this one only because I don't have Windows PC/Laptop (I use Linux as daily driver). At work, I do have Windows but IT Security has disabled all USB ports so that's a difficult option.
My questions are
1. Is there any alternative for Linux users to restore IMEI? So far I am unable to find anything. Combo of Virtual Machine or Wine is not working.
2. Is it possible using ADB/Fastboot tools?
* In case answer is NO for 1 and 2, what is the success chances of MTK Droid Tools? Important to mention that I do not have any backup of first ROM I was using before upgrade, no backup of EFS or NVRAM partitions, etc.
My phone is still functioning perfectly well with all features except IMEI issue (hence no calls or sms) and this will require a big heart for me to use it as a paper weight or email assistant.
Thanks to everyone for the time in reading my TL; DR post.
No. The only legal way to fix the imei issue if flashing a full stock doesn't work is send it in and they will charge you for a new mother board.
Messing with imei is very illegal in some countries and as such banned here.
Thanks, advice is still under warranty so I will try to get it from seller (if they accept).
I got hold of this perseus which has no mobile signal because previous owner deleted EFS partition by mistake. There is no IMEI, that's why it's not registering on the mobile network. Then again, its bootloader got locked by installing latest stock MIUI 11 global through MiFlashTool. So, I can't get to the point of repairing the IMEI with the stock recovery.
When I try to unlock bootloader it says to authorize the device from developer option, but that authorization requires SIM connectivity. Without sending SMS or without using mobile data it can't authorize the device and it won't let me unlock bootloader.
So here I am stuck with a flagship level phone without any signal. Everything else like wifi & bluetooth seems to be working fine.
Any suggestions from the great minds of xda?
Any method to write IMEI with the bootloader locked?
I've been looking for two days on how to solve this. Seems like there's not a lot to do unless I can unlock the bootloader. Even the EDL mode is locked. I turned to Miracle Tool for Xiaomi but their website says servers are currently not working. Then there's Chimera Tool, but it's too expensive to buy for just one phone.
Then I found out there are two more ways of getting to EDL mode. One is, opening up the device and shorting JTAG pins to boot into EDL, which is commonly known as test point method. And the other is, using an EDL cable which I can easily make at home.
Now I'm going to make an EDL cable to see if I can get into EDL mode successfully. If I can, then I will be able to repair the IMEI with other softwares. Although I don't have a QCN file for the MIX 3 yet, I'll concentrate on getting to EDL mode first.
:fingers-crossed:
EDL cable method don't work on these newer phones anymore. And these are also EDL-locked so test point method needs an authorized xiaomi account to access using EDL. If you google "Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts" then you'll find an excellent article that points out the issue in this new security system. Because of this my phone is now network-dead and can never be fixed from Bangladesh.
If anyone finds any solution to this problem in future please do let me know here. Thank you.
This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
KaptinBoxxi said:
This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
Click to expand...
Click to collapse
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
JayTM said:
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
Click to expand...
Click to collapse
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
KaptinBoxxi said:
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
Click to expand...
Click to collapse
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
JayTM said:
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
Click to expand...
Click to collapse
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
KaptinBoxxi said:
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
Click to expand...
Click to collapse
Good luck to you.
I contacted TCL support myself with no luck. They immediately put my case in pending close status.
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
JayTM said:
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
Click to expand...
Click to collapse
I'll check it out. If its possible to view the code in a tool like dnSpy or extract files from the exe with 7zip, its possible to use with our device, i'm sure as long as the commands are similar
Well you're in luck as it is just a .bat file program simple notepad++ will do.
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Tech101yt said:
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Click to expand...
Click to collapse
Have had the phone for less than 6 months and I'm already having LCD issues. When the display is off, just sitting on a table or something, it'll flash white randomly like its getting an electric signal at random. Its nothing I did. I've never hard dropped the thing. Everywhere I go pretty much is carpeted except work. If manufacturer warranty doesn't cover me, I'll stop recommending the phone to people
I actually switched to an Essential Phone recently. Way better experience, way cheaper too. I have around a dozen of them anyway and have been selling em on swappa (dunno if I'm allowed to say that here, but oh well) lol
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
mschoolbus said:
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
Click to expand...
Click to collapse
Nah its turned off. It flashes like a broken LCD would look. All snowy and stuff like an old TV. Its not notifications, just a bad LCD
that sucks... could try reseating the screen's ribbon cable :-/
can anybody share the full update rom about android 11?
top170 said:
can anybody share the full update rom about android 11?
Click to expand...
Click to collapse
I don't believe anyone has Logcatted the update process yet to get the firmware, but on the subject of this post, I do have some updates
I was digging through my Logcat from january and realized I missed something massive. I have yet to figure out the URL structure, but I have all the info for it.
So when you go to the following link, it gives a bunch of errors of missing info
https://g2master-sa-east.tclclouds.com/notify_new.php
For the firmware here on this post at least, each value from my device is
Code:
id = 0156260
curef = T799B-2ALCUS11
vk = 741ace917e3527af81412ca93b0fcce2de04a264
salt = 1611977254070885419
fv = 4DJ1LM10
tv = 4DJBLMB0
op = 1000
status = 999
mode = 2
cltp = 10
type = firmware
formatted from logcat
reportContent= {"id":"0156260","salt":"1611977254070885419","curef":"T799B-2ALCUS11","fv":"4DJ1LM10","tv":"4DJBLMB0","mode":"2","cltp":"10","type":"Firmware","op":"1000","status":"999","vk":"741ace917e3527af81412ca93b0fcce2de04a264"}
no matter what, I get the errors on the web page
After playing with some custom ROM, my device is stuck in EDL mode. i.e Stuck in primary bootloader. I cannot get to the secondary bootloader. either, recovery mode or fast boot mode.
Solution and issues faced.
Solution 1: Flash original Rom via Mi flash tool.
Issues: Xiaomi restricts the user to flash room when the device is in EDL mode. After some research found only authenticate accounts can install ROM in EDL mode via the mi flash tool. It will ask for EDL authentication. that I don't have access to.
I think the only solution is to somehow reverse back to fast boot or recovery mode and install back the rom.
Has anybody faced such issue and know the solution.
simonastani said:
After playing with some custom ROM, my device is stuck in EDL mode. i.e Stuck in primary bootloader. I cannot get to the secondary bootloader. either, recovery mode or fast boot mode.
Solution and issues faced.
Solution 1: Flash original Rom via Mi flash tool.
Issues: Xiaomi restricts the user to flash room when the device is in EDL mode. After some research found only authenticate accounts can install ROM in EDL mode via the mi flash tool. It will ask for EDL authentication. that I don't have access to.
I think the only solution is to somehow reverse back to fast boot or recovery mode and install back the rom.
Has anybody faced such issue and know the solution.
Click to expand...
Click to collapse
Your device can't be stuck in EDL mode timeless, to get it out of there, you just have to disconnect it from the PC and press the three buttons at the same time for about 10 seconds.
A different thing is that your device can't enter to fastboot nor recovery. Firstly get it out from EDL mode and see which modes are available after that.
SubwayChamp said:
Your device can't be stuck in EDL mode timeless, to get it out of there, you just have to disconnect it from the PC and press the three buttons at the same time for about 10 seconds.
A different thing is that your device can't enter to fastboot nor recovery. Firstly get it out from EDL mode and see which modes are available after that.
Click to expand...
Click to collapse
My secondary bootloader files are corrupted and can't get to it. Have only access to EDL mode. Can't get back to fast boot or recovery mode. The only option found is to somehow install flashable firmware via QFIL and get back to the secondary bootloader to access the flash tool of vendor-specific devices.
simonastani said:
My secondary bootloader files are corrupted and can't get to it. Have only access to EDL mode. Can't get back to fast boot or recovery mode. The only option found is to somehow install flashable firmware via QFIL and get back to the secondary bootloader to access the flash tool of vendor-specific devices.
Click to expand...
Click to collapse
Well, to be clear and not put effort where no results have to be expected; there’s no a secondary bootloader, this device have a fastboot mode (accessed usually pressing PWR + volume down buttons), a recovery mode (usually accessed pressing PWR + volume up), an EDL mode (usually accessed on an unlocked device pressing the two volume buttons at same time while connecting to PC or through test point method), and additionally a user space friendly fastbootd mode that only can be accessed using either ADB or fastboot command, also can be accessed through some custom recoveries in the PWR menu.
If you are totally sure you tried all the combination keys indicated WHILE your device is off, then you have to move it to the next:
- Search for a patched Firehose file either for your specific device or from a device with the same motherboard that can work too onto your device, this is to bypass the Mi account authorization or to work in qfil.
- Search for an engineer firmware for your device, if something exists have to bypass the Mi Flash tool restriction.
SubwayChamp said:
Well, to be clear and not put effort where no results have to be expected; there’s no a secondary bootloader, this device have a fastboot mode (accessed usually pressing PWR + volume down buttons), a recovery mode (usually accessed pressing PWR + volume up), an EDL mode (usually accessed on an unlocked device pressing the two volume buttons at same time while connecting to PC or through test point method), and additionally a user space friendly fastbootd mode that only can be accessed using either ADB or fastboot command, also can be accessed through some custom recoveries in the PWR menu.
If you are totally sure you tried all the combination keys indicated WHILE your device is off, then you have to move it to the next:
- Search for a patched Firehose file either for your specific device or from a device with the same motherboard that can work too onto your device, this is to bypass the Mi account authorization or to work in qfil.
- Search for an engineer firmware for your device, if something exists have to bypass the Mi Flash tool restriction.
Click to expand...
Click to collapse
My device is poco x3 pro. unable to find the patched firehose file..
simonastani said:
My device is poco x3 pro. unable to find the patched firehose file..
Click to expand...
Click to collapse
Man, you are not reading well, it's not so simple like that, I can't give you the exact solution in your hands but I giving you the direction that you have to take in order to find some solution and avoid taking it to a service center, not all countries have one at hand like mine.
- Search for a programmer firehose similar to your device if the exact for your model doesn't exist.
- Search for a programmer firehose for sm7150, it's the same as yours. Take a look here https://www.droidwin.com/patched-firehose-file/
- Search for an engineering/combination ROM for your device (it must be specific for your device, not for a similar one), this is one example https://testedrombd.com/poco-x3-pro-eng-fix-firmware/ some engineering ROM have the ability to bypass restrictions, not always, but it is worth to give it a try.
- And the last resort, exploiting/modifying/editing firehose vulnerabilities, read this https://github.com/bkerler/edl
SubwayChamp said:
Man, you are not reading well, it's not so simple like that, I can't give you the exact solution in your hands but I giving you the direction that you have to take in order to find some solution and avoid taking it to a service center, not all countries have one at hand like mine.
- Search for a programmer firehose similar to your device if the exact for your model doesn't exist.
- Search for a programmer firehose for sm7150, it's the same as yours. Take a look here https://www.droidwin.com/patched-firehose-file/
- Search for an engineering/combination ROM for your device (it must be specific for your device, not for a similar one), this is one example https://testedrombd.com/poco-x3-pro-eng-fix-firmware/ some engineering ROM have the ability to bypass restrictions, not always, but it is worth to give it a try.
- And the last resort, exploiting/modifying/editing firehose vulnerabilities, read this https://github.com/bkerler/edl
Click to expand...
Click to collapse
Yeah. Its not simple. Prior to giving link ,I have tried those methods. Thanks for the information
From my findings.
1. Patch programmer firehose file for sm7150 not found anywhere. Tried using different patch firehose file of other compatible devices that uses 860 chipset. Unsuccessful result.
2. Tried Engineering ROM of Vayu. Unable to bypass restrictions. It ask for edl authentication same as of vendor specific rom. I think the reason is xiaomi restrict user to flash room via edl mode. Still searching some way to bypass authentication.
3. Last resort. modifying firehose and hex files. Need a lot of research.
Didn't find any solution for poco x3 pro specific devices in community.
Can We install 860 chipset flashable frimware of oneplus via QFIL . Need to tried that one. Is it possible.?
simonastani said:
Yeah. Its not simple. Prior to giving link ,I have tried those methods. Thanks for the information
From my findings.
1. Patch programmer firehose file for sm7150 not found anywhere. Tried using different patch firehose file of other compatible devices that uses 860 chipset. Unsuccessful result.
2. Tried Engineering ROM of Vayu. Unable to bypass restrictions. It ask for edl authentication same as of vendor specific rom. I think the reason is xiaomi restrict user to flash room via edl mode. Still searching some way to bypass authentication.
3. Last resort. modifying firehose and hex files. Need a lot of research.
Didn't find any solution for poco x3 pro specific devices in community.
Can We install 860 chipset flashable frimware of oneplus via QFIL . Need to tried that one. Is it possible.?
Click to expand...
Click to collapse
QFIL is slightly outdated, so it needs a special programmer, even I don't know if it can work for new UFSs (or a limited range of them) it used to work for devices with eMMCs.
Xiaomi restricts users to flash in EDL mode using Mi Flash tool (the restriction can't apply beyond this tool).
A firmware from other device definitely will brick it.
Research if the PX3P has a counterpart device, I mean Xiaomi released every year a certain model for Global and the same model (with other name) as it happened i.e. with the Mi A3 and the MiCC9 and other models though, in this case it could be possible that the programmer file for this model could work for you.
Also, I saw on the OnePlus thread a tool capable to flash through EDL, maybe replacing the files it could work, I didn't try it yet.
E eu fui passar a .eu via Fastboot no meu e tava demorando dms... fui e fechai o CMD, e matei meu celular