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
Related
Hi all android gurus, I have a little problem to which I wonder if there is a solution or not
I was given a oneplus 3 that I can keep if I can get it to work.
The guy had installed twrp and CM14.1
and then he doesn't know how but it's stuck in fastboot mode with locked bootloader.
trying to unlock via adb say it can't be done remotely.
All commands I tried say it's "not allowed remotely"
Windows device manager say it is an "android device"
Trying to boot to recovery or os doesn't work
both these options just give lines of text saying what don't work.
What do all you experts say, is there a way out of this, or should I throw the phone away?
He already bought a new phone so I guess it's mine to either fix or trash.
meonit said:
Hi all android gurus, I have a little problem to which I wonder if there is a solution or not
I was given a oneplus 3 that I can keep if I can get it to work.
The guy had installed twrp and CM14.1
and then he doesn't know how but it's stuck in fastboot mode with locked bootloader.
trying to unlock via adb say it can't be done remotely.
All commands I tried say it's "not allowed remotely"
Windows device manager say it is an "android device"
Trying to boot to recovery or os doesn't work
both these options just give lines of text saying what don't work.
What do all you experts say, is there a way out of this, or should I throw the phone away?
He already bought a new phone so I guess it's mine to either fix or trash.
Click to expand...
Click to collapse
If its stuck in Fastboot, you can fastboot flash the stock firmware for your device.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Don't worry dude, There is always a way.
meonit said:
Hi all android gurus, I have a little problem to which I wonder if there is a solution or not
I was given a oneplus 3 that I can keep if I can get it to work.
The guy had installed twrp and CM14.1
and then he doesn't know how but it's stuck in fastboot mode with locked bootloader.
trying to unlock via adb say it can't be done remotely.
All commands I tried say it's "not allowed remotely"
Windows device manager say it is an "android device"
Trying to boot to recovery or os doesn't work
both these options just give lines of text saying what don't work.
What do all you experts say, is there a way out of this, or should I throw the phone away?
He already bought a new phone so I guess it's mine to either fix or trash.
Click to expand...
Click to collapse
Try flashing a new recovery of your choice in Fastboot mode, but for flashing it first you have to unlock your Bootloader, which you can do it with the help of an Android-SDK package for your pc.
sanjeevikrishna said:
Try flashing a new recovery of your choice in Fastboot mode, but for flashing it first you have to unlock your Bootloader, which you can do it with the help of an Android-SDK package for your pc.
Click to expand...
Click to collapse
when I try to unlock bootloader i am getting:
FAILED (remote: oem unlock is not allowed)
meonit said:
when I try to unlock bootloader i am getting:
FAILED (remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Not all bootloader can be unlocked, and the ones that can be unlocked can't all unlock via Fastboot.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
Yes,there are several unbrick tools on the forum i used this one and it worked for me!
I am not able to share links so im posting a few screew shots but if you google oneplus 7 pro unbrick you ahould find this thread easy
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
I replied to you from the xda labs app and i couldnt attach a link but it works from the browser so i apologise for my first reply hope this one is more helpfull
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3934659/amp/
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
M3DUS4 said:
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
Click to expand...
Click to collapse
this could be because the galaxy A51 wasnt built with fastboot, and the code to launch this option was just reused from a different device, or because something isnt connecting properly.
Hello, I have the same ... Android 11 (and currently 12) (from Frija). So it is not the fault of incorrect configuration or with connecting. Only something is wrong with this phone ...
I have this device and this solved it for me:
Enable OEM unlocking in developer settings
Shut down the phone
Hold volume up and volume down
Plug in a USB cable connected to a computer (the computer being turned on)
Keep holding
You're in download mode!
Side note: This might not work in USA or Canada, I am from europe and it works here. I have no idea if it works in another region. Also, you can't just flash a recovery.img on Samsung since there is no real "fastboot", you have to use download mode and Odin.
But I know how to enter download mode... Problem is Fastboot mode...
There is no fastboot mode on a modern Samsung device. If there is, it's fake and you cannot flash anything with it. As you can see even from Wikipedia, Odin is the Samsung replacement of fastboot.
So no fastboot, only download mode.
If a guide is saying to use fastboot, it is not compatible with Samsung.
If you would tell me why you specifically need fastboot, I'll be happy to tell you how you can do it with Odin, if possible.
Because I have Samsung Galaxy A51 5G (A516B) with new Android 12 and I can't do a root! Because I can't upload TWRP (custom recovery) because I haven't OEM unlock option in Deveoper Option. I tried trick with set back date by 7days but not succes. Everything I;ve metioned here - I did at my phone with Android 11.
And... I have read that I can turn this fu**ing OEM option by comend at ADB: fastboot oem unlock.
Phew ...
So this fastboot method is the last method to do a root with my phone.
Upload TWRP by Odin in download mode -ends red warning - of corse...
Have you any ideas?
I would be grateful for help...
I have read this fastboot method at:
How to Unlock Bootloader On Samsung Galaxy Phones [EASY GUIDE]
Are you looking for a Complete tutorial on How To Unlock Bootloader on Samsung Galaxy Phones? If yes, then you have come to the right place.
www.guidetoroot.com
Yeah, that guide is not relevant on any modern Samsung device. Besides, even if it was, which it isn't, you would first need to enable OEM unlocking from the Developer Settings.
But the fact that you don't have an option for OEM unlock is weird, since I have the exact same device model and it is there for me.
May I ask what is your region and is your phone locked to a telephone carrier?
My region is PLS - Poland. And not - phone is not locked. Have you the newest system Android 12?
Yes, I do. It's weird that there isn't even an option for you.
I'll try to come up with some new ideas if I have time...
I'll be glad for it...
Hej, do you have any idea?
stanwin said:
Hej, do you have any idea?
Click to expand...
Click to collapse
Have you tried everything listed here?
BloodyFruitDestroyer said:
Have you tried everything listed here?
Click to expand...
Click to collapse
Yes, I did. Evething exept the last one...
You could try it. It might be risky, but it's the only option I personally can come up with right now.
I've tried this option but Odin stuck on "files verification". Any help?
have any of you encountered this problem?
And how did you solve it?
You can also try searching for combination firmware for your device online
Just as the title says; I have the unlock token and I've tried everything I can think of to flash it and nothing's worked. I have OEM unlocking enabled, the phone is permanently carrier unlocked, USB debugging is enabled, I've made sure to download a new version of Platform Tools, I've moved the .bin file to the same directory as Platform Tools, the phone comes up in ADB and fastboot when I check, it just won't write and I can't figure out why... usually it just hangs at sending 'cust-unlock' etc. but never progresses past that. Can anyone help me figure this out?
EDIT: Resolved! Me being dumb, not realized I'd only tried USB 2.0 ports; using a 3.2 port did the trick instantly.
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
FoxyDrew said:
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
Click to expand...
Click to collapse
Yea, that's what's baffling; I can jump back and forth between adb and bootloader/fastboot pretty easily but I just can't send the unlock token. I have seen a couple weird errors though, like if I'm in bootloader and do 'fastboot OEM unlock' and it fails (since I can't get the token to flash) and afterward I try 'fastboot devices' sometimes fastboot crashes to the 'press any key to reboot' screen.
Could this just be an outdated driver issue? I thought they were up to date...
Have u try using other cable or even try on different PC?
hendavi said:
Have u try using other cable or even try on different PC?
Click to expand...
Click to collapse
I've tried multiple USB ports and the original cable as well as others; I've confirmed commands like 'ADB reboot bootloader' and 'fastboot reboot bootloader' work and I've even updated the ADB/fastboot drivers just in case... still nothing. I haven't tried a different PC yet but I suppose that's next
No matter what I try, this is what I get every time I try it from the bootloader. I've tried from bootloaderd/recovery, but it fails there too saying something like 'writing not allowed' or something... I have OEM unlock turned on and it's carrier unlocked, so I have no clue what's stopping this from working.
What's really weird is I actually got this to work once before on this same device, but had to reset the phone back to stock T-Mobile branded software using the MSM tool; the first time around, I was able to enter the unlock token and just unlock it like normal (fastboot OEM unlock). Now that I've reset the phone and I'm trying again, it just won't work... really perplexed on this one.
UPDATE
I had to pull up an image of my mobo's io panel because I couldn't remember and couldn't see which ports were which; once I moved the cable to a USB 3.2 port, it worked... I guess I'd only been trying it on USB 2.0s before so it didn't work.
Thanks for your help!
I had same issue on my OnePlus 8 TMobile. Have to disable driver signatures. This shows you how. Yes, the link is for a diff phone, but just follow the disable driver signatures part of it and it will then show up in fastboot
https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/
EDIT: False alarm. I was sent an unlock code for an older device I have instead of the one I just bought. Should've double checked it first.
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