Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Robert1852 said:
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
That always works.. use method 2
dmilz said:
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
That always works.. use method 2
Click to expand...
Click to collapse
Not this time... That is the tool I mentioned, only gets me back to the bootloop
Robert1852 said:
Not this time... That is the tool I mentioned, only gets me back to the bootloop
Click to expand...
Click to collapse
I know what you talking about.. Went through that too when i used method one.. use method 2..it will flash stock OOS and you will boot successfully
If you already did..try once more..download the tools over again
dmilz said:
I know what you talking about.. Went through that too when i used method one.. use method 2..it will flash stock OOS and you will boot successfully
If you already did..try once more..download the tools over again
Click to expand...
Click to collapse
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Robert1852 said:
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Click to expand...
Click to collapse
Ooh ok.. i see.. hope you will find a way out
Robert1852 said:
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Click to expand...
Click to collapse
Probably a stupid question but have you tried flashing oxygen os recovery and then tried to flash stock ROM?
Xceeder said:
Probably a stupid question but have you tried flashing oxygen os recovery and then tried to flash stock ROM?
Click to expand...
Click to collapse
That unbrick tool also flashes the stock recovery. I cant flash anything using fastboot because the bootloader is locked
Robert1852 said:
That unbrick tool also flashes the stock recovery. I cant flash anything using fastboot because the bootloader is locked
Click to expand...
Click to collapse
And why is it locked then? Why would you ever relock your bootloader? You should be able to unlock it anyway without going in to settings. Are you sure you are using the correct drivers? Windows installs the wrong once by default.
Puddi_Puddin said:
And why is it locked then? Why would you ever relock your bootloader? You should be able to unlock it anyway without going in to settings. Are you sure you are using the correct drivers? Windows installs the wrong once by default.
Click to expand...
Click to collapse
It has never been unlocked. In the settings is the "Allow OEM Unlock" option which you should check before you can unlock the bootloader. As long as I can't boot the phone I can't check this option, or someone must know a workaround. Yes I'm pretty sure I'm using the correct drivers
Robert1852 said:
It has never been unlocked. In the settings is the "Allow OEM Unlock" option which you should check before you can unlock the bootloader. As long as I can't boot the phone I can't check this option, or someone must know a workaround. Yes I'm pretty sure I'm using the correct drivers
Click to expand...
Click to collapse
If you plug your phone in how does it show up under Device Manager? Have you also tried "fastboot OEM Unlock"?
Puddi_Puddin said:
If you plug your phone in how does it show up under Device Manager? Have you also tried "fastboot OEM Unlock"?
Click to expand...
Click to collapse
When it's in the bootloader menu it shows up as "Android Bootloader Interface", when it's in EDL mode it shows up as "Qualcomm HS-USB QDLoader 9008 (COM3)". It connects fine with the pc and flashes everything without problems as far as I can see. Yeah it says "FAILED (remote: oem unlock is not allowed)" probably because the allow oem unlock option in the settings isn't checked.
Most likely won't do anything, but have you tried a different computer? Seems like it would make no difference but tiny things like that have saved me in the past.
ZVNexus said:
Most likely won't do anything, but have you tried a different computer? Seems like it would make no difference but tiny things like that have saved me in the past.
Click to expand...
Click to collapse
Yea I know what you mean I tried it on a few different computers, even with different cables but it doesn't make a difference...
Robert1852 said:
Yea I know what you mean I tried it on a few different computers, even with different cables but it doesn't make a difference...
Click to expand...
Click to collapse
Pretty sure you are using wrong drivers. You should be able to unlock the bootloader even tho it is remote. When I first bricked my phone I forgot about the drivers aswell. My phone booted up and showed. System: Failed, Userdata:Failed. This means it failed to detect those partitions which you can find in unbrick program itself called system.img, userdata.img. You can actually flash these manually with fastboot flash system system.img but I also got the "Remote is not allowed error". After booting into disabled Driver Signature Enforcement mode and changing the drivers from on the guide I could actually flash these partitions. Your phone has to show up as Qualcomm 9008 or something close and not as Android Interfere Device. I have helped multiple people fixing their phone with this guide and they also had a locked bootloader and they also did not have the correct drivers.
Boot into https://www.google.com/amp/s/www.ho...so-that-you-can-install-unsigned-drivers/amp/ then install the driver linked on the Unbrick Guide. Your phone should show up correctly. Then run the unbrick guide as admin and it should go through flawless.
Puddi_Puddin said:
Pretty sure you are using wrong drivers. You should be able to unlock the bootloader even tho it is remote. When I first bricked my phone I forgot about the drivers aswell. My phone booted up and showed. System: Failed, Userdata:Failed. This means it failed to detect those partitions which you can find in unbrick program itself called system.img, userdata.img. You can actually flash these manually with fastboot flash system system.img but I also got the "Remote is not allowed error". After booting into disabled Driver Signature Enforcement mode and changing the drivers from on the guide I could actually flash these partitions. Your phone has to show up as Qualcomm 9008 or something close and not as Android Interfere Device. I have helped multiple people fixing their phone with this guide and they also had a locked bootloader and they also did not have the correct drivers.
Boot into https://www.google.com/amp/s/www.ho...so-that-you-can-install-unsigned-drivers/amp/ then install the driver linked on the Unbrick Guide. Your phone should show up correctly. Then run the unbrick guide as admin and it should go through flawless.
Click to expand...
Click to collapse
Tried everything it says in the guide about the drivers (even the last part about installing the certificates) but it just keeps showing up as qualcomm hs-usb qdloader 9008, even though I'm pretty sure they are installed correctly. It just won't show up as Qualcomm 9008, as it is supposed to, whatever I try. But it looks like these drivers are only for the EDL mode, and as far as I know it is normal for the phone to show up as Android Bootloader Interface when it's in the bootloader menu. And you can't use fastboot from EDL mode... Will try it later again on a different pc though, really hope you are right about the drivers after all
Hi Robert,
I am having same problem with my oneplus3. I also tried both unbrick methods and tried different oxygen ROMs.
Are you able to fix your phone?
Thanks in Advance,
Anil
Have you tried this http://www.androidbrick.com/oneplus-one-two-3-3t-5-mega-unbrick-guide-twrp-flashing/
Robert1852 said:
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Click to expand...
Click to collapse
Hi
Go back to an older Version...3.xx
worked for me
be warned ..3.xxx formats internal memory
I also have the same problem, I'll try to restore to old version too.
Do you also have artifacts on the screen?
Related
Hi all,
My OTA update kept failing so I attempted a manual update to 4.04.
I missed updating the boot.img file. I did the system, recovery and radio then relocked the bootloader.
When I turn it on, it stays on the google splash screen. When I go into bootloader mode and try recovery mode, I get the red triangle. My computer does not seem to be recognizing the phone, I get the error: device not found.
Is there something I might try?
Thanks in advance
AV8ing said:
Hi all,
My OTA update kept failing so I attempted a manual update to 4.04.
I missed updating the boot.img file. I did the system, recovery and radio then relocked the bootloader.
When I turn it on, it stays on the google splash screen. When I go into bootloader mode and try recovery mode, I get the red triangle. My computer does not seem to be recognizing the phone, I get the error: device not found.
Is there something I might try?
Thanks in advance
Click to expand...
Click to collapse
In fastboot mode (obviously), unlock the bootloader, flash the boot image, and leave the bootloader unlocked. Done.
Thanks for the quick repy efrant! A big question is how do I unlock the bootloader if my computer doesn't recognize the phone. I am getting "device not found" so I seem to be unable to unlock the bootloader in the first place.
AV8ing said:
Thanks for the quick repy efrant! A big question is how do I unlock the bootloader if my computer doesn't recognize the phone. I am getting "device not found" so I seem to be unable to unlock the bootloader in the first place.
Click to expand...
Click to collapse
So your GNex is booted in fastboot mode and your computer does not recognize it? If this is the case, it is likely a driver issue, and you should re-install.
It is normal that your GNex is not recognized by your computer when booted not in fastboot mode, when you can't boot.
efrant said:
So your GNex is booted in fastboot mode and your computer does not recognize it? If this is the case, it is likely a driver issue, and you should re-install.
It is normal that your GNex is not recognized by your computer when booted not in fastboot mode, when you can't boot.
Click to expand...
Click to collapse
Hey efrant ^^ I'll sort it out ^^ (if you don't mind)
Dude, chec my sig, all the drivers and tutorials needed, can be found in the Win8 thread.
Follow that tut. then the phone should be recognized. Then erase the phone With:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
This ensures, that the flash is successful. If you don't erase first, it's likely, that the phone won't correctly write the files.
Then flash the files, with these codes:
Code:
fastboot flash boot (Always do this first) <Fille directory\file name.img>
fastboot flash system <Fille directory\file name.img>
fastboot flash recovery <Fille directory\file name.img>
DO NOT ERASE/FLASH userdata!! Do that, and you WILL lose ALL of your data!
If you want, I can help you, with tamviewer. I've helped a few people, this way It has always worked
Normally it does recognize the phone, but it doesn't seem to since I messed this up. I will try to re-install the drivers to see if that works. It is in fastboot mode, I hear the tone from the computer that something has connected when I reboot the fastboot, but it doesn't get recognized.
AV8ing said:
Normally it does recognize the phone, but it doesn't seem to since I messed this up. I will try to re-install the drivers to see if that works. It is in fastboot mode, I hear the tone from the computer that something has connected when I reboot the fastboot, but it doesn't get recognized.
Click to expand...
Click to collapse
Go into the dev manager, and look for: Android 1.0
If you see that, then Update devuice drivers -> Select from a list -> Samsung ADB Interface
That should do the trick
Thanks much, familyguy59. I'll try this now.
AV8ing said:
Thanks much, familyguy59. I'll try this now.
Click to expand...
Click to collapse
No prob. That's what some of us, have made to a "quest" Instead of flaming n00bs, help them, and make sure, they find their place, in this community
Thanks so much efrant and familyguy59! There were a couple of bumps in the road, but I flogged my way through them. I thought I had bricked my phone for sure. Once again, thanks so much.
AV8ing said:
Thanks so much efrant and familyguy59! There were a couple of bumps in the road, but I flogged my way through them. I thought I had bricked my phone for sure. Once again, thanks so much.
Click to expand...
Click to collapse
No prob, dude! That's what we're here for
familyguy59 said:
No prob. That's what some of us, have made to a "quest" Instead of flaming n00bs, help them, and make sure, they find their place, in this community
Click to expand...
Click to collapse
+1 to this guy XD
Sent from my Galaxy Nexus using XDA
jzero88 said:
+1 to this guy XD
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
And the "xD" was neccessary... in what way? ^^ It is true, though.
If you aren't feeling the same, then it's your thing. I'm here, to help others, and help them understand, what, what features do, and what is needed, to do what....
Hi, my N7 is bricked and I wanted to fix it.
I tried to flash ROM but couldn't do it since my computer wont recognize my N7 (except in Recovery Mode-> Sideload).
I think it has something to do with the "developer options -> need to check USB Debugging", however, I can't do that since my phone when turned on, Google Logo appears, then afterwards, BLACK SCREEN (and now in a loop, but there is no X logo just plain black).
My phone is rooted & unlocked. Out of curiousity (My fault), I bricked my N7.
I've read a lot of article on how to unbrick my N7 and I think I now know how to do it- through Android SDK/ADB Tool. I've also read the a guide on how to change drivers (and tried it in all possible ways I can think of), and it did install the driver. However searching my N7 through ADB Tool doesn't go through.
adb devices
List of devices attached
(**nothing follows**)
But if I turn my N7 to Recovery Mode->apply update from adb:
will show the result:
adb devices
List of devices attached
**serial number** sideload
I don't know what other ways in order to unbrick my N7.
I hope you can help me with it.
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Use wugs program but tick tablet is in bootloop.
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Thanks for the info man!
AnarchoXen said:
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Click to expand...
Click to collapse
Hi, thanks for the info... I already solved my problem.. If only I have read your post earlier I could've saved xx hours in my research!! LOL
donb1 said:
Use wugs program but tick tablet is in bootloop.
Click to expand...
Click to collapse
I tried, but N7 isn't recognized by PC. So the main problem is really how to make my N7 recognized by PC (ADB/bootloader).
But problem fixed now. Thanks!
Calvin Gross said:
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Click to expand...
Click to collapse
Before I fixed my N7, this is what I tried. But the problem is, PC wont recognize/find my N7 when I do:
adb devices nor fastboot devices
But, I already fixed my problem. Thanks for the response! Greatly appreciate it!
I am not new to rooting and unlocking Androids. My LG G3's UI would randomly freeze where I had to reboot the device to have it working again. Today I decided to flash the vanilla unicorn rom in recovery. I downloaded the rom and copied it over to the phone but the copy process kept getting stuck at some point, that I always had to cancel it.
So I decided to wipe cache and data to just reinstall the official d855 CM13 rom I had earlier on the device's storage, the wipe got stuck for at least 20 mins. I got impatient and removed the battery trying to reboot into recovery, but I was stunned and stuck on the LG Splash screen logo, I kept trying to reboot into recovery but couldn't get past the LG splash screen.
I then decided to try rebooting into fastboot, I was able to boot into fastboot the normal way without any issues but every attempt at getting TWRP just wasn't yielding anything useful. The closest I've gotten to seeing TWRP since then was with the fastboot command
Code:
fastboot boot recovery.img
which reboots showing the TWRP splash screen image without actually showing TWRP, but I've noticed I can access adb while the screen is stuck on the TWRP splash screen image.
I can't do any sideload of the zips on my computer because TWRP just stays there stuck on the splash screen so I can't enable sideloading. I have spent hours with this and it has taken too much of my time, attempts at
Code:
fastboot flash recovery recovery.img
just returns with an error in cmd with FAILED (remote: flash write failure).
I can't figure out what to do anymore, I'm left with a phone that can't boot into the rom and recovery, only the fastboot and download mode works. I just need the phone to let me boot into recovery so I can flash the files I need to and have my phone back to its earlier state.
I'll really appreciate everyone's support, thanks!
geek-x said:
I am not new to rooting and unlocking Androids. My LG G3's UI would randomly freeze where I had to reboot the device to have it working again. Today I decided to flash the vanilla unicorn rom in recovery. I downloaded the rom and copied it over to the phone but the copy process kept getting stuck at some point, that I always had to cancel it.
So I decided to wipe cache and data to just reinstall the official d855 CM13 rom I had earlier on the device's storage, the wipe got stuck for at least 20 mins. I got impatient and removed the battery trying to reboot into recovery, but I was stunned and stuck on the LG Splash screen logo, I kept trying to reboot into recovery but couldn't get past the LG splash screen.
I then decided to try rebooting into fastboot, I was able to boot into fastboot the normal way without any issues but every attempt at getting TWRP just wasn't yielding anything useful. The closest I've gotten to seeing TWRP since then was with the fastboot command which reboots showing the TWRP splash screen image without actually showing TWRP, but I've noticed I can access adb while the screen is stuck on the TWRP splash screen image.
I can't do any sideload of the zips on my computer because TWRP just stays there stuck on the splash screen so I can't enable sideloading. I have spent hours with this and it has taken too much of my time, attempts at just returns with an error in cmd with FAILED (remote: flash write failure).
I can't figure out what to do anymore, I'm left with a phone that can't boot into the rom and recovery, only the fastboot and download mode works. I just need the phone to let me boot into recovery so I can flash the files I need to and have my phone back to its earlier state.
I'll really appreciate everyone's support, thanks!
Click to expand...
Click to collapse
Does your computer recongnise your phone. If it does you (probably) can use LG up tool to flash kdz file
dusan17 said:
Does your computer recongnise your phone. If it does you (probably) can use LG up tool to flash kdz file
Click to expand...
Click to collapse
I have tried using the flash tool, but I can't get into Download mode to use the LG Flash tool to get back to stock. All I get is fastboot.
There was a tutorial about using two wires on the emmc, but I haven't been able to get the Qualcomm HD_USB 9008 to show up in Device manager.
Sent from my ONE A2005 using Tapatalk
geek-x said:
I have tried using the flash tool, but I can't get into Download mode to use the LG Flash tool to get back to stock. All I get is fastboot.
There was a tutorial about using two wires on the emmc, but I haven't been able to get the Qualcomm HD_USB 9008 to show up in Device manager.
Click to expand...
Click to collapse
I have the same case with my old LG L90. I spent a lot of time trying to get it back to life without success . I have read another post similar to this but the wire thing worked. I really don't know then.
dusan17 said:
I have the same case with my old LG L90. I spent a lot of time trying to get it back to life without success . I have read another post similar to this but the wire thing worked. I really don't know then.
Click to expand...
Click to collapse
What kind of wire did you use in getting it to work?
And how were you able to get windows to show the QLoader usb com port. ?
geek-x said:
What kind of wire did you use in getting it to work?
And how were you able to get windows to show the QLoader usb com port. ?
Click to expand...
Click to collapse
I didn't want to mess around with motherboard so i gave phone to my uncle because he is better than me in that stuff. But sadly we didn't bring it back to life.
dusan17 said:
I didn't want to mess around with motherboard so i gave phone to my uncle because he is better than me in that stuff. But sadly we didn't bring it back to life.
Click to expand...
Click to collapse
Damn.
geek-x said:
Damn.
Click to expand...
Click to collapse
I saw people unbrick devices that way we propably did somenthing wrong. For the wires i would use copper wires.
Do you have Qualcomm drivers installed in pc?
I have unbricked many mobile using this pin shortening trick.it's simple.just make sure you are shortening the right pins.
Jahanzaibawan said:
Do you have Qualcomm drivers installed in pc?
I have unbricked many mobile using this pin shortening trick.it's simple.just make sure you are shortening the right pins.
Click to expand...
Click to collapse
I can't get the Qualcomm drivers to show up in Device Manager, even after installing the Qualcomm drivers and I have enabled test mode and all that. My com ports don't show anything Qualcomm at all.
Jahanzaibawan said:
Do you have Qualcomm drivers installed in pc?
I have unbricked many mobile using this pin shortening trick.it's simple.just make sure you are shortening the right pins.
Click to expand...
Click to collapse
Does it also matter that I am using a USB 3.0 port? My laptop has no 2.0 ports.
This might be helpful http://forum.xda-developers.com/spr...fix-hard-brick-recovery-guide-t3132359/page59
dusan17 said:
This might be helpful http://forum.xda-developers.com/spr...fix-hard-brick-recovery-guide-t3132359/page59
Click to expand...
Click to collapse
Thanks for that post. I'll give it a try again tonight, I just need the Qualcomm 9008 drivers to come up.
Cause I noticed every time attach the wire to the board, windows recognizes the phone with an error "USB device not recognized" and in device manager a yellow warning mark next to one of the USB device icons.
Sent from my ONE A2005 using Tapatalk
geek-x said:
Thanks for that post. I'll give it a try again tonight, I just need the Qualcomm 9008 drivers to come up.
Cause I noticed every time attach the wire to the board, windows recognizes the phone with an error "USB device not recognized" and in device manager a yellow warning mark next to one of the USB device icons.
Click to expand...
Click to collapse
I that case right click chose update drivers and chose drivers manualy. Something like that should help you get device recognized
dusan17 said:
I that case right click chose update drivers and chose drivers manualy. Something like that should help you get device recognized
Click to expand...
Click to collapse
What directory will I choose to install the drivers from, the Qualcomm installation directory doesn't seem to contain the actual driver files.
geek-x said:
What directory will I choose to install the drivers from, the Qualcomm installation directory doesn't seem to contain the actual driver files.
Click to expand...
Click to collapse
Uf, i don't know it should be listed.
geek-x said:
Does it also matter that I am using a USB 3.0 port? My laptop has no 2.0 ports.
Click to expand...
Click to collapse
Yup.mostly 3.0 doesn't work.80% 3.0 cause the problem.
Jahanzaibawan said:
Yup.mostly 3.0 doesn't work.80% 3.0 cause the problem.
Click to expand...
Click to collapse
I'll try to get a USB 2.0 laptop to try this on. I just hope it works this time.
I was unrooting my phone and I must've skipped a few steps but now my phone is bricked I guess. All I can do at the moment is get into the bootloader but whenever I try and flash anything (recovery,roms etc) I don't permission since I locked my bootloader (it said in a tutorial.. whoops). I tried to follow the unbricking guide here on XDA but it tells you to install weird qualcomm drivers and whenever I try and apply it to my device in device manager it just says that it's not compatible with my device.
So yeah, my bootloader is locked but I need to flash a recovery to get me out of this mess, what do I do?
Have you tried fastboot oem unlock?
It "might" work even if the related setting (in Developer Options) is disabled.
After doing that, try to normally restore the stock firmware.
Ps note that you'll definitely lose all data
Simone98RC said:
Have you tried fastboot oem unlock?
It "might" work even if the related setting (in Developer Options) is disabled.
After doing that, try to normally restore the stock firmware.
Ps note that you'll definitely lose all data
Click to expand...
Click to collapse
Yeah but it just fails
edit- i'll retry the unbricking guide tomorrow
The guide still doesn't work for me, I'm just having problem with the drivers you're meant to use.
I posted on there my issue on more detail.
Update- I fixed it.
I wasn't going into proper recovery mode (I had to turn it off completely and hold volume while plugging in). Then, it popped up on device manager under USB and the drivers worked. Afterwards, I just followed the rest of the tutorial haha.
i installed cm14.1 today from the cyanogenmod website i had everything running fine until i reboot into recovery. i got a black screen and it didnt bot into recovery at all so i held my power button and volume down and nothing happens. i cant even boot up into fast boot or anything. nothing is turning my phone on. when i connect it to my pc nothing happens. is there anything i can do?
There's a mega unbrick guide for the OnePlus 3, use that then install the correct firmware and install the custom TWRP and re flash the ROM
i tried that method but the device doesnt even show up on my pc
envious86 said:
i tried that method but the device doesnt even show up on my pc
Click to expand...
Click to collapse
Get this sorted yet? You'll need a modified TWRP recovery for the newest CM based builds. I went through the same thing yesterday or the day before. Try holding volume down and power for like 30 seconds until you feel it vibrate that it is rebooting. Then hold volume *UP* while it reboots or if you see the "your device is not safe..." flash screen hurry and press volume down and go into fastboot. From there you can fastboot flash a new recovery.
I had the same problem as well, in device manager go to ports (com & LPT) and it will show up there under qualcum device. Don't forget to go and turn off certificate verification
Thanks guys I'll try this after work. Hopefully it works. If not sure oneplus are hopefully releasing a new phone soon
No it didn't work. I have a feeling I deleted something I shouldn't have because I was clearing out my files before I restarted and that was that.
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Just use the recovery rahditzz provided you with a link, if your phone is stuck on black screen with white led hold your power button until it turns off, then boot to fastboot and flash the recovery and you will boot...
rahditzz said:
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Click to expand...
Click to collapse
thanks didnt work. when i fastboot flash recovery and boot again it just goes into a black screen again
Then use unbrick method 2..
rahditzz said:
Then use unbrick method 2..
Click to expand...
Click to collapse
neither method works. all i can do is get into fastboot mode thats it. it wont show up on my pc at all
Method 2 workshop 100%, unless its a hardware fault..
Are you pushing volume up while plugging in cable?
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
I jeep getting the sahara communication failed error
envious86 said:
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
Click to expand...
Click to collapse
Your running vista???? Good god update your OS!!
Maybe your fastboot drivers got updated? There were some reports around this. You could try reinstalling the drivers and following the unbrick guide without an internet connection.
Sent from my ONEPLUS A3003 using Tapatalk
Cool u can boot into Fastboot, what error do you get when you type Fastboot devices? Nothing shows up?