Related
I have OPPO A3s need to remove user password somehow, even in recovery mode phone asking for locks creen password to factory reset or flash, phone goes in Emergency Download Mode (EDL) if open recovery, connect USB cable to PC and click on Build number 3 times.
So far i can think of two solutions:
1. Mount Filesystem (this guide) with Qualcomm Flash Image Loader (QFIL), phone is detected in QFIL as HS-USB QDLoader 9008 once in EDL mode, but then what, i dont have MBN file required to mount filesystem can someone help?
2. Flash stock firmware, i can download two, from official website in CPH1853_11_A.31.qzip which i can extract, but then what?
Other firmware is unofficial in Oppo_A3S_CPH1853_11_A.21.ofp format this cannot be flashed by any tool i know of, there is info online that OFP file can be converted to proper format for QFIL (with scatter file and xml) by software+usb dongle (Miracle Box, UFI Box), but they are not free.
P.S. I am noob please help.
Hello
hello , does anyone have oppo a3s download certificate, that the only thing standing between me and unlocking it
oppo with new security needs to open the phone made jtag or isp connection direct to cpu to erase pattern
touji said:
oppo with new security needs to open the phone made jtag or isp connection direct to cpu to erase pattern
Click to expand...
Click to collapse
why here is no loader for oppo A3s Like other QUALCOMM devices
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
how do i unlock bootloader on my lg k51
How to Unlock Bootloader of LG Phones Official Method
This is the guide of LG Android Smartphones how to Unlock Bootloader of LG Phones Official Method To Unlock LG G6, LG G7, LG V30, LG V40
www.gizdev.com
I've got my hands on this phone. I've read through all of the replies and I see that @Warlockguitarman has come up with a universal mediaTek method I suppose. So far just going into what I know about LG I've been able to get into fastbootd mode very easily. After that it's a pain in the ass.
You need to download the Minimal Adb and Fastboot tools or just use the latest platform tools. For the people who didn't read the previous posts, the command to reboot to fastboot, is:
Code:
adb reboot fastboot
You'll be rebooted to fastbootd, which is fastboot but moved to the userspace to allow for "flawless" system tweaks.
In fastbootd you can't do much until you've already updated you're drivers from the Device manager. You'll wanna update the LG K500 device I believe. This is the weird part because I can't seem to get consistent results.
Originally I tried using Android Bootloader Interface driver to talk to the device and I noticed that I was getting a HAL issue. Which meant that my cable or driver was messed up. So naturally I tried the LG Adb drivers next. And this time I kept getting (No Link). I then tried searching for some OEM commands. In our devices case, they're hidden by our carriers. So there's not much we can do about that.
On LG's official developer website for unlocking the bootloader, the command to get the OEM unlock code is "fastboot oem device-id". So I tried this as well, and I get a combo of the 2 errors from above. I need more tests from others. If you need help with getting to fastbootd or getting your device to showup in fastboot just ask. We'll help(or at least I will)
On top of everything else, I believe that in order to unlock the bootloader we have to put the device in emergency download mode so that we can dump the full rom of our devices using some low level mediatek interface perhaps. If we can dumb the bootloader, we can extract the hidden OEM commands to see exactly what we need to see. And as @Warlockguitarman says, one of the main issues in getting root is disabling dm-verity. Or boot verification in vbmeta.img.
You can get root without disabling avb, you use patched magisk boot.img and flash in fastbootd, I have my bootrom and preloader dumped and fully understand how the unlock is done, but the correct signature needs to be done to the modified seccfg to be able to flash it to correctly unlock the bootloader and so far only paid tools can do this for the time being... and on the HAL error, that is because fastbootd removes oem commands, so no oem unlock command will work, the seccfg holds the bootloader lock and unlock info an 01 needs to be changed to an 03 and then flashed back. So far only bootrom allows the seccfg.img to be flashed and it requires the correct signature. Check out the mtkclient tool.
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
The tool works for the k51! Go unlock your bootloaders
greetings again mr.warlockwizardguitarman...if you could spare the time..and possible,list the steps for the mtk bootloader unlock for the k51,???couple paragraphs or such,in which you did this...ill be able to figure everything out from there,just a lil garbled r.now..learning to much to quickly,and no experience...lol phew..like i said b4,just started doing the phones from computers,,but,i know py.c,java so,just tryn to put it all together...if you woud be so kind t.y.
How to unlock bootloader and root the LG Stylo 6 and K51 K61 and other K model LG devices
STYLO 6 MTKCLIENT INSTRUCTIONS FOR FLASHING, BACKING UP, UNLOCKING THE BOOTLOADER, AND ROOTING ON WINDOWS 10/11: !!!WARNING!!! ATTEMPT THIS AT YOUR OWN RISK, READ THE FULL TUTORIAL BEFORE YOU START!!! I AM NOT RESPONSIBLE FOR ANY BRICKED...
forum.xda-developers.com
..
I have a Lg k41s
with root with and bootloader unlocked, in
android 9, I could get into the recovery stock,
aply update-from adb, but what the adb said; drive does not load into the directory.
but on android 10 all the stars disappeared, and the powers of heaven were shaken ,, the recovery disappeared does not enter, if you can give me a light, as I enter the fastboot, please
Hello everyone,
I believe that by now the phone is completely bricked but I would like to try to recover it in some way.
my Sony XZ Kagura it doesn't work anymore, it looks bricked. It has the original firmware on at the moment (the bootloader is unlocked).
it does not go into fastboot, nor recovery, nor adb, and when I attach it to the charger not even the led lights up.
Emma just doesn't see him.
Flashtool sees it but with debugging off
Windows sees the device as QUSB__BULK, but today in a test it saw it as a SOMC flash device.
In this way I was able to use the S1 Tool program by connecting the "test points" on the motherboard, to attempt a recovery in EDL mode, but S1 Tool after recognizing the device stops in the procedure saying "not supported".
for knowledge before it finally freezes days ago, the blue notification LED flashed a few times and then nothing.
has anyone had this problem? thanks to who will answer.
Manu21Blackjack said:
Hello everyone,
I believe that by now the phone is completely bricked but I would like to try to recover it in some way.
my Sony XZ Kagura it doesn't work anymore, it looks bricked. It has the original firmware on at the moment (the bootloader is unlocked).
it does not go into fastboot, nor recovery, nor adb, and when I attach it to the charger not even the led lights up.
Emma just doesn't see him.
Flashtool sees it but with debugging off
Windows sees the device as QUSB__BULK, but today in a test it saw it as a SOMC flash device.
In this way I was able to use the S1 Tool program by connecting the "test points" on the motherboard, to attempt a recovery in EDL mode, but S1 Tool after recognizing the device stops in the procedure saying "not supported".
for knowledge before it finally freezes days ago, the blue notification LED flashed a few times and then nothing.
has anyone had this problem? thanks to who will answer.
Click to expand...
Click to collapse
Same situation here have u fixed?
no unfortunately other people told me that S1Tool cannot recognize the chip, I tried with the qualcomm software (QPST tool) but I am missing files necessary for the recovery and I do not know how to find them, by now I have given up
Droneship said:
Same situation here have u fixed?
Click to expand...
Click to collapse
did you manage to fix it? How is it going?
Manu21Blackjack said:
did you manage to fix it? How is it going?
Click to expand...
Click to collapse
Nope there is no edl tool for Xperia devices till now except z1
Manu21Blackjack said:
did you manage to fix it? How is it going?
Click to expand...
Click to collapse
I'm trying to unbrick a Z3 and found this thread
Modifying https://github.com/bkerler/edl edlclient/Config/usb_ids.py and adding
Code:
default_ids = [
[0x0fce, 0x9dde, -1],
....
default_diag_vid_pid = [
[0x0fce, 0x9dde -1], # SONY EDL
...
(and Drivers/51-edl.rules)
I get almost a result using:
Code:
./edl printgpt --loader=/media/thread/500gb-qc/brick/edl/Loaders/sony/007530e100010001_25b44831ab8f8396_fhprg.bin
Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022.
main - Using loader Loaders/qualcomm/factory/msm8974AC/006b10e100310000_cc3153a80293939b_fhprg.bin ...
main - Waiting for the device
main - Device detected :)
sahara - Protocol version: 2, Version supported: 1
main - Mode detected: sahara
sahara -
------------------------
HWID: 0x007b40e100010004 (MSM_ID:0x007b40e1,OEM_ID:0x0001,MODEL_ID:0x0004)
CPU detected: "MSM8974AB"
PK_HASH: 0xfffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Serial: 0xffffffff
sahara - Protocol version: 2, Version supported: 1
sahara - Uploading loader Loaders/qualcomm/factory/msm8974AC/006b10e100310000_cc3153a80293939b_fhprg.bin ...
sahara - 32-Bit mode detected.
sahara - Firehose mode detected, uploading...
sahara
sahara - [LIB]: Error: Cannot receive specified number of program headers
Connection detected, quiting.
But clearly there is something i haven't quite read up on yet. EDIT: LIKE USING THE WRONG LOADER and note ( edl/Loaders/qualcomm/factory/msm8974ab/ ) I've been working on extracting the slb etc from the firmware, i accidentally flashed something wrong a late night.
so there is edl and qdl
GitHub - andersson/qdl
Contribute to andersson/qdl development by creating an account on GitHub.
github.com
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
threader said:
I'm trying to unbrick a Z3 and found this thread
Modifying https://github.com/bkerler/edl edlclient/Config/usb_ids.py and adding
Code:
default_ids = [
[0x0fce, 0x9dde, -1],
....
default_diag_vid_pid = [
[0x0fce, 0x9dde -1], # SONY EDL
...
(and Drivers/51-edl.rules)
I get almost a result using:
Code:
./edl printgpt --loader=/media/thread/500gb-qc/brick/edl/Loaders/sony/007530e100010001_25b44831ab8f8396_fhprg.bin
Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022.
main - Using loader Loaders/qualcomm/factory/msm8974AC/006b10e100310000_cc3153a80293939b_fhprg.bin ...
main - Waiting for the device
main - Device detected :)
sahara - Protocol version: 2, Version supported: 1
main - Mode detected: sahara
sahara -
------------------------
HWID: 0x007b40e100010004 (MSM_ID:0x007b40e1,OEM_ID:0x0001,MODEL_ID:0x0004)
CPU detected: "MSM8974AB"
PK_HASH: 0xfffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Serial: 0xffffffff
sahara - Protocol version: 2, Version supported: 1
sahara - Uploading loader Loaders/qualcomm/factory/msm8974AC/006b10e100310000_cc3153a80293939b_fhprg.bin ...
sahara - 32-Bit mode detected.
sahara - Firehose mode detected, uploading...
sahara
sahara - [LIB]: Error: Cannot receive specified number of program headers
Connection detected, quiting.
But clearly there is something i haven't quite read up on yet. EDIT: LIKE USING THE WRONG LOADER and note ( edl/Loaders/qualcomm/factory/msm8974ab/ ) I've been working on extracting the slb etc from the firmware, i accidentally flashed something wrong a late night.
so there is edl and qdl
GitHub - andersson/qdl
Contribute to andersson/qdl development by creating an account on GitHub.
github.com
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Click to expand...
Click to collapse
A different loader for same CPU still can be used, Sony is prevent me and you load that loader with Secure Boot and Sony sake authencation
Manu21Blackjack said:
Hello everyone,
I believe that by now the phone is completely bricked but I would like to try to recover it in some way.
my Sony XZ Kagura it doesn't work anymore, it looks bricked. It has the original firmware on at the moment (the bootloader is unlocked).
it does not go into fastboot, nor recovery, nor adb, and when I attach it to the charger not even the led lights up.
Emma just doesn't see him.
Flashtool sees it but with debugging off
Windows sees the device as QUSB__BULK, but today in a test it saw it as a SOMC flash device.
In this way I was able to use the S1 Tool program by connecting the "test points" on the motherboard, to attempt a recovery in EDL mode, but S1 Tool after recognizing the device stops in the procedure saying "not supported".
for knowledge before it finally freezes days ago, the blue notification LED flashed a few times and then nothing.
has anyone had this problem? thanks to who will answer.
Click to expand...
Click to collapse
Same as me but XZ2, there is no solution till now
Manu21Blackjack said:
Hello everyone,
I believe that by now the phone is completely bricked but I would like to try to recover it in some way.
my Sony XZ Kagura it doesn't work anymore, it looks bricked. It has the original firmware on at the moment (the bootloader is unlocked).
it does not go into fastboot, nor recovery, nor adb, and when I attach it to the charger not even the led lights up.
Emma just doesn't see him.
Flashtool sees it but with debugging off
Windows sees the device as QUSB__BULK, but today in a test it saw it as a SOMC flash device.
In this way I was able to use the S1 Tool program by connecting the "test points" on the motherboard, to attempt a recovery in EDL mode, but S1 Tool after recognizing the device stops in the procedure saying "not supported".
for knowledge before it finally freezes days ago, the blue notification LED flashed a few times and then nothing.
has anyone had this problem? thanks to who will answer.
Click to expand...
Click to collapse
I finally can unbrick my xperia xz2, its requires desolder ufs/emmc storage chip from mainboard and use jtag box to force flash working firmware directly to ufs/emmc chip then solder it back to mainboard (this is my way)
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