Database Users

Nexus S ICS Problems Driver

prejudice to any forum.
I state that I'm an Italian who speaks no English, he writes, so forgive me for possible misunderstandings, but I'm posting the translation running google.
So are the owner of the Nexus 9023's version and then I wanted to try ICS via the Tools Cescomn I first unlocked the bootloader then root permissions and then I put a rom ics moddata atrraverso the recovery that I have changed as the guide told me. Then again, I want to change rom and then I decide to put the rom 4.0.3 Stock. So attraverlo the usb cable connected to the device I transfer the file ZD3PyN0t.zip from about 160MB. Reboot the device into fastboot recvovery I access the run and wipe and then install the rom. I was faced with the device locked with the recovery (after logging in and selecting the recovery fastboot I get black screen and then after a while you start the device) so everything is ok nothing anormale.Il problem is that there is to recognize the device in windows (both x32 and win7 win7 x64 win xp) I did the test with a nexus s aggiornatosi via ota to ics and then he immediately recognized the driver I've tried are good. Windows tells me unknown device unknown device or manually by selecting the driver. If you check the details of the device exactly match that of my friend who received ICS by ota.
What can I do?

try install google driver first
download it from here android sdk
this is the instruction
http://developer.android.com/sdk/win-usb.html

Done and redone.
facts of the problem occurs with my device, with that of a friend of mine (who has received ics via ota) no problem installing everything perfectly.
Putting it in download mode I recognized the same.
someone give me a tip?

Go to windows, manage devices, search for your phone, driver, update driver, select manually, choose android device and point it to the driver files. If it still does not work, i say you reflash your rom..
Sent from my Nexus S using XDA

Lazer Bear said:
Go to windows, manage devices, search for your phone, driver, update driver, select manually, choose android device and point it to the driver files. If it still does not work, i say you reflash your rom..
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
I tried many times to install the driver manually and do not go.
Now maybe I understand the problem .. a few days ago I got the ota update to 4.0.4 ics, the nexus has downloaded and installed.
The recovery tells me it's always locked, but after you press recovery from fastboot you press vol + + power and the recovery appears.
Turning the menu will not find anywhere the written MPT.
How can I fix?
The CWM does not make me install.
give me help.
thanks

Solution: 50% when unlocking bootloader

