Related
Can anyone help me with the firehose and XML files for a Samsung A71 ?
I have hard bricked it and i can only acces it through EDL.
Thank you.
SanduBalon said:
Can anyone help me with the firehose and XML files for a Samsung A71 ?
I have hard bricked it and i can only acces it through EDL.
Thank you.
Click to expand...
Click to collapse
Here is what I found:
Once your Qualcomm Android device has entered EDL mode, you can connect it to the PC and use tools like QPST or QFIL to flash firmware files to unbrick or restore stock ROM.
QPST:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
And:
Unbricking and QPST - All Snapdragon / Qualcomm devices
Hello All, First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive: The link to QPST...
forum.xda-developers.com
QFIL:
How To Flash Qualcomm Mobile Device Using QFIL Flashing Tool – StockRomFlash
www.stockromflash.com
But I do not have the files you asked for. Sorry.
Please could somebody get us the firehose // .mbn file
SanduBalon said:
Can anyone help me with the firehose and XML files for a Samsung A71 ?
I have hard bricked it and i can only acces it through EDL.
Thank you.
Click to expand...
Click to collapse
i have a same probleme ,have you find a solution plz
has anyone here found any solution?
HERE
Hi friends, I currently have the version V405UA020f 00 USC US OP 0310 installed, and I need to go back to some version of ATT since I need it to ask me for the unlock network code. I have downloaded the backup of the user @AsItLies but I don't know how to restore it from QFIL, can someone guide me? I have tried loading only the .xml file but when pressing Download I immediately get an error.
romanrsr said:
Hi friends, I currently have the version V405UA020f 00 USC US OP 0310 installed, and I need to go back to some version of ATT since I need it to ask me for the unlock network code. I have downloaded the backup of the user @AsItLies but I don't know how to restore it from QFIL, can someone guide me? I have tried loading only the .xml file but when pressing Download I immediately get an error.
Click to expand...
Click to collapse
I've not had much luck getting qfil to load a backup, but you could post a screenshot of what you have before it doesn't work, someone may be able to help.
2 ways that will definitely work; 1) do ea partition one at a time (yes, it's time consuming) 2) use bkerler edl utilities (these are python based and it's a command line interface).
So now you know of course, but for anyone else, crossflashing does not unlock the sim. If it's locked, stay on oem firmware until you get it unlocked. Or else u face the prob romanrsr is facing now.
cheers
AsItLies said:
I've not had much luck getting qfil to load a backup, but you could post a screenshot of what you have before it doesn't work, someone may be able to help.
2 ways that will definitely work; 1) do ea partition one at a time (yes, it's time consuming) 2) use bkerler edl utilities (these are python based and it's a command line interface).
So now you know of course, but for anyone else, crossflashing does not unlock the sim. If it's locked, stay on oem firmware until you get it unlocked. Or else u face the prob romanrsr is facing now.
cheers
Click to expand...
Click to collapse
Hi AsItLies, Thank you very much for sharing your knowledge!
I have been able to flash partition 0 with QFIL, there were no errors but now the phone does not turn on at all. I have put it to charge for more than an hour but it shows no signs of life. It is also not detected by the PC when I connect it. Do you know how I can solve it? Thanks again!
romanrsr said:
Hi AsItLies, Thank you very much for sharing your knowledge!
I have been able to flash partition 0 with QFIL, there were no errors but now the phone does not turn on at all. I have put it to charge for more than an hour but it shows no signs of life. It is also not detected by the PC when I connect it. Do you know how I can solve it? Thanks again!
Click to expand...
Click to collapse
I can only guess, as that isn't usual. It may well still be in edl mode. To get out of edl, hold vol minuse and pwr button for at least 5 sec. And also, leaving it in edl mode, it will 'time out', but it doesn't auto boot by itself.
iirc, when flashing the 'luns' in qfil, after ea one it will reboot and u have to go back to edl mode again.
when you say you 'flash partition 0 with QFIL', is that with the xml? or you did all of slot A by hand (one by one)?
cheers
AsItLies said:
I can only guess, as that isn't usual. It may well still be in edl mode. To get out of edl, hold vol minuse and pwr button for at least 5 sec. And also, leaving it in edl mode, it will 'time out', but it doesn't auto boot by itself.
iirc, when flashing the 'luns' in qfil, after ea one it will reboot and u have to go back to edl mode again.
when you say you 'flash partition 0 with QFIL', is that with the xml? or you did all of slot A by hand (one by one)?
cheers
Click to expand...
Click to collapse
I do not think it is in EDL mode, since when I connect it to the PC it does not detect any port, and in the device manager it does not detect it either. I've already tried hold vol minuse and pwr button for several seconds, but nothing happens. Screen always black.
I have flashed from QFIL with the xml.
romanrsr said:
I do not think it is in EDL mode, since when I connect it to the PC it does not detect any port, and in the device manager it does not detect it either. I've already tried hold vol minuse and pwr button for several seconds, but nothing happens. Screen always black.
I have flashed from QFIL with the xml.
Click to expand...
Click to collapse
pretty sure that if edl mode 'times out' (because it hasn't been used or accessed), then it's not going to show up in device manager.
yes the flashing with qfil and the xml will need to go out of edl mode and back in for ea lun. Flashing the 0 lun alone isn't going to fix anything, have to do them all.
Your only option here is to keep trying. There's no magical 'press this button' to fix this. If you try and can't get it out of edl mode, try going back in edl mode. The device will go into edl mode from any screen, but in some cases you won't get any kind of a 'count down', you just have to count or maybe the screen will change, then spam vol up.
good luck
AsItLies said:
pretty sure that if edl mode 'times out' (because it hasn't been used or accessed), then it's not going to show up in device manager.
yes the flashing with qfil and the xml will need to go out of edl mode and back in for ea lun. Flashing the 0 lun alone isn't going to fix anything, have to do them all.
Your only option here is to keep trying. There's no magical 'press this button' to fix this. If you try and can't get it out of edl mode, try going back in edl mode. The device will go into edl mode from any screen, but in some cases you won't get any kind of a 'count down', you just have to count or maybe the screen will change, then spam vol up.
good luck
Click to expand...
Click to collapse
You were correct! I Press the volume down + power keys, and then pressing the up key several times the QFIL detected it again. I have already flashed your backup and boot OK.
Now I have the following problem, when I insert another SIM it does not appear to enter the unlock code, but I get the error "This phone is permanently locked and can not be unlocked", did you have any experience with this?
It occurred to me to try to update it to the latest version via FOTA and LG Software, but it tells me that the latest version is already installed. Can you think of something? Thanks!
Unfortunately I've no experience there at all, always buy phones that are unlocked, have never had a carrier locked phone.
check with at&t, if the device is eligible to be unlocked, I think they are obligated by law to help.
cheers
AsItLies said:
Unfortunately I've no experience there at all, always buy phones that are unlocked, have never had a carrier locked phone.
check with at&t, if the device is eligible to be unlocked, I think they are obligated by law to help.
cheers
Click to expand...
Click to collapse
Many Thanks AsItLies, I ask you one last question. I have found some files in the forum (AT&T Android 10 (30b) .bin files), but they don't have the .xml files. Do you know how I can flash these files with QFILL or how to generate the .xml?
romanrsr said:
Many Thanks AsItLies, I ask you one last question. I have found some files in the forum (AT&T Android 10 (30b) .bin files), but they don't have the .xml files. Do you know how I can flash these files with QFILL or how to generate the .xml?
Click to expand...
Click to collapse
Which files exactly are you referring to? There are some files because of IMEI and serial number that you should not flash.
AsItLies said:
Which files exactly are you referring to? There are some files because of IMEI and serial number that you should not flash.
Click to expand...
Click to collapse
Check this:
File folder on MEGA
mega.nz
File folder on MEGA
mega.nz
File folder on MEGA
mega.nz
romanrsr said:
Check this:
File folder on MEGA
mega.nz
Click to expand...
Click to collapse
Use this xml. I created it to flash Q all at once, there aren't 0-6 luns, as the names are unique and not needed.
But just as a warning, it should work, I've used it, but it's only been tested on my device, which was originally at&t. And, I'd point out, doing this isn't going to unlock the sim.
cheers
The 3/2022 update from F(x)tec says it will be mere weeks to delivery, still nothing here!
Moderators emailed me after my last rant in another section - to you, I cannot reply from that email because the service only receives.
If there really is no activity on this device, at least periodically update the forum with a sticky with a dated status. Sure, I'm probably the only one who comes back in hopes of seeing some activity, but in case there are others, it is the least you can do. If the device is dead before arrival, say so!
When (if) this arrives, I plan to explore the different ROMS. F(x)Tec promised there would be at least three available: Ubuntu Touch, LineageOS, and Stock. I chose Ubuntu Touch, but I want to (safely) switch ROMS. While I am a developer, I have zero experience with Android development, so I can't whip it up myself. I need instructions, options, etc.
Will there be a TWRP or equivalent recovery? Can I back-up and restore the system without messing directly with ADB and fastboot? Does the Lineage team have any progress reports on porting to this device? Do they have one to work on? Will Stock be Android 12L? What other teams are creating or porting ROMS to this device? Will there be continued attention and updates for a few years? Will GSI ROMS work on this? Which variety?
Once again, I took this chance based on my perceived reputation of XDA. This is your phone, designed for geeks like me. Show me I am not playing a fool.
If it makes you feel better, upon arrival, I plan on porting as many of the different Android flavours as I can over to the Pro1X, along with sources. This includes TWRP.
My tracking number says it's currently in Alaska.
I just got mine and already broke it lul.
My fault for not taking a full backup image before messing with it.
@snortphome its not easily possible to brick this device.
Did you do the full recovery reflash using the provided EDL images?
Pro1X - Stock Android OS (Build Number: v2.1.2_20220707)
NEW Version of guide here Below the original text:(above inserted by EskeRahn) If youre reading this, it seems like you miss the good old Android OS or youve accidentally fried your PrawnX already! Dont worry! We have your back. The link below is the full build of the Pro1X stock Android OS (v2.1...
community.fxtec.com
To flash using EDL and Linux:
Install EDL-Tool by berkele
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
Put Pro¹ X in EDL mode using `adb reboot edl` when you got adb available. Else
Pro¹-X needs to be put in EDL mode manually. Hold power and vol + and vol - During boot and release all after android logo flashes up shortly and goes into a dark screen second. If it stays dark after you removed the combo, Prawn is in EDL mode.
If it is booting or showing fastboot, redo. I needed 5 tries first.
Check if the usb connected Pro¹ X is in EDL mode using lsusb, it should show:
`Bus 003 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)`
Then become root or do the following with sudo each:
```
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram_unsparse0.xml patch0.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram1.xml patch1.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram2.xml patch2.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram3.xml patch3.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram4.xml patch4.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram5.xml patch5.xml .
```
If any of the commands get stuck, redo the finger combo and enter EDL again.
I did not need to do that since all went well with original cable and Pro¹ X not touched during flash.
reboot prawn with
`edl --loader=prog_firehose_ddr.elf reset reboot`
F(x)tec will release flashing instruction using Qulcomms QFIL software on windows soon.
Above method is what testers used to install new firmware versions while no OTA mechanism was available.
eltmosen said:
@snortphome its not easily possible to brick this device.
Did you do the full recovery reflash using the provided EDL images?
Pro1X - Stock Android OS (Build Number: v2.1.2_20220707)
NEW Version of guide here Below the original text:(above inserted by EskeRahn) If youre reading this, it seems like you miss the good old Android OS or youve accidentally fried your PrawnX already! Dont worry! We have your back. The link below is the full build of the Pro1X stock Android OS (v2.1...
community.fxtec.com
To flash using EDL and Linux:
Install EDL-Tool by berkele
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
Put Pro¹ X in EDL mode using `adb reboot edl` when you got adb available. Else
Pro¹-X needs to be put in EDL mode manually. Hold power and vol + and vol - During boot and release all after android logo flashes up shortly and goes into a dark screen second. If it stays dark after you removed the combo, Prawn is in EDL mode.
If it is booting or showing fastboot, redo. I needed 5 tries first.
Check if the usb connected Pro¹ X is in EDL mode using lsusb, it should show:
`Bus 003 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)`
Then become root or do the following with sudo each:
```
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram_unsparse0.xml patch0.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram1.xml patch1.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram2.xml patch2.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram3.xml patch3.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram4.xml patch4.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram5.xml patch5.xml .
```
If any of the commands get stuck, redo the finger combo and enter EDL again.
I did not need to do that since all went well with original cable and Pro¹ X not touched during flash.
reboot prawn with
`edl --loader=prog_firehose_ddr.elf reset reboot`
F(x)tec will release flashing instruction using Qulcomms QFIL software on windows soon.
Above method is what testers used to install new firmware versions while no OTA mechanism was available.
Click to expand...
Click to collapse
Hi, thank you very much for your thorough instructions!
I'm sure they will be very helpful to both me when I mess something up more in the future and to others! I was not aware that EDL mode was existant, I was solely using fastboot.
As for me, it wasn't fully bricked, I still had the stock recovery (boot_a and boot_b were flashed over), and after a bit of hunting around, I found a google drive link (on the thread you linked, actually!) for the stock android on the fxtec community forums, as well as links to Ubuntu touch and SailfishOS builds which I was able to flash and achieve a usable operating environment.
I'm now having quite a lot of fun with this phone!
I got mine in my hands now. It already comes bootloader unlocked.
blackknightavalon said:
I got mine in my hands now. It already comes bootloader unlocked.
Click to expand...
Click to collapse
Have fun! And backup your persist partition to not loose the attestation keys by chance.
eltmosen said:
Have fun! And backup your persist partition to not loose the attestation keys by chance.
Click to expand...
Click to collapse
I've lost count of how many soft bricks I've had to fix on OnePlus devices alone. As long as I can back up my internal storage I'll be just fine.
abtekk said:
If it makes you feel better, upon arrival, I plan on porting as many of the different Android flavours as I can over to the Pro1X, along with sources. This includes TWRP.
Click to expand...
Click to collapse
It does. I'm hoping I like the phone and it lasts for years. I don't expect to replace my Pixel 6, and I want to see what all these other os's do.
Hello everyone!
I hope this is seen, because I need your help, well, days ago I wanted to install the pixel experience rom, everything was going well, but when it was installed, I had problems with wifi, and only worked with mobile data (it should be noted that it was Android 13 and my version is merlin). Well, then I decided to change it and return it to stock rom but it has been a tragedy since then. First, I think that being mediatek, the device does not allow to be flashed with mitool, I've tried everything, install twrp but did not serve and now does not let me enter fastboot, what do you recommend? It could be solved (by myself or a technician), or better I give it as dead? I hope your prompt response
estebg_1300 said:
Hello everyone!
I hope this is seen, because I need your help, well, days ago I wanted to install the pixel experience rom, everything was going well, but when it was installed, I had problems with wifi, and only worked with mobile data (it should be noted that it was Android 13 and my version is merlin). Well, then I decided to change it and return it to stock rom but it has been a tragedy since then. First, I think that being mediatek, the device does not allow to be flashed with mitool, I've tried everything, install twrp but did not serve and now does not let me enter fastboot, what do you recommend? It could be solved (by myself or a technician), or better I give it as dead? I hope your prompt response
Click to expand...
Click to collapse
Miflash works with Qualcomm and Media Tek but for the latter it is better to use
https://xiaomitools.com/sp-flash-tool-en/
The problem is that the phone must be in Fastboot mode.
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/merlin/
TWRP/O.F A11 et A12
Have you tried with the TWRP of:
Wipe/format data type yes
reboot TWRP
flash a recovery rom
bro, try this one, though it was for redmi 6A.
I think the method there could be tried on other xiaomi phones.
goodluck!
Fix HardBrick Redmi 6A (no recovery and no fastboot, only black screen)Fix without need Authotization stuff
----------------------------------------------------------------------- Finally I could fix my redmi 6A after suffering hardbrick. I couldnot enter to recovery neither to fastboot mode. My redmi 6A just give me a black screen with vibration on...
forum.xda-developers.com
Tajil said:
bro, try this one, though it was for redmi 6A.
I think the method there could be tried on other xiaomi phones.
goodluck!
Fix HardBrick Redmi 6A (no recovery and no fastboot, only black screen)Fix without need Authotization stuff
----------------------------------------------------------------------- Finally I could fix my redmi 6A after suffering hardbrick. I couldnot enter to recovery neither to fastboot mode. My redmi 6A just give me a black screen with vibration on...
forum.xda-developers.com
Click to expand...
Click to collapse
Bro, do you know what to put in download agent, scatter loading file and authenticator file?, it gives me an error
NOSS8 said:
Miflash works with Qualcomm and Media Tek but for the latter it is better to use
https://xiaomitools.com/sp-flash-tool-en/
The problem is that the phone must be in Fastboot mode.
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/merlin/
TWRP/O.F A11 et A12
Have you tried with the TWRP of:
Wipe/format data type yes
reboot TWRP
flash a recovery rom
Click to expand...
Click to collapse
And how I can flash the recovery rom if my phone doesnt power on, and xiaomi mi tool doesnt recognize too my phone? I cant enter in fastboot and recovery mode, help me please
estebg_1300 said:
And how I can flash the recovery rom if my phone doesnt power on, and xiaomi mi tool doesnt recognize too my phone? I cant enter in fastboot and recovery mode, help me please
Click to expand...
Click to collapse
In the 1st post you say you have installed the TWRP.
See here
https://forum.xda-developers.com/t/recover-from-hard-brick-no-fastboot-or-recovery.4469431/
https://forum.xda-developers.com/t/...otloop-hard-brick-softbrick-solution.4460191/
https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/
NOSS8 said:
En la primera publicación dices que tienes instalado el TWRP.
Mira aquí
https://forum.xda-developers.com/t/recover-from-hard-brick-no-fastboot-or-recovery.4469431/
https://forum.xda-developers.com/t/closed-evergo-100-working-poco-m4-pro-5g-redmi-note-11t-india-miui-all-mediatek-devices-bootloop-hard- ladrillo-softbrick-solution.4460191/
https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/
Click to expand...
Click to collapse
Is there a way that we can talk privately and I can explain better and you can guide me to do the procedure?
estebg_1300 said:
Is there a way that we can talk privately and I can explain better and you can guide me to do the procedure?
Click to expand...
Click to collapse
Sorry but I only have Qualcomm devices.
See with the links above or do some research.
EDIT:
You must install specific drivers to see the phone on the pc.
NOSS8 said:
Sorry but I only have Qualcomm devices.
See with the links above or do some research.
EDIT:
You must install specific drivers to see the phone on the pc.
Click to expand...
Click to collapse
how I do the last that you say?
estebg_1300 said:
how I do the last that you say?
Click to expand...
Click to collapse
I posted some links that might be useful, that's all.
I searched with:
Xiaomi mediatek hard bricked, no fastboot
For example:
https://phonesinnigeria.com/unbrick-hard-bricked-dead-mtk-android-device/
"First connect your phone to your pc, if your pc does not make the sound of usb connection, press the volume key (up or down) on your device till you hear sound on your pc, and also your phone will start vibrating but if it does not vibrate keep on pressing the volume key (up or down) as many times as possible till your phone start vibrating. Then it starts connecting and disconnecting in your pc."
NOSS8 said:
I posted some links that might be useful, that's all.
I searched with:
Xiaomi mediatek hard bricked, no fastboot
For example:
https://phonesinnigeria.com/unbrick-hard-bricked-dead-mtk-android-device/
"First connect your phone to your pc, if your pc does not make the sound of usb connection, press the volume key (up or down) on your device till you hear sound on your pc, and also your phone will start vibrating but if it does not vibrate keep on pressing the volume key (up or down) as many times as possible till your phone start vibrating. Then it starts connecting and disconnecting in your pc."
Click to expand...
Click to collapse
now I get 'the last usb device you connected did not work properly and Windows does not recognize it'.
What should I do now?
estebg_1300 said:
now I get 'the last usb device you connected did not work properly and Windows does not recognize it'.
What should I do now?
Click to expand...
Click to collapse
Maybe change the usb port or install other drivers, but as I told you above, I don't know the tools for MediaTek but it's much easier to restore them for free than the Qualcomm ones.
Do some research on the internet and take the time to fully understand.
NOSS8 said:
Maybe change the usb port or install other drivers, but as I told you above, I don't know the tools for MediaTek but it's much easier to restore them for free than the Qualcomm ones.
Do some research on the internet and take the time to fully understand.
Click to expand...
Click to collapse
and you know anyone that know about mtk and can help me? Thanks btw
estebg_1300 said:
and you know anyone that know about mtk and can help me? Thanks btw
Click to expand...
Click to collapse
See here
https://forum.xda-developers.com/f/redmi-note-9-guides-news-discussion.10961/
Maybe him
VD171
forum.xda-developers.com
download agent (DA), already filled if we use spflash. if not just browse and search inside spflash folder (there 3 to 4 DA file there).
scatter file, you get it from the stock firmware, extract the firmware, check inside the folder. you could directly browser from scatter input to the firmware folder.
auth file, just donload it from the link, extract it and in spflash-- auth file input just browse the file
exactly what I did here, u could do it bro:
Tajil said:
bro, try this one, though it was for redmi 6A.
I think the method there could be tried on other xiaomi phones.
goodluck!
Fix HardBrick Redmi 6A (no recovery and no fastboot, only black screen)Fix without need Authotization stuff
----------------------------------------------------------------------- Finally I could fix my redmi 6A after suffering hardbrick. I couldnot enter to recovery neither to fastboot mode. My redmi 6A just give me a black screen with vibration on...
forum.xda-developers.com
Click to expand...
Click to collapse
Tajil said:
download agent (DA), already filled if we use spflash. if not just browse and search inside spflash folder (there 3 to 4 DA file there).
scatter file, you get it from the stock firmware, extract the firmware, check inside the folder. you could directly browser from scatter input to the firmware folder.
auth file, just donload it from the link, extract it and in spflash-- auth file input just browse the file
Click to expand...
Click to collapse
Thanks, but read and trying translate to spanish for english, this error appears in every time that i try to put the phone in my pc
Tajil said:
exactly what I did here, u could do it bro:
Click to expand...
Click to collapse
usb device is not recognized
the last device you connected to this computer did not work and Windows does not recognize it.' is what appears in the image I sent you
estebg_1300 said:
usb device is not recognized
the last device you connected to this computer did not work and Windows does not recognize it.' is what appears in the image I sent you
Click to expand...
Click to collapse
it maybe driver issues
try installing some driver needed:
-mtk driver
-libusb-win
-xiaomi usb driver
-vcom driver
-etc ...
Tajil said:
it maybe driver issues
try installing some driver needed:
-mtk driver
-libusb-win
-xiaomi usb driver
-vcom driver
-etc ...
Click to expand...
Click to collapse
now I have this problem...
Hi everyone, days ago I posted on the forum that I had a bootloop, I could not enter fastboot or recovery, well, I managed to install the rom by sp flash tool without errors, but now I get the error "nv data is corrupted" as seen in the video that I attach, anyone know of a viable solution? What is free and do not have any other problem and my phone back to normal? Because I can enter fastboot and maybe download or twrp or download pixel experience or a rom, What do you recommend?
Here is free log in info . Not sure how long it will last ...you must hurry...lol . You have to follow what I say . First need to downloader loader v4.1.7.2 heres the link .
https://www.gaprologin.com/download
Now you need to find your file needed to unbrick .
You need Qualcomm drivers install . Open up device manger , put phone in edl mode.
Under ports you should see your phone show up " Qualcomm HS-USB QDLoader 9008 (COM?) what ever comport you in. once you have all that done ...Next open up loader v4.1.7.2 .
Here is a must do or wont work ... where it says " In Company" change to India and leave second line ASY/Changan
Now enter this info
INOPTP000669
ii53JC&x&^
000000
Loader will open , next Open OFP on loader. Find your file . Or drag and paste it. " Hit start ". Have all three buttons pushed in on phone and plug into USB . should start to flash
Have fun until it expires
You can try flashing your OP 11 ...DONT DO IT .... need different loader
Not working, it does not detect the device even with windows in test mode.
Log shows this:
2023/03/07 22:59:15][0x35a0][op_device_scan_connected_devices:436] [opdevice][95BDCFF8] [COM4] INFO: Device connection detected.
[2023/03/07 22:59:15][0x35a0][oplus_device_manager_notify:48] [opdevice][FTGUIDev] Notifing new device information to 3 listeners.
[2023/03/07 22:59:15][0x35a0][qcom_flash_agent_device_callback:4630] [FTGUIDev] Device manager is not activated. Ignore. (Device Name: Qualcomm HS-USB QDLoader 9008 (COM4))
[2023/03/07 22:59:15][0x35a0][op_device_scan_connected_devices:445] [opdevice] scan port stop
[2023/03/07 22:59:19][0x3584][WndProc:156] [opdevice] receive WM_DEVICECHANGE wParam: 7
[2023/03/07 22:59:19][0x3584][WndProc:170] [opdevice] receive WM_DEVICECHANGE lParam NULL
[2023/03/07 22:59:19][0x3584][WndProc:180] [opdevice] not DBT_DEVICEREMOVECOMPLETE, quit
[2023/03/07 22:59:19][0x3584][WndProc:156] [opdevice] receive WM_DEVICECHANGE wParam: 7
[2023/03/07 22:59:19][0x3584][WndProc:170] [opdevice] receive WM_DEVICECHANGE lParam NULL
[2023/03/07 22:59:19][0x3584][WndProc:180] [opdevice] not DBT_DEVICEREMOVECOMPLETE, quit
[2023/03/07 22:59:27][0x2fd0][OpFlashLogManager:rint:24] [UI] {
"Name": "IDC_SYSLINK_OPEN_CUR_LOG",
"Value": 10007
}
Dude it working
Canuck Knarf said:
Dude it working
Click to expand...
Click to collapse
Login works, but it doesn't detect the device.. is there any tricks ?
zopostyle said:
Login works, but it doesn't detect the device.. is there any tricks ?
Click to expand...
Click to collapse
Yeah you need the right ofp file with out that login info ...loader dont work
Canuck Knarf said:
Yeah you need the right ofp file with out that login info ...loader dont work
Click to expand...
Click to collapse
I already have. It's not detect the com3
zopostyle said:
I already have. It's not detect the com3
Click to expand...
Click to collapse
Once the loader open, lick on Open OFP find your file . another part of loader will pop up click ok ...that will load your file ...hit start ...push all three buttons and plug into USB
zopostyle said:
I already have. It's not detect the com3
Click to expand...
Click to collapse
try another port..and dose it show up in device manager under ports...? in edl mode
Same results, tried different port, different cable...
zopostyle said:
Same results, tried different port, different cable...
Click to expand...
Click to collapse
you have to hit start first...then hold all three button and plug in should bring up starting to download once edl pop up in device manager
Canuck Knarf said:
you have to hit start first...then hold all three button and plug in should bring up starting to download once edl pop up in device manager
Click to expand...
Click to collapse
Hum that did the trick. But now I get this error
zopostyle said:
Hum that did the trick. But now I get this error
Click to expand...
Click to collapse
do it again
Canuck Knarf said:
do it again
Click to expand...
Click to collapse
Same thing.
zopostyle said:
Same thing.
Click to expand...
Click to collapse
Is it hard bricked..??
Canuck Knarf said:
Is it hard bricked..??
Click to expand...
Click to collapse
Yes, I have to use the edl test point to it to enter in EDL Mode. Fastboot enhanced bricked it.
Im going to try it on my oneplus 10 pro NE2210..see if a problem with it
Canuck Knarf said:
Im going to try it on my oneplus 10 pro NE2210..see if a problem with it
Click to expand...
Click to collapse
I've also tried different ofp files, ne2210, ne2213 and ne2215 all stops at VIP.
zopostyle said:
I've also tried different ofp files, ne2210, ne2213 and ne2215 all stops at VIP.
Click to expand...
Click to collapse
OK I'm flashing mine rate now
Im going to give you another loader