I think I've managed to successfully brick my phone through the following process...
1. boot into recovery
2. enable sideload mode
3. adb sideload the OxygenOS beta 9 image (downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_9/)
Everything went smoothly and the sideload process finished successfully. Rebooted the phone, wandered away for a bit...and now it's just a black screen that won't turn on. Plugging it into my laptop I see that is identifying itself as a QUSB__BULK device:
Code:
usb 1-1.4.4: new high-speed USB device number 18 using xhci_hcd
usb 1-1.4.4: New USB device found, idVendor=05c6, idProduct=9008
usb 1-1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.4.4: Product: QUSB__BULK
usb 1-1.4.4: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 1-1.4.4:1.0: Qualcomm USB modem converter detected
usb 1-1.4.4: Qualcomm USB modem converter now attached to ttyUSB0
What are my options at this point? All of the recovery guides I've been able to find so far start by downloading some Windows utilities, and I don't have easy access to a Windows machine.
Use the Hard Brick guide, download the full tool unbrick guide and it should work fine, follow method 2. you can find hard unbrick guide on google.
Unfortunately, the hard unbrick guide (if you mean forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/) seems to be Windows-only (it has instructions for downloading lots of Windows device drivers, etc), and as I said in my original question, I don't have a Windows machine handy.
So I have not looked alot around but I haven't seen any guides or something for Linux, but 2 ideas:
1: try that guide, maybe Linux won't need the drivers and it would work just fine.
2: you can download a windows image, install it on a Virtual Machine,unbrick your phone and then delete the VM and everything.
Is your phone's bootloader unlocked? If yes, things will much more simple.
anyway, try download full 3.2.8 ROM from OP site, boot your phone to fastboot mode and sideload it.
Related
Hello all,
I got an old 5830 Galaxy Ace I wanna hand over to a friend. I want to flash stock ROM onto it.
When I start the phone normally I can connect via USB cable and see the files on the device.
However when entering 'downloading' mode (power+volume down+home) I get the error: This device cannot start. (Code 10) "A request for the USB BOS descriptor failed." (copied from Device Manager properties of Samsung USB Composite Device). I also see this ballon pop in in the sys tray
The device does NOT show up in either Odin or Flashtool.
I am on Win 8.1 64bit laptop. I have searched and trawled the internet already and did the following:
- disabled signature verification in startup options of windows
- installed fastboot drivers via flashtool
- installed Samsung USB drivers
- tried 4 different USB ports and two different cables (and also on another laptop)
Can anyone give me a suggestion. I have not found 5830 specific USB drivers for example (nor do I know if they even exist). Any help is appreciated!
Regards,
Roel
SOLVED...sort of...
I used a workaround. I used a Windows 7 computer and there it worked perfect.
roel1976 said:
Hello all,
I got an old 5830 Galaxy Ace I wanna hand over to a friend. I want to flash stock ROM onto it.
When I start the phone normally I can connect via USB cable and see the files on the device.
However when entering 'downloading' mode (power+volume down+home) I get the error: This device cannot start. (Code 10) "A request for the USB BOS descriptor failed." (copied from Device Manager properties of Samsung USB Composite Device). I also see this ballon pop in in the sys tray
The device does NOT show up in either Odin or Flashtool.
I am on Win 8.1 64bit laptop. I have searched and trawled the internet already and did the following:
- disabled signature verification in startup options of windows
- installed fastboot drivers via flashtool
- installed Samsung USB drivers
- tried 4 different USB ports and two different cables (and also on another laptop)
Can anyone give me a suggestion. I have not found 5830 specific USB drivers for example (nor do I know if they even exist). Any help is appreciated!
Regards,
Roel
Click to expand...
Click to collapse
hi, i had same USB problem, windows7 worked for this old phone
After installing the dual boot bios on my teclast air III (M5C5) I tried to install Windows. Unfortunately, just before completion the installation was cancelled because of the following error: "Windows could not update the computer's boot configuration. Installation cannot proceed."
If I start my tablet and choose Windows, I get the following Recovery page:
The boot configuration data file is missing some required information.
File:\BCD
Error code: 0x0c0000034
You'll need to use recovery tools, if you don't have them...
Press the WIndows key for UEFI Firmware Settings
Click to expand...
Click to collapse
Of course I've tried to press the Windows key, but nothing happens. I've tried all keys and several common combinations, but none of them did anything, except spamming Ctrl-Alt-Delete, which forced a shutdown.
I can enter the BIOS, but for some reason there's no option to select Boot from USB stick (only UEFI OS and Windows Boot Manager). The strange thing is that I've used this usb stick to install Windows on the tablet in the first place and I've tried both GPT and MBR and used a usb 2.0 stick in a 2.0 hub, so the usb stick shouldn't be the problem I guess.
But probably even worse is that I cannot get into DNX mode anymore, so I can't install Android either. If I try I get the following message (instead of " Waiting for fastboot commands" ):
BOM Selection Switch (SW1B1) has been changed, but cannot take action. system will reset in 3 seconds
Click to expand...
Click to collapse
For some reason there is not much information about this error message and I could not find solutions to a similar problem ("BOM selection switch SW1B1 has changed Force_Windows"). In a desperate attempt I've tried to enable fastboot in BIOS to see if that would make a difference, but it doesn't.
Any help is welcome, thanks in advance!
Are U sure you have flashed/installed the right BIOS/Firmware ? double check it !
Also if your USB drive is USB3.0 your hub must be 3.0 too OR you must connect the USB drive directly to the OTG cable.
Mikha777 said:
Are U sure you have flashed/installed the right BIOS/Firmware ? double check it !
Also if your USB drive is USB3.0 your hub must be 3.0 too OR you must connect the USB drive directly to the OTG cable.
Click to expand...
Click to collapse
It was a 2.0 drive in a 2.0 hub. But I've tried with a usb 3.0 stick in a 3.0 hub as well and that doesn't work either.
I've had some problems flashing the BIOS. Initially I tried the simple method using the UpdateIFWI app (using the Mirek V7 rom and downloaded the UpdateIFWI app seperately) with the bios "Dualboot Bios Tested C6J6 And C8J7" from here, but that didn't work. Then I used the Mirek's flash tool to update the BIOS and unfortunately selected the latest version, which apparently is not compatible. Luckily DNX mode worked and I could use the tool in this thread to flash the correct BIOS. I used the dualboot bios from techtablets. It finished with FPT operation passed, but did not automatically reboot. After manually rebooting, it launched the screen with the options Android and a small Windows logo. I selected Windows and it started the Windows installer from the USB stick and the rest I've described above. If I start my tablet now, the Android and Windows logo are equally large (so it did install a part of Windows?). Unfortunately I haven't checked if DNX mode worked between flashing Dual boot and installing Windows.
I've ordered an USB programmer already
Hi folks, lately I wanted to root my phone to disable annoying storage shortage popups, and chose path of TWRP (twrp-3.2.2-0-rolex) + SuperSU (SR5-SuperSU-v2.82-SR5-20171001224502)
But after I flashed recovery partition with fastboot I wasn't able to boot my device, was continuously seeing MI logo.
By the way after I flashed recovery partition I checked boxes to install TWRP app.
I was following instructions in this thread: https://forum.xda-developers.com/redmi-4a/how-to/root-redmi-4a-t3726735
But as a result I wasn't able to boot my device, after some more lookup in one of forums I read that problem could be solved by replacing aboot system file with file provided by author.
Problem is that that file was prepared for Redmi 3S, while mine is 4A.
As a result I have totally bricked phone, which doesn't want to boot, even display is not turning on.
After leaving phone for few days, i started to see that hope as red LED light on home button was blinking when holding power button.
Now in my Linux machine I see these logs:
usb 1-2: new high-speed USB device number 9 using xhci_hcd
usb 1-2: New USB device found, idVendor=05c6, idProduct=900e
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: QHSUSB__BULK
usb 1-2: Manufacturer: Qualcomm CDMA Technologies MSM
Anyone have idea how I can get access to internal storage again?
I want to replace that aboot file with original one, and continue solving ROOTing issue.
Thanks in advance!
clumsywalker said:
Hi folks, lately I wanted to root my phone to disable annoying storage shortage popups, and chose path of TWRP (twrp-3.2.2-0-rolex) + SuperSU (SR5-SuperSU-v2.82-SR5-20171001224502)
But after I flashed recovery partition with fastboot I wasn't able to boot my device, was continuously seeing MI logo.
By the way after I flashed recovery partition I checked boxes to install TWRP app.
I was following instructions in this thread: https://forum.xda-developers.com/redmi-4a/how-to/root-redmi-4a-t3726735
But as a result I wasn't able to boot my device, after some more lookup in one of forums I read that problem could be solved by replacing aboot system file with file provided by author.
Problem is that that file was prepared for Redmi 3S, while mine is 4A.
As a result I have totally bricked phone, which doesn't want to boot, even display is not turning on.
After leaving phone for few days, i started to see that hope as red LED light on home button was blinking when holding power button.
Now in my Linux machine I see these logs:
usb 1-2: new high-speed USB device number 9 using xhci_hcd
usb 1-2: New USB device found, idVendor=05c6, idProduct=900e
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: QHSUSB__BULK
usb 1-2: Manufacturer: Qualcomm CDMA Technologies MSM
Anyone have idea how I can get access to internal storage again?
I want to replace that aboot file with original one, and continue solving ROOTing issue.
Thanks in advance!
Click to expand...
Click to collapse
Your better choice must be flash with fastboot method. You did some mistakes its better do a clean flash. If you have some sensors or wifi issues after that you must do a edl mode flash.
Your problem was you don't flashed lazyflasher to remove the crypto of the data partition
manucarcor said:
Your better choice must be flash with fastboot method. You did some mistakes its better do a clean flash. If you have some sensors or wifi issues after that you must do a edl mode flash.
Your problem was you don't flashed lazyflasher to remove the crypto of the data partition
Click to expand...
Click to collapse
Try with test point. I do before when i put miui 10 for mi 6.
Did you fix it?
If not then short the test point . In your device manager on the PC you make sure that there is Qualcomm hs-usb qdloader 9008 port and use a old version of Mi Flash tool 2015 because latest version of Mi Flash tool can't detect it after that download the Global ROM flash it via MI Flash tool and get the magic done make sure you select flash all .....
Complete Wipe system , dalvik and cache , also vendor , data too and Install ROM as new ...
I was trying to reflash the system ROM, and accidentally canceled the ./flash_all script... Now, when I connect my phone, dmesg -w running on my host (Arch Linux) returns this:
HTML:
[22650.389556] usb 3-1.3: new high-speed USB device number 73 using xhci_hcd
[22650.485540] usb 3-1.3: New USB device found, idVendor=05c6, idProduct=9008, bcdDevice= 0.00
[22650.485542] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[22650.485543] usb 3-1.3: Product: QUSB_BULK_CID:0402_SN:301E7E84
[22650.485544] usb 3-1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[22650.492441] qcserial 3-1.3:1.0: Qualcomm USB modem converter detected
[22650.492528] usb 3-1.3: Qualcomm USB modem converter now attached to ttyUSB0
Update: So I've discovered now that my phone is apparently in Qualcomm's QDL, or Emergency Download mode... I found a tool here that apparently allows you to flash an image to a device running in this mode...
Were you able to unbrick your phone?
peneoark said:
Were you able to unbrick your phone?
Click to expand...
Click to collapse
Not yet...
same problem here, i tried install new update and now my phone don't turn on, only appears Qualcomm HS-USB 9008 when connecting usb
So apparently I never updated this thread... I ended up just RMAing my phone, but this is the bug that bricked my phone: https://bugs.archlinux.org/task/63370
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
davidw.roggenkamp said:
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
Click to expand...
Click to collapse
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
waiflih said:
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
Click to expand...
Click to collapse
I installed and used ADB into Linux Mint 20; but it ended with the same result.
davidw.roggenkamp said:
I installed and used ADB into Linux Mint 20; but it ended with the same result.
Click to expand...
Click to collapse
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
reg66 said:
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
Click to expand...
Click to collapse
Tried this with the same result.
https://adbdriver.com/downloads/
Plug your phone on side port and reboot to fastboot then use this app to fix fastboot mode
If you already plugged the USB cable to the side port and still not able to use fastboot, it is probably a Windows problem. The Android fastboot exe is not properly signed so you need to disable Windows' driver signature check before installing the ADB/Fastboot drivers.
I cannot post link but search for "android fastboot driver disable driver signature enforcement". Disable the signature check then install the fastboot drivers.
Here is the quick run-down of the steps.
1. In command console and in Admin mode, run this command and then restart => bcdedit /set testsigning on
2. Install adb and fastboot stuff
3. After successful install, in command console and in Admin mode, run this command and then restart => bcdedit /set testsigning off
For ADB/Fastboot driver, i use the one by "fawazahmed0" here in XDA. The title of the thread is [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows.
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
davidw.roggenkamp said:
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
Click to expand...
Click to collapse
Are you sure your using the side port ?
Created a new topic, disregard