Database Info

Hard bricked my OnePlus One by just rebooting it, help! [5$ REWARD]

I will be straightforward:
I bought an used OPO, I booted it up, configured the phone, took a photo and then decided to reboot it (turn off and then turn on), then my device simply hard bricked.
1. I already tried turning it on, the device does nothing (no vibration).
2. I already tried using Power + Vol Up and Power + Vol Down, nothing happens (no vibration).
3. Windows recognizes the device as "QHSUSB_BULK", I already tried installing the drivers and using ColorOS flashing tool from here http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , the device IS RECOGNIZED by the tool, but when I start flashing, it starts a loop when trying to flash the "8974_msimage.mbn" file (the progress bar goes until the end and then the process repeat in the same file).
Yes, the device has the bootloader unlocked, because the previous owner flashed a custom ROM, custom kernel and SuperSU.
No, the device isn't recognized by adb.
No, the device isn't recognized by fastboot.
I already tried searching on Google for this issue, everyone who had this issue never replied saying that they fixed the issue...
I never had any kind of soft/hard brick on my Moto G 2014 (and I flashed custom ROMs constantly on it)... so... can someone help me? Thanks!
I'm also willing to give 5$ on PayPal to someone who can fix this issue.

Also, if I try to use the ColorOS flashing tool, the device disconnects in the middle of the process, causing the infinite flash loop.

First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English

sino1641 said:
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
Click to expand...
Click to collapse
Nah, your english is fine, I could understand what you are saying.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After I clicked "Start"
Then the "device plugged in" sound plays and the process repeats...
It keeps doing this:
(If you can't view the images, click here:
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-39-42.png
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-40-18.png
http://lori.mrpowergamerbr.com/sharex/2016-07-22_10-41-05.gif
)

Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.

sino1641 said:
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
Click to expand...
Click to collapse
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers

MrPowerGamerBR said:
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
Click to expand...
Click to collapse
Open Device Manager.
Press Power &Vol Up for about 10 seconds.
See if it will change between 9008 and 9006.

I have same thing did it work
I am just wondering if u managed to fix it.

I had the exact same issue. To stop the device from disconnecting, I needed to remove all existing drivers, let the phone charge, plug it into the PC. Hold volume up + power until the PC recognises it. Then I used the color OS flashing tool.
I had to run it as administrator, and it worked fine on Windows 10, without anything extra. However remember you'll lose all your stuff. Lucky for me I had a backup of my entire phone on my PC when I switched file system to F2FS.
This issue in itself has really baffled me. It happened to me when flashing sultans rom, and the phone completely bricked. However I'm using the rom now after fully recovering the device... I guess it's just down to bad luck?

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Nope, never fixed it, I don't even have the device anymore (now rocking a Moto G Turbo)

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Don't use "msm8974-download-manager" use qfil to recover the phone. Worked for me.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/

Download 2012 qhs diagnostic driver and use xp machine.It will work just fine.

install a fresh windows either x32/x64 winxp/win 7 extract color OS and install the correct drivers

[Hisense A5] How to Enter Hardware EDL mode

Hisense A6, A6L, A5 ... can not unlock bootloader
you can enter A5 hardware edlmode
teardown your phone
jump this point with clip(?)
and connect usb cable
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if can not enter
you need take off power cable ( right bottom corner)
and retry
you can enter EDL mode
you need A5's QFIL firmware

joygram said:
Hisense A6, A6L, A5 ... can not unlock bootloader
you can enter A5 hardware edlmode
teardown your phone
jump this point with clip(?)
and connect usb cable
if can not enter
you need take off power cable ( right bottom corner)
and retry
you can enter EDL mode
you need A5's QFIL firmware
Click to expand...
Click to collapse
Hi, thanks for the useful information.
Previously I bricked my A5 and was able to re-flash with 6.09.06.
I thought I would be able to issue the "adb reboot edl" command. But it didn't seem to work for me.
If I issue the "adb devices" command, I get the response "List of devices attached" with a number and the word "device".
I can do an "adb shell" command ... works well ... can go in there and put in some linux commands.
But when I issue the "adb reboot edl" command, it appears to work. The phone becomes unresponsive. If I issue the command "adb devices", it says that nothing is there.
But when I go into the QFIL program ... there is "No Port Available".
Any ideas ?

