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

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 Poco x3 Pro Hardbricked!

after i got into Fastboot Mode for a Longtime about 30mins.. my Phone got blackscreen and no sign of Light even in Notification Light. i tried to turn it on holding the Power Button for about 30sec or more it doesnt do anything.. soo i go to Device Manager and i see in ports that the Phone is detected with labaled name "Qualcom SDH 9008" and installed MiFlash Tool, and i was trying to Flash it when i press Refresh it detects as "COM3" after searching on YouTube for lot of many ways i didnt find any solution like FireHose File to bypass MiFlash Auth. but i didnt see anything for Poco x3 Pro. no luck!
i already TestPoint the back of the Phone but the only Prob is the Auth thing in account to Proceed to Update firmare file .tgz
can someome help me pleaseee its been Day 4 of searching and still no luck! my Phone is sleeping for 4days now. and i dont have any Phone. im from Philippines by the way.
{
"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"
}

PHnambawan said:
after i got into Fastboot Mode for a Longtime about 30mins.. my Phone got blackscreen and no sign of Light even in Notification Light. i tried to turn it on holding the Power Button for about 30sec or more it doesnt do anything.. soo i go to Device Manager and i see in ports that the Phone is detected with labaled name "Qualcom SDH 9008" and installed MiFlash Tool, and i was trying to Flash it when i press Refresh it detects as "COM3" after searching on YouTube for lot of many ways i didnt find any solution like FireHose File to bypass MiFlash Auth. but i didnt see anything for Poco x3 Pro. no luck!
i already TestPoint the back of the Phone but the only Prob is the Auth thing in account to Proceed to Update firmare file .tgz
can someome help me pleaseee its been Day 4 of searching and still no luck! my Phone is sleeping for 4days now. and i dont have any Phone. im from Philippines by the way.
View attachment 5333005
Click to expand...
Click to collapse
Listen to me carefully extract the .tgz file in a folder and download platform tools from the web and also extract platform tools files also in the same folder where you extracted the .tgz files after keeping both file extraction in a folder then turn your phone in. Fastboot mode and plug in and run the flash all .bat file it gonna take around 10-15 minutes and your device will recover

Did it solve your problem??

You are most likely in EDL mode. In order to get out of it, you need to snap off the battery and connect it back. Perhaps no flashing is needed

You can try to find authorized user patch for miflash somewhere on net but don't get your hope up as poco is relatively new

oleg.ignatov2011 said:
You are most likely in EDL mode. In order to get out of it, you need to snap off the battery and connect it back. Perhaps no flashing is needed
Click to expand...
Click to collapse
Does this method really work? im on Redmi Note 9 Pro, Hardbricked as well, and also stuck at edl authentication ehrn attempting to flash fastboot rom

oleg.ignatov2011 said:
You are most likely in EDL mode. In order to get out of it, you need to snap off the battery and connect it back. Perhaps no flashing is needed
Click to expand...
Click to collapse
Does This Method Work? Im on Redmi Note 9 pro hardbricked as well, I Also cant get past to Edl Authentication

Did you resolve the issues. and method used. I am also stucked in the same.
kiyookusanagi said:
Does This Method Work? Im on Redmi Note 9 pro hardbricked as well, I Also cant get past to Edl Authenticatio
Click to expand...
Click to collapse

If your computer is detected as QH 9008 or similar, it seems to be more of a hardware fault than a software one, since it indicates that the CPU is not having good communication with the UFS memory.

PHnambawan said:
i already TestPoint the back of the Phone but the only Prob is the Auth thing in account to Proceed to Update firmare file .tgz
Click to expand...
Click to collapse
How did you do this?
Can you explain the process step by step, pls.
I've tried with several different ways but no one works. Phone isn't getting in EDL.

Realme 5i phone dead but can be detected in Windows 10

So i was trying to install twrp and it failed and the phone displayed this "the current image(boot/recovery) have been destroyed" and keeps turning on and off. Later it restarts and got stuck in the logo "Realme with powered by Android". I don't know what happened. I can't press volume up and power button. So I waited till it drains its battery. So I tried charging it back and it shows charging red. Then when it reaches to a point where it can turn on, It got stuck in the charging white logo thingy and it wont let me do anything.
But after a few tries it finally wont turn on.
I tried connecting it to the computer and somehow it shows an unknown driver.
QUSB_BULK_CID:0411_SN:B3336417
{
"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"
}
I have no idea what that is but I know that "B3336417" is the ID of the phone.
Can anyone help me how to fix this phone?

Assuming you've correctly installed ADB driver on Windows 10 then if USB Debugging didn't get enabled on phone you'll NOT see the phone in Windows' Device Manager under Portable Devices - where it should be shown.

Try installing MTK Drivers, it should fix the problem
EDIT: Then flash Stock ROM using SP Flash Tool V5

jwoegerbauer said:
Assuming you've correctly installed ADB driver on Windows 10 then if USB Debugging didn't get enabled on phone you'll NOT see the phone in Windows' Device Manager under Portable Devices - where it should be shown.
Click to expand...
Click to collapse
I pressed volume up + volume down + power button and it takes me to fastboot mode. Do you know how to restore back the phone? where can I find the stock rom for realme 5i?

NoveNoki said:
Try installing MTK Drivers, it should fix the problem
EDIT: Then flash Stock ROM using SP Flash Tool V5
Click to expand...
Click to collapse
I pressed volume up + volume down + power button and it takes me to fastboot mode. Do you know how to restore back the phone? where can I find the stock rom for realme 5i?

Grim Face said:
I pressed volume up + volume down + power button and it takes me to fastboot mode. Do you know how to restore back the phone? where can I find the stock rom for realme 5i?
Click to expand...
Click to collapse
Here are official ROM files from all Realme phones: https://www.realme.com/eu/support/software-update just search for your phone and you should find it, tho you will need a computer so you can flash the files
EDIT: Do you know if your device uses MediaTek chip?

NoveNoki said:
Here are official ROM files from all Realme phones: https://www.realme.com/eu/support/software-update just search for your phone and you should find it, tho you will need a computer so you can flash the files
EDIT: Do you know if your device uses MediaTek chip?
Click to expand...
Click to collapse
My phone uses Snapdragon but I finally have OrangeFox recovery

NoveNoki said:
Here are official ROM files from all Realme phones: https://www.realme.com/eu/support/software-update just search for your phone and you should find it, tho you will need a computer so you can flash the files
EDIT: Do you know if your device uses MediaTek chip?
Click to expand...
Click to collapse
Can I flash my rom to the Orange Fox Recovery mode? It seems that my OS is gone.

Grim Face said:
Can I flash my rom to the Orange Fox Recovery mode? It seems that my OS is gone.
Click to expand...
Click to collapse
I think you should be able to, i am not too sure. But i whould recommend you to flash it manually using the fastboot mode, tho if you can try flashing it from the recovery

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.