Database Info

[Q][Help]Nexus S major problems

SOLVED
Well I hope my Nexus S didn't brick. Well I will start off with what happened. I've been running ICS Slim for a while and I noticed it started to become very buggy. Been busy for a few days so I havnt had time to fix anything. Well today I had some free time so I was going to just connect my SNS to my pc to transfer important files and pictures. My PC (Windows 7) kept giving me "USB Device not recognised" errors. I have correctly installed the adb drivers and have connected my SNS to the same computer. I also tried another connection usb cable to see if my original was defective but no avail. I also tried my netbook with both usb cords becuase I also had this SNS connected to the netbook before (Win7 Also) with correct adb drivers.... still nothing. I then go to rom manager download codename android and successfully install the rom. Tried everything again and still no connection. After shutting down the SNS and strating it again multiple times and trying multiple things my SNS went into "safe mode". Curious I thought there must be something wrong with some system files that don't get written over when a new rom is installed with a factory reset. I decided to turn off my SNS and turn it on one more time and I get this screen which ive never seen before.
{
"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"
}
It also says between Downloading.... and Do not turn off target!!!!:
USB Control Init
USB Control Init end
Please help because I need this phone for work and I cannot afford a new one... Just really hope it didnt bite the dust.
Samsung Nexus S i9020a Koodo
FIX:
had the same problem. DEFINITELY FIXED NOW.
Whenever, I connected my Nexus S to any OS a USB Storage Mode dialogue used to pop up and once I clicked Turn On, the PC would find the mass storage. About a week ago, this functionality has stopped completely. I plug the USB cable and nothing happens but the phone starts charging.
I have read many posts about this. I have tried the removing the battery, Rebooting, Trying the boot loader screen, erasing the USB storage, resetting to factory settings, Erasing and dismounting the SD Card from the Boot loader, cleaning the USB Port, trying different USB cables (nokia, parrot, original Nexus etc)....
What has worked for me was the NEEDLE trick. Get a needle and bend the USB hub beneath the phone towards to the top. (What I realized is that it was pushed all the way to the bottom, lifting it up about 1 mm has centered it). I plug the USB and pops up the USB storage mode interface.
So, it turns out a hardware issue, probably a doggy USB port on the NEXUS easily gets disturbed. Using different cables usually helps the problem, especially cheap cables tend to damage the port easier.
So, I would recommend every one to use proper USB cables; the original nexus cable, a nokia cable or decent quality cable. (Do not use the ones from cheap car chargers etc).
Secondly, do not reset your phone for nothing.
Thirdly, keep your phone clean.
I hope this information helps someone. Thanks.
Click to expand...
Click to collapse
source: http://www.google.com/support/forum/p/Google Mobile/thread?tid=4dedeb14b7ccb58e&hl=en

Update: Decided to turn off the Nexus S..... Stupid idea I guess because It wont turn on any more.... Plugging into a computer still says "USB Device not recognised" though so I have no clue...
Would really love some help please

Can you get into recovery? Or Hboot?

rocket999 said:
Can you get into recovery? Or Hboot?
Click to expand...
Click to collapse
No recover. Whats Hboot? No fastboot screen... So I thinks its dead.

Trying unbrickable resurrector but cannot find device
Desperate need of help please

do you have CWM installed on your nexus??
use mount/storage then connect it to Computer

galaxy tab p1000
this screen shot is the same of download mode in the galaxy tab p 1000, in this mode, with program "ODIN" you can put in your device the rom, kernel and radio! ww w.team overcome.net/p1000/?page_id=17 this is a guide for flash the p1000, i don't know if that function for NS ! I'm sorry.

[Q][Help]USB Problems
I just removed my simcard and reinserted it again and my phone started normally.... weird...
But still at problem #1. Cannot mount usb. Windows 7 Still says "USB device not Recognised". My guess is that the usb port is broken. Its quite common apparently so i'm gunna see if Koodo will fix it.
Before I send it in should I go to a stock rom, stock baseband, and lock bootloader. or can I send it in with CyanogenMod 9?

Tw1tchy said:
I just removed my simcard and reinserted it again and my phone started normally.... weird...
But still at problem #1. Cannot mount usb. Windows 7 Still says "USB device not Recognised". My guess is that the usb port is broken. Its quite common apparently so i'm gunna see if Koodo will fix it.
Before I send it in should I go to a stock rom, stock baseband, and lock bootloader. or can I send it in with CyanogenMod 9?
Click to expand...
Click to collapse
go back to stock and lock bootloader so they wont void your warranty