try step.
no adb required.
just jump point and connect power cable.
you should retry until catch QFIL catch port.
CrotteDeChien said:
Hi, thanks for the useful information.
Previously I bricked my A5 and was able to re-flash with 6.09.06.
I thought I would be able to issue the "adb reboot edl" command. But it didn't seem to work for me.
If I issue the "adb devices" command, I get the response "List of devices attached" with a number and the word "device".
I can do an "adb shell" command ... works well ... can go in there and put in some linux commands.
But when I issue the "adb reboot edl" command, it appears to work. The phone becomes unresponsive. If I issue the command "adb devices", it says that nothing is there.
But when I go into the QFIL program ... there is "No Port Available".
Any ideas ?
Click to expand...
Click to collapse

Anybody who knows:
How do you open the device without breaking it?
Ehere to begin to open it?
What tools (i.e. screwdrivers T5?) you need?
Does an Edl-Hardware USB-Cable works with the Hisense to enter Edl-Mode? How?

Yeah, how to open the Hisense A5?

Use something like a guitar pic (plastic plectrum) on the edge of the cover and open the cover carefully i.e. upper front.

lillo9546 said:
Yeah, how to open the Hisense A5?
Click to expand...
Click to collapse
I used just my fingernail. You can start opening from the weakest point which is near the sim card port.

Hi Everyone, thanks you your tips.
I went to a phone repair place and paid them 20 AUD to open the phone.
I am having trouble getting the phone into edl mode, (which I found means Extended Download Mode BTW).
Reading more there is information regarding PCB (printed Circuit Boards) and the test points. These are the points we are mean to be "jumping".
What is the sequence of events ? Do I turn off the phone first ? Do I turn on the phone while having the points jumped ?
Do I connect the phone to the computer via USB first, and then allow debugging ... and THEN jump the points with tweezers or a paperclip ?
Any ideas would be greatly appreciated.

CrotteDeChien said:
I am having trouble getting the phone into edl mode, (which I found means Extended Download Mode BTW).
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
See after Step 6., but really be careful. Good luck
https://in.c.mi.com/thread-387857-1-0.html

Entered EDL mode after tearing down my phone. Flashed the "prog_emmc_.... .mbn" and "rawprogram_000b....." files with QFil successfully. But my phone just lights up, shows Hisense logo when try to start the device. Same bricked device.
Any idea?

Mehedi34 said:
Entered EDL mode after tearing down my phone. Flashed the "prog_emmc_.... .mbn" and "rawprogram_000b....." files with QFil successfully. But my phone just lights up, shows Hisense logo when try to start the device. Same bricked device.
Any idea?
Click to expand...
Click to collapse
Dear Mehedi,
use the base firmware 6.03.02 for edl-mode flashing in Qfil provided from gowin132
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Then flash this in Qfil see here some general infos
https://forum.xda-developers.com/showpost.php?p=82654769&postcount=79
use "prog_emmc_firehose_8937_ddr_000bf0e1.mbn"
from the package of joygram
Flash each partition in Qfil Partition Manager (Menu Tools)
After that reboot the device and it should work.
Then upgrade to latest 6.09.06 with TFMode (microSD)
https://forum.xda-developers.com/showpost.php?p=82583733&postcount=28

see also here
https://forum.xda-developers.com/an...nfo-thread-t4101945/post82794951#post82794951

JLowe said:
see also here
https://forum.xda-developers.com/an...nfo-thread-t4101945/post82794951#post82794951
Click to expand...
Click to collapse
Successfully unbricked my phone. Thanks everyone [email protected] @joygram @gowin132

Mehedi34 said:
Successfully unbricked my phone. Thanks everyone [email protected] @joygram @gowin132
Click to expand...
Click to collapse
Good to hear that you're successful! You can't soft brick these China Qualcomm Smartphones
Have fun with this great device!

