Related
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
try using search next time because its already been talked abput here https://forum.xda-developers.com/oneplus-6/help/relock-bootloader-t3798135
Actually, I DID read that. I didn't just roll off the cabbage truck. If you have time to post snippy replies (I also searched YOUR post history), then maybe you can point out where in that thread the answer to my question is. I could see if there was a thread where this specifically happened, or if it had been talked about over and over, but I couldn't find one. You do know this is a fairly new device, right? TBH, you're just being rude. To count on someone to hit the right search terms for a single thread where the info exists is just asinine.
1) I have not seen anyone with this situation on the OP6 yet
2) The OP5T had an unbrick tool
3) Most phones have a way to restore the OS to factory
If it can't be restored without calling OnePlus, then why not just say so? I'll answer for you, it's because you actually enjoy replying in such a manner. Grow up.
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Flapjack said:
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
Click to expand...
Click to collapse
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
[email protected] said:
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
I did, but I got the "software image does not exist" error. Does it matter whether I downloaded the 5.13 or 5.15 vesion?
mikex8593 said:
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
Click to expand...
Click to collapse
I tried several times. It throws the following error, which when searched for, always seemed to be someone forgetting to enable OEM unlocking in settings:
Code:
FAILED (remote: oem unlock is not allowed)
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Flapjack said:
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Click to expand...
Click to collapse
Hi buddy,
I tired to relock the bootloader and success in that but the phone stuck at fastboot mode, neither restarting to system nor to anything. Kindly help me if i can flash the stock rom in locked bootloader is so how.
THanks in adv
Did you try msm download tool ?
My OnePlus was bricked and it's bootloader is locked too, I have tried most of the steps like msm and those Bat files etc. But error is coming
"Remote : Flashing is not allowed in locked state"
Even tried that all in one tool that also can't unlock my bootloader
Now plz someone show me steps it will be a great help
Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.
I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.
Hello there!
My phone was bricked because I was flashing xiaomi.eu ROM in fastboot mode using cmd, and the flashing process was stopped midway.
I am able to enter into EDL mode only and only by using the test points, my phone is recognised as "Qualcomm HS-USB QDLoader 9008" as it should and also appears in MiFlash.
But when I try to flash a ROM (I tried global and Chinese) it gives me this error: "object reference is not set to an instance of the object".
I believe I have all the necessary drivers and my battery is probably long dead since the phone has been bricked for about a month now.
I read a bunch of articles describing similar problems but none of them gave a clear answer.
BlackTrade30 said:
Thank you for the quick reply!
I was guessing I needed an authorized account but MiFlash usually clearly indicated when you did. Something like "Authentication error". At least I have a solution!
Also, the thread you linked; the guy had symptoms that are exactly the same as I have. Unfortunately, he hasn't replied to me yet. According to him, he managed to get the phone unbricked using QFIL but didn't describe how. But thank you for bringing it to my attention!
Click to expand...
Click to collapse
Some old phones can be flashed without authorization but the k30 pro / poco f2 pro cannot.
Hello!
I have exactly the same problem as you (phone bricked after xiaomi.eu fastboot update) but i don't manage to enter in EDL mode even with testpoint... What did you used to do it?
Also, how much did you pay for the auth account perm?
Thanks.
Try flash it by UMT
MaximeMNT said:
Hello!
I have exactly the same problem as you (phone bricked after xiaomi.eu fastboot update) but i don't manage to enter in EDL mode even with testpoint... What did you used to do it?
Also, how much did you pay for the auth account perm?
Thanks.
Click to expand...
Click to collapse
Hello!
I manager to fix the phone!
Entering EDL mode should be possible using the test points.
Make sure your battery is disconnected.
Connect the USB to your phone but not to the PC.
Then short out the two pins.
I used tweezers to short them out.
While shorted plug in the USB the the PC. The PC then should detect the phone as a COM-PORT, you need the drivers if it says bulk device. It has to be USB 9008.
Now you need someone who can flash.
Mod edit: Paid services TG link removed.
EDL are Qcom's special access protocol. You should be able to flash via Qfil or Qpst suite, not Mi tool.
MA7MOD_GSM said:
Try flash it by UMT
Click to expand...
Click to collapse
UMT is free tool ???
NOSS8 said:
Some old phones can be flashed without authorization but the k30 pro / poco f2 pro cannot.
Click to expand...
Click to collapse
Respected sir,
Soft bricked locked bootloader Redmi 4 has same error in edl mode. Initially it was successfully flashed in edl with miflash few days ago to global fastboot rom Santoni_10.3NAMMIXM. It was working properly. Then It was showing latest update available 11.0.2NAMMIXM in setting, I downloaded and rebooted then after sometime It redirected 'mi recovery 3.0' instead of restarting the mobile automatically. Then i choosen to 'reboot to system' by volume buttons. Then it stucked on mi logo. Now i can't enter in "mi recovery 3.0". But by volume buttons i can fastboot, and In edl by shorting test points. Both are detecting device in miflash tool.
Fastboot mode flashing gives me "critical partition error"
EDL mode gives "object reference not set as an object" error in miflash tool this time.
Dear sir any suggestion or resolve for that.please help.
Thank you sir
chandan shah said:
Respected sir,
Soft bricked locked bootloader Redmi 4 has same error in edl mode. Initially it was successfully flashed in edl with miflash few days ago to global fastboot rom Santoni_10.3NAMMIXM. It was working properly. Then It was showing latest update available 11.0.2NAMMIXM in setting, I downloaded and rebooted then after sometime It redirected 'mi recovery 3.0' instead of restarting the mobile automatically. Then i choosen to 'reboot to system' by volume buttons. Then it stucked on mi logo. Now i can't enter in "mi recovery 3.0". But by volume buttons i can fastboot, and In edl by shorting test points. Both are detecting device in miflash tool.
Fastboot mode flashing gives me "critical partition error"
EDL mode gives "object reference not set as an object" error in miflash tool this time.
Dear sir any suggestion or resolve for that.please help.
Thank you sir
Click to expand...
Click to collapse
Hello,
Voila, a perfectly detailed and unequivocal post as we would like to see more often.
Have you tried re-flashing 10.3NAMMIXM?
Send me the Miflash log (starting with Miflash "version") in private messages.
NOSS8 said:
Hello,
Voila, a perfectly detailed and unequivocal post as we would like to see more often.
Have you tried re-flashing 10.3NAMMIXM?
Send me the Miflash log (starting with Miflash "version") in private messages.
Click to expand...
Click to collapse
Yes sir.
I have tried to refresh again in edl mode for SANTONI_10.3NAMMIXM but gives same error all the time.
Most surprising thing is that just 7 days ago i had been successfully flashed 10.3nammixm
But on the same version miflash tool, same computer, same rom file, this time it gives error: "object reference not set as an object"
Mi flash tool : miflash20220218
I sent you log on private conversation please check.
Thank you for quick response sir.
NOSS8 said:
Hello,
Voila, a perfectly detailed and unequivocal post as we would like to see more often.
Have you tried re-flashing 10.3NAMMIXM?
Send me the Miflash log (starting with Miflash "version") in private messages.
Click to expand...
Click to collapse
Thank you sir for your suggestion.
I have revived again my redmi 4 device.
Flashed an older version of rom santoni_global_images_V8.2.12.0.MAMMIEA_20170629.0000.00_6.0_global_751410291c.tgz
With miflash-20220218
Thanks again.
Hi all
I had just finished installed Lineage and twrp succesfully to setup this phone, but I then discovered that the unlocked bootleader was preventing me to install Netflix.
I then tried to re-lock it via "fastboot oem lock" which apparently worked, but the side effect was that my main system is now not booting at all.
And when I've then tried to unlocking it again, it just fails, so I'm currently closed out.
Right now I can only access fastboot mode.
Any idea if this can be saved?
thank you
It can be saved but you need to use EDL mode (Emergency Download Mode). This mode is locked by Xiaomi and you Need an authorized account to use It.
You have 2 options:
- Pay a man that have an authorized account and can flash the stock rom from EDL.
- Go to an authorized Xiaomi center.
Thank you. Luckily that was not the right answer.
I've managed to put the phone in EDL mode via hardware, after opening it up.
After bypassing also the lack of helo message error, I've finally manage to flash with Xiaomi Flash tool and regained access to it.
Hello everybody,
i'm not new in custom roms, but i have a problem, i can't solve by myself:
I flashed an unlocked Mi5 to linageos 19.1 without problems.
I had the bad idea to relock the bootloader due to security reasons (fastboot oem lock).
Now the device is not booting anymore, i can just see the Mi-Logo flashing very shortly.
I can access fastboot, but can't boot into recovery.
I tried to unlock the device again, but the Mi Unlocker fails and prompts me to go to the developer options in Miui, which is clearly impossible.
Any chance to proceed from fastboot (fastboot oem unlock does not work...) ?
Thanks, Jan
congrats, you succesfully hard bricked your phone. please take it for a walk to the xiaomi service and pay for gettting it fixed. who told you it is a good idea to relock the bootloader with a custom rom installed ?
Fytdyh said:
congrats, you succesfully hard bricked your phone. please take it for a walk to the xiaomi service and pay for gettting it fixed. who told you it is a good idea to relock the bootloader with a custom rom installed ?
Click to expand...
Click to collapse
actually, i remember some banking apps complained about the locked bootloader. I thought i can lock/unlock it in fastboot mode, but looks like i was wrong.
I will give the MiFlash Tool a chance, but i have not much hope...
@Fytdyh: do you think, Xiaomi Service can fix it ?
jever2k said:
actually, i remember some banking apps complained about the locked bootloader. I thought i can lock/unlock it in fastboot mode, but looks like i was wrong.
I will give the MiFlash Tool a chance, but i have not much hope...
@Fytdyh: do you think, Xiaomi Service can fix it ?
Click to expand...
Click to collapse
Make sure if your bootloader is really locked or not using fastboot command
fastboot oem device-info
OR,
fastboot getvar unlocked
If it's not locked, you can simply flash your stock rom using flash tool available for mi. Before downloading a rom from internet, take note of your device info using fastboot command ,
fastboot getvar all
And if bootloader is really locked, you have to flash stock rom from EDL mode. You may have to remove back cover to turn on EDL mode. Your device has snapdragon chipset (Plus point). Watch tutorials about xiaomi edl rom flash - snapdragon. You can go to service centre. If they tell you that you have to replace motherboard, don't be agree. Tell them to flash rom using EDL mode.
Tawsif999 said:
Make sure if your bootloader is really locked or not using fastboot command
fastboot oem device-info
OR,
fastboot getvar unlocked
If it's not locked, you can simply flash your stock rom using flash tool available for mi. Before downloading a rom from internet, take note of your device info using fastboot command ,
fastboot getvar all
And if bootloader is really locked, you have to flash stock rom from EDL mode. You may have to remove back cover to turn on EDL mode. Your device has snapdragon chipset (Plus point). Watch tutorials about xiaomi edl rom flash - snapdragon. You can go to service centre. If they tell you that you have to replace motherboard, don't be agree. Tell them to flash rom using EDL mode.
Click to expand...
Click to collapse
looks like i am getting closer... located the two EDL points to short during PC connection, installed the Qualcomm serial driver. For a second i see the device appearing as COM6 but then it disappears again and is not availiable anymore.
Any hints ?
Thanks again, Jan
jever2k said:
looks like i am getting closer... located the two EDL points to short during PC connection, installed the Qualcomm serial driver. For a second i see the device appearing as COM6 but then it disappears again and is not availiable anymore.
Any hints ?
Thanks again, Jan
Click to expand...
Click to collapse
Try this to solve the issue.
If it doesn’t help, read this to boot properly into edl
jever2k said:
Hello everybody,
i'm not new in custom roms, but i have a problem, i can't solve by myself:
I flashed an unlocked Mi5 to linageos 19.1 without problems.
I had the bad idea to relock the bootloader due to security reasons (fastboot oem lock).
Now the device is not booting anymore, i can just see the Mi-Logo flashing very shortly.
I can access fastboot, but can't boot into recovery.
I tried to unlock the device again, but the Mi Unlocker fails and prompts me to go to the developer options in Miui, which is clearly impossible.
Any chance to proceed from fastboot (fastboot oem unlock does not work...) ?
Thanks, Jan
Click to expand...
Click to collapse
Flash stock recovery for your device via fastboot, then you should be able to boot into recovery or flash a stock system.img or your full stock firmware for your device, then unlock the bootloader(fastboot oem unlock) then flash TWRP and LineageOS again.
Droidriven said:
Flash stock recovery for your device via fastboot, then you should be able to boot into recovery or flash a stock system.img or your full stock firmware for your device, then unlock the bootloader(fastboot oem unlock) then flash TWRP and LineageOS again.
Click to expand...
Click to collapse
But he mentioned, bootloader fails to unlock. Actually it's hard brick(Even though he can boot into fastboot,the bootloader is locked. So nothing to do with fastboot).Without unlocked bootloader, flashing something from fastboot will hard brick his device completely (Will not be able to boot into fastboot). Or flashing will be denied
Tawsif999 said:
Try this to solve the issue.
If it doesn’t help, read this to boot properly into edl
Click to expand...
Click to collapse
OK, next level reached. The phone is connected to the com-port and the correct driver is displayed.
The whole procedure is a bit unstable, i need to connect the phone several times, to get a stable EDL mode.
The Xiaomi Flasher recognizes the phone, but flashing does not succeed. Sometimes it's not able to receive a kind of Hello message, sometimes it displays "object reference not set to an instance of an object".
I also downloaded the QPST flasher, but have no plan, how to use it.
I'll keep on trying!
Thanks to all, who helped me to reach this point!
jever2k said:
OK, next level reached. The phone is connected to the com-port and the correct driver is displayed.
The whole prcedure is a bit unstable, i need to connect the phone several times, to get a stable EDL mode.
The Xiaomi Flasher recognizes the phone, but flashing does not succeed. Sometimes it's not able to receive a kind of Hello message, sometimes it displays "object reference not set to an instance of an object".
I also downloaded the QPST flasher, but have no plan, how to use it.
I'll keep on trying!
Thanks to all, who helped me to reach this point!
Click to expand...
Click to collapse
I found something new by watching this video. Maybe you don't understand hindi(India is our relative country, so I do).
Lemme explain,
This guy's xiaomi k20 pro phone hard bricked with a locked bootloader. He tried a lot to repair it(by deep flash or something idk). But everything failed. At last he came to this step of EDL mode. But xiaomi Edl mode flash requires an "AUTHORIZED MI ACCOUNT" . Xiaomi people pay to get authorized account license that normal users don't have. So the guy contacted with them on a telegram page called "Mod Edit: Name Removed" . They told him that they will repair his phone via teamviewer. All he had to do is pay some $ & connect phone in edl mode. Rest of the things were done by them. And his phone repaired successfully! (Watch the video from 4:00)
So In his video, he is telling to go to that page & contact with "Mod Edit: Name Removed" there. They take 20-25$ (depends on device). If you tell them you're from Mod Edit: Name Removed's video, they will give some discount
Tawsif999 said:
But he mentioned, bootloader fails to unlock. Actually it's hard brick(Even though he can boot into fastboot,the bootloader is locked. So nothing to do with fastboot).Without unlocked bootloader, flashing psomething from fastboot will hard brick his device completely (Will not be able to boot into fastboot). Or flashing will be denied
Click to expand...
Click to collapse
Yeah, I jumped the gun and posted before seeing all the replies in the thread describing their whole scenario, should've known better.
They obviously need a hardware approach, i.e. JTAG/RIFF/Octoplus or replace motherboard.
Tawsif999 said:
I found something new by watching this video. Maybe you don't understand hindi(India is our relative country, so I do).
Lemme explain,
This guy's xiaomi k20 pro phone hard bricked with a locked bootloader. He tried a lot to repair it(by deep flash or something idk). But everything failed. At last he came to this step of EDL mode. But xiaomi Edl mode flash requires an "AUTHORIZED MI ACCOUNT" . Xiaomi people pay to get authorized account license that normal users don't have. So the guy contacted with them on a telegram page called "Mod Edit: Name Removed" . They told him that they will repair his phone via teamviewer. All he had to do is pay some $ & connect phone in edl mode. Rest of the things were done by them. And his phone repaired successfully! (Watch the video from 4:00)
So In his video, he is telling to go to that page & contact with "Mod Edit: Name Removed" there. They take 20-25$ (depends on device). If you tell them you're from Mod Edit: Name Removed's video, they will give some discount
Click to expand...
Click to collapse
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
jever2k said:
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
Click to expand...
Click to collapse
jever2k said:
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
Click to expand...
Click to collapse
That's expensive. Anyway, it will be better if you don’t waste time on this. Just go for 3rd party help(From that official telegram channel or service centre). That will cost less
Tawsif999 said:
That's expensive. Anyway, it will be better if you don’t waste time on this. Just go for 3rd party help(From that official telegram channel or service centre). That will cost less
Click to expand...
Click to collapse
Thanks Tawsif for the good hints and links.
I don't really depend on the phone, so i will keep trying.
It's not wasted time, it's mainly learning new stuff and improving skills.
I believe, i'm not too far away and if it works, it's the best satisfaction.
If not, i bricked an old Mi 5.
All the best,
Jan