So, here's my dilemma. I'm trying to re-install my stock RUU, but it won't seem to initiate when I open the file. Yes, the set up wizard starts properly, but once I accept T&C ...it just goes away without starting up the process.
My theory is that ADB won't relay commands to my phone while in fastboot mode. When my phone is booted up and I open an cmd terminal in the adb folder, it works just fine. Sees my device perfectly and can reboot to bootloader, but once in bootloader no longer recognizes any further adb commands.
This used to work perfectly before......before I had to re-image the HDD on my PC. I feel like I must be missing a driver somewhere, but I've checked and rechecked everything I know and everything SEEMS to be in order. What on earth could I be missing??
I'm trying to wipe my phone to stock since I can't receive phone calls while running ViperM8 ROM any longer. Expert advice here would be greatly appreciated.
When your phone is in bootloader, it is in fastboot mode and will only accept fastboot commands, not adb. Be sure you have fastboot drivers. Best all in one drivers is installing Java SDK. That is how I got fastboot to work. You could alternatively run an ruu.zip from the root of the SD card.
Uzephi said:
When your phone is in bootloader, it is in fastboot mode and will only accept fastboot commands, not adb. Be sure you have fastboot drivers. Best all in one drivers is installing Java SDK. That is how I got fastboot to work. You could alternatively run an ruu.zip from the root of the SD card.
Click to expand...
Click to collapse
That makes sense since I can use "adb reboot bootloader" when the phone is booted just fine, but the command "adb devices" doesn't register anything. I used to be able to run my RUU exe from my PC with my phone in bootloader mode just fine, but now it just doesn't seem to work.
So I'm guessing I just need to find the actual RUU zip and manually install it using "fastboot oem rebootRUU" ?
Thanks for the response.
http://forum.xda-developers.com/att-htc-one-m8/general/exe-zip-ruu-m8att-4-4-4-s-off-onlynewest-t3015680
Need s-off, but the bootable ruu zips will work, just rename as dottat instructs.
Uzephi said:
http://forum.xda-developers.com/att-htc-one-m8/general/exe-zip-ruu-m8att-4-4-4-s-off-onlynewest-t3015680
Need s-off, but the bootable ruu zips will work, just rename as dottat instructs.
Click to expand...
Click to collapse
Awesome. I found that thread in my searches after your last reply. I appreciate the help. Now to test this when I get off work.
Related
Okay, here we go. I am new to rooting and I have already unlocked the bootloader on my device (HTC Evo 4G LTE). It still has S-on. After I unlocked my bootloader, I continued on to flash TWRP Recvovery onto my phone using fastboot. My phone does not have an SD card. However, no matter how many times I download the newest version of TWRP or rename the file or change the directory in the command prompt...it says "error: cannot load recovery image". When I attempt to restart in recovery mode, I get this red triangle with an explanation point! I have tried over and over again, but since I cant flash this recovery, i have an unlocked bootloader for practically no reason. I need to get past this step in order to start flashing custom ROM's. I even used RegawMOD EVO 4G LTE Rooter. After i click "Root Me" it puts my device into fastboot and attempts to submit the unlock token to HTCDev.com even though I already did that! I am stuck :crying:
Go here and download the recovery to your ADB tools folder.
http://techerrata.com/file/twrp2/jewel/openrecovery-twrp-2.3.3.0-jewel.img
You can rename the file "twrp" without the quotation marks. Make sure the file doesn't have an extra img extension or it won't work. Once you do this reboot your phone to the bootloader. Connect your phone to your computer via USB cable. You should see the word Fastboot in red highlights change to Fastboot USB. Open up ADB and type "fastboot flash recovery twrp.img" (without quotation marks) then press enter. At this point TWRP recovery should be installed on your phone.
If these are the steps you have followed, disregard.
The advice is free....the bandwidth, not so much
Thank You for Replying Good Sir!
1)when i download any twrp file and try to open it on my computer, it says "the disc image file is corrupted"
2)when i attempt to open ADB , it flashes up then off. I cant read what it says
3)i entered the command in the command prompt and it just says waiting for device
gratealex8 said:
1)when i download any twrp file and try to open it on my computer, it says "the disc image file is corrupted"
2)when i attempt to open ADB , it flashes up then off. I cant read what it says
3)i entered the command in the command prompt and it just says waiting for device
Click to expand...
Click to collapse
Download this extract it to your desktop and run your commands from that folder by pressing shift and right clicking on an empty spot inside the folder and choose open cmd window here.
There is a readme.txt inside follow the instructions on how to fastboot flash twrp (Copy and paste is the easiest way to do this that way there are no typo's)
Use v2.4.1.0 if you are on the latest OTA
Use v2.3.1.0 otherwise
idk whats wrong!!
I did exactly as you said, yet the command prompt just says waiting for device. I'm not sure what to do anymore because regardless of following these instructions, I CANT FLASH TWRP RECOVERY TO MY PHONE. I believe the problem is with my phone but Im running out of options. its beginning to look like I unlocked my bootloader for nothing :/
gratealex8 said:
I did exactly as you said, yet the command prompt just says waiting for device. I'm not sure what to do anymore because regardless of following these instructions, I CANT FLASH TWRP RECOVERY TO MY PHONE. I believe the problem is with my phone but Im running out of options. its beginning to look like I unlocked my bootloader for nothing :/
Click to expand...
Click to collapse
Try these drivers.Install them and reboot your PC once rebooted go to add/remove programs and delete HTC Sync
Getting frustrated
bigdaddy619 said:
I did this and again all I get in the command prompt is waiting for device. No more ideas huh?
Click to expand...
Click to collapse
use command fastboot erase cache and cmd says waiting for device. nothing happens in fastboot. i think i may have a bad driver? tried htc sync and wont recognize phone, possibly due to cm. tried 3 of mdms htc drivers, but nothings working
Did you run "fastboot devices" first to make sure the PC recognized the device?
computer recognizes phone whilst phone is not in bootloader. when you phone is in fastboot its supposed to read fastboot usb, but it just says fastboot. then i get a prompt on comp that windows cant recognize the device.
i have the ruu downloaded does anyone remember what i have to rename it to? its like PJ53.img but im not sure. you move the ruu to the root of sd card and and flash via bootloader that why instead of adb
Linch89 said:
i have the ruu downloaded does anyone remember what i have to rename it to? its like PJ53.img but im not sure. you move the ruu to the root of sd card and and flash via bootloader that why instead of adb
Click to expand...
Click to collapse
PJ53IMG.zip
thanks i just found andybones old thread. these types of things really need to be stickied
Alright lads, I got a major issue that is kicking my ass. I need your help please.
Basically the HTC ONE X+ keeps getting error closed in ADB sideload whenever I try to sideload a rom or do anything else for the matter.
adb usb = Error Closed
Adb push and pull = Error Closed.
I can get my device listed but thats about it.
The Issue goes further. I relocked the bootloader in order to install the RUU. Yet I get the error 131 custormer ID error.
I can't access the SD partition on the my computer screen as it doesn't show.
I can't get back to stock rom.
I can't install a new rom.
I can unlock and relock my bootloader.
I can install TWRP and CWM.
I can use fastboot usb. [Very limited]
The issue with fastboot usb is that it keeps saying error device not found and then it refuses to do anything.
I have installed and reinstalled the ADB drivers, SDK manager and htc sync manager.
The biggest issue at the moment is that I can't install any rom whatsoever.
Which basically means, its a potato.
HALLLLP. The htc one x is a international version. UK Vodafone more specifically. Hboot-1.35.0000
Oh yeah, the mount does not work in TWRP and CWM.
I tried different USB ports, cables and even a different computer.
Everything has been wiped. I factory reset it and wiped out other parts in TWRP and CWM in an effort to start from scratch.
Nothing seems to work though...
Edit: I narrowed down the issue
It seems that i can't flash boot.img when my bootloader is unlocked as:
'boot.img'...FAILED (command write failed (Unknown error))
therefore I can't load roms without it crashing on me.
I can however put things into the 'sd card' by loading a broken rom [crashes to process android]. But thats about it. so far.
Oh I also updated the hboot to 1.72
NinjaKenZen said:
Alright lads, I got a major issue that is kicking my ass. I need your help please.
Basically the HTC ONE X+ keeps getting error closed in ADB sideload whenever I try to sideload a rom or do anything else for the matter.
adb usb = Error Closed
Adb push and pull = Error Closed.
I can get my device listed but thats about it.
The Issue goes further. I relocked the bootloader in order to install the RUU. Yet I get the error 131 custormer ID error.
I can't access the SD partition on the my computer screen as it doesn't show.
I can't get back to stock rom.
I can't install a new rom.
I can unlock and relock my bootloader.
I can install TWRP and CWM.
I can use fastboot usb. [Very limited]
The issue with fastboot usb is that it keeps saying error device not found and then it refuses to do anything.
I have installed and reinstalled the ADB drivers, SDK manager and htc sync manager.
The biggest issue at the moment is that I can't install any rom whatsoever.
Which basically means, its a potato.
HALLLLP. The htc one x is a international version. UK Vodafone more specifically. Hboot-1.35.0000
Oh yeah, the mount does not work in TWRP and CWM.
I tried different USB ports, cables and even a different computer.
Everything has been wiped. I factory reset it and wiped out other parts in TWRP and CWM in an effort to start from scratch.
Nothing seems to work though...
Edit: I narrowed down the issue
It seems that i can't flash boot.img when my bootloader is unlocked as:
'boot.img'...FAILED (command write failed (Unknown error))
therefore I can't load roms without it crashing on me.
I can however put things into the 'sd card' by loading a broken rom [crashes to process android]. But thats about it. so far.
Oh I also updated the hboot to 1.72
Click to expand...
Click to collapse
If you can push files on sd card, use the TWRP back-up from here to restore to stock.
http://forum.xda-developers.com/showthread.php?t=2414238
You'll at least get it working again.
Thanks, somehow when I updated the bootloader, the boot.img restriction got lifted after I just entered the command again when 'unknown failure' came up. I was at this point able to access the sd card under a buggy rom start-up.I used TWRP to flash a new rom.
Fixed.
Hi..
I also can't connect my device to PC
I need help ..
fastboot not working never
loaybilal said:
Hi..
I also can't connect my device to PC
I need help ..
fastboot not working never
Click to expand...
Click to collapse
To anyone in the same situation adb sideload does not transfer the file to the sdcard permanently. To sideload correctly, you need to pick that option from the recovery first and then when the phone is waiting for the sideload type:
adb sideload <PACKAGE>
after some hours of research mine worked (TWRP v2.7.0.1)
imcontreras said:
To anyone in the same situation adb sideload does not transfer the file to the sdcard permanently. To sideload correctly, you need to pick that option from the recovery first and then when the phone is waiting for the sideload type:
adb sideload <PACKAGE>
after some hours of research mine worked (TWRP v2.7.0.1)
Click to expand...
Click to collapse
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
roshak said:
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
Click to expand...
Click to collapse
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
imcontreras said:
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
Click to expand...
Click to collapse
So now! I could get my devices connected and listed with updating the drivers (Win 8.1) ...
Then I could push the SuperSU.zip and install it... Is there any way to check if it's ready for flashing a ROM?
roshak said:
So now! I could get my devices connected and listed with updating the drivers (Win 8.1) ...
Then I could push the SuperSU.zip and install it... Is there any way to check if it's ready for flashing a ROM?
Click to expand...
Click to collapse
Im not sure if this will answer your question:
When you upload your rom using sideload will automatically flash it to your device
imcontreras said:
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
Click to expand...
Click to collapse
Thank you!
So I recently had my phone temporarily rooted via weaksauce, however, after updating to Sense 6 with the Verizon OTA update, weaksauce will not root properly and it continues to fail. Is there no way to fix this or am I missing something with the OTA update? I sort of need to use weaksauce because I am not confident in my rooting ability to be able to restore the phone to factory when I turn it in for an upgrade in a few months.
none
I would start over. The posts on how to root are very good. There are also youtube videos you can watch. It really is very easy to root this device. if nothing else load a program called team viewer on your computer and I will root it for you, but I want you to try first. You will use something called rumrunner. PM me if you need help
AlphaMons said:
So I recently had my phone temporarily rooted via weaksauce, however, after updating to Sense 6 with the Verizon OTA update, weaksauce will not root properly and it continues to fail. Is there no way to fix this or am I missing something with the OTA update? I sort of need to use weaksauce because I am not confident in my rooting ability to be able to restore the phone to factory when I turn it in for an upgrade in a few months.
Click to expand...
Click to collapse
I would second that. If you are going to root a phone for the first time this is the one to start with. It is extremely well documented and this is a very helpful forum. I had the same feelings when I started (HTC Wildfire) back in the day and I did about everything wrong but in the end figured it out. Now there a several helpful threads and videos as stated above. I would recommend that you do a dry run, have everything together and go through the steps one by one in your mind or on paper before doing the actual root. You may miss something but your odds are better. Trust yourself I thoroughly believe any can root this phone and it's easier than you think and the value besides learning of the great ROMs that are here etc. is well worth it. Even if you temp root it you are going to have to know what to do to get it back before you turn it in so the knowledge will be necessary.
Are you on hboot 2.49
statmonkey said:
I would second that. If you are going to root a phone for the first time this is the one to start with. It is extremely well documented and this is a very helpful forum. I had the same feelings when I started (HTC Wildfire) back in the day and I did about everything wrong but in the end figured it out. Now there a several helpful threads and videos as stated above. I would recommend that you do a dry run, have everything together and go through the steps one by one in your mind or on paper before doing the actual root. You may miss something but your odds are better. Trust yourself I thoroughly believe any can root this phone and it's easier than you think and the value besides learning of the great ROMs that are here etc. is well worth it. Even if you temp root it you are going to have to know what to do to get it back before you turn it in so the knowledge will be necessary.
Click to expand...
Click to collapse
rumrunner will not work if he's on the ota update of sense 6, he will have to flash a custom recovery, do a nandroid backup, flash vipermax rom, and run firewater.
as to the OP, it's very easy to do, follow the guides for setting up SDK/ADB, download the appropriate custom recovery for your device (i personally like TWRP the best), place that file in your adb folder that you made from the SDK/ADB guide, unlock your bootloader if not already (i did mine via HTCdev, they have a guide). then boot into the bootloader via power+vol down, scroll with volume keys, and select with power button, go to fastboot, plug in your usb cable to your computer, if you have the drivers it will change on your device "fastboot usb". then open up a command prompt in your SDK/ADB folder (do this by shift+right click in the folder and select open command prompt here). in your command prompt type in "adb devices" to make sure your drivers are right and it see's your device. now type in "fastboot oem rebootRUU", your phone will go to a black screen that says HTC on it. now type in "fastboot flash recovery "put the name of the recovery file here".img", then after that completes without any errors, type "fastboot reboot-bootloader" press the power button with bootloader selected, scroll to recovery and press power button, once you're in recovery, do a nand backup of your stock rom, after you've done that while still in recovery, i would strongly suggest saving this backup file to your computer, you can do this in ADB by typing in "adb pull /sdcard/TWRP" and it will pull the entire directory with your backup in it.
to gain s-off and fullroot, download vipermax rom for your device, while in recovery still, you can put the rom zip file in your ADB folder, and in ADB type "adb push "Name of the zip file" /sdcard" and it will copy and paste the rom zip to your sd card, once you see it finish in the command prompt, click on install on your phone, scroll to the zip file and click on it.
when the phone boots up, make sure you connect to wifi and go through the setup, once that is done download the Firewater file, and follow the instructions. and you should get s-off, now in adb type "adb reboot recovery" and then click on restore, and restore your stock rom, now you're stock rooted, with s-off.
set up ADB guide/download here http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=226534558
TWRP guid/download here http://forum.xda-developers.com/showthread.php?t=2498746
Vipermax rom download here http://forum.xda-developers.com/showthread.php?t=2596938
Firewater guide/downloade here http://firewater-soff.com/instructions/
And i think that should be it, if after you do this and want to flash back stock recovery it's pretty simple, find and download the recovery image for the version of rom, you're using, for instance, your ota update should or will probably be in your downloads folder, if you open it with zip, (i use winrar) you will find a zip in it named "Firmware.zip" open it up, and you will see a file named recovery, extract it to your ADB Folder, boot into the "Fastboot oem rebootRUU", then simply type "fastboot flash recovery recovery.img" let that finish, then type "fastboot reboot" and it will start your phone, and now you'll have the stock recovery and be able to receive and install future OTA updates, if there is any. >.<
mrkrowely said:
rumrunner will not work if he's on the ota update of sense 6, he will have to flash a custom recovery, do a nandroid backup, flash vipermax rom, and run firewater.
as to the OP, it's very easy to do, follow the guides for setting up SDK/ADB, download the appropriate custom recovery for your device (i personally like TWRP the best), place that file in your adb folder that you made from the SDK/ADB guide, unlock your bootloader if not already (i did mine via HTCdev, they have a guide). then boot into the bootloader via power+vol down, scroll with volume keys, and select with power button, go to fastboot, plug in your usb cable to your computer, if you have the drivers it will change on your device "fastboot usb". then open up a command prompt in your SDK/ADB folder (do this by shift+right click in the folder and select open command prompt here). in your command prompt type in "adb devices" to make sure your drivers are right and it see's your device. now type in "fastboot oem rebootRUU", your phone will go to a black screen that says HTC on it. now type in "fastboot flash recovery "put the name of the recovery file here".img", then after that completes without any errors, type "fastboot reboot-bootloader" press the power button with bootloader selected, scroll to recovery and press power button, once you're in recovery, do a nand backup of your stock rom, after you've done that while still in recovery, i would strongly suggest saving this backup file to your computer, you can do this in ADB by typing in "adb pull /sdcard/TWRP" and it will pull the entire directory with your backup in it.
to gain s-off and fullroot, download vipermax rom for your device, while in recovery still, you can put the rom zip file in your ADB folder, and in ADB type "adb push "Name of the zip file" /sdcard" and it will copy and paste the rom zip to your sd card, once you see it finish in the command prompt, click on install on your phone, scroll to the zip file and click on it.
when the phone boots up, make sure you connect to wifi and go through the setup, once that is done download the Firewater file, and follow the instructions. and you should get s-off, now in adb type "adb reboot recovery" and then click on restore, and restore your stock rom, now you're stock rooted, with s-off.
set up ADB guide/download here http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=226534558
TWRP guid/download here http://forum.xda-developers.com/showthread.php?t=2498746
Vipermax rom download here http://forum.xda-developers.com/showthread.php?t=2596938
Firewater guide/downloade here http://firewater-soff.com/instructions/
And i think that should be it, if after you do this and want to flash back stock recovery it's pretty simple, find and download the recovery image for the version of rom, you're using, for instance, your ota update should or will probably be in your downloads folder, if you open it with zip, (i use winrar) you will find a zip in it named "Firmware.zip" open it up, and you will see a file named recovery, extract it to your ADB Folder, boot into the "Fastboot oem rebootRUU", then simply type "fastboot flash recovery recovery.img" let that finish, then type "fastboot reboot" and it will start your phone, and now you'll have the stock recovery and be able to receive and install future OTA updates, if there is any. >.<
Click to expand...
Click to collapse
Really an excellent post it's nice to have all that in one place. I also was unable to get rumrunner to work and have used firewater quite successfully (which was part of what I was trying to point out above). Also, I was unable to get HTCdev to unlock my phone. That may or may not be about me. I am a Linux person and I think I might have had the wrong adb/fastboot at the time. The one in the android sdk did not work for me but for anyone on LInux who is interested the one in this link did http://forum.xda-developers.com/htc-one-max/help/andrenaline-rom-constant-reboot-t2853591
Once again, excellent summary, I will be bookmarking this for later.
I think all of the above info is great and everyone trying to help is awesome. However I really liked having a soft root via weaksauce for a very limited amount of apps like titanium backup and root explorer. So am I to understand that there is no newer Weaksauce or similar available for 4.4.2 and sense 6?
Enjoyment to the MAX!
bryanfritz1 said:
I think all of the above info is great and everyone trying to help is awesome. However I really liked having a soft root via weaksauce for a very limited amount of apps like titanium backup and root explorer. So am I to understand that there is no newer Weaksauce or similar available for 4.4.2 and sense 6?
Enjoyment to the MAX!
Click to expand...
Click to collapse
As far as I am aware firewater still works. I used it just a few days ago and just saw a post today http://forum.xda-developers.com/htc-one-max/help/gain-s-off-t2849836 although he doesn't clearly state that he was using sense 6,
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Ok, I am an idgit. Could a mod move this to the Q&A forum? Apologies.
EqualOpportunityDork said:
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Click to expand...
Click to collapse
ADB works in an OS or in custom recovery and fastboot works in the bootloader. ADB doesn't work if the phone is in bootloader. I think you will have to run a RUU then go into stock recovery and do a factory reset. Let the phone boot normally then you can start the custom routine. You might also check to see if your ADB & fastboot are up to date. To run the RUU you will have to relock your bootloader since you are S-ON.
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
EqualOpportunityDork said:
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
Click to expand...
Click to collapse
Another quick thought, you wouldn't happen to be using Win 8 are you? If so, Win 8 doesn't see hboot 1.44 you are going to have to use a Win 7, Mac or Linux machine. Sorry, I didn't catch it earlier. Here is a how to for Linux and you don't have to install it permanently on your computer:
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
Click to expand...
Click to collapse
Dude, you are my hero. I couldn't get fastboot to work, because I had missed the part where I needed to preface it with sudo. I had adb and fastboot running a couple of days ago on my Mint install, but I didn't realize I was missing 4 freaking letters to get it right. Just flashed latest twrp and booted into recovery, no problem.
Thanks again, for the help, even if I should have found that on my own, sooner. I thought I had really hosed something on my phone. Now I can move on to hopefully not screwing something else up.
You could have used flashify to flash a recovery.IMG. free app from app store
I mentioned trying Flashify in the OP.