5 Methods to enter EDL mode on any Xiaomi smartphones [Qualcomm]
5 Methods to enter EDL mode on any Xiaomi smartphones [Qualcomm]
1. Boot EDL Mode via ADB Commands
2. Use Fastboot to Boot EDL mode on any Xiaomi smartphones
3. Use Hardware Buttons
===> Turn off your device.
===> Press and hold the Power + Volume Down buttons together and immediately connect the device to the PC.
===> It will automatically boot into EDL mode and LED lights may blink.
4. Use Deep Flash Cable
5. Use PCB Test Points

Well I guess I bricked my phone. I had it rooted with google play services but wanted to reset it. After a factory reset it seems like I'm stuck in a boot loop or something and also can't get into TF mode to flash the original firmware again.
I had many services disabled but nothing uninstalled before the factory reset.
Does anyone know what I can do to unbrick it or get into TF mode?

hammelgammler said:
Well I guess I bricked my phone. I had it rooted with google play services but wanted to reset it. After a factory reset it seems like I'm stuck in a boot loop or something and also can't get into TF mode to flash the original firmware again.
I had many services disabled but nothing uninstalled before the factory reset.
Does anyone know what I can do to unbrick it or get into TF mode?
Click to expand...
Click to collapse
Just follow this here
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
joygram uploaded a new version R04 which include original Edl firmware 6.09.06. So just flash this in qfil and then reboot to system and then go into qfil for root and flash the modified partitions.
If this doesn't work you can try the old way:
Before the way was as here described you needed first to in qfil 6.03.02 then going into TF-Mode to flash actual 6.09.06, reboot to system and then again Qfil for root,...
https://forum.xda-developers.com/android/help/hisense-a5-info-thread-t4101945
Good luck!

JLowe said:
Just follow this here
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
joygram uploaded a new version R04 which include original Edl firmware 6.09.06. So just flash this in qfil and then reboot to system and then go into qfil for root and flash the modified partitions.
If this doesn't work you can try the old way:
Before the way was as here described you needed first to in qfil 6.03.02 then going into TF-Mode to flash actual 6.09.06, reboot to system and then again Qfil for root,...
https://forum.xda-developers.com/android/help/hisense-a5-info-thread-t4101945
Good luck!
Click to expand...
Click to collapse
I made a deep flash cable myself but sadly that doesn't seem to work either. Maybe I did something wrong with the cable but it seems all good to me. I can connect another phone with it and it functions normally, so the only thing that can be defect is the switch/button itself which shorts/connects the green and black wire together.
When I plug the Hisense in my computer with the button pressed it "starts normally" into the boot loop or something and when I let go off the button nothing happens.
As far as I read, you press the button, plug the phone into the computer and after about 8 seconds or so you let go off the button and it will boot into edl mode. But it doesn't seem to work for me.
Thank you. Any help would be very appreciated.
Edit: Okay I got it. For some reason I had to press the button on the cable, volume up/down and power button together for a few seconds until it showed up i QFIL.

JLowe said:
Just follow this here
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
joygram uploaded a new version R04 which include original Edl firmware 6.09.06. So just flash this in qfil and then reboot to system and then go into qfil for root and flash the modified partitions.
If this doesn't work you can try the old way:
Before the way was as here described you needed first to in qfil 6.03.02 then going into TF-Mode to flash actual 6.09.06, reboot to system and then again Qfil for root,...
https://forum.xda-developers.com/android/help/hisense-a5-info-thread-t4101945
Good luck!
Click to expand...
Click to collapse
Same me. I had rooted it but i tried to reflash stock firmware and now has bootloop. How imcan fix? If i flash root it will boot, but i want to go back to stock

Mehedi34 said:
I used just my fingernail. You can start opening from the weakest point which is near the sim card port.
Click to expand...
Click to collapse
I also used my fingernail too, its easy to handle,

Moto One Macro - Bricked Device