EDIT: SOLUTION (Not a fix)
For those who are stuck at "50% saying current account is different from the a/c info of device"
It is due to the database miss-match in their server ,the possible sollution are :
Remember: for MediaTek devices you will have to first flash a China Dev ROM onlu then you can get the unlock successful.
But this is not a recommendation for Qualcomm Devices.
1. Go to i.mi.com and look weather your device shows up in the find device (this is required only to be sure as to your device is connected to their server and they have updated the info on your Device too).
2. Reset your Phone sign in and turn on find device. turn on usb debug and oem unlock connect to pc allow whatever is asked on your phone also check always trust, then open adb folder and open cmd there and type adb devices your phone will ask for authorisation allow it and check always trust.
3. Mail your concern with user ID and also the snapshot of the error as they will ask for it,to your regional service (I am an indian so i had to mail it at [email protected])(just google contact xiaomi) wait for their reply.
You can PM these persons on MIUI forum regarding the 50% stuck issue.
{ EDIT 2:
You may contact these person in MIUI forum:
1) vincent_khoo
2) PatrickXi
( @bravonova gave me these names you may try I haven't cross checked as mailing will most probably solve) }
The last method should Work for everyone as it's a db miss-match which should be fixed after this.
PS: This a solution and not a fix so it will take time.
PPS: Don't blame me for all the trouble Blame Xiaomi.

ilvmyname said:
Ok, so I have been trying to move to miui 8 global beta version now for a long time and haven't succeeded, the updater app says could not verify update package.
I have a pretty good net connection so that's not an issue.
Also If I try download latest rom it says "Can't download update, wait a minute or two" and this it has been saying for about a week now (ironic).
So, I requested for unlocking the bootloader got the confirmation messages after 3 days tried to unlock now stuck at 50% saying "account is different from the account in the phone info"
I don't want to use the fast boot edl method of flashing rom as my lappy keeps getting sudden shutdown, so I don't want it to shutdown in between and get hard bricked.
I have tried MiPc suit but since it cannot do a backup(again app bug) so cannot flash through it.
I have looked in to the mi cloud and my phone does gets located.(possible solution given for unlock bootloader but even that didn't work).
Can anyone please help me on this or will I have to be on this ****ty unrooted Rom forever.
Currently on miui 7.5.3.0 global stable rom.
Any suggestions will be appreciated ty
Click to expand...
Click to collapse
I unlocked it just today!make sure all drivers are installed..boot into fastboot mode :- power off then hold vol down + power button.w8 for the drivers to get installed
Now boot into recovery mode :- turn off device and hold volume up + power button.w8 for the drivers to get installed.
I was stuck at the same 50% error..one of d xda member told me to boot into recovery mode and let the drivers get installed and taddaa...bootloader unlocked
Make sure u r logged in to the same account in ur phone u r using to unlock the bootloader

I fixed this by updating to latest version in miui app in fastboot mode.

Same problem for me. I tried using the MIUI PC Suite, it tells me my phone isnt up to date even though it is. Recovery mode drivers fail. Requested unlock over 2 weeks ago and got the SMS 9 day ago... still stuck at 50% error. Its driving me nuts.

Warrimonk said:
Same problem for me. I tried using the MIUI PC Suite, it tells me my phone isnt up to date even though it is. Recovery mode drivers fail. Requested unlock over 2 weeks ago and got the SMS 9 day ago... still stuck at 50% error. Its driving me nuts.
Click to expand...
Click to collapse
i today unlocked my bootloader...try doing this go into recovery mode by pressing power+volumeup button. You will see a picture telling you to connect ur phone to pc using usb cable..connect your phone to your pc now w8 and let the drivers get installed and try again..i did dis and unlocked it today before that i was getting the same error even today got the same error before doing this.

hitesh1792 said:
i today unlocked my bootloader...try doing this go into recovery mode by pressing power+volumeup button. You will see a picture telling you to connect ur phone to pc using usb cable..connect your phone to your pc now w8 and let the drivers get installed and try again..i did dis and unlocked it today before that i was getting the same error even today got the same error before doing this.
Click to expand...
Click to collapse
First of all thanks for the reply sir but
I tried entering to recovery mode and then connect to pc but nothing happens, I mean it does not show connected even after say 5 minutes.
Although when trying to enter into the fastboot mode and then connecting to pc the drivers do get install and it shows connected and stucks at 50%
I do have adb drivers RN3 USB drivers installed on my pc
But all things in vain.

Garyj881 said:
I fixed this by updating to latest version in miui app in fastboot mode.
Click to expand...
Click to collapse
I am sorry sir but I didn't get you, you updated to latest version of miui through the updater app right? And then entered to fastboot mode to unlock right?
My updater app also doesn't work It says cannot verify update package and so I am stuck like from all corners.

ilvmyname said:
First of all thanks for the reply sir but
I tried entering to recovery mode and then connect to pc but nothing happens, I mean it does not show connected even after say 5 minutes.
Although when trying to enter into the fastboot mode and then connecting to pc the drivers do get install and it shows connected and stucks at 50%
I do have adb drivers RN3 USB drivers installed on my pc
But all things in vain.
Click to expand...
Click to collapse
Are you able to see this pic on your device when you enter recovery mode??

hitesh1792 said:
Are you able to see this pic on your device when you enter recovery mode??
Click to expand...
Click to collapse
Yes

ilvmyname said:
Yes
Click to expand...
Click to collapse
connect your device to your pc and let the drivers get installed...and if u are using a desktop pc do not use the usb port which is at the front of the cpu..use the one which are at the back of the cpu...the image i am attaching shows which drivers get installed.
after drivers get installed remove usb cable and again boot into fastboot mode (power + volume down ) and try again to unlock bootloader

hitesh1792 said:
connect your device to your pc and let the drivers get installed...and if u are using a desktop pc do not use the usb port which is at the front of the cpu..use the one which are at the back of the cpu...the image i am attaching shows which drivers get installed.
after drivers get installed remove usb cable and again boot into fastboot mode (power + volume down ) and try again to unlock bootloader
Click to expand...
Click to collapse
Okay, so i am missing drivers i guess.
Have you pre installed any drivers if so can you provide me a link?
as when i connect into recovery mode only the bootloader interface driver get install and nothing else and hence it still doesn't show connected in the recovery mode.

ilvmyname said:
Okay, so i am missing drivers i guess.
Have you pre installed any drivers if so can you provide me a link?
as when i connect into recovery mode only the bootloader interface driver get install and nothing else and hence it still doesn't show connected in the recovery mode.
Click to expand...
Click to collapse
strange!bootloader interface driver gets installed when connected in fastboot mode..uninstall that driver connect your phone in recovery mode and see if dese drivers get installled..nope i do not have any link because as soon as i connected my phone into recovery mode the drivers automatically got installed!
ps :- i was able to unlock bootloader after flashing kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000.23_5.1_global_f5889c1549

i too have the same problem !! if you got the solution please tell me !!

T/[email protected]$ said:
i too have the same problem !! if you got the solution please tell me !!
Click to expand...
Click to collapse
i was able to unlock the bootloader after flashing kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000 .23_5.1_global_f5889c1549...
i was not able to unlock it before i connected my phone into recovery mode and installed the drivers on my pc..as soon i did it the bootloader got unlocked .before that i was getting the same error even after flashing the V7.3.7.0.LHOMIDD firmware

hitesh1792 said:
i was able to unlock the bootloader after flashing kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000 .23_5.1_global_f5889c1549...
i was not able to unlock it before i connected my phone into recovery mode and installed the drivers on my pc..as soon i did it the bootloader got unlocked .before that i was getting the same error even after flashing the V7.3.7.0.LHOMIDD firmware
Click to expand...
Click to collapse
how to flash kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000 .23_5.1_global_f5889c1549.?
when i connect my device in recovery mode nothing happens

For Kenzo / SD / Snapdragon only.
1. Install Mi PC Suite, plug your phone in and install the app on the phone when it prompts (then close mi pc suite) - this provides all the drivers needed for the next step
http://en.miui.com/thread-92720-1-1.html < Mi PC Suite
2. reboot the phone to recovery mode ( Vol UP + Power ), let drivers install on pc - wait, then reboot again to fastboot mode (VOL Down + Power) let drivers install on pc - wait - it might take a few minutes to install the drivers don't unplug the phone during this time.
3. download and install the unlock tool - log into your account, after it checks you have permission press unlock
http://en.miui.com/unlock/ < unlock tool
----------------------------
(if it still fails proceed to next step)
4. use xiao mi flash beta and install the latest kenzo global fast boot image (I have heard some people needed to use the Chinese dev firmware- the global stable worked for me though), use the clean all option selected at the bottom of mi flash. (this will erase ALL data on the phone)- backup before doing this.
http://en.miui.com/thread-281979-1-1.html <- xiao mi flash beta
5. let phone boot up first time, log into the mi account on the phone with your email / password, if your phone number doesn't work then select option to log in with email / password.
6. reboot to fastboot again and press unlock it should proceed now
Do at own risk I am not responsible for bricked devices.

T/[email protected]$ said:
how to flash kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000 .23_5.1_global_f5889c1549.?
when i connect my device in recovery mode nothing happens
Click to expand...
Click to collapse
it must install the drivers...please do check out the steps mentioned above by the xda member "otyj" he helped me to unlock my bootloader

I had the same problem and believe me I did everything possible as you are also advised in this forum.
But it had nothing to do with this.
Just wait and watch.. try everyday once and I think you will get in 7-10 more days.
I was also frustated at that time but now I can unlock everysingle time I want when it gets locked.

otyg said:
For Kenzo / SD / Snapdragon only.
1. Install Mi PC Suite, plug your phone in and install the app on the phone when it prompts (then close mi pc suite) - this provides all the drivers needed for the next step
http://en.miui.com/thread-92720-1-1.html < Mi PC Suite
2. reboot the phone to recovery mode ( Vol UP + Power ), let drivers install on pc - wait, then reboot again to fastboot mode (VOL Down + Power) let drivers install on pc - wait - it might take a few minutes to install the drivers don't unplug the phone during this time.
3. download and install the unlock tool - log into your account, after it checks you have permission press unlock
http://en.miui.com/unlock/ < unlock tool
----------------------------
(if it still fails proceed to next step)
4. use xiao mi flash beta and install the latest kenzo global fast boot image (I have heard some people needed to use the Chinese dev firmware- the global stable worked for me though), use the clean all option selected at the bottom of mi flash. (this will erase ALL data on the phone)- backup before doing this.
http://en.miui.com/thread-281979-1-1.html <- xiao mi flash beta
5. let phone boot up first time, log into the mi account on the phone with your email / password, if your phone number doesn't work then select option to log in with email / password.
6. reboot to fastboot again and press unlock it should proceed now
Do at own risk I am not responsible for bricked devices.
Click to expand...
Click to collapse
where can i find fastboot images ?
and when i plugin in recovery mode nothing happens !!
and your were telling that app will be installed in phone when we connect wiith mi pc suit, can you clearly explain it ?

otyg said:
For Kenzo / SD / Snapdragon only.
1. Install Mi PC Suite, plug your phone in and install the app on the phone when it prompts (then close mi pc suite) - this provides all the drivers needed for the next step
http://en.miui.com/thread-92720-1-1.html < Mi PC Suite
2. reboot the phone to recovery mode ( Vol UP + Power ), let drivers install on pc - wait, then reboot again to fastboot mode (VOL Down + Power) let drivers install on pc - wait - it might take a few minutes to install the drivers don't unplug the phone during this time.
3. download and install the unlock tool - log into your account, after it checks you have permission press unlock
http://en.miui.com/unlock/ < unlock tool
----------------------------
(if it still fails proceed to next step)
4. use xiao mi flash beta and install the latest kenzo global fast boot image (I have heard some people needed to use the Chinese dev firmware- the global stable worked for me though), use the clean all option selected at the bottom of mi flash. (this will erase ALL data on the phone)- backup before doing this.
http://en.miui.com/thread-281979-1-1.html <- xiao mi flash beta
5. let phone boot up first time, log into the mi account on the phone with your email / password, if your phone number doesn't work then select option to log in with email / password.
6. reboot to fastboot again and press unlock it should proceed now
Do at own risk I am not responsible for bricked devices.
Click to expand...
Click to collapse
Okay I will try flashing a rom through MiFlash toll b'coz the above methods didn't work and will quote if that's how it gets fixed

Oneplus 5 trouble with unlocking bootloader and TWRP

Hello this is my first post. I have searched the threads and internet for answers but I have not been able to find a solution.
I have been customizing my phones since the days of baked black bean on my galaxy S1, but I am no expert at this stuff. Until about a week ago, I was happily running RR on the OPO (great ROM) but it has gotten a bit slow so I figured it was time to get a OP5.
When I boot into fastboot, my device is recognized with the command fastboot devices. My phone showed the following:
fastboot mode
product_name - QC_Refernce_Phone
VARIANT - MSM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - c7ccda2
SECURE BOOT - yes
DEVICE STATE - locked
When I ran fastboot oem unlock, CMD prompt shows FAILED, however, the option to unlock the bootloader shows up on the OP5. I go through the process and wipe data. My phone now shows that it is unlocked, and I go into developer options to get advanced reboot/USB debugging/verify OEM unlock is still enabled. When I go back to fastboot, I am unable to flash TWRP. I have now seen a number of errors, usually:
FAILED (remote: Requested download size is more than max allowed) or target did not report max download size, or command write failed (no error). I have tried installing 4 different versions of ADB/fastboot from different sources, and I have tried TWRP cheeseburger 46, 58, and 62. I have also tried two different USB ports and 4 different USB drivers.
Does anyone know what could cause these issues or how to get TWRP installed? Any help would be much appreciated. I really want to get rooted and get substratum running.

hmm
did you type fastboot devices to check that u got connection ? do you have another pc to try ? another usb port
edit: also try disable developer option and aplly it again with oem unlock tapp
EDIT2: if you cant still get it work you can try
Advanced settings -> Backup & reset -> Reset all settings and after that unlock bootloader

I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.

bro do u find solutions for this

I found an actual fix for this problem. Basically I had to download Large Address Allocation Tool (LAA) which you can find online. I would link to it but I do not have the website handy.
I found this solution after soft bricking my phone by installing Oreo (I don't suggest using VPN to pretend you are in Canada. Just run the beta or wait for the US release).
Essentially, you just need to run this tool on your adb.exe. From what I understand, the issue is just that adb is not using enough RAM. I think you'll need to be running Windows 7 64bit with at least 4GB RAM. I hope this info can help someone else!

jsnell said:
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
Click to expand...
Click to collapse
Ever since i ditched windows and went with ubuntu i have not had one single driver issue, not one single hiccup on anything. It's been two months.. I'm never going back. lol. Every time I use adb and or fastboot it always works.

Unable to unlock bootloader after 327 firmware update

Hey guys i just updated to firmware 327 from 326.. I am using fully stock rom with locked bootloader.. I wanted to unlock bootloader but was unable to do so.. Whenever I try to run the unlock.bat file the black cmd screen remains stuck and nothing happens.. Plz help me i wanna try few roms so help me to unlock bootloader (6gb variant)
Is this because of the latest firmware??

Hi.
Link for official unlock tools
Look on the Driver & Tools
Version UnlockTool 2018/05/04548.6 KBytes
Unlock Device App: Unlock boot loader
Notice:
Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App,
including but not limited to the following: once you activate the App you will not be able to recover your

andriyhar said:
Hi.
Link for official unlock tools
Look on the Driver & Tools
Version UnlockTool 2018/05/04548.6 KBytes
Unlock Device App: Unlock boot loader
Notice:
Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App,
including but not limited to the following: once you activate the App you will not be able to recover your
Click to expand...
Click to collapse
Bro official unlocking method will void warranty even after i relock my bootloader later right? So i wanna do it the unofficial way so i can relock bootloader and go back to stock if I wish and would get ota updates

I unlocked my boooader after updating to 327.
Is your phone detected in Fastboot mode?

baunthiyal said:
I unlocked my boooader after updating to 327.
Is your phone detected in Fastboot mode?
Click to expand...
Click to collapse
Yes it's detected.. Bt the black cmd screen gets stuck while unlocking

Any solution guys plz need help

try using cmd prompt in administrator mode....

ujilraj said:
try using cmd prompt in administrator mode....
Click to expand...
Click to collapse
Tried already bro nothing works i read somewhere that windows 10 have issues to unlock bootloader and everything works fine with windows 7.. But this thing doesn't make any sense according to me :/

Well, I am not an expert in this. It should just work. And the Windows 10 thing is absurd. I am using Windows 10. Plus, development mode is not enabled in my laptop.
Credits to the following -
@Sudeep Duhoon for this guide - [UNLOCK/RELOCK] Bootloader Unofficailly and Flash TWRP+Root
ASUS for phone, drivers, rom, this and that
Mod edit. Link removed. Reference: https://forum.xda-developers.com/one...rward-t3765018
@Saktis_STi for raw factory rom
@Shivam Kumar Jha for fixing the script
@Sujeet Ranipa for drivers link
@esashwin for testing

Use unlock.sh instead of unlock.cmd
If the phone is indeed detected in fastboot mode using
Code:
fastboot devices
, try running the script from unlock.sh instead of unlock.cmd.
I have not been unable to flash fastboot stock ROM from this laptop using the .bat file but for some reason, .sh file works fine.
Just install Git on windows. It will give you a wrapper to run shell scripts on your windows machine (Git BASH).
Again, I am not an expert. This might not work but at least it won't corrupt anything.

This happened to me as well, its problem with your pc(i mean drivers or just your os or maybe the usb ports, use 2.0 ports preferably) i have two pcs with windows 10 installed in both. One is updated and the other outdated. It failed in my updated pc, tried all methods like install, uninstall drivers, disabled driver signing, used different cables, used different usb ports 3.0, 2.0 but nothing worked. Atlast i gave it a try with my outdated windows 10 pc. It worked liked a charm. It has something to do with the drivers i suppose. Try in a different pc it might just work right for u as well

_uchihaitachi_ said:
Tried already bro nothing works i read somewhere that windows 10 have issues to unlock bootloader and everything works fine with windows 7.. But this thing doesn't make any sense according to me :/
Click to expand...
Click to collapse
Try anyother pc
Many users solved unlock problems by changing pc

yuvatheja said:
This happened to me as well, its problem with your pc(i mean drivers or just your os or maybe the usb ports, use 2.0 ports preferably) i have two pcs with windows 10 installed in both. One is updated and the other outdated. It failed in my updated pc, tried all methods like install, uninstall drivers, disabled driver signing, used different cables, used different usb ports 3.0, 2.0 but nothing worked. Atlast i gave it a try with my outdated windows 10 pc. It worked liked a charm. It has something to do with the drivers i suppose. Try in a different pc it might just work right for u as well
Click to expand...
Click to collapse
Ok bro thanks for help.. Will try on another pc coz my pc has only 3.0 and 3.1 ports ?

iamfarhanansari said:
Try anyother pc
Many users solved unlock problems by changing pc
Click to expand...
Click to collapse
Ok bro thanks for help

Phone is not detected.
baunthiyal said:
I unlocked my boooader after updating to 327.
Is your phone detected in Fastboot mode?
Click to expand...
Click to collapse
I have this same issue my phone is not detected.
Please help.

I too have same problem
C:\>cd unlock
C:\unlock>fastboot devices
J7AAGF02D693CWW fastboot
C:\unlock>unlock
------------------------
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device

Solution to unlocking bootloader where screen blacks out on flashing
yuvatheja said:
This happened to me as well, its problem with your pc(i mean drivers or just your os or maybe the usb ports, use 2.0 ports preferably) i have two pcs with windows 10 installed in both. One is updated and the other outdated. It failed in my updated pc, tried all methods like install, uninstall drivers, disabled driver signing, used different cables, used different usb ports 3.0, 2.0 but nothing worked. Atlast i gave it a try with my outdated windows 10 pc. It worked liked a charm. It has something to do with the drivers i suppose. Try in a different pc it might just work right for u as well
Click to expand...
Click to collapse
I had the same issue, after reading to many webpages, stumbled on this official unlock tool apk. Once the bootloader is unlocked using the app, the phone reboots into ASUS UNLOCK MODE with device status as unlocked and message to restart the phone. Heres the catch this is already the fastboot mode so flash TWRP at this stage. If you restart the phone in fastboot before flashing twrp, on running the flash cmd the screen of your phone would black out with a message "press any key to shutdown". Hope this helps.
unlock tool apk

then how do I install that official unlock tool in fastboot mode. since I can only access CSC FASTBOOT MODE.

(SOLVED) Urgent ! My OP8P is dead I think, stuck Fastboot

Hello everyone !
I'm new on this forum but I really need your help. I tried to fix my mistake all day long yesterday (9am to 2am non stop).
So, basically, I have a OnePlus 8 Pro, Model IN2023.
I had OOS 11 updated. I tried to install OOS 12 Bêta and I did but I had a indian version so a lot of bugs.
I wanted to go back to OOS 11 but it was impossible because I was now in an indian version.
I tried with MyApplication2 to local upgrade and downgrade as recommand in Internet.
I tried to unlock bootloader and the following steps but here my problem:
I unlocked my bootloader then I misclick and I locked again my bootloader.
Then my phone just crashed and put this message:
"The current image (boot/recovery) have been destroyed and can not boot."
So, I forced to turn off the phone and try to go in EDL mode but:
1. ADB doesn't work anymore
2. Fastboot work fine
3. EDL mode is impossible
So, my bootloader is unlocked again. My phone is stuck on Fastboot mode:
Fastboot mode
Product_name - kona
Variant - SM8 UFS
Bootloader version -
Baseband version -
Serial number - eed52b71
Secure boot - yes
Device state - unlocked
I used the official firmware on OnePlus website, I used Python and Payload_dumper.py to have the .img from the .bin of the official firmware.
I tried to flash all the images, I tried to install TWRP, I tried almost everything I found but still stuck in Fastboot. Recovery mode doesn't work.
I tried to boot, to flash, to do everything I could.
I also tried MSM Download Tool but nothing appears inside.
Now, when I connect my phone, it's with a cable in USB-C but 3.0, not 2.0. Maybe that's the problem ?
When I plug my phone, in Device Manager, I have a "!" but the phone is recognized under
"Qualcomm HS-USB QDLoader 9008 (COM6). When I click on it, it says (sorry, I'm about to translate from french):
"Windows can not verify the numeric signature for the drives required for this peripheric. It is possible that a material ou software modification has been installed a corrupted file or with an incorrect signature, or it is a malware from an unknown source (Code 52)"
Please help me, contact me on Whatsapp, or here. Let's do this in direct.
Btw, I have a Macbook Pro to do all this. I used also Windows with Bootcamp.

So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.

andshura said:
So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.
Click to expand...
Click to collapse
Im happy you fixed your phone.
Read this before you even think to go to A12 again on this device.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com