Related
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.
Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium
WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.
Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium
ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.
dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?
dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.
Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...
I own a HTC One V. And I did something at the TWRP menu like installing this CARBON-JB-UNOFFICIAL-20131022-1552-primoc thing.. and ever since then the phone doesn't boot.. it won't even go to that menu where it says FASTBOOT{ I think it's called the recovery menu :3 }
But, I charge it.. And then I plug it into the comp, it just connects and disconnects, like it's giving a faint indicator of life :3
Please help. I was on Ignorance V5..
Installing a rom can't hard brick your device.
Try to shut it down by holding the power button and immediately press vol down + power to enter your bootloader. Then you can select recovery and install a backup of your ignorance rom or do whatever you want.
BTW: It looks like you forgot to install the kernel for the custom rom.
ManishByatroy said:
I own a HTC One V. And I did something at the TWRP menu like installing this CARBON-JB-UNOFFICIAL-20131022-1552-primoc thing.. and ever since then the phone doesn't boot.. it won't even go to that menu where it says FASTBOOT{ I think it's called the recovery menu :3 }
But, I charge it.. And then I plug it into the comp, it just connects and disconnects, like it's giving a faint indicator of life :3
Please help. I was on Ignorance V5..
Click to expand...
Click to collapse
Most likely you flashed the wrong ROM.
PrimoU <> PrimoC
Boot loader should still work as expected I guess:
<vol.down>+<power> should get you to the hboot menu.
kvestas said:
Most likely you flashed the wrong ROM.
PrimoU <> PrimoC
Boot loader should still work as expected I guess:
<vol.down>+<power> should get you to the hboot menu.
Click to expand...
Click to collapse
It's not going into Boot Loader. If it did, I would flash back Ignorance.
Please help
ManishByatroy said:
It's not going into Boot Loader. If it did, I would flash back Ignorance.
Please help
Click to expand...
Click to collapse
Did you try fastboot command to reboot into bootloader?
The command might be accepted by phone during it's initial loading stage:
* connect phone to a computer
* run command (e.g. fastboot reboot-bootloader), must be waiting for response from device
* reboot your phone
* if you are lucky enough the command will be accepted on load.
jonas2790 said:
Installing a rom can't hard brick your device.
Try to shut it down by holding the power button and immediately press vol down + power to enter your bootloader. Then you can select recovery and install a backup of your ignorance rom or do whatever you want.
BTW: It looks like you forgot to install the kernel for the custom rom.
Click to expand...
Click to collapse
It isn't going to bootloader when i press power+volume down button.. :\
If I could enter the bootloader menu, I wouldn't have been this worried. :3
kvestas said:
Did you try fastboot command to reboot into bootloader?
The command might be accepted by phone during it's initial loading stage:
* connect phone to a computer
* run command (e.g. fastboot reboot-bootloader), must be waiting for response from device
* reboot your phone
* if you are lucky enough the command will be accepted on load.
Click to expand...
Click to collapse
Can you please tell me where to run this Command? I'm a noob sorry. :/
ManishByatroy said:
Can you please tell me where to run this Command? I'm a noob sorry. :/
Click to expand...
Click to collapse
This command has to be run on a computer.
Similar as you are running fastboot commands to root phone or install custom recovery.
Please google if you are not familiar with fastboot commands at all.
Make sure you have installed proper phone usb drivers to make your phone "visible" from computer.
Btw how did you get running Ignorance?
kvestas said:
Did you try fastboot command to reboot into bootloader?
The command might be accepted by phone during it's initial loading stage:
* connect phone to a computer
* run command (e.g. fastboot reboot-bootloader), must be waiting for response from device
* reboot your phone
* if you are lucky enough the command will be accepted on load.
Click to expand...
Click to collapse
kvestas said:
This command has to be run on a computer.
Similar as you are running fastboot commands to root phone or install custom recovery.
Please google if you are not familiar with fastboot commands at all.
Make sure you have installed proper phone usb drivers to make your phone "visible" from computer.
Btw how did you get running Ignorance?
Click to expand...
Click to collapse
My friend got ignorance running for me.. Like I don't know what and where to enter these fast boot commands.. Any link to learn or you explaining will be appreciated.
phone is blank. hasnt lighted a pixel in a week
phone is charged. how do i know this? because i charged it for 3 days :3
tried all combinations of buttons to get to bootloader. i just cant!!!
i connect it to a comp, it connects and disconnects simultaneously.. :/
pls tell me what to do
ManishByatroy said:
phone is blank. hasnt lighted a pixel in a week
phone is charged. how do i know this? because i charged it for 3 days :3
tried all combinations of buttons to get to bootloader. i just cant!!!
i connect it to a comp, it connects and disconnects simultaneously.. :/
pls tell me what to do
Click to expand...
Click to collapse
You may download and try this tool:
http://forum.xda-developers.com/showthread.php?p=46202420
This might be easier to start from.
kvestas said:
You may download and try this tool:
http://forum.xda-developers.com/showthread.php?p=46202420
This might be easier to start from.
Click to expand...
Click to collapse
Just tried it. I selected device but stuck on downloading drivers
Thanks for the help tho mate
ManishByatroy said:
Just tried it. I selected device but stuck on downloading drivers
Thanks for the help tho mate
Click to expand...
Click to collapse
You can download HTC drivers from almost any other hOV thread.
Like this one in example:
http://forum.xda-developers.com/showthread.php?t=1996665
Basic Requirements. 4th item.
Remember, all you need to try with this tool is to reboot into bootloader. Try to click the tool button while your phone is starting to load.
By the way, you may find fastboot files in that thread as well (Basic Requirements. 5th item).
kvestas said:
You can download HTC drivers from almost any other hOV thread.
Like this one in example:
http://forum.xda-developers.com/showthread.php?t=1996665
Basic Requirements. 4th item.
Remember, all you need to try with this tool is to reboot into bootloader. Try to click the tool button while your phone is starting to load.
By the way, you may find fastboot files in that thread as well (Basic Requirements. 5th item).
Click to expand...
Click to collapse
Yes, I have the HTC Sync installed which gives the necessary drivers for the recognition of HTC phones.. ( My ONE V)
But, the computer just sounds that music when a USB device is connected, the phone is dead. Not even lighting up..
The WinDroid isn't recognizing my device as well..
ManishByatroy said:
Yes, I have the HTC Sync installed which gives the necessary drivers for the recognition of HTC phones.. ( My ONE V)
But, the computer just sounds that music when a USB device is connected, the phone is dead. Not even lighting up..
The WinDroid isn't recognizing my device as well..
Click to expand...
Click to collapse
The computer should not recognize your phone because it is not loaded completely (neither os, neither recovery).
But it might be recognized for a few seconds only while trying to load os. And you might be able to supply reboot command at that particular moment.
Just try what I said.
kvestas said:
You may download and try this tool:
http://forum.xda-developers.com/showthread.php?p=46202420
This might be easier to start from.
Click to expand...
Click to collapse
kvestas said:
The computer should not recognize your phone because it is not loaded completely (neither os, neither recovery).
But it might be recognized for a few seconds only while trying to load os. And you might be able to supply reboot command at that particular moment.
Just try what I said.
Click to expand...
Click to collapse
Yeah.. I tried that.. But nothing is working.. The OS too isn't booting up. So I don't really know when my phone is on or off
ManishByatroy said:
Yeah.. I tried that.. But nothing is working.. The OS too isn't booting up. So I don't really know when my phone is on or off
Click to expand...
Click to collapse
Do you mean led is always off?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
Try holding power button down for 30s.
kvestas said:
Do you mean led is always off?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
Try holding power button down for 30s.
Click to expand...
Click to collapse
Tried. Ain't working. LED ain't even turning on while charging too.. So there's really no way to find out whether it's charging..
Update : Still haven't fixed my phone. Any help would be appreciated. Can't enter Bootloader menu. Phone when connected to computer, gives "sound" that every normal USB when connected gives.. So the phone isn't completely dead. After connecting, the computer doesnt react in any way :crying:
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?
Hello,
I really dont know what to do anymore.
No matter which ROM I flash, I always get stuck in a bootloop. I always wait 20-25 for a boot, but it doesnt pass the bootanimation.
Here is what happened:
My PC didnt recognize my phone anymore even though I didnt change any driver settings or something like that. Same with other PCs, not even showing up in device manager at all. So I thought I messed up some settings in my phone, thats why I wiped data, system, cache, internal store, then pushed a new ROM to my phone via USB OTG, but it doesnt boot at all. Phone still doesnt get recognized by any pc, not even in TWRP or bootloader.
Here are the things I tried so far:
- Ressurrection Remix (latest 3 versions) with OpenGapps
- Lineage OS with DynamicGapps
- both of them without any gapps
- OMNI Rom with DynamicGapps
I also did a factory reset before every flash. After 20 minutes of bootloop I also tried a 2nd boot for 20 minutes...nothing.
Since I cant access my phone from PC I cant flash stock ROM (or is it possible to flash it via TWRP?). I guess I just wiped something that I shouldnt have wiped. Does anyone have an idea what else I could try?
I had something similar happen to my 5x a while back. After fiddling with drivers/device manager etc, I found this on net which actually worked for me:
Solution 5 – Uninstall Android drivers if PC not recognizing phone
Sometimes you might not have the latest drivers, or your drivers might not be properly installed, so in order to fix issues with Android devices and Windows 10, it’s advised that you uninstall your Android drivers. To do so, follow these steps:
Connect your Android device to your computer and open Device Manager.
In Device Manager locate your Android device. Usually it’s located in Other Devices or in Portable devices section, but the location might be different on your computer.
Right click the device and choose Uninstall.
uninstall-driver
After the drivers have been uninstalled, disconnect your Android device.
Reconnect it again, and wait for Windows 10 to install its drivers again.
Check if your Android device is now recognized.
---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------
Above post fixed my driver/PC not recognizing phone issue. As far as your bootloop issue, I'm assuming your bootloader is still unlocked, right? If so, and if above fix works where PC recognizes phone, try flashing google factory images via fastboot commands.
jrotert said:
I had something similar happen to my 5x a while back. After fiddling with drivers/device manager etc, I found this on net which actually worked for me:
Solution 5 – Uninstall Android drivers if PC not recognizing phone
Sometimes you might not have the latest drivers, or your drivers might not be properly installed, so in order to fix issues with Android devices and Windows 10, it’s advised that you uninstall your Android drivers. To do so, follow these steps:
Connect your Android device to your computer and open Device Manager.
In Device Manager locate your Android device. Usually it’s located in Other Devices or in Portable devices section, but the location might be different on your computer.
Right click the device and choose Uninstall.
uninstall-driver
After the drivers have been uninstalled, disconnect your Android device.
Reconnect it again, and wait for Windows 10 to install its drivers again.
Check if your Android device is now recognized.
---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------
Above post fixed my driver/PC not recognizing phone issue. As far as your bootloop issue, I'm assuming your bootloader is still unlocked, right? If so, and if above fix works where PC recognizes phone, try flashing google factory images via fastboot commands.
Click to expand...
Click to collapse
Since it doesnt show up in device manager, I cant uninstall the driver there.
I also tried it on a new PC that did never get in touch with an android phone - nothing. Not even a sound when I plug it in. The phone is just charging, thats it.
Have you tried using a different cable?
Keksdroid said:
Hello,
I really dont know what to do anymore.
No matter which ROM I flash, I always get stuck in a bootloop. I always wait 20-25 for a boot, but it doesnt pass the bootanimation.
Here is what happened:
My PC didnt recognize my phone anymore even though I didnt change any driver settings or something like that. Same with other PCs, not even showing up in device manager at all. So I thought I messed up some settings in my phone, thats why I wiped data, system, cache, internal store, then pushed a new ROM to my phone via USB OTG, but it doesnt boot at all. Phone still doesnt get recognized by any pc, not even in TWRP or bootloader.
Here are the things I tried so far:
- Ressurrection Remix (latest 3 versions) with OpenGapps
- Lineage OS with DynamicGapps
- both of them without any gapps
- OMNI Rom with DynamicGapps
I also did a factory reset before every flash. After 20 minutes of bootloop I also tried a 2nd boot for 20 minutes...nothing.
Since I cant access my phone from PC I cant flash stock ROM (or is it possible to flash it via TWRP?). I guess I just wiped something that I shouldnt have wiped. Does anyone have an idea what else I could try?
Click to expand...
Click to collapse
try Wug's Nexus Root Toolkit he is able to flash phone in bootloop
panicbear said:
Have you tried using a different cable?
Click to expand...
Click to collapse
I dont have any other cable, but maybe I should get a new one just to test. The cable I have is just 3 months old and was high quality....
pincher65 said:
try Wug's Nexus Root Toolkit he is able to flash phone in bootloop
Click to expand...
Click to collapse
Yeah I always used that tool in the past. But since my PC doesnt recognize the phone at all, not even in fastboot mode, that doesnt help me. I really need a solution that works just with TWRP...
Edit: Just an idea from my side. Would it work if someone, who just cleaned flashed, makes an nandroid backup, which I just restore with TWRP?
what radio at you installed? 7.1.1 02.2017 for TWRP
pincher65 said:
what radio at you installed? 7.1.1 02.2017 for TWRP
Click to expand...
Click to collapse
Radio is m8994f-2.6.36.2.20 - flashed it in December.
For TWRP?? Can I flash the stock zim through TWRP?
Keksdroid said:
For TWRP?? Can I flash the stock zim through TWRP?
Click to expand...
Click to collapse
yes. also PixelROM has full img
pincher65 said:
yes. also PixelROM has full img
Click to expand...
Click to collapse
Okay I will try that. I guess I will loose TWRP when I flash it?!
Keksdroid said:
Okay I will try that. I guess I will loose TWRP when I flash it?!
Click to expand...
Click to collapse
No.
pincher65 said:
No.
Click to expand...
Click to collapse
So I tried the stock rom and pixel rom, both when I try to flash them I get the Error message "Zip file is corrupt". There is no md5sum to check if its really corrupt...
Keksdroid said:
So I tried the stock rom and pixel rom, both when I try to flash them I get the Error message "Zip file is corrupt". There is no md5sum to check if its really corrupt...
Click to expand...
Click to collapse
disable check md5sum in setting TWRP.
pincher65 said:
disable check md5sum in setting TWRP.
Click to expand...
Click to collapse
Either way I'm blind, or I dont have that setting...
Keksdroid said:
Either way I'm blind, or I dont have that setting...
Click to expand...
Click to collapse
sorry, I have inattentively read the previous post. redownload zip if doesn't help, then your recovery is damaged and it is necessary to look for a way to connect him to PC
Problem solved. Got a new USB cable today, it worked now. Flashed stock image, it finally booted.
But wow, the old cable is already broken after 3 months...well it still charges very fast, but thats it.
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?