Hello folks, please help me ASAP, as I have no other devices in me and both my private and work related things are associated with my phone so...
I was doing this and since im noob I was going step by step so i dont mess something and yet that happened. you can read from there what I was doing and what happened.
Basically I tried to flash firmware by executing line by line of commands and now my phone is dark (nothing can be done with physically clicking the buttons). Its connected with the PC so sometimes i can hear that USB sounds you know.. Anyway, can you please assist me how to proceed and go back to normal ?

Open device manager and look for Qualcomm
if you see that your Device is in EDL Mode.

Try this tool
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

sd_shadow
Nope, nothing with qualcomm in my device manager.
And after running "bank-flash" my device now rebooted to fastboot.

KomitaMKD said:
sd_shadow
Nope, nothing with qualcomm in my device manager.
And after running "bank-flash" my device now rebooted to fastboot.
Click to expand...
Click to collapse
ok, I'm not sure what the flashing problem is.
rerun
Code:
fastboot getvar all

sd_shadow said:
ok, I'm not sure what the flashing problem is.
rerun
Code:
fastboot getvar all
Click to expand...
Click to collapse
I pressed the button to start the mobile and now its stuck/taking too long on the motorola logo.
running the bank flash file in this state gives me this now
Code:
working path= C:\Users\trajk\Downloads\rescuetool_JimnyPlus_64
Loading Da...
Loading Da OK!
Loading Scatter file...
ChecksumLevel = 2!
Loading Scatter file success!
Loading AuthFile...
Loading Auth OK!
Waiting for com port cable insert...
Please insert comport...

KomitaMKD said:
I pressed the button to start the mobile and now its stuck/taking too long on the motorola logo.
running the bank flash file in this state gives me this now
Code:
working path= C:\Users\trajk\Downloads\rescuetool_JimnyPlus_64
Loading Da...
Loading Da OK!
Loading Scatter file...
ChecksumLevel = 2!
Loading Scatter file success!
Loading AuthFile...
Loading Auth OK!
Waiting for com port cable insert...
Please insert comport...
Click to expand...
Click to collapse
Blankflash only works with EDL Mode (black screen)

10 minutes later im still stuck on the Motorola - Powered by Android logo

So, how do I proceed now?

Try this guide, my friend: https://forum.xda-developers.com/t/...your-bricked-motorola-moto-one-macro.4145191/

VD171 said:
Try this guide, my friend: https://forum.xda-developers.com/t/...your-bricked-motorola-moto-one-macro.4145191/
Click to expand...
Click to collapse
Im not sure how to use this
Official Stock Rom by LOLINET: https://mirrors.lolinet.com/firmware/moto/lima/official
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

KomitaMKD said:
So, how do I proceed now?
Click to expand...
Click to collapse
You need to reboot to fastboot mode, unplug USB, and hold the volume button and power, till you see the fastboot screen.

You have
Code:
ro.carrier: reteu

sd_shadow said:
You have
Code:
ro.carrier: reteu
Click to expand...
Click to collapse
Okay that did the work now my phone is off - black after i pressed the buttons...
Now which one should i download? Should i use the Android 10 one or the 9 one you mentoined previously (if its the same). btw before i do anything i had android 9 running with the november patch

I tried that Android 10 and this is what i did.
Extracted Mediatek and the firmware in same folder, did the cmd thing from the xml through the spanish web site, ran the bat file and nothing happened.
Now ill be trying with the android 9 version

Okay guys im not able to successfully run the flashfile.bat

I tried with the (Optional) Automatic BAT file made by Eufracio López and it did the trick!!! I was able to flash Android 10!

KomitaMKD said:
I tried with the (Optional) Automatic BAT file made by Eufracio López and it did the trick!!! I was able to flash Android 10!
Click to expand...
Click to collapse
Nice job, my friend.

I would like to thank you all who spared some of your
VD171 said:
Nice job, my friend.
Click to expand...
Click to collapse
Thanks to you and @sd_shadow , I really appreciate your quick assistance

