Related
Here's the problem..my Nexus S power button isn't working, so I was using other hardware keys to shut down, turn on and such. Now I got into a problem. I installed chainfire3d drivers and now the phone won't boot and since my power button is broken, I can't access recovery. I can get into fastboot but the volume up/volume down buttons won't work so I can't select the option "RECOVERY" plus my PC doesn't recognize that my phone is in fastboot (I'm using Windows 8, 64bit.)
Can someone help me with this, if it's possible? How do I get into recovery?
Thank you in advance.
SlashSpeed said:
Here's the problem..my Nexus S power button isn't working, so I was using other hardware keys to shut down, turn on and such. Now I got into a problem. I installed chainfire3d drivers and now the phone won't boot and since my power button is broken, I can't access recovery. I can get into fastboot but the volume up/volume down buttons won't work so I can't select the option "RECOVERY" plus my PC doesn't recognize that my phone is in fastboot (I'm using Windows 8, 64bit.)
Can someone help me with this, if it's possible? How do I get into recovery?
Thank you in advance.
Click to expand...
Click to collapse
There might be several solutions to your problem. According to what youve written it seems that the powerbutton is stuck in the "ON" position, right? Meaning that the phone turns on when you insert the battery. It would also mean that in bootloader you cant select anything because the powerbutton is "pressed". Sadly if this is the case, having properly working drivers wouldnt help since phone wont be detected until the powerbutton is in the "OFF" position.
Case 1: powerbutton in "ON" position
Solution 1: Send your phone to repair. Sadly you will have to pay for that since your warranty is void (unlocking the bootloader voids the warranty as far as i know". Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Solution 2: Since your warranty is void, do it yourself. NS disassembly is quite easy and theres nothing to be afraid of. In this case theres just some dust so once you také it appart and clean the powerbutton it should work again. Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Case 2: powerbutton in "OFF" position
There are plenty of tutorials around here on getting drivers to work. General advice would be reinstall the drivers, try different ports, try to do it from other computer.
Hope this helps, good luck
cahir_cz said:
There might be several solutions to your problem. According to what youve written it seems that the powerbutton is stuck in the "ON" position, right? Meaning that the phone turns on when you insert the battery. It would also mean that in bootloader you cant select anything because the powerbutton is "pressed". Sadly if this is the case, having properly working drivers wouldnt help since phone wont be detected until the powerbutton is in the "OFF" position.
Case 1: powerbutton in "ON" position
Solution 1: Send your phone to repair. Sadly you will have to pay for that since your warranty is void (unlocking the bootloader voids the warranty as far as i know". Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Solution 2: Since your warranty is void, do it yourself. NS disassembly is quite easy and theres nothing to be afraid of. In this case theres just some dust so once you také it appart and clean the powerbutton it should work again. Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Case 2: powerbutton in "OFF" position
There are plenty of tutorials around here on getting drivers to work. General advice would be reinstall the drivers, try different ports, try to do it from other computer.
Hope this helps, good luck
Click to expand...
Click to collapse
Hey, thanks for the help, much appreciated. I'll try to open the case and clean the power button if possible and see if it's gonna work then.
On the other note, after 3 hours of searching I finally found the right solution. When on the Google screen, Windows recognized the phone as "Nexus". I clicked on it in device manager and installed Android ADB interface driver (which I downloaded via SDK manager). Windows then recognized the device in cmd via adb and I could reboot into recovery with the command "adb reboot recovery".
What a relief! :victory:
SlashSpeed said:
Hey, thanks for the help, much appreciated. I'll try to open the case and clean the power button if possible and see if it's gonna work then.
On the other note, after 3 hours of searching I finally found the right solution. When on the Google screen, Windows recognized the phone as "Nexus". I clicked on it in device manager and installed Android ADB interface driver (which I downloaded via SDK manager). Windows then recognized the device in cmd via adb and I could reboot into recovery with the command "adb reboot recovery".
What a relief! :victory:
Click to expand...
Click to collapse
Congratulations Never knew you can use adb while booting Good luck with the cleaning
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
SlashSpeed said:
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
Click to expand...
Click to collapse
well get in to fastboot menu and original flash firmware
should i take u step by step? or u have some idea of fastboot?
uxmanz said:
well get in to fastboot menu and original flash firmware
should i take u step by step? or u have some idea of fastboot?
Click to expand...
Click to collapse
I can get into the fastboot menu, but I can't use the volume up/down buttons and I don't think that my computer recognizes the device in fastboot at all, because of the broken power button. If you could help me somehow, then I would really be in your debt.
SlashSpeed said:
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
Click to expand...
Click to collapse
Asking for it aren't you?
Chainfire isn't compatible with Jellybean. Seriously.
Google-file CD Gadget USB Device is what becomes detected as "Nexus" later in the boot process. Have you tired detecting devices with adb devices?
polobunny said:
Asking for it aren't you?
Chainfire isn't compatible with Jellybean. Seriously.
Google-file CD Gadget USB Device is what becomes detected as "Nexus" later in the boot process. Have you tired detecting devices with adb devices?
Click to expand...
Click to collapse
Yeah...learned it the hard way..I'm too stubborn sometimes. Chainfire3D actually worked on CM10 on the Optimus Black, seems like here it wasn't the case..
Anyway, about that, yeah, I did and it doesn't detect it. Can I somehow turn the CD gadget USB device back into Nexus, like it was before or?
SlashSpeed said:
Yeah...learned it the hard way..I'm too stubborn sometimes. Chainfire3D actually worked on CM10 on the Optimus Black, seems like here it wasn't the case..
Anyway, about that, yeah, I did and it doesn't detect it. Can I somehow turn the CD gadget USB device back into Nexus, like it was before or?
Click to expand...
Click to collapse
I believe you could always enter download mode and ODIN back to stock in the worst case scenario.
polobunny said:
I believe you could always enter download mode and ODIN back to stock in the worst case scenario.
Click to expand...
Click to collapse
I tried that, but nothing happened, I couldn't enter download mod, probably because the power button is broken and it's probably on "ON".
SlashSpeed said:
I tried that, but nothing happened, I couldn't enter download mod, probably because the power button is broken and it's probably on "ON".
Click to expand...
Click to collapse
If you can enter bootloader mode you can enter download mode.
polobunny said:
If you can enter bootloader mode you can enter download mode.
Click to expand...
Click to collapse
I can enter download mode by holding down Volume Up and Volume Down together right? It doesn't work sadly..
SlashSpeed said:
I can enter download mode by holding down Volume Up and Volume Down together right? It doesn't work sadly..
Click to expand...
Click to collapse
Make sure your phone is connected to your PC. Then hold VOL down and press power if I recall correctly. It might be both volume keys together that you hold, but either way you need to make sure you phone is connected to your computer.
polobunny said:
Make sure your phone is connected to your PC. Then hold VOL down and press power if I recall correctly. It might be both volume keys together that you hold, but either way you need to make sure you phone is connected to your computer.
Click to expand...
Click to collapse
Tried both, with just volume down and volume down + up and nothing. My phone was connected to the PC. I can only enter the bootloader..
SlashSpeed said:
Tried both, with just volume down and volume down + up and nothing. My phone was connected to the PC. I can only enter the bootloader..
Click to expand...
Click to collapse
If you hold the middle of the volume key while connecting the USB cable (not pressing power) do you see anything?
polobunny said:
If you hold the middle of the volume key while connecting the USB cable (not pressing power) do you see anything?
Click to expand...
Click to collapse
I can't do that, because as soon as I plug in the battery the phone turns on..but yeah, I tried what you said and nothing.
SlashSpeed said:
I can't do that, because as soon as I plug in the battery the phone turns on..but yeah, I tried what you said and nothing.
Click to expand...
Click to collapse
Ah obviously. I'm out of idea here, someone else might chime in. Other than making the power button work, you might have thrown yourself into a real problem this time.
polobunny said:
Ah obviously. I'm out of idea here, someone else might chime in. Other than making the power button work, you might have thrown yourself into a real problem this time.
Click to expand...
Click to collapse
If nothing else helps, I guess I'll just send it to a repair center for the power button. I wanted to do that anyway and I sadly I have a real reason.. :/
Polobunny, I appreciate your efforts though.
Edit: Took my phone to a repair center, screw it.
After using this tool you will have the chinese rom installed. (H2OS = Hydrogen OS)
Instructions how to use can be found: HERE
There is only one difference. To boot into Qualcomm download mode you need to press Volume up + Volume down when phone is powered off.
There is also a guide on YouTube. --> LINK
You can easily go to OxygenOS with official Updater app.
Just download OxygenOS OTA.zip and choose it with updater.
After reboot i personally would factory reset the phone.
Downloadlink MSMTOOL:
MEGA
Thread for OTA.zip:
Oneplus 7 Repo Oxygen OS builds
Feel free to report about your experience!
Thanks:
@Titokhan - for the Update.zip files
@Thyson - for testing the MSM Tool and reporting
@jmax91 - for the tip (tool)
@LloydSmallwood - for the unbrick guide
Finally MsmDownloadTools for our OnePlus 7. Has anyone tried it yet?
Confirmed, an XDA partner has already used it and revived his OnePlus 7 !!!
Link from partner's message:
https://forum.xda-developers.com/showpost.php?p=79989363&postcount=32
Kollachi said:
After using this tool you will have the chinese rom installed. (H2OS = Hydrogen OS)
You can easily go to OxygenOS with official Updater app.
Just download OxygenOS OTA.zip and choose it with updater.
After reboot i personally would factory reset the phone.
Downloadlink MSMTOOL:
MEGA
Thread for OTA.zip:
Oneplus 7 Repo Oxygen OS builds
Note: I didnt test it! @Thyson tried it and reported its working. Feel free to report guys.
Thanks:
@Titokhan - for the Update.zip files
@Thyson - for testing the MSM Tool and reporting
@jmax91 - for the tip (Tool)
Click to expand...
Click to collapse
Hello friend, add to your thread the steps that mark the original link of this MsMDownloadTool:
Link: https://repairmymobile.in/flash/oneplus-7-flash-file/amp/
How to Flash OnePlus 7:
1- Install Qualcomm Driver.
2- Make sure your device getting identified in device manager as Qualcomm HS-USB Diagnostic 9008.
3- Use both Volume as boot key.
4- Run MSM Download tool.
5- Click on verify, if it display message ok then you are ready to go.
6- Click on start to Flash.
7- Download Progress will be displayed.
8- When completed, Download complete will be displayed.
tURkOsANsE said:
1- Install Qualcomm Driver.
2- Make sure your device getting identified in device manager as Qualcomm HS-USB Diagnostic 9008.
3- Use both Volume as boot key.
4- Run MSM Download tool.
5- Click on verify, if it display message ok then you are ready to go.
6- Click on start to Flash.
7- Download Progress will be displayed.
8- When completed, Download complete will be displayed.
Click to expand...
Click to collapse
I think the steps should be clear. It's always the same since OnePlus 3/T. There is only one little different thing.
Kollachi said:
I think the steps should be clear. It's always the same since OnePlus 3/T. There is only one little different thing.
Click to expand...
Click to collapse
Hi friend, what is that different thing you say? Some is the first time we have a OnePlus, so we do not know.
Another question I have is that my OnePlus 7 works fine, but I wanted to see if this program recognizes me my OnePlus in case I ever need it, how can I enter the necessary mode to be detected by this program?
I press volume up and volume down and then I connect the cable, at that moment the program makes me "connected" (see attached image, left side), but after a few seconds it appears that "disconnected" and the phone restarts and OSS starts .
When I connect it, the images "Qualcomm HS-USB QDLoader 9008 (COM3) appear in the device manager.
I do not understand why my mobile when I connect it by pressing the volume buttons and without touching anything of the program it appears that connected and after a few seconds it disconnects itself and OOS restarts.
Regards, and thank you very much.
tURkOsANsE said:
Hi friend, what is that different thing you say? Some is the first time we have a OnePlus, so we do not know.
Another question I have is that my OnePlus 7 works fine, but I wanted to see if this program recognizes me my OnePlus in case I ever need it, how can I enter the necessary mode to be detected by this program?
I press volume up and volume down and then I connect the cable, at that moment the program makes me "connected" (see attached image, left side), but after a few seconds it appears that "disconnected" and the phone restarts and OSS starts .
When I connect it, the images "Qualcomm HS-USB QDLoader 9008 (COM3) appear in the device manager.
I do not understand why my mobile when I connect it by pressing the volume buttons and without touching anything of the program it appears that connected and after a few seconds it disconnects itself and OOS restarts.
Regards, and thank you very much.
Click to expand...
Click to collapse
The different part is you need to press volume up and volume down. With the older phones there was only one button. Don't remember volume up or down.
Not sure why your phone disconnecting automatically.
Kollachi said:
The different part is you need to press volume up and volume down. With the older phones there was only one button. Don't remember volume up or down.
Not sure why your phone disconnecting automatically.
Click to expand...
Click to collapse
Hi friend, could you try if the same thing happens to you?
Made the mistake of locking my bootloader directly and bricked the hell out of my standard 7. I kept getting "Your device is corrupt and it can't be trusted". No Recovery accessible, only bootloader.
Followed the steps here and everything is back to normal now!
GoToNap said:
Made the mistake of locking my bootloader directly and bricked the hell out of my standard 7. I kept getting "Your device is corrupt and it can't be trusted". No Recovery accessible, only bootloader.
Followed the steps here and everything is back to normal now!
Click to expand...
Click to collapse
Hello friend, could you help me to know why when I connect my device appears as connected and after 10 seconds it automatically restarts the OOS operating system? My phone works well, it's just a test to know if one day I have a brick to know that this program works in my case.
I would need (now that your device works, like mine) to start in a way that the program detects and looks "connected", then wait a moment and without pressing any button on the program or phone to see if it restarts alone. I am thinking that if the phone works well, the program when connected only starts the system automatically.
Read some messages above in case I have not explained myself well.
Could someone who has a good phone confirm this? Can the program attempt to automatically restart the device if the "Start" button of MsmDownloadTool is not pressed within 10 seconds?
Thanks greetings.
tURkOsANsE said:
Hi friend, could you try if the same thing happens to you?
Click to expand...
Click to collapse
Yep, same here. Maybe it's because device isn't bricked. I'm not sure about that. Never tried MSMTool when my device wasn't bricked.
Kollachi said:
Yep, same here. Maybe it's because device isn't bricked. I'm not sure about that. Never tried MSMTool when my device wasn't bricked.
Click to expand...
Click to collapse
hello, thanks for trying it, then that happens, if it is not locked it restarts, or maybe the EDL mode restarts for security if you don't press Start on the Msm tool.
---------- Post added at 12:20 PM ---------- Previous post was at 12:10 PM ----------
Indeed we have already resolved the doubt about why EDL mode is disconnected after 10 seconds. It is a security system, you have 10 seconds to press Start. here another partner who has tried it and that happened to him, until he hit start and flashed everything well.
Comrade comment: https://forum.xda-developers.com/showpost.php?p=79997414&postcount=54
tURkOsANsE said:
Hello friend, could you help me to know why when I connect my device appears as connected and after 10 seconds it automatically restarts the OOS operating system? My phone works well, it's just a test to know if one day I have a brick to know that this program works in my case.
I would need (now that your device works, like mine) to start in a way that the program detects and looks "connected", then wait a moment and without pressing any button on the program or phone to see if it restarts alone. I am thinking that if the phone works well, the program when connected only starts the system automatically.
Read some messages above in case I have not explained myself well.
Could someone who has a good phone confirm this? Can the program attempt to automatically restart the device if the "Start" button of MsmDownloadTool is not pressed within 10 seconds?
Thanks greetings.
Click to expand...
Click to collapse
I see that you sent a private message to me also and mentioned that you got into the Bootloader. That is not what you need.
First of all, you will need to install the qualcom drivers from here: https://www.androidjungles.com/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
Afterwards, you will need to hold both volume buttons, and after a few seconds connect your phone to the computer via cable (while still holding the volume buttons).
The phone will be detected as a Qualcom device and you cand start following the tutorial that was provided earlier.
GoToNap said:
I see that you sent a private message to me also and mentioned that you got into the Bootloader. That is not what you need.
First of all, you will need to install the qualcom drivers from here: https://www.androidjungles.com/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
Afterwards, you will need to hold both volume buttons, and after a few seconds connect your phone to the computer via cable (while still holding the volume buttons).
The phone will be detected as a Qualcom device and you cand start following the tutorial that was provided earlier.
Click to expand...
Click to collapse
Hello friend, I already managed to enter the EDL mode correctly, the doubt is that when I connected it after 10 seconds, the phone disconnected and relapsed. That's why I said that if I could test now that your phone works, it also automatically restarts without touching any Msm program button once connected in EDL mode.
Something with EDL mode in OP7 is currently wrong.
As the predecessors wrote, after connecting, it is interrupted after a few seconds and the phone reboots.
I also have OP3, OP6 in them after the EDL mode is switched on the connection is maintained all the time.
Andro_Nicus said:
Something with EDL mode in OP7 is currently wrong.
As the predecessors wrote, after connecting, it is interrupted after a few seconds and the phone reboots.
I also have OP3, OP6 in them after the EDL mode is switched on the connection is maintained all the time.
Click to expand...
Click to collapse
That's what @Thelargeportion wrote at OP7Pro thread:
"Yes, it did on mine. I've just used this tool to recover from root to stock.
Noted that if the program isn't started within 10 seconds, the phone rebooted automatically, I'm guessing as some sort of security lock. Restarted in EDL, connected to the MSMDownloadtool and executed the program as soon as it was connected and it flashed absolutely fine.
Note that after the phone is restarted after a successful flash, it takes about 1-2 minutes to boot again having stuck on the OnePlus boot logo."
Could be true. But nevermind... It works and that's important.:laugh:
Yes, it is the most important thing that it flashes the system image.
However, it does not maintain a permanent session in EDL as
in previous OnePlus models, and that may be worrying.
Andro_Nicus said:
Yes, it is the most important thing that it flashes the system image.
However, it does not maintain a permanent session in EDL as
in previous OnePlus models, and that may be worrying.
Click to expand...
Click to collapse
I can Tell you, after days with a bricked Phone and seeking for a Tool. You really don't Care about permanent Sessions.
Regrads
Thyson
If something works differently, it usually is always puzzling.
That is why all these posts appeared on this subject.
Andro_Nicus said:
If something works differently, it usually is always puzzling.
That is why all these posts appeared on this subject.
Click to expand...
Click to collapse
Hello friend, yes, that happens to all of us, it is not an isolated case, but if once you enter EDL mode and connect the phone to the PC and it appears "connected", you press start and everything works. You must press start in 10 seconds since entering EDL mode, once you press start, it no longer restarts and blinks correctly.
This of the 10 seconds occurs in all OnePlus 7 series (normal and PRO).
Comment where I ask about 10 seconds and colleagues confirm that they used the tool: https://forum.xda-developers.com/showpost.php?p=79997414&postcount=54
So i did something extremely stupid. I flashed an android 9 STOCK ROM while i was in android 10 to fix a magisk and WIFI issue i was having. As a result i cant get into fastboot now and i can only turn the phone on by holding power + volume up button. But doing so only shows the logo for some time which then freezes and the screen goes black. I think the phone has been hard bricked and my only option maybe the unbrick tool. But i can't understand how to use it. I have followed some threads but some of the things aren't adding up. For example in device manager my phone is being detected as Qualcomm HS-USB Diagnostic 900E(COM4) whereas it's supposed to be Qualcomm HS-USB Diagnostic 9008. And also pressing pressing ENUM in the unbrick tool does not detect my device. Any help would be appreciated.
UPDATE : Holding down both volume buttons and power button got me into fastboot mode but the normal way didn't. And from there I discovered I still had stock recovery. I just reset data and everything booted back up properly.
wolfsbane169 said:
So i did something extremely stupid. I flashed an android 9 STOCK ROM while i was in android 10 to fix a magisk and WIFI issue i was having. As a result i cant get into fastboot now and i can only turn the phone on by holding power + volume up button. But doing so only shows the logo for some time which then freezes and the screen goes black. I think the phone has been hard bricked and my only option maybe the unbrick tool. But i can't understand how to use it. I have followed some threads but some of the things aren't adding up. For example in device manager my phone is being detected as Qualcomm HS-USB Diagnostic 900E(COM4) whereas it's supposed to be Qualcomm HS-USB Diagnostic 9008. And also pressing pressing ENUM in the unbrick tool does not detect my device. Any help would be appreciated.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80011568&postcount=2
_disable driver signature : https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
_update drivers
[ https://www.youtube.com/watch?v=jtc7EhNsfPA&feature=youtu.be ]
_ https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
daitalos said:
https://forum.xda-developers.com/showpost.php?p=80011568&postcount=2
_disable driver signature : https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
_update drivers
[
&feature=youtu.be ]
_ https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
Click to expand...
Click to collapse
I was able to fix the problem. Holding down both volume buttons and power button got me into fastboot mode but the normal way didn't. And from there I discovered I still had stock recovery. I just reset data and everything booted back up properly
wolfsbane169 said:
I was able to fix the problem. Holding down both volume buttons and power button got me into fastboot mode but the normal way didn't. And from there I discovered I still had stock recovery. I just reset data and everything booted back up properly
Click to expand...
Click to collapse
Great to hear that your phone is back!
Please Help Me!:crying:
My 7 Pro has been bricked.
circumstance：
i press VolUp + Power for a while, there are showed <!> screen (= warn for unlocking) only a few seconds.
but fastboot screen is not displayed. black out.
of course, recovery is the same. (black out)
if i connect 7 Pro to a PC, there is a response for a moment, but it does not appear in the device manager (similar things appear in the "Port").
when i flashed
OnePlus7ProOxygen_21.E.15_OTA_015_all_1907281610_e735c0c31ada4eee.zip
and
Magisk-v19.4.zip
from TWRP, It became current state after this operation.
This is the first time such a brick.
Does anyone have the same situation or have a solution?
MtnOrf said:
Please Help Me!:crying:
My 7 Pro has been bricked.
circumstance：
i press VolUp + Power for a while, there are showed <!> screen (= warn for unlocking) only a few seconds.
but fastboot screen is not displayed. black out.
of course, recovery is the same. (black out)
if i connect 7 Pro to a PC, there is a response for a moment, but it does not appear in the device manager (similar things appear in the "Port").
when i flashed
OnePlus7ProOxygen_21.E.15_OTA_015_all_1907281610_e735c0c31ada4eee.zip
and
Magisk-v19.4.zip
from TWRP, It became current state after this operation.
This is the first time such a brick.
Does anyone have the same situation or have a solution?
Click to expand...
Click to collapse
MSMDownload Tool.
That will get you back to a fresh OS.
MtnOrf said:
Please Help Me!:crying:
My 7 Pro has been bricked.
circumstance：
i press VolUp + Power for a while, there are showed <!> screen (= warn for unlocking) only a few seconds.
but fastboot screen is not displayed. black out.
of course, recovery is the same. (black out)
if i connect 7 Pro to a PC, there is a response for a moment, but it does not appear in the device manager (similar things appear in the "Port").
when i flashed
OnePlus7ProOxygen_21.E.15_OTA_015_all_1907281610_e735c0c31ada4eee.zip
and
Magisk-v19.4.zip
from TWRP,It became current state after this operation.
This is the first time such a brick.
Does anyone have the same situation or have a solution?
Click to expand...
Click to collapse
I actually also bricked mine today and also had to use the msm download tool.
It was fairly easy and I was happy with the process.
No worries ?
tech_head said:
MSMDownload Tool.
That will get you back to a fresh OS.
Click to expand...
Click to collapse
Device manager shows "Qualcomm HS-USB Diagnostics 900E(COM5)".
so(?) there are no responses in MSM tool.
schorrie said:
I actually also bricked mine today and also had to use the msm download tool.
It was fairly easy and I was happy with the process.
No worries
Click to expand...
Click to collapse
thanks.
but, ,my device manager shows "Qualcomm HS-USB Diagnostics 900E(COM5)".
so(?) there are no responses in MSM tool.
Do I need to use an EDL cable...?
I had this exact same problem last night. Plug it in via USB and make sure you have volume on your speakers. Press and hold volume up, down and power and for some reason the bootloader will come up. Pick power off, then press volume up and down at the same time and plug your USB cable into the phone and listen for the connection sound.
Tried to press power+volume up, doesn't work. Is there any other way?
tainka said:
Tried to press power+volume up, doesn't work. Is there any other way?
Click to expand...
Click to collapse
connect to computer while doing and it works
You can boot into recovery without having to plug into a computer by holding power + volume up, and then once you get to the "this device is unlocked, press power key to continue" screen, rather than just waiting for that screen to disappear, press the power key and then you should be taken to recovery... at least, that's how I was able to do it
ShotSkydiver said:
You can boot into recovery without having to plug into a computer by holding power + volume up, and then once you get to the "this device is unlocked, press power key to continue" screen, rather than just waiting for that screen to disappear, press the power key and then you should be taken to recovery... at least, that's how I was able to do it
Click to expand...
Click to collapse
Its an issue after latest update, so we have to connect to PC and then Power + Vol Up
inningsdefeat500 said:
Its an issue after latest update, so we have to connect to PC and then Power + Vol Up
Click to expand...
Click to collapse
Ah gotcha, that makes sense, I've never been able to get recovery booting via power + volume up, until I randomly tried pressing the power button at the device unlocked screen, and for some reason doing that took me into recovery
ShotSkydiver said:
Ah gotcha, that makes sense, I've never been able to get recovery booting via power + volume up, until I randomly tried pressing the power button at the device unlocked screen, and for some reason doing that took me into recovery
Click to expand...
Click to collapse
What is the unlocked screen? Never saw this
Are you powering off your phone first? If so wait a few seconds after then hold down both power + volume up buttons at the same time and hold for 10 seconds. It still works for me doing it this way.
xfaega said:
Are you powering off your phone first? If so wait a few seconds after then hold down both power + volume up buttons at the same time and hold for 10 seconds. It still works for me doing it this way.
Click to expand...
Click to collapse
Yes, I tried a few times when phone is off. But it butting up like always to the os.
Volume Up + Power, Splash Screen, Continue pressing the volume up button works for me..
tainka said:
Yes, I tried a few times when phone is off. But it butting up like always to the os.
Click to expand...
Click to collapse
Try this. Hold the volume up button first then the power button. See if this will work.
Thanks, i succeeded with the cable method
edwardob said:
connect to computer while doing and it works
Click to expand...
Click to collapse
Oh man!! you saved my life!! Lots of thanks.
Very helpful!
edwardob said:
connect to computer while doing and it works
Click to expand...
Click to collapse
This works like a charm. I was about to give up my phone because of this predicament, I didn't want to have any issues restoring my phone in the future in case. THANKS A BUNCH!
It's kinda strange but it is bootloader issue. I am on BTK3 firmware (latest Android 10 release) and i'm experiencing such misbehave of key-kombo to enter ot recovery mode since September or October FW update. Has jus tried to downgrade bootloader to initial firmaware (ATGM) by flashing BL in odin and now i can enter recovery by only pressing vol-up + bixby. It work always. Cables, headphones... nothing needed. just keys-combo.
Then i tried to update BL to latest Android 10 (BTK3) and again recovery mode doesn't work. Only if N9860 connected to PC by cable and even with that it doesn't work for me 10 out of 10 times.
Can someone text/call Samsung support to report this issue ?
BTW thanks to @Mentalmuso for helping me!
Same things happen to Android 11.
Tried to flash on my N9860 old BL over Android 11 firmware (was installed before that, all files AP, BL, CP, CSC), flash was ok, but system was unable to load. constantly bootloops. but i was able again to enter recovery without cable and etc. Tried to wipe cache and factory reset from default recovery but no luck - bootloop.
I thought that game over and old BL is not compatible with new android 11.
But then i wanted to try do the same but with custom binaries (@Mentalmuso TWRP and kernel) and ta-da - system loaded from the first try. For me it's surprise. Now i have Android 11 latest FW for TGY (CUA3) with initial BL from the box (ATGM) and everything looks like working fine. No error in OS, no random reboots (at least after 30 minutes of test) and recovery can be simply loaded only by key combo, without any cables, headphones and PC.
I'm happy now =)
Strange thing is that after fladhing old BL system did not show error message that vbmeta changed and some error in vbmeta header. It was showed always on Android 10. But i flashed twrp again (it has vbmeta inside .zip) to be safe lol.