Hi, I need your help here. I'm trying to fix my friends phone for her. What she told me is that it got stuck at the second boot screen after an update. She also said that it happened before and her father got it working. So my first thought was to clean flash stock firmware but I can't get ADB working. I've installed usb drivers and minimal ADB and fastboot but it doesn't recognize the phone in "adb devices" (I have no idea if USB debugging was on in dev options but I'm assuming it wasn't). I have no idea what to do now as I'm not that familiar with Xiaomi firmware.
Thanks in advance.
Edit: Xiaomiflash sees the device but not as COM.. but 72e728fb (?) and trying to flash it in this state ends with error:Flash xbl error
Related
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
Ok so first off just wanted to say that i succesfullt rooted my Moto g 4.4.2.. Had SuperSu and all was fantastic...a day went by and i decided that i wanted to put run CMrom .. i was having a few issues so i decided that i would clear the dalvik and all that.
But this is where i messed up.. i wasnt paying attention and Deleted EVERYTHING..including the os.
Now im at a loss because my computer wont recognize my device ..even if im in fastboot or recovery.. i cant get it to show up in adb when i type adb devices or anything! So how can i flash an os when my device isnt recognized??.. There is 1 thing, When im in fastboot and i click the Superboot.bat it acts like it did when i first rooted it... but does me no good i still cant do anything... and yes ive read every guide i could find but i just cant get it recognized... Is there something im missing?
I appreciate any help with this as i am now without a phone... Thanks guys
Edit: Oh and just incase i forgot to mention i believe i have all the drivers and adb..all that...Like i said i rooted succesfully
With the phone in fastboot mode and connected to your computer, do you get the device's serial # when you type "fastboot devices" ?
audit13 said:
With the phone in fastboot mode and connected to your computer, do you get the device's serial # when you type "fastboot devices" ?
Click to expand...
Click to collapse
nope, i tried to get it to show up in every mode and way i could come up with.. nothing
Are you trying the fastboot commands on a Win7 or XP machine? I don't think ADB commands will not work when the phone is in fastboot mode,
It's a Windows 8 machine.
Any suggestions I'm still stuck
Try to flash a ROM in fastboot on a Win7 (x86 or x64) or XP (x86) machine.
Just tried it man... Still no luck. . Man what am I doing here? Do you have a link maybe I'm doing it wrong from the one I'm reading... But the machines just will not get the device
Put your phone into fastboot mode, connect the USB cable, do you see the Moto G appear as an android device in Device Manager on your Win7 or XP machine?
Delphi Hacker said:
Ok so first off just wanted to say that i succesfullt rooted my Moto g 4.4.2.. Had SuperSu and all was fantastic...a day went by and i decided that i wanted to put run CMrom .. i was having a few issues so i decided that i would clear the dalvik and all that.
But this is where i messed up.. i wasnt paying attention and Deleted EVERYTHING..including the os.
Now im at a loss because my computer wont recognize my device ..even if im in fastboot or recovery.. i cant get it to show up in adb when i type adb devices or anything! So how can i flash an os when my device isnt recognized??.. There is 1 thing, When im in fastboot and i click the Superboot.bat it acts like it did when i first rooted it... but does me no good i still cant do anything... and yes ive read every guide i could find but i just cant get it recognized... Is there something im missing?
I appreciate any help with this as i am now without a phone... Thanks guys
Edit: Oh and just incase i forgot to mention i believe i have all the drivers and adb..all that...Like i said i rooted succesfully
Click to expand...
Click to collapse
I think you need to restore your stock rom
This thread will help u
http://forum.xda-developers.com/showthread.php?t=2542219
no my device is not recognized no matt r what I do
After booting your phone in fastboot mode and connecting it to a Win7 or XP machine, you see no unknown devices in Device Manager?
Do you have pds partition since you cleared everything.
"fastboot devices" does this command shows any device or your device recognized by pc or not.
This may be useful - http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
but how can i flash the stock firmware when its not recognized?
Hi guys,
Before i start, just be informed that i have tried google all possible solutions and tried them but to no avail. I know its a long shot but perhaps someone may be able to help however small the chances are.
My phone is a Xiaomi Redmi Note 3 Snapdragon variant and is rooted.
What happened was, i tried installing TWRP (kenzo version) on my phone and so following the "instructions" in the downloaded file.
I used Flashify to flash the boot.img and then redmi_note_3_Twrp.img then the phone prompted me to reboot.
Now my phone is stuck in bootloop. The only thing i can do is to boot into Fastboot. So i tried accessing fastboot via ADB hoping to be able to some how flash the original boot.img back.
The problem i have now is that i am unable to access the phone at all even though i can go into fastboot. It wont be detected by my PC. I tried Minimal ADB and Fastboot and PdaNet.
Is there any other way for me to detect my phone and run some form of command to get it started again? Any help at all is appreciated. The phone is fairly new and i'm regretting trying to get the latest ROM for it.
I'm hoping i'll have some luck in a helpful community such as this.
Thanks guys.
Omg!! someone with the same problem as me. The same happened to me. Flashed a CWM file now am stuck in a Bootloop and ADB wont find my device either
Marticco said:
Omg!! someone with the same problem as me. The same happened to me. Flashed a CWM file now am stuck in a Bootloop and ADB wont find my device either
Click to expand...
Click to collapse
Fret not my friend. For i have found the solution and managed to unbrick my phone. Thank the good guys at MIUI for this.
Head over to the MIUI forum and search unbrick under the Redmi Note 3 forums. I can't post the link here unfortunately
You can also thank me after you unbrick your phone.
This only applies if you are uaing the Redmi Note 3 Pro
yea unfortunately i dont use that phone. I have a Lava Iris x1 Grand (Lollipop). I am still trying to get ADB find my device
Marticco said:
yea unfortunately i dont use that phone. I have a Lava Iris x1 Grand (Lollipop). I am still trying to get ADB find my device
Click to expand...
Click to collapse
Well if that's the case i suggest googling how to get into EDM mode for ur phone and using your phone brand's flash tool to flash a new ROM onto your phone. This means you will not be able to save your phone's memory. Is your phone's bootloader unlocked?
willetan said:
Well if that's the case i suggest googling how to get into EDM mode for ur phone and using your phone brand's flash tool to flash a new ROM onto your phone. This means you will not be able to save your phone's memory. Is your phone's bootloader unlocked?
Click to expand...
Click to collapse
yes it is unlocked,
i think? When i entered fastboot mode. One of my apps says bootloader enabled and when i typed 'fastboot devices' in the Minimal ADB and Fastboot its shows:
0123456789ABCDEF devices
whereas if I type 'adb devices' i just shows:
List of devices attached
The main problem is the driver, i cant get adb to find my device. I have tried the universal usb drivers like Kouch but no success. My device is listed in the Unspecified section in my computer
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.
Hi there!
After unblocking bootloader, I flashed patched magisk for rooting. With fastboot.
Since then, the phone is in bootloop.
I can get to fastboot and recovery.
The laptop doesn't recognize the opo. It says unknown device...
Tried all drivers.
Tried msm but it won't Work becouse of the "unknown device" issue...
I think I deleted to many things...
I really need your help!!
Samsung was easier
Fixed it
Tried a different computer