KomitaMKD said:
Hello folks, please help me ASAP, as I have no other devices in me and both my private and work related things are associated with my phone so...
I was doing this and since im noob I was going step by step so i dont mess something and yet that happened. you can read from there what I was doing and what happened.
Basically I tried to flash firmware by executing line by line of commands and now my phone is dark (nothing can be done with physically clicking the buttons). Its connected with the PC so sometimes i can hear that USB sounds you know.. Anyway, can you please assist me how to proceed and go back to normal ?
Click to expand...
Click to collapse
Hi @KomitaMKD this is vignesh , i am also using Moto One Macro device , Lastweek i have thought to flash my mobile due to some reason first time my device became brick... I am not ble to do anything its come startup failure ! Message .... I felt really bad ... Then almost i tried 8 hrs continuously for recovering my phone.. finally i found it. I recovered my mobile. Below i will give a link just go through it , that will help your mobile to become normal.
[RECOVER][UNBRICK][BLANKFLASH] How unbrick your bricked Motorola Moto One Macro
This script was made by Eufracio López (yehison). Thank you very much ! 1. First, you have to download required contents: Minimal ADB and Fastboot Tool: https://androidmtk.com/download-minimal-adb-and-fastboot-tool Motorola Device Manager...
forum.xda-developers.com

Question Read Flash unbrick unlock bypass FRP & More

Hello Everyone.. here is the Instructions for OnePlus Nord CE 2-
Note:
backup Internal storage, contact message etc before process
In case, even after flashing completed successfully but some time device does not boot, only black screen, no charging sign either then don't panic, device has entered into emergency download mode, if you face the same then it's time to flash preloader.bin file.
1. Reading Firmware from Device
we download Require files USBDK Driver, Mediatek Driver & The Program
We Install both USBDK and Mediatek driver on our computer
disable windows defender and extract Program
Run Program
Select 'Firmware reader' Option and Mark The Full Firmware Option and Click 'Start Button'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
turn Phone off, Press Volume up and down key and Insert USB
Reading Process Started. it will take around 15Min, once done we collect Firmware in Out Directory (it will Include nvram too)
unlocking bootloader:
there is a fastboot access issue on this device, you can try exploit method which is located Mediatek/service section...
bypass FRP lock:
From the very first Screen we Select FRP bypass Option and click 'START' Button
turn Phone off press volume up and down key and then insert usb
once done we disconnect device
Flashing Firmware:
we Go to Mediatek/Firmware Flashing Option
Select second Method 'write all partition' locate the firmware folder
click 'flash' button
turn phone off Press Volume up & down key and then inset usb
wait until success. done

Sry for the following stupid questions but:
-) How do I start the program in win64?
-) Can I use this to dump the current android rom of my phone and get boot.img+vbmeta.img thus being able to root the phone using magisk?

trohn_javolta said:
Sry for the following stupid questions but:
-) How do I start the program in win64?
-) Can I use this to dump the current android rom of my phone and get boot.img+vbmeta.img thus being able to root the phone using magisk?
Click to expand...
Click to collapse
Extract zip, run rom2box.exe
yes you can dump current ROM, Mediatek/firmware-reader

mark332 said:
Extract zip, run rom2box.exe
yes you can dump current ROM, Mediatek/firmware-reader
Click to expand...
Click to collapse
Turns out my work laptops antivirus instantly removed the .exe

Does the bootloader need to be locked to get into this preload mode and to dump the rom? I already unlocked it before.
Now if I hold up and down volume and plug in the phone Rom2box says "..handshake failed..". Rebooted after installing mediatek and usbdk drivers and I also tried different usb ports.

trohn_javolta said:
Does the bootloader need to be locked to get into this preload mode and to dump the rom? I already unlocked it before.
Now if I hold up and down volume and plug in the phone Rom2box says "..handshake failed..". Rebooted after installing mediatek and usbdk drivers and I also tried different usb ports.
Click to expand...
Click to collapse
The same story for me, the phone can't be put in preload or download mode or whatever they call it. I know one thing it is my last Oneplus phone if they're all going to be pain in the arse like this one. I guess it's back to my old 6t for another while then.

