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....
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...
After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.
Its simple, you need to setup the drivers for your computer to connect via fastboot. Then you can simply flash the stock images by google.
mortenmhp said:
Its simple, you need to setup the drivers for your computer to connect via fastboot. Then you can simply flash the stock images by google.
Click to expand...
Click to collapse
How??? I've tried to already from the toolkit
sinaisinai43 said:
How??? I've tried to already from the toolkit
Click to expand...
Click to collapse
sigh.
dont use the toolkit.
there's a nice thread in general about how to return to stock. even gives a section on how deal with drivers.
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.
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?