sean1984 said:
go back to stock and lock bootloader so they wont void your warranty
Click to expand...
Click to collapse
Thx but I fixed my USB port myself ! But if I ever have problems again I will remember what you said.
Posted my fix on the OP

nexus s usb not recognized
sir, plz help me i have a nexus s i9023 i have tired everything like format system boot sd card cache everything so i think that my nexus s should recognized windows after thes. but now nothing effect and i can acces anythink just fastboot or clockwork mod recovery i have also noticed that when i pluged usb cable on nexus s with computer it stays on charging but after on fastboot my laptop not recognized my nexus s but the charging option is enable so i can ensure that there is no hardware problem i have charged nexus s through data cable but not recognized on coclworkmod i have also try to unmout sd card or usbstorage but nothing effect plz help me

Thanks for the thread.
" Needle trick " worked perfect. [ lifting the usb charging pin - with a needle - on the phone so its center. ]

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

Huawei P30 (ELE-L29 EMUI 11.0.0.159 C431) Testpoint Mode

Hi, I want to unlock bootloader of my phome and root it via Magisk method. But recently I've discovered that there is no way to unlock bootloader when you upgraded to EMUI 11. Dc-Phoenix + HCU doesn't support after EMUI 10 software testpoint. So the only way is try to Hardware testpoint method. I disassembled the phone and reach the motherboard and testpoint pin without damaged it. I short the testpoint pin with metal ground, plugged the USB and managed to enable the testpoint mode (the screen was black.) But then I saw my computer cannot detect my phone in testpoint mode, there is no "Huawei USB COM 1.0" or "USB Ser". I find drivers for Huawei USB COM 1.0 but still no change at all. I check the "Device Manager -> Install Legacy Driver -> Install From Disc" but there is no Huawei Incorporated drivers. I think my PC's problem that cannot detect my device in testpoint mode is the drivers. Here is what I did step by step;
1- Battery fulled and power off, phones back cover removed carefully and reached the mothet board. Testpoint pin founded.
2- Huawei USB COM 1.0 drivers installed to PC (driver file from PotatoNV GitHub page.)
3- USB-A side plugged to PC and USB-C side is waiting
4- A conductive metal tool (mine is pointed tweezer) grabbed and shorted to pin to metal ground and I keep them so.
5- While keeping the testpoint shorted, I plugged the USB-C side to phone and waited couple of second.
Then when I look at the PC, there is no change. No device detected. First, I was think that I couldn't manage the testpoint shorting but when I plugged the Phone to PC without shorting, the Huawei boot screen appears. When I short the testpoint and plugged it, the screen is black which means the device is in test point mode. But then, PC is not detecting my phone. So my guess is that the problem is the drivers.
EDIT: I find out I could use the HiSuite Proxy app to downgrade from EMUI 11 to EMUI 10 so I can use the DC-Phoenix + HCU, but I tried this method before disassembling the phone. It didn't work that time. 2 days ago, I tried again this method to downgrade and use the software testpoint and I successfully downgraded it. The problem was HiSuite 10.0.0.550 cannot flash EMUI 11 but HiSuite 10.1.... can flash EMUI 11. I was in 11.0.0.159 firmware version and downgraded to 10.1.0.150 firmware version.
After that day, I decided to start to unlock method by DC-Phoenix and HCU but before buying timed licence I want to be sure that everything is okey. First, I plugged to phone to PC and that is the end of the way. There is no way to connecting PC after downgrade. I searched it from XDA and find out that after some security patchs or firmware versions if you try to downgrade, your USB activities are locked. And when you reach to latest version (version before I downgrade from), USB problem is solved. This is about the Huawei's new security patch, I guess. Many of Huawei P40 user is complaining about same problem. They are telling that in P40 after 11.0.0.180 update, if they try to downgrade, there USB functions are limited (no fast charge, no OTG or USB driver, no PC connecting). So, if you're using your Huawei phone and you are in EMUI 11 and after some update you will be get this problem too. There is no way to unlock bootloader or root on EMUI 11. There is no way to downgrade. But I searched and find out that you can flash any stock rom by SigmaKey. It is very expensive but you can flash stock rom to downgrade. You need just dload files (that 3 zips) and unzip the update.app and ptable.app files. Do that for 3 zip packages. And you can flash roms without any problem.
What I tried and discovered is dload method won't work this USB problem. Everyone knows that you can't downgrade from EMUI 11 by dload method. I downgrade with HiSuite Proxy to EMUI 10.1.0.150 and after downgrade I tried to dload method to upgrade firmware to 10.1.0.161. Dload is failed in %94 and I restarted device. The version is upgraded to 10.1.0.161 and all user data formatted but USB problem is not solved. When I upgraded to latest firmware, the problem is solved. But I want to downgrade without any problem and root this phone.
My biggest advice to anyone who have the Huawei phone, DO NOT UPGRADE YOUR PHONE WITHOUT SEARCHING THE NEW VERSION. IT IS LIKE HUAWEI FORCING EVERYONE TO UPGRADING THERE PHONE OR CANNOT DOWNGRADE TO ANY FRIMWARE.
Does anyone has same problem with me? What is the solution for this? I removed the back of the phone for nothing. I have to unlock the bootloader and root this device. I would really appreciated if you can help me.

