Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
trp6senile said:
Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
Click to expand...
Click to collapse
Take out the battery, put it back together, power on the phone while holding down the volume down key til you get the splash screen, that'll boot you to the bootloader...
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
trp6senile said:
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
Click to expand...
Click to collapse
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
acejavelin said:
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
Click to expand...
Click to collapse
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
trp6senile said:
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
Click to expand...
Click to collapse
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: http://www.htc.com/us/support/content.aspx?id=6196 once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
acejavelin said:
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: <link> once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
Click to expand...
Click to collapse
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
trp6senile said:
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
Click to expand...
Click to collapse
You can also use a live Linux CD like Ubuntu and boot that and install the Linux version of ADB, it works fine.
Related
Ok so I wanted to try out some new Tom's besides the cm7 weeklies and figured I should do a deeper wipe than just the normal cwm wipe but I can't seem to figure put how to get fastboot working I set it up on my phone and navigated to the file ln my laptop and just issued a reboot so I knew how it worked before I started wiping but it just sat there and never rebooted I have is there additional files I need besides the fastboot exe to do a wipe. And is it advised to erase all the partitions before flashing a new rom or is it not needed
Sent from my MB860 using XDA App
I don't know for sure so I'll just tell you what I have in my folder where I have my fastboot.exe. I also have the adb files which include:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
Not sure if that means anything though. Have you updated your drivers recently? What OS does your laptop use? I know if you have the wrong drivers it can cause problems like using 32 bit drivers on a 64 bit system.
As far as wiping, it is recommended especially if you go from a different ROM to another. I usually use this which was suggested by a user named @CaelanT:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
jonnyboyC13 said:
Ok so I wanted to try out some new Tom's besides the cm7 weeklies and figured I should do a deeper wipe than just the normal cwm wipe but I can't seem to figure put how to get fastboot working I set it up on my phone and navigated to the file ln my laptop and just issued a reboot so I knew how it worked before I started wiping but it just sat there and never rebooted I have is there additional files I need besides the fastboot exe to do a wipe. And is it advised to erase all the partitions before flashing a new rom or is it not needed
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Well just updated motohelper and no luck still no response in fastboot maybe my procedure is wrong in what way do you wipe
Sent from my MB860 using XDA App
ok learning process. didn't even realize you needed adb to use fastboot. so i got that on my laptop.
adb isn't recognizing my phone either so i think i'm still missing something
Right now i know i have the motohelper install adb and and the fastboot files. I may have some other files when i first got my phone that just installed with it was still blurred but i don't know
Do you have "USB Debugging" checked when using adb?
How did you unlock the bootloader? It seems weird that it's not working since you need an unlocked bootloader to run CM7 (which you said you had) and you need fastboot to unlock the bootloader. I don't understand what could have changed since then. Are you using a different computer now?
Just to make sure we're on the same page, are you putting the phone into fastboot before you issue the fastboot commands?
[Turn off phone->Hold Vol down and press power->Keep holding Vol down until it says "Fastboot" at the top of the screen->Release Vol down and then press Vol up]
jonnyboyC13 said:
ok learning process. didn't even realize you needed adb to use fastboot. so i got that on my laptop.
adb isn't recognizing my phone either so i think i'm still missing something
Right now i know i have the motohelper install adb and and the fastboot files. I may have some other files when i first got my phone that just installed with it was still blurred but i don't know
Click to expand...
Click to collapse
Yep usb debugging is on
honestly i don't know why it's not working it just says waiting for device, all i need to do is just put into fastboot on my phone, navigate to the fastboot.exe on the command promt. Then plug in in the phone and issues the command correct. are there any other things that need to be running to get it working. is there another step before this for the computer to recognize my phone
There are only 2 things I can think of after the details you have given me:
1. Are you making sure it says "Starting fastboot protocol" at the top of the screen before you issue the commands?
and
2. Have you rechecked your drivers? To me this sounds like the issue if everything else is in place. Try plugging the phone into your computer while it's turned on and switching the "USB Connection" from "None" to "Windows Media" then to "Mass Storage" and finally "Phone Portal", making sure you allow it to install any proper drivers on each connection (takes a few seconds). It's also important to select OK each time you change the connection.
Also, did you get the correct adb files in the same folder as fastboot.exe?
Other than these 2 suggestions I don't know what could be causing the issue. At this point I would be seeking help myself.
jonnyboyC13 said:
Yep usb debugging is on
honestly i don't know why it's not working it just says waiting for device, all i need to do is just put into fastboot on my phone, navigate to the fastboot.exe on the command promt. Then plug in in the phone and issues the command correct. are there any other things that need to be running to get it working. is there another step before this for the computer to recognize my phone
Click to expand...
Click to collapse
ok did some more searching it is the driver just have to figure out what i need to get on my computer now
Ok haven't wiped yet but i got the right driver on my computer now adb now can discover my device and a did a fastboot reboot and it worked cool beans.
just in case anyone else is having a similar problem i had to download the MOTODEV usb driver here http://developer.motorola.com/docstools/USB_Drivers/ and yes had to sign up for MOTODEV to do it but whatever got it working and i'm pumped
My phone has banished me from using it for about 3 months now. I repeatedly apologized for upsetting it, and begged of it to allow me back in. But it's a cold machine, which feels no empathy and cares not for my well-intentioned promises of never angering it again.
I understand it's reluctance to believe my words, as this is not the first time I've committed such atrocities. You see, I bricked it doing the same thing once before. Likewise, I was never able to fix it. Instead, I pawned it off to an Android developer in the office and he was able to fix it after a few hours of struggling. I've since moved to a different office on the other side of the country, and he was unable to remember exactly what he did that finally fixed it.
On to the important things:
What happened exactly?
I was installing a ROM (I can't remember which one at this point, it's been a while). Something counterproductive happened during the install, and sent it into a bootloop.
Symptoms?
1. It starts booting as normal. HTC logo for a few seconds, goes black as if it's going to the next screen, then it reboots.
2. This time it has the HTC logo with "Entering Recovery..." in pink above it.
3. I get a very quick (a few milliseconds, tops) glimpse of the CWM loading screen, then it reboots and goes back to step 1.
4. It repeats indefinitely, and would probably do so for eternity.
What can I actually do?
I can get to the bootloader screen, and cycle through the options (Fasboot, Recovery, Factory Reset, Simlock, Image CRC, Show Barcode), and I can drill into each section and see their child options. However anything I try to do, just sends me into the bootloop.
However, it does still say it's Unlocked in the bootloader. It has the "Tampered" and "Unlocked" alerts at the top.
What have I tried?
I've tried more random things than I can possibly recite right now. I even went to the extremes of dual booting Windows 8 on my Macbook, so I could start trying some of the Windows-only suggestions, like using the All-In-One Toolkit. The biggest issue, is that nothing I use can find the device. Not ADB or Fastboot on Mac, not ADB or Fasboot on Windows, and not the All-In-On-Toolkit. The only thing I ever get is "Waiting for device" or "Device not found".
Any help would be much appreciated. Thanks in advance guys!
rvrzl said:
My phone has banished me from using it for about 3 months now. I repeatedly apologized for upsetting it, and begged of it to allow me back in. But it's a cold machine, which feels no empathy and cares not for my well-intentioned promises of never angering it again.
I understand it's reluctance to believe my words, as this is not the first time I've committed such atrocities. You see, I bricked it doing the same thing once before. Likewise, I was never able to fix it. Instead, I pawned it off to an Android developer in the office and he was able to fix it after a few hours of struggling. I've since moved to a different office on the other side of the country, and he was unable to remember exactly what he did that finally fixed it.
On to the important things:
What happened exactly?
I was installing a ROM (I can't remember which one at this point, it's been a while). Something counterproductive happened during the install, and sent it into a bootloop.
Symptoms?
1. It starts booting as normal. HTC logo for a few seconds, goes black as if it's going to the next screen, then it reboots.
2. This time it has the HTC logo with "Entering Recovery..." in pink above it.
3. I get a very quick (a few milliseconds, tops) glimpse of the CWM loading screen, then it reboots and goes back to step 1.
4. It repeats indefinitely, and would probably do so for eternity.
What can I actually do?
I can get to the bootloader screen, and cycle through the options (Fasboot, Recovery, Factory Reset, Simlock, Image CRC, Show Barcode), and I can drill into each section and see their child options. However anything I try to do, just sends me into the bootloop.
However, it does still say it's Unlocked in the bootloader. It has the "Tampered" and "Unlocked" alerts at the top.
What have I tried?
I've tried more random things than I can possibly recite right now. I even went to the extremes of dual booting Windows 8 on my Macbook, so I could start trying some of the Windows-only suggestions, like using the All-In-One Toolkit. The biggest issue, is that nothing I use can find the device. Not ADB or Fastboot on Mac, not ADB or Fasboot on Windows, and not the All-In-On-Toolkit. The only thing I ever get is "Waiting for device" or "Device not found".
Any help would be much appreciated. Thanks in advance guys!
Click to expand...
Click to collapse
Sorry I don't know how drivers work on a Mac.
the procedure from a PC would be
boot to bootloader
choose fastboot
plug in usb to phone
you now see fastboot usb in bootloader
from command prompt type "fastboot erase cache" then fastboot reboot
try to boot phone.
if it fails
reboot to bootloader
reflash recovery
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot
make sure your recovery is named like above and in the same folder as fastboot
clsA said:
Sorry I don't know how drivers work on a Mac.
the procedure from a PC would be
boot to bootloader
choose fastboot
plug in usb to phone
you now see fastboot usb in bootloader
from command prompt type "fastboot erase cache" then fastboot reboot
try to boot phone.
if it fails
reboot to bootloader
reflash recovery
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot
make sure your recovery is named like above and in the same folder as fastboot
Click to expand...
Click to collapse
Thanks for the help clsA
I gave this a try, but like I expected I'm just getting a "waiting for device" message from fastboot.
This time around (in Windows), I did notice that I'm also getting an error about the USB device not being recognized. I don't think it's initializing correctly because Windows says it's malfunctioning. Nothing has happened to the device itself (no bangs, drops, water, etc), and this wasn't a problem until after it was bricked, so I doubt it's hardware related.
Interestingly, under the Device Manager, it is listed under "Android USB Devices" as "My HTC" so it seems to know what it is. My drivers appear to be up to date. Any other suggestions? Thanks again.
rvrzl said:
Thanks for the help clsA
I gave this a try, but like I expected I'm just getting a "waiting for device" message from fastboot.
This time around (in Windows), I did notice that I'm also getting an error about the USB device not being recognized. I don't think it's initializing correctly because Windows says it's malfunctioning. Nothing has happened to the device itself (no bangs, drops, water, etc), and this wasn't a problem until after it was bricked, so I doubt it's hardware related.
Interestingly, under the Device Manager, it is listed under "Android USB Devices" as "My HTC" so it seems to know what it is. My drivers appear to be up to date. Any other suggestions? Thanks again.
Click to expand...
Click to collapse
Install the drivers included in the All in one kit or install HTC sync (not recommended)
Sent from my TouchPad using xda app-developers app
[RESOLVED!]
For anyone else who might be having this problem
1. I was finally able to resolve this by downloading the archive provided by Esau Silva, which (I'm assuming) had updated versions of adb, and fastboot for Mac/OSX: http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx
2. I booted to the bootloader (power + volume down for 10 seconds), went to the Fastboot option, then plugged my phone into my Macbook; enabling Fastboot USB.
3. I opened terminal, CD'd into the directory containing adb/fastboot, and then ran "./fastboot devices" to see if it recognized my device. Sure enough, with Fastboot USB on and the updated adb, it recognized the device.
4. Then I ran "./fastboot erase cache" which allowed me to boot back into the bootload, and then properly boot into recovery, finally seeing ClockworkMod Recovery again.
5. From CWMR I erased the cache again, erased the dalvik cache, and then did a full wipe/factory reset.
6. Then I booted back into CWMR once again, and chose sideload. Then back on my Macbook I was able to run "./adb devices" to make sure adb could see my HTC One. Once I confirmed it could see it, I ran "./adb sideload nameofrom.zip"
After the sideload was complete, I was back up and running.
Big thanks to clsA who got me Googling fastboot a bit more. Hopefully this helps someone else!
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Esploded said:
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Click to expand...
Click to collapse
Do you have adb? If you do the command is adb reboot recovery. Need to know more it just cycles? If so then try to push both power button and and both volumes until it has lights flashing at the bottom and reboots dont let go until it reboots. Other then that I am not sure. I tried to boot to recovery the manual way and it doesnt work. Which is why i Always use that to reboot recovery. Wait, I figured it out. Hold down volume power dont let go until bootloader comes up then let go of both. use volume down and select recovery and bam!
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
jhr5474 said:
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
Click to expand...
Click to collapse
I'll give the fastboot utility a shot, hopefully it works. Thank you
Esploded said:
I'll give the fastboot utility a shot, hopefully it works. Thank you
Click to expand...
Click to collapse
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
jhr5474 said:
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
Click to expand...
Click to collapse
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Esploded said:
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Click to expand...
Click to collapse
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
jhr5474 said:
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
Click to expand...
Click to collapse
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Esploded said:
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Click to expand...
Click to collapse
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
sdamark said:
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
Click to expand...
Click to collapse
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Esploded said:
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Click to expand...
Click to collapse
No, If you have twrp use adb push and push a rom to your phone and then flash it and your fine.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
If you can get into your rom, go to settings..power and at the bottom disable fastboot
Esploded said:
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
Click to expand...
Click to collapse
1. Charge your phone (about 24 hours).
2. Let him rest (about 24 hours) without turning on.
3. Connect device to PC with original wire (Win7 preferred).
There is possibility that your BB will recognize phone.
I unlocked the bootloader and went to root. on the first reboot after rooting it's stuck on the boot animation. When i plug the device into my PC and use the cmd prompt "adb devices" it won't see it. I help the power button and vol down to get to fastboot and my pc still won't see it. i've tried to factory reset though fast boot, says erasing, then reboots and still stuck. I updated everything in adb and still nothing. Everything went fine with unlocking the bootloader, but rooting it totally messed something up.
I can't seem to figure out how to get my PC to see this thing again. It's kind of a crap tablet to begin with, and now i brick it? totally frustrated.
Thanks
when you connect to pc,did you hear pop up connect sound..if yes then you connect to your pc..download google factory image,flash system.img,boot.img and all other .img image..hopefully you can restore tab back to nermal..good this is your tablet already unlocked bootloader.
Sent from my Nexus 9 using Tapatalk
Adb can do almost nothing when your device is in fastboot mode. Use fastboot to see if your device is connected to your computer if you didn't do so.
try "fastboot devices".
corkiejp said:
try "fastboot devices".
Click to expand...
Click to collapse
I just got "waiting for any device". I have the path set up to "C:\android-sdk\tools;C:\android-sdk\platform-tools". I haven't changed anything since i unlocked the bootloader so i'm just confused.
kacang87 said:
when you connect to pc,did you hear pop up connect sound..if yes then you connect to your pc..download google factory image,flash system.img,boot.img and all other .img image..hopefully you can restore tab back to nermal..good this is your tablet already unlocked bootloader.
Click to expand...
Click to collapse
The safely removed hardware icon does show up in the task bar. When i got to printers and devices there is an "android".
https://www.dropbox.com/s/a5chez6r9cuxjzo/Capture.JPG?dl=0
Can i use that port to force adb to see it? Not sure if this helps
gotta run to work, i'll mess with it this afternoon. Thanks guys.
First make sure your in "fastboot" mode and not in the bootloader.
Your device should show up as under Android Device as "Android Bootloader Interface" in device manager on your PC.
If not there then your drivers are not configured correctly, Nexus Root Toolkit has a guide on how to setup drivers correctly.
corkiejp said:
First make sure your in "fastboot" mode and not in the bootloader.
Your device should show up as under Android Device as "Android Bootloader Interface" in device manager on your PC.
If not there then your drivers are not configured correctly, Nexus Root Toolkit has a guide on how to setup drivers correctly.
Click to expand...
Click to collapse
I tried uninstalling the drivers from device manager and that didn't seem to do it. I went into the sdk and deleted them from the sdk then reinstalled them through the sdk and that seemed to work. I feel like i should have thought of that! duh. flashing CM13 now! hope i can get this to work haha jeeze.
thanks for the help guys
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
ItsJono said:
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
Click to expand...
Click to collapse
I believe you need to configure in the developers options that you don't want to have the recovery overwritten on reboot. What also seems to work is to boot into the TWRP from the command line via 'fastboot boot <recovery-file-name>'
I have the exact same problem. I have installed all drivers and adb, but as soon as i am into fastboot and my device doesnt show up in the command line. If i want to install the recovery the command line just says <waiting for device> and nothing happend.
I already enabled the "Enable AT Port" Settings (http://forum.le.com/in/index.php?threads/le-max-2-x820-qpst-not-working.14820/) but i think this is not permanent turned on on my phone, because i have to repeat this step after every reboot.
Anybody got some tips?
Edit: Also booting directly into TWRP doesnt work, 'fastboot boot <recovery-file-name>' just ends up in <waiting for device>..
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
RovnyiK said:
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
Click to expand...
Click to collapse
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Kampfgans said:
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Click to expand...
Click to collapse
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
RovnyiK said:
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
Click to expand...
Click to collapse
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Kampfgans said:
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Click to expand...
Click to collapse
Kampfgans: Klingt irgendwo zwischen lustig und richtig bedrohlich...
Lots of ROMs (including most CM variants) like to "automatically 'recover'" recoveries, that is they overwrite the recovery partition with a copy of the "original" every time you reboot.
I seem to remember that my first attempt to overwrite the stock recovery using "fastboot flash recovery <twrp-image-name>" also didn't succeed in making TWRP "stick".
Within the CM13 which I installed next (over the stock v15) there is a developer option to control that, but in this case I simply used a trick, which seems to bypass the recovery overwrite: I told the phone to boot the TWRP recovery over USB after flashing.
It went like this:
fastboot flash recovery <name-and-path-of-TWRP-recovery> //puts the TWRP image on the recovery partition
fastboot boot <name-and-path-of-TWRP-recovery> //bypasses the recovery overwrite logic of either the bootloader or whereever it hides
That booted TWRP over USB and allowed me to install CM13.
There I disabled recovery overwrite in the deveoper's options and I've never had issues with TWRP disappearing since.
Actually you should in theory be able to leave the stock recovery in place and still use TWRP by booting it over USB on the fastboot command line.
I install drivers and USB but when trying to go to fast boot I receive "waiting for device"