Accessing it by way of Recovery mode is also broken. To try it yourself, boot in to Recovery, connect your phone to your computer with usb-c cable. Multi-tap version number, it will eventually ask you if you want download mode and you click yes. It will attempt reboot into download mode, fail and then will `normal` boot phone.

trohn_javolta said:
Turns out my work laptops antivirus instantly removed the .exe
Click to expand...
Click to collapse
fixed a clean version + code available in public https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/

Hi, I just tried ROM2box 2.5. I got five of these messages then kicked into recovery `Preloader - [LIB]: [31mStatus: Handshake failed, retrying...[0m`

Quaicheist said:
Hi, I just tried ROM2box 2.5. I got five of these messages then kicked into recovery `Preloader - [LIB]: [31mStatus: Handshake failed, retrying...[0m`
Click to expand...
Click to collapse
connect in Proper way= install Latest usbdk and mtk driver, start process turn Phone off press volume up & down key and then Insert USB, once the Phone is detected release keys

Thanks for the info, though I have been doing that setup all along. I dual windoze and Linux. My windows is a custom minimal version of windows 10 with feck all on it. I upgraded this phone to stock 12 beta yesterday and ROM2Box for a wonder is happily doing a dump of that. It should be interesting when I downgrade to stock 11 and try to do a dump of that.

@mark332 thanks for the advice, phone happily did dump with the OxygenOS 12 Open Beta 1 but refused point blank to do a dump with OxygenOS 11 Build number: IV2201_11_A13. Is there any difference in your phone setup to my own - bootloader unlocked?

Quaicheist said:
@mark332 thanks for the advice, phone happily did dump with the OxygenOS 12 Open Beta 1 but refused point blank to do a dump with OxygenOS 11 Build number: IV2201_11_A13. Is there any difference in your phone setup to my own - bootloader unlocked?
Click to expand...
Click to collapse
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11

mark332 said:
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11
Click to expand...
Click to collapse
Hi @mark332, sorry I wasn't able to get to you sooner about this. Coredump was only possible with OxygenOS 12.1 beta, BROM was definitely locked down in 11. I succeeded with 12 but 'out' folder looks incomplete, files like ''preloader' which is in the beta package are missing from the dump. I don't think I would be able return to stock with ROM2box, maybe manually with fastboot commands.

Well downgrading this phone from OxygenOS 12 beta 1 to OxygenOS 11 has left it without a working touch screen in the normal mode or recovery so it is now a dust collector unless Oneplus / Oppo are willing to fix it.

Quaicheist said:
Well downgrading this phone from OxygenOS 12 beta 1 to OxygenOS 11 has left it without a working touch screen in the normal mode or recovery so it is now a dust collector unless Oneplus / Oppo are willing to fix it.
Click to expand...
Click to collapse
I'm just curious how did you downgrade?

mark332 said:
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11
Click to expand...
Click to collapse
Brom is enabled on A11 I've reflashed my device recovery partition when i was stuck

ko_hi said:
I'm just curious how did you downgrade?
Click to expand...
Click to collapse
I guess I used OnePlus's rollback guide once too often besides it is a beta, I was bound to get bitten in the arse evenually; https://community.oneplus.com/thread?id=1110424001643544581

Quaicheist said:
I guess I used OnePlus's rollback guide once too often besides it is a beta, I was bound to get bitten in the arse evenually; https://community.oneplus.com/thread?id=1110424001643544581
Click to expand...
Click to collapse
I guess if BROM mode works, use the bypass method to flash back to A11.v

Ah you see, the fecking phone managed to rollback to 11 but the touch screen driver is broken I guess. Physical buttons work but touch is broken. So I have contacted Oneplus tech support so we'll see what response I get tomorrow.

Trouble Unlocking Bootloader