Are there any updates on how to fix this?
I managed to find a way to flash a custom rom on p30, GSI... But when i tried to downgrade to unlock my bootloader with hcu and dcu using soft test point, i was stuck with this problem. No usb, no fastboot, no test point. They locked us in a cage. If someone knows how to fix this, i will be more than happy to post a tutorial for all the huawei users on how to unlock their bootloaders and flash a custom rom. Cheers!

You need a special cable for the phone to be detected in COM 1.0 mode on device with patched bootloader. Search for "huawei com 1.0 cable" on Google for a way to modify regular USB-C cable.

you need a modified cable like this one to enter to com 1.0
first make jumper test point cable then insert cable to your pc
and done
{
"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"
}

Hello, I have a problem with my Huawei P30. And nothing else. I can go to fastboot mode, I can also do a test point. But nothing more. With UnlockTool software, I wanted to upgrade the phone, but during the update, I had a problem. He gives me this as my phone version. (Unlock Tool).
So I try to update with firmwares without any idea of the right firmware to download.
I NEED HELP PLEASE.

Question [Fixed] Issue with MSM tool on LE2110

EDIT: Solution here https://forum.xda-developers.com/t/fixed-issue-with-msm-tool-on-le2110.4452133/post-86963931
Hi everyone, after hours of internet searches and scratching my head trying different methods over and over, I've decided to post here asking for help since I'm totally lost.
First of all, I got a bricked Oneplus 9 LE2110 (chinese model) that I'm trying to restore to any semblance of operation.
I've followed this FizzyAps tutorial https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
I got the drivers installed and MDM recognizes the device.
{
"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"
}
The first weird behavior I have is that whenever every 10 seconds or so, the device disconnects from the computer, then automatically reconnects again (I get the windows sound of a new usb device plugged in and out, and also the device is removed from the device manager and MSM).
Anyway, whenever I try to flash the phone with the configuration above, I get one of the following errors:
The dreaded "Sahara Communication Failed" If I just follow the tutorial to the letter.
If I hold volume UP+DOWN pressed at all times after connecting the phone, the error I get is different;
As a last resort, I tried using the Lite Firehose checkbox, but then it MSM prompts that the image does not match the device:
I was unable to find an image for LE2110 anywhere on the internet, but according to reports from other forum posts, the firmware I'm using (lemonade_22_O.07_210412.ops) should work.
Anyway, if anyone has a OEM LE2110 image that can be shared, it would be helpful.
Can anyone help me fix this issue?
Worth mentioning that I've tried multiple different USB ports, but I'm not using the OEM cable since my computer does not have a USB-C port, and the cable which came with the phone is USB-C on both ends. I'm using a high quality USB 3.1 cable instead.
Windows firewall and antivirus are disabled while trying to flash the phone.
About booting into EDL, the phone does not give any cue, as I just get an unlit black screen at all times, even when the device is recognized as QDLoader9008. I tried powering it off first by holding power for 15 seconds and even let the battery dry for a month, but when trying again the results were the same.

