I got it working after praying for about 30 min lol, changed it back to stock then returned it to the seller. NO MORE. ill get a Samsung and have some peace of mind.
Thanks for your HELP!!!
Thanks for your quick response & advices, I really appreciate.I would STRONGLY urge you to have the following in place before proceeding:
- SDK platform tools originally provide the FASTBOOT.EXE program and ADB and so forth for you to call upon with the command prompt in the DOS-like environment. If you didn't know this, I would urge you to read up on this stuff as much as possible before you attempt anything. Don't feel bad if you're a newbie-- we all have to begin somewhere -- so Google "Android Studio" and "SDK Platform Tools" and take it all in....
- This thread was meant for those on Android 11 ONLY. If you're on 12, I don't think this will work. At all.
- Download a functioning MSM Tool (last I checked it was India, look at all the MSM Tool threads in this forum) and be sure it can recognize your device because I'd say you now have a more than coin-flip's chance of having to use it.
- For goodness sakes, make sure your PC drivers work in bootloader mode beforehand -- I would even disable "driver signing" in Windows 10 (look at the link I provided on page 2 of this thread).
Hi i tried this after I cannot boot to edl, but I got stuck in the waiting for device situation, I typed CTRL C and now I cannot boot to fastboot at all, someone can help me? the pc is recognizing the phone but by the QCOM driver.++This post is ONLY for those unfortunate souls who see <awaiting any device> in Fastboot mode for minutes while following the Instructions in Post #1++
- Once your OP9 screen shows Fastboot mode and you see <awaiting any device> for several minutes
- hit CTRL C to stop the flashing process
- go to Device Manager in Windows and look for the yellow-triangled ! device. LE2115 -- that's your unrecognized Fastboot device
- right click it and select update driver
- select "Browse my computer for drivers" and then "Let me pick from a list..."
- select ADB interface (and you might further need to pick the Universal or Samsung Android device) and install it
- once that driver window closes, go back to the PowerShell window
- type fastboot devices
=if you see a small string of characters, you're good. Go to the last step!
=if you only get another prompt, you need to unplug the OP9 and then reconnect it. Since you just updated the driver, Windows should now recognize and engage the driver for the Fastboot mode OP9. Confirm this by looking for a small string once you again type fastboot devices
=if you still don't get a small string confirming device recognition, try updating the driver again. And again. Because, you know, Windows. If you never succeed in getting Windows to recognize the OP9 in Fastboot mode, you might need to try downloading another ADB driver. But you really can't go further in this flashing process till the OP9 is recognized in Fastboot mode. Only then can you go on...
- the last step! Type rescuefastbootd.bat to complete the flashing process in Fastboot mode. With any luck, your OP9 will now flash the 2nd set of images and then reboot normally, on OOS 11.2.2 in slot B, and you will see the orbiting dots of a normal OOS boot. When you do, you can unplug your phone from the PC. Success!!
I've provided an AFH mirror for OOS' full OTA 220.127.116.11AA for convenient download.