I am having hard time unlocking my Poco F1's bootloader, to start installing custom ROMs.
The phone's responding and is compatible with adb commands, in stock ROM and as well as in recovery. But in fastboot mode, it's having issues.
When phone is in fastboot mode and connected with the PC, it recognises the device and has a phone serial number in place when running the fastboot devices command. Just after 2-3 seconds of connection, the fastboot devices command holds for a while and returns multiple question marks(???????) in the place of device serial number.
I have tried switching PCs and changing USB cable and still same error. I am yet to try in on Windows 7, but have tried it on Windows 10 and 11. All gave same issues. Some PC don't even detect the device and the phone charges only. I have made sure the correct bootloader drivers are installed in Device Manager every time too.
The Mi Unlock tool says there is no device connected due to this. It is annoying me to the point that I have even tried using a 2.0 USB extension cable to see if it works. I would have tried with a USB 2.0 hub but I sadly don't own one and I don't want to buy it just for this.
Any insights or help will be of great help, thanks in advance.

If you think you have followed all the steps correctly, I suggest you read this article that I read yesterday. I had read that some models, including the Pocophone f1, use a special security.
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
If the problem you are experiencing is not caused by what is described in this article, I suggest that you double-check the steps you have followed.I had a similar problem before and solved the problem using the driver installation option in the mi flash application.

canero said:
If you think you have followed all the steps correctly, I suggest you read this article that I read yesterday. I had read that some models, including the Pocophone f1, use a special security.
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
If the problem you are experiencing is not caused by what is described in this article, I suggest that you double-check the steps you have followed.I had a similar problem before and solved the problem using the driver installation option in the mi flash application.
Click to expand...
Click to collapse
Thanks for responding, I will take a look at the article once.
I have made sure that all steps were followed correctly and I think everything was in order. I have already made sure correct drivers were installed multiple times.
What's weird with my device is that, unlike other Poco F1 devices this one in particular does not have any OTG option in settings, I don't know if it's a software or a hardware issue. The device is on MIUI 12.0.3 Stable(QEJMIXM).

OTG option? OTG is not the traditional adapter that we use to insert a usb stick into the phone? are there some parts that I know are missing, please inform me

Bhavik479 said:
I am having hard time unlocking my Poco F1's bootloader, to start installing custom ROMs.
The phone's responding and is compatible with adb commands, in stock ROM and as well as in recovery. But in fastboot mode, it's having issues.
When phone is in fastboot mode and connected with the PC, it recognises the device and has a phone serial number in place when running the fastboot devices command. Just after 2-3 seconds of connection, the fastboot devices command holds for a while and returns multiple question marks(???????) in the place of device serial number.
I have tried switching PCs and changing USB cable and still same error. I am yet to try in on Windows 7, but have tried it on Windows 10 and 11. All gave same issues. Some PC don't even detect the device and the phone charges only. I have made sure the correct bootloader drivers are installed in Device Manager every time too.
The Mi Unlock tool says there is no device connected due to this. It is annoying me to the point that I have even tried using a 2.0 USB extension cable to see if it works. I would have tried with a USB 2.0 hub but I sadly don't own one and I don't want to buy it just for this.
Any insights or help will be of great help, thanks in advance.
Click to expand...
Click to collapse
I read the article again and I want to ask a part that stuck in my mind. Do you not use the unlock software to unlock the bootloader? As far as I know, it is not possible to perform this operation with ADB commands.

canero said:
I read the article again and I want to ask a part that stuck in my mind. Do you not use the unlock software to unlock the bootloader? As far as I know, it is not possible to perform this operation with ADB commands.
Click to expand...
Click to collapse
Kindly read my original post again, I do use the Mi Unlock tool and do connect the phone via Fastboot/Bootloader mode.

I think we can solve this problem, only my ability to speak English makes it difficult for me sometimes. If you want, let's try again step by step, you can call me on Instagram for this? my instagram account name: canerorak_

hello my friend. I solved this problem for you personally. Follow the steps in screenshots
After step 2, I restart the phone without disconnecting the usb.Then I activate usb debugging mode.After entering fastboot mode, I open the mi unlock application and repeat the step in the images.If you encounter the warning I mentioned in step 2 again, press and hold the volume down + power button for 10 seconds and enter fast mode again. That's all.The unlock button has become active. Now the system recognizes my device because I have installed the drivers required for fastboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