Replying to myself to confirm that this zip fixes the issue with the default configuration:
ONE PLUS 9 EU MSM TOOL TESTED
This was a Untested MSM .OPS file for the EU Variant use at your own risk. This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof. This will fail verification when pressing...
forum.xda-developers.com
Anyone with LE2110 don't use FizzyApps tutorial or files, please use this link instead.

GryphusR said:
Replying to myself to confirm that this zip fixes the issue with the default configuration:
ONE PLUS 9 EU MSM TOOL TESTED
This was a Untested MSM .OPS file for the EU Variant use at your own risk. This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof. This will fail verification when pressing...
forum.xda-developers.com
Anyone with LE2110 don't use FizzyApps tutorial or files, please use this link instead.
Click to expand...
Click to collapse
Interesting. Sounds like the tool posted there may be a universal MSM like the Indian 9 Pro's then because it shouldn't have worked for your device either if it was a Chinese variant.

EtherealRemnant said:
Interesting. Sounds like the tool posted there may be a universal MSM like the Indian 9 Pro's then because it shouldn't have worked for your device either if it was a Chinese variant.
Click to expand...
Click to collapse
I was also surprised because I got the phone bricked on the first place by trying to flash an EU ROM instead than the Global ROM. But since another person with a LE2110 said it worked, I decided to give it a try and indeed it worked at the first attempt.
On the original FizzyApps thread, someone said that LE2110 also work, but for whatever reason it does not. Being a Chinese variant it would not surprise me if there are different "revisions" of LE2110 model number, and perhaps some are incompatible with older versions of the FW

GryphusR said:
EDIT: Solution here https://forum.xda-developers.com/t/fixed-issue-with-msm-tool-on-le2110.4452133/post-86963931
Hi everyone, after hours of internet searches and scratching my head trying different methods over and over, I've decided to post here asking for help since I'm totally lost.
First of all, I got a bricked Oneplus 9 LE2110 (chinese model) that I'm trying to restore to any semblance of operation.
I've followed this FizzyAps tutorial https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
I got the drivers installed and MDM recognizes the device.
View attachment 5626537
View attachment 5626541
The first weird behavior I have is that whenever every 10 seconds or so, the device disconnects from the computer, then automatically reconnects again (I get the windows sound of a new usb device plugged in and out, and also the device is removed from the device manager and MSM).
Anyway, whenever I try to flash the phone with the configuration above, I get one of the following errors:
The dreaded "Sahara Communication Failed" If I just follow the tutorial to the letter.
View attachment 5626547
If I hold volume UP+DOWN pressed at all times after connecting the phone, the error I get is different;
View attachment 5626549
As a last resort, I tried using the Lite Firehose checkbox, but then it MSM prompts that the image does not match the device:
View attachment 5626551
I was unable to find an image for LE2110 anywhere on the internet, but according to reports from other forum posts, the firmware I'm using (lemonade_22_O.07_210412.ops) should work.
Anyway, if anyone has a OEM LE2110 image that can be shared, it would be helpful.
Can anyone help me fix this issue?
Worth mentioning that I've tried multiple different USB ports, but I'm not using the OEM cable since my computer does not have a USB-C port, and the cable which came with the phone is USB-C on both ends. I'm using a high quality USB 3.1 cable instead.
Windows firewall and antivirus are disabled while trying to flash the phone.
About booting into EDL, the phone does not give any cue, as I just get an unlit black screen at all times, even when the device is recognized as QDLoader9008. I tried powering it off first by holding power for 15 seconds and even let the battery dry for a month, but when trying again the results were the same.
Click to expand...
Click to collapse

It meant to have a black screen in edl mode, I got driver from op remote flash team & MSM tool which worked on op9 & pro version of global. Mine a le2110 too . I still had bugs after flashing global so the remote team flashed it with Chinese ROM & I flashed it back to oxygen using fizzys ROM , works great now but after updating OTA it says my device is a le2115 OP said that's normal , here's link m8 https://mega.nz/folder/wTZRkKyA#q146JvIeKkD2B6qnIN9F2Q
I had problem with driver because I got AMD CPU, always use original cable when flashing , I keep one for that , it's a signed driver as well

It worked one month ago, but I played with my phone again and this MSM tool doesnt work now even with the same cable (now im trying different cables) in the same port i used last time
it fails at Firehose GetUfsInfo but if i continue holding volume+, it will get to FirehoseCheckRSP Failed Errno 258

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.