Hi everyone,
A couple of days ago I rooted my Op6 and then decide to flash No limits rom via recovery (blu spark), as I was used to do with my last android phone, the Samsung Galaxy Note II.
Unfortunately I missed something and now it is stuck in the bootloader screen. Nothing works from the phone and I couldn’t revive it. I use a Mac but I tried all tools that are adviced here on XDA with my friend’s Sony Vaio but without success.
I managed to update drivers but I cannot run a flash-all.bat and I cannot use MSMdownload tool.
How can I do? Thanks to anyone who will manage to help me!!
EDIT: Sorry, just noticed you say you cant use the MSM tool. This one worked for me.
You could try this
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
Worked for me.
Check the guide about unbricking and if You are unable to use flash-all.bat so you Have to flash commands One by One. It's worked for me a few of months ago.
It doesn’t work either that way. I updated my drivers, but no computer is recognizing the phone.
I tried from changing usb cable or port to changing computer, to change methods.
I didn’t found any solution here on XDA, I tried everything!!
Make sure u use the cable included with the phone. Some cables doesn't work
Neither. I tried with the original and two others that I have.
if possible do you have windows? the flash-all.bat works for windows and is better to use(i was unable to use it normally in linux). What happens when you show flash.bat?
I tried Mac and Windows. On Windows it always shows in terminal "waiting for any device", even if I uploaded the drivers and made everything possible.
Did you put your OP6 into fastboot mode in correct way? I mean you might be doing the wrong procedure when entering fastboot mode.
It happened to me for the first time, I came from Samsung and I thought the phone needs to be stayed on the fastboot menu screen just like Samsung but no.
You need to turn it off and reboot it while pressing home and vol down button simultaneously until the PC recognize.
Good luck unbricking~
I always powered it on via power+volume up before connecting to the usb cable, because connecting it while powered off always resulted to power it on automatically on bootloader screen
Related
So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Update: I've been trying different cables. I found one where the computers will see that a devices is connected, but am getting "USB device not recognized" with either set of drivers that I have on both computers. Making progress, but could still use some help.
DiGi760 said:
So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Click to expand...
Click to collapse
I had a problem similar to that about a year ago, somewhere in these forums was the suggestion to remove the SD card and then do a factory reset, it worked for me. My xoom just stopped working, I thought at first it was a flat battery but after charging the symptoms were the same as yours, might be worth searching through the forums if you haven't already
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
Sorry can't help , mine is just over 2 years old and except for that one problem have never had any issues so have never needed to even connect it to a PC
DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
I recently discovered these handy files when I needed to return to stock:
4G Xoom (MZ600) Restore
3G Xoom (MZ601/3) Restore
WiFi Xoom (MZ604) Restore
If you need to find out which Xoom model it is, power on whilst holding the volume down button, this will take you in to fastboot. Then (you sound like you'd know how do this, PM me if you don't) use "fastboot getvar all". This will return the model.
Unzip the file above, there's a batch file in there which will install the drivers, then fastboot the firmware over.
If you boot to fastboot, then run the batch file, it installs the drivers, then "adb device", then it asks if your device is connected - it won't show up cos it's in fastboot. Just ignore that and say yes, and it'll start flashing the files.
Sorry if I'm too late - don't visit these boards much these days. Good luck, let me know if this works.
Thanks for giving me something to try. I uninstalled the moto drivers I had and installed the ones included in the zip file and restarted my computers. The Windows 8 computer never recognizes that the xoom is connected in any mode. The 7 machine does see it in fastboot mode but as a "fastboot" device for which it fails to find drivers. When I run fastboot getvar all, all I get is <waiting for device>.
I do know that this is a wifi only (mz604) xoom. Thanks for the image files. If I can get this stupid thing to communicate with a computer, I think I'll be in business.
In fastboot mode (vol -) it won't acknowledge that it's connected. Just fastboot your image over and it will work.
If I try to do anything with fastboot, it just says "< waiting for device >". Fastboot doesn't see a device to flash to.
OK, it's either your cable or your driver. Many cables are for charging only, and have no data lines. I throw those away.
As to drivers, I'm Debian for 15 years so can't advise on Winduhs.
Oh, one more thing: I've noticed that on my old HP laptop I had to use a certain USB port, or else it wouldn't comm with my phone for fundamental actions like loading new firmware.
These were the drivers I used: https://motorola-global-portal.cust...sion/L3RpbWUvMTM4NjM1MjA0NC9zaWQvWEo3SWU5SGw=
They don't seem to be windows 8 certified though.
Sent from my Nexus 5 using Tapatalk
We finally got it. We used DriverEasy to look for drivers because we have a bunch of extra licenses and the drivers we had obviously weren't working. DriverEasy was able to install an "Android Bootloader" driver that must not be part of the SDK. Once that was installed, I was able to use fastboot to flash the images from above. The device is in good working order again and fully updated.
Thanks for all your help.
Always nice to hit the Thanks button for those who've helped.
Solved,
if your story sounds similar to mine(Go to TL;DR) Refer to post 4
ok, where to begin
my N5 was A-OK just 3 days ago running the Dev Preview of Lollipop. by A-OK i mean that it worked but with a few
bugs
(its the dev preview i know, its got bugs) like when i stayed on an app, e.g spotify, and exited to the home screen it
would take like 15 sec for all the apps on the home screen (like 6) to appear. There is not where the problem lies.
Again 3 days ago. i poked around both ROM sections to find a Lollipop based on that was to my liking, found one and
directly downloaded it to my phone (in hindsite it would of been better to do it on my comp) and being no stranger
to flashing ROMs i went on auto-pilot adn begun the wiping of cache and factory resetting, setting up for the move to
more stable ROM. When it was time to flash the ROM I completely downloaded was no where to be found, a bit
panicked i went to a backup i had on the device, it did its thing and i booted it up but it went back to Clockworkmod
recovery screen That's problem No. 1 . I rebooted it still the same thing. Scouring through
the web for help on setting ADB to sideload the ROM. The thing is that when i hooked up my phone to my desktop
it didn't recognize the device, The correct drivers are installed but it doesn't recognize the device its labeled as
unknown USB device. That's problem No. 2
*update i plugged in my N5 and the comp read it as a N5 but when i selected the option to sideload it it doesn't
recognize it anymore
and problem No. 3 is USB debugging might be turned off
TL;DR? 1. Boots into Clockworkmod
2. my computers don't recognize the device
3. USB debugging might be off
-Q: Can USB Debugging be enabled some other way.
Any help is appreciated
why is it double spaced? i find it a bit eye-straining reading that much all bunched together
Setup fastboot on your computer. Once done open a command prompt and type fastboot devices. If it doesnt display a long line of numbers and letters the computer isnt recognizing the device. At this point try a different usb port, and try a different cord, until it recognizes. The fastboot flash the images for 5.0. 1. =profit.
Lokke9191 said:
Setup fastboot on your computer. Once done open a command prompt and type fastboot devices. If it doesnt display a long line of numbers and letters the computer isnt recognizing the device. At this point try a different usb port, and try a different cord, until it recognizes. The fastboot flash the images for 5.0. 1. =profit.
Click to expand...
Click to collapse
ok, used a different cable and it now recognizes it.
tried fastboot devices and nothing
tried ADB devices and numbers appeared and what state the device is in, recovery.
thank you thank you thank you sooo much
all is good
My Nexus 5 is alive,
i tried to upgrade to 5.0 directly and kept getting errors e.g archive does not have boot.sig/ system.sig. That lead me to look up Boot.sig/System.sig, that lead me to a blog saying i could fix the problem if i added something to the directory, forgot how to get to environmental variables, i went and watched the vid that helped my set up adb/sdk and thats when it clicked..
What if i tried flash-all with KitKat and voila it started running the process of flashing. Since it was basically a new phone unrooted and everything it had the system update to lollipop.
Good day gents and ladies
Well let me start from the beginning.
I'm was using mi-globe 6.12.22
Last week Friday evening downloaded 7.2.9 mi-globe,read around the mi-globe forum.Didn't see anything funny so flashed via twrp on Saturday morning.Hmmmmmmmm this is when all my problems started.
Basically what I should of done is download 7.2.9,new 3.0.3 twrp for norgat,go into recovery flash new recovery, restart recovery,flash 7.2.9 and then have happy days.But it wasn't to be and now I'm basically sitting with a useless mi4c device.
The device works but warms up and I only get about 4 hours battery life.
If I try boot into recovery I just get black screen.
If I connect device to PC it is not recognized, have tried 3 x different laptop/PC's and different cables.
So fastboot,mi-flash,mi-unlock are all not possible as device is not recognized.
I have been trying different solutions without any success.
I think if it would be possible to root device directly without PC then maybe it will be possible to get flashfire working and I can flash new norgat recovery?
Any suggestions would be greatly appreciated?
NB.I have tried loading Qualcomm drivers ,google drivers etc etc.no luck can't connect my device too PC,either get device not recognized or the PC doesn't even see the device.Enable USB debugging etc etc nothing works.Been fiddling for 4 days!!!!!!!
Tried to root with kingoroot,framaroot directly on device etc nothing works?
Please help,else device is a nice piece of plastic that holds paper down on my table.lol
BR
Ant
have you tried fastboot
fastboot oem edl
Click to expand...
Click to collapse
then MiFlash to flash official rom
Fastboot don't work,as PC don't see the phone?
DeAntman said:
Fastboot don't work,as PC don't see the phone?
Click to expand...
Click to collapse
Is usb charging via pc working and have you tried miui updater? , This seems weird state you have ... If none working might be tried deep flash cable flashing ... Or go to nearest service center. Hope that help. Best luck.
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
DeAntman said:
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
Click to expand...
Click to collapse
You havent answered the miui updater part, have you tried flash miui rom.zip, using miui updater apps ?
Does fastboot mode boot on your phone ? i mean the bunny sceen showed up ?
For dfc here the link http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Please take dfc as last resort. And do research more on this... Do with your own risk. Good luck
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
DeAntman said:
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
Click to expand...
Click to collapse
Before this has your pc able to use the miflash ? Try to follow this guide to setup it correctly http://en.miui.com/thread-136188-1-1.html ... I follow this guide and the adb n fastboot even works on an old pentium 4, 512mb ram, win xp laptop.
Ps: I think, its only a matter of incorrect driver setup on your side, best luck.
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
chaosrde said:
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
Click to expand...
Click to collapse
Strange suggestion but try a different pc. My phone isnt recognised when I try to install magisk on my phone on my home pc but it works on my work pc.
I got about 9 different USB ports on my home PC and none work
Also download platform-tools_r29.0.2-windows for fastboot etc.
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Icculus760 said:
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Click to expand...
Click to collapse
I am using the OEM cable, straight out the box. I'm gonna try meddling with it again when I get home and see if I can get it working.
bigAL99 said:
Also download platform-tools_r29.0.2-windows for fastboot etc.
Click to expand...
Click to collapse
Ive done a fair bit of searching but I can't find anywhere to download older version of platform tools, I have the current build 29.0.5.
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.