canero said:
hello my friend. I solved this problem for you personally. Follow the steps in screenshots
After step 2, I restart the phone without disconnecting the usb.Then I activate usb debugging mode.After entering fastboot mode, I open the mi unlock application and repeat the step in the images.If you encounter the warning I mentioned in step 2 again, press and hold the volume down + power button for 10 seconds and enter fast mode again. That's all.The unlock button has become active. Now the system recognizes my device because I have installed the drivers required for fastboot
View attachment 5752897View attachment 5752899View attachment 5752901
Click to expand...
Click to collapse
Thanks for your time and effort in finding a potential solution for me.
But I hate to say that I have already tried installing Mi drivers through Mi Unlock Tool like you have suggested here. That is not the problem.

Bhavik479 said:
Thanks for your time and effort in finding a potential solution for me.
But I hate to say that I have already tried installing Mi drivers through Mi Unlock Tool like you have suggested here. That is not the problem.
Click to expand...
Click to collapse
I understand you.just clicking the install drivers button, wait for the confirmation screen and restart the phone by pressing the power button for 7 seconds without disconnecting the device from the usb.After the device is turned on, turn the usb debugging mode off and on again, and without disconnecting the usb, press and hold the volume down + power key for 7 seconds and log in to fastboot again.Close and open the mi unlock tool and apply the driver update option again. To get the correct result, use usb 2.0 port and windows 10. Even adding a new user on your computer and applying these steps from the new user account will give the correct result.

Some sentences may be wrong because I wrote with google translate. I'm doing this job, I could help you if you called me on Instagram. I don't have any free time now, take care of yourself, I hope you solve the problem

canero said:
I understand you.just clicking the install drivers button, wait for the confirmation screen and restart the phone by pressing the power button for 7 seconds without disconnecting the device from the usb.After the device is turned on, turn the usb debugging mode off and on again, and without disconnecting the usb, press and hold the volume down + power key for 7 seconds and log in to fastboot again.Close and open the mi unlock tool and apply the driver update option again. To get the correct result, use usb 2.0 port and windows 10. Even adding a new user on your computer and applying these steps from the new user account will give the correct result.
Click to expand...
Click to collapse
As far as I understood, start from fastboot connected state, check for drivers button, the dialogue will ask to reconnect, but do not reconnect. Restart phone by long pressing power button, toggle off and on USB debugging option, restart to Bootloader while still staying connected by pressing Power + Volume Down button. Fastboot shows up and it shows 'Mi Drive Installed' dialogue on screen. Re launch Mi Unlock Tool and hit Unlock option.
If this was the procedure you wanted to convey, I will say sadly it did not work. I successfully got Mi Drive Installed dialogue without disconnecting USB, but still Mi Unlock Tool shows No Device Connected upon relaunching it.

Bhavik479 said:
Anladığım kadarıyla, fastboot bağlı durumundan başlayın, sürücüleri kontrol edin buton, diyalog yeniden bağlanmayı isteyecek, ancak yeniden bağlanmayın. Güç düğmesine uzun basarak telefonu yeniden başlatın, USB hata ayıklama seçeneğini kapatıp açın, Güç + Sesi Kısma düğmesine basarak bağlı kalırken Bootloader'a yeniden başlayın. Fastboot belirir ve ekranda 'Mi Drive Yüklendi' diyaloğunu gösterir. Mi Unlock Tool'u yeniden başlatın ve Unlock seçeneğine basın.
İletmek istediğiniz prosedür buysa, ne yazık ki işe yaramadığını söyleyeceğim. USB bağlantısını kesmeden başarılı bir şekilde Mi Drive Yüklendi diyaloğunu aldım, ancak Mi Unlock Tool, yeniden başlatıldığında hala Cihaz Bağlı Değil gösteriyor.
Click to expand...
Click to collapse
Do not close the mi unlock app after you see the warning that the driver is installed.restart the fastboot mode. When doing this, remember that the usb debugging mode is turned off and the phone is connected to the computer.

Finally, reset your phone and computer and try everything from the beginning. I'm sorry if it's not solved despite everything. This problem is very annoying, don't forget to tell me if you solve it one day. Good luck