I recently managed to royally screw up installing Havok OS on my OP7 Pro.
I managed to get OOS installed and everything appears to be working.
However, when I was about to give it another crack, I rebooted into fastboot and the device is showing as "msmnile" and it's not detected by my computer.
Seems to me as though the fastboot ROM is FUBARd... Any ideas how to reflash it?
Install the adb for OnePlus that's automatically pops up when you connect your USB to the PC. Your phone might not show up but this drivers will. You can do it in fastboot mode or adb mode. If not go and search for OnePlus drivers
I had the same issue once. If twrp is still working you can try flashing a stock rom. Everything is in it to fox this. Then wipe system data en cache etc and flash your prevered custom rom.
Otherwise it could be a driver issue. Win 10 doesnt support everything without good drivers and there is even een issue with use of some Usb3 ports VS Usb2. Just try some ports and some drivers on diverend machines.
Last stage is a full factor recovery with
quallcomm download mode. Then every thing Will. Be wiped and you need to unlock boadloader etc again.
Related
First time poster, long time lurker. I downloaded TWRP and installed the recovery image but soft bricked my phone. Silly me remembered I had a backup made in CWM but not in TWRP. This is when you say to run boot.img but unfortunately I can not get the drivers to install properly on my Windows 7 x64 machine, due to not having them on here to begin with. So I have no One X drivers on the computer, I have MIUI and CM10 downloaded but can not get them to load due to not flashing properly, and TWRP with no backup. I have followed all the forums to delete drivers, re-install HTC Sync, manually point to the drivers but no dice. So.....what should I do :fingers-crossed:
Mode please close, I have resolved the issue.
Please post your solution for the benefit of others. That is how this forum works, its basically a database of issues and solutions that everyone can use.
I also think you are/were confused. The phone doesn't need to be working to get the drivers on your PC. You can download them from a variety of places. If you have HTC Sync properly installed, the drivers needed to connect your phone (USB mount, adb, fastboot, etc.) are installed. But if you have connection problems, updating these drivers or re-installing them will sometimes resolve the issue.
It seems that all you needed to do is get the drivers properly installed, then mount USB and put the ROM on the phone's SD, and flash boot.img using fastboot.
You're absolutely right. The solution was that I kept looking for fastboot to identify the device, and in my head that mean I couldn't push or flash to it. So I ended up just flashing TWRP recovery again, then it booted to CM10. Now im dealing with a whole new issue, but I'm going to work through it before I post again. Thanks.
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
baked cake said:
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
Click to expand...
Click to collapse
fastboot doesn't show a serial number for that device. At least never has for me. If 'fastboot devices' lists something like
Code:
List of devices attached
???????? fastboot
then you're good to go.
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
baked cake said:
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
Click to expand...
Click to collapse
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
shinobisoft said:
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
Click to expand...
Click to collapse
ill give it a try, but i have tried just about every recovery file i can get my hands on and no luck, also looks like winds 8 doesn't want to acknowledge my phones existence. I downloaded and installed the driver from LG but still no luck, windows 8 is giving me a failed descriptor error as well.
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
baked cake said:
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
Click to expand...
Click to collapse
I'd say that was/is the correct port name. I don't have that device anymore so I cannot say for sure.
Sent from my LG-P769 using Tapatalk
ok, so this is a follow up on some things i have tried recently.
Since my last post i have:
1. put the sdcard into my tablet, and formatted it/ ran an error scan on it via windows.
2. i then flashed a recovery file via my phones fastboot, i pulled that card put it back in tablet to see what files it installed.
3. according to windows, flash recovery installed a .LOST folder with nothing in it, which is the same thing my tablet has on its internal memory, so i don't think there's anything wrong there.
4. phone still cant boot past LG logo(or recovery), or charge the battery when plugged in.
5. I still get a stall get_descriptor error when connected via usb, and commands such as fastboot reboot don't work, tho the phone will say its rebooting (it says its rebooting then just sits there and does nothing, command prompt will say action completed).
6. one thing i have tried as well, is telling windows not to automatically install drivers, then uninstalling my phone from device manager.
Whats interesting about this was that windows was installing its own ADB modem driver from it's own library every time i plugged in the phone. After disabling auto drivers, and reinstalling my LG drivers, the phone simply remains an unknown device.
Some things I have tried include pointing windows to the driver folder, both the downloaded folder and the folder windows installed it to. Neither worked.
The next thing I tried is the have disc option on both. Although there are setup information files in the install folder (about 50 of em), pointing the phone to each file one at a time did not work.
What did work, interesting enough was pointing the phone to a set of Naked Drivers I downloaded, although none of those drivers are specifically for my phone, and they only gave me the same problem I had when i had windows auto installing its own driver.
LG L5 612 - fastboot issue
Hi,
I have an LG L5 612.
I'm trying to perform below actions, but always get "waiting for device" ... and nothing happens.
fastboot reboot-bootloader
fastboot flash boot boot.img
"adb devices" lists my device correctly, while "fastboot devices" output nothing.
C:\ADB>adb devices
List of devices attached
LGOTMS840b676a device
C:\ADB>fastboot devices
C:\ADB>
C:\ADB>fastboot reboot-bootloader
< waiting for device >
Hi guys hopefully I posted this in the right place. I have a rooted Nexus 5 with multirom installed and had a few ROMs in mind that I wanted to try out, most of them just installed simply and booted without problems however when I chose to try and install slimrom or another (can't remember the name of the other ROM sorry) a message would appear stating I need to install a different bootloader IMG to install/ boot that ROM. I searched around for a while and found an image to install through twrp but when I installed it I now can't boot the phone to launch a ROM or get into recovery mode as the screen will go black. Any ideas? I'm trying to used adb to install a twrp img but so far it doesn't detect the device :/ I would much appreciate any help or suggestions! Ask me if you have any questions! Thanks.
Have tried to flashing back to a completely stock rom?
Problem is I can't get my computer to recognize my nexus 5 in the boot loader mode if I could I could then flash twrp again and flash the stock rom but it doesn't detect
Does the phone boot into fastboot mode? You tried different USB ports, cables, computers, and operating systems?
The only mode I can get my Nexus into is boot loader mode so yes fast boot. I have a windows xp and 8 so I use 8 as its the only PC that I can run adb & fast boot on without problems. I have used a USB cord the recognized my sisters phone also so it shouldn't be a faulty cable I'm pretty sure. Thanks for those ideas I appreciate your help a lot!
Rooted Droid said:
The only mode I can get my Nexus into is boot loader mode so yes fast boot. I have a windows xp and 8 so I use 8 as its the only PC that I can run adb & fast boot on without problems. I have used a USB cord the recognized my sisters phone also so it shouldn't be a faulty cable I'm pretty sure. Thanks for those ideas I appreciate your help a lot!
Click to expand...
Click to collapse
Use the cable that came with the phone.
Use this well made thread
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I once wiped my system and rebooted and got stuck in a loop. at his thread is what I used to save my phone. Hope it helps.
Sent from my Nexus 5 using Tapatalk
Speaking from personal experience, I found that the USB cable could make a difference. I also have Samsung phones and, although the USB cable allowed win7 to install drivers, I could never flash anything. Once I switched back to the original cable, flashing works without any problems.
tahnks guys i managed to fix my problem using the nexus in bootloader mode on Windows 7 as windows 8 and xp wouldn't recognize it for some reason. From there i managed to install twrp reset the device, flash theserurection remix rom and flash a correct bootloader. Thanks for your help as it lead me in the right direction!
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay, probably need to reinstall recovery and flash a clean rom again. Try the "fastboot boot recovery.img" command and it's giving me a "waiting for any device". Googling says it's a driver error, but that's strange because I have used my phone on this computer before with ADB and fastboot. Fastboot and ADB commands work fine on my Oneplus 3T.
A week ago I also had the problems after the Magisk update. But connecting to the PC worked normally for me. Once you've installed the drivers, there shouldn't be any problems. You could use a different cable.
Incidentally, Magisk only messed up the boot image. It is sufficient if you flash your boot.img, then the twrp.zip, reboot into recovery, then the magisk.zip.
That was completely enough for me. Cell phone works normally again, without data loss.
Good luck!
Yeah that's exactly what I am trying to do, I can't even flash the boot.img to get into recovery, my computer won't recognize the device for some reason now. Do you know where I can find the drivers? I could only find shady 3rd party sites. Thanks!
Tried installing drivers from here, no change.
Download Latest OnePlus USB Drivers for Windows and Mac
Download The Latest OnePlus USB Drivers For All OnePlus Android Smartphones. We Have Included USB drivers for Both Windows And Apple MAC OS Users. Download Links Given Below.
www.getdroidtips.com
This is installed and works with me
ghost323 said:
This is installed and works with me
Click to expand...
Click to collapse
No joy, looks like that's the same file as the one I downloaded. Thanks for your help anyways.
Now I can't even turn my phone off lol. It woke itself up this morning magically and now whenever I hit power off in fastboot it just boots up again into fastboot. Might have to send it in...the horror
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
ghost323 said:
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
Click to expand...
Click to collapse
Haha yeah, it's like your kid who refuses to go to bed and is throwing a tantrum. Yeah two different computers that are known to have worked with this phone in the past (how I unlocked the bootloader in the first place). Different ports, different cables. It seems like I'm having the same issue that a lot of other people are having with the last Magisk update, except they're able to flash the recovery image in fastboot to get back running.
This is a ****ty situation! That was really a nasty magisk update. I wonder why its consequences are so different, even though it is the same cell phone.
fastboot cannot recognize device but adb can
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both. Oneplus 7 pro is running 10.3.0GM21AA >fastboot devices >adb devices List of devices attached 966c8016...
forum.xda-developers.com
Look at this. Maybe it will help you so that your computer recognizes the cell phone again.
Hello!
I have tried to upgraded my phone to Lineage 18.1 but it did not work.
This is what I did so far:
1) Installed the NEWEST TWRP and unfortunately I have deleted the OS. After that, the USB connection worked fine and I was able to see all files on my phone.
2) I've found a stock recovery.img that I have used and then the problem started. After installing that recovery.img file now I have TWRP (older version) 2.7.0.0 and:
a) when connected through USB , my computer does make sound, but it does NOT recognize my phone any more. Yes, I do have the newest USB drivers installed
b) when connected through USB and when I run this command: fastboot devices, then it DOES shows my device number, but it DOES NOT any devices using adb command.
c) when booting into fastboot, the phone shows just the black screen with the android faded icon.
d) I can boot into TWRP but there is no system or recovery files in there and it look like it's just useless.
I'm not sure what to do next. It looks like the phone is soft-bricked.
Any help will be appreciated.
Thank you
the first thing i would try is flashing twrp 3.6 (the newest) using fastboot. not sure why you would flash an old recovery version. if data recovery is not an issue then the opo is even fixable after a hardbrick (i used to have it). i used the color os method but that was ages ago. now there is a slightly easier way somewhere here on xda if you want the opo to in out of the box condition.
maybe try the whole thing using a secondary old laptop (if possible) or a virtual machine. otherwise i have no idea. sounds like a lot of trial and error might be needed. good luck.