ok guys this is not my first rodeo. I have hacked all my prior phones but I need some assistance here...
I have unlocked my bootloader, rooted and installed CWM. Now I am trying to install a system writable Kernel and modules so I can install a Rom. I am having a problem getting ADB to see my phone. When I do adb devices it comes up blank and will not push the modules to my phone. I have re-installed the HTC manager driver files and restarted my PC. Windows 7 64 bit.
Can someone give me some ideas on how to get adb to see my phone?
Also can someone give me some specific instructions with adb commands to install the kernel and modules and what exactly I need to have in my adb folder??
Any help is appreciated...
Memnoch73 said:
ok guys this is not my first rodeo. I have hacked all my prior phones but I need some assistance here...
I have unlocked my bootloader, rooted and installed CWM. Now I am trying to install a system writable Kernel and modules so I can install a Rom. I am having a problem getting ADB to see my phone. When I do adb devices it comes up blank and will not push the modules to my phone. I have re-installed the HTC manager driver files and restarted my PC. Windows 7 64 bit.
Can someone give me some ideas on how to get adb to see my phone?
Also can someone give me some specific instructions with adb commands to install the kernel and modules and what exactly I need to have in my adb folder??
Any help is appreciated...
Click to expand...
Click to collapse
As far as getting your phone to be recognized, try installing HTC Sync and then immediately uninstalling it, I have seen this fix many people's driver issues.
This is how I usually flash my kernels: Assuming you have fastboot in the same folder as adb, put the boot.img and the modules.zip in that same folder. Boot into recovery. In recovery do:
adb push modules.zip /sdcard/whatever (whatever folder you keep your flashables in)
Then hit install in recovery, find the file you just pushed and flash it. Then do:
adb reboot bootloader
Then while you are in bootloader (Should say "fastboot usb" in red) do this:
fastboot flash boot boot.img (replace boot.img if your file is named differently)
You should see it flash the file, and finally do:
fastboot reboot
Thanks man. I think I have it now. When I did fastboot devices it showed my phone. Also I was confused about the modules after more reading I just put them on my sd card and flashed them in recovery.
I have the stock system writable kernel installed and modules flashed. All looks good. Booted up and its says dsb's kernel in my about phone.
I think I'm off to flash a rom now.
Thanks
Related
After trying to flash AndroWook using Goo Manager, I managed to become stuck in the boot animation. I've tried fastbooting stock system blobs, with no good results. I flashed CWM over TWRP, but CWM can't find any files on my SD. Now I'm trying to ADB push a blobfile (using these directions http://forum.xda-developers.com/showpost.php?p=25216525&postcount=23), but I'm not finding my device.
Can anyone please help me out? I'm so tired of my bricked Prime. There has to be some way that I can be able to flash a ROM onto this thing.
If you have a ROM in a blobbed format, then try the following, as you apparently can connect to your TFP via fastboot:
fastboot -i 0x0b05 flash staging BlobbedRomThatYouAreLoading
This should be similar to the method you used in flashing CWM over TWRP, except you're flashing to the staging partition instead of the recovery partition. On reboot, your ROM should install and load.
A lot of users seem to be having problems connecting to TFP over ADB when in CWM. I'd personally stick with TWRP, as it seems more stable.
Edit:
If the above doesn't work, then I would try flashing TWRP again, then while in TWRP, see if you can connect via ADB. If ADB is still not recognizing your device, then please see this thread and try re-installing your ADB drivers using there:
http://forum.xda-developers.com/showthread.php?t=1426502
kokopuphz said:
If you have a ROM in a blobbed format, then try the following, as you apparently can connect to your TFP via fastboot:
fastboot -i 0x0b05 flash staging BlobbedRomThatYouAreLoading
This should be similar to the method you used in flashing CWM over TWRP, except you're flashing to the staging partition instead of the recovery partition. On reboot, your ROM should install and load.
A lot of users seem to be having problems connecting to TFP over ADB when in CWM. I'd personally stick with TWRP, as it seems more stable.
Edit:
If the above doesn't work, then I would try flashing TWRP again, then while in TWRP, see if you can connect via ADB. If ADB is still not recognizing your device, then please see this thread and try re-installing your ADB drivers using there:
http://forum.xda-developers.com/showthread.php?t=1426502
Click to expand...
Click to collapse
been here done this, install the universal naked drivers first.... then install twrp since it seems to work better then cwm.... then adb push a small file to see of it actually works then push rom and install....
I've got this working up until I try to push something. Pushing something fails because of a "Read only file system."
How do I get my prime to be read/write?
You should fastboot flash twrp, boot to recovery, fixpermissions, then push the rom
Sent from my Transformer Prime TF201 using xda premium
Fixing permissions from TWRP did not help.
im just getting told that fastboot is a not a recognised command which seems like a nooby outcome
I rooted my htc evo 4g lte and have twrp installed, and tried to flash a rom, when i rebooted it always takes me back to hboot screen and is stuck there, won't actually boot up. I am able to go to recovery and use twrp including usb mount (maybe a zip i could flash to help). I have searched for awhile but haven't found any real solution for my phone yet.
I have S-on, no external sd card.
If you need any more info just ask.
Thanks in advance for the help!
Extract the boot.img from the rom, place it in adb folder and put phone in fastboot
Type fastboot flash boot boot.img and restart the phone
solved!!!!!!!
om4 said:
Extract the boot.img from the rom, place it in adb folder and put phone in fastboot
Type fastboot flash boot boot.img and restart the phone
Click to expand...
Click to collapse
Thankyou so much for the fast reply, and fix!! I did what you said and it worked! The funny thing is that it was my first flash, is there something i did or should avoid to have this happen to me again? Any way I am so grateful and now am going to try out team venoms viper4g 2.0.2 new rom!
If others have the same problem and want more detailed info about what I did:
1. downloaded sdk manager developer.android.com/sdk/index. html opened the program and installed platform tools
2. Since I have twrp I put into recovery and mounted usb found the zip of the rom i wanted to flash opened it found the boot.img and copied it to the folder where platform tools where installed (C:\Users\yourname\AppData\Local\Android\android-sdk\platform-tools)
3. got back to hboot screen
4. opened cmd to the folder by typing: cd then file path like mine above
5. then in cmd typed fastboot flash boot boot.img it will do its thing
6. restart phone and hopefully work for you too!
vipomorge said:
Thankyou so much for the fast reply, and fix!! I did what you said and it worked! The funny thing is that it was my first flash, is there something i did or should avoid to have this happen to me again? Any way I am so grateful and now am going to try out team venoms viper4g 2.0.2 new rom!
If others have the same problem and want more detailed info about what I did:
1. downloaded sdk manager developer.android.com/sdk/index. html opened the program and installed platform tools
2. Since I have twrp I put into recovery and mounted usb found the zip of the rom i wanted to flash opened it found the boot.img and copied it to the folder where platform tools where installed (C:\Users\yourname\AppData\Local\Android\android-sdk\platform-tools)
3. got back to hboot screen
4. opened cmd to the folder by typing: cd then file path like mine above
5. then in cmd typed fastboot flash boot boot.img it will do its thing
6. restart phone and hopefully work for you too!
Click to expand...
Click to collapse
If you are s-on, the kernel won't flash with the rom so you have to flash it separately like om4 showed you. Some roms, like MeanRom have modified their install script to automatically load the kernel to avoid this extra step.
The latest Mean installer failed for me, as did the latest Viper, something to keep in mind if you try those and they don't boot
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
also to note....you dont have to install linux to get s-off....if you follow my guide you can do it straight from a live disk rather than installing it....so it wont erase or mess up your windows partition at all
Solved!
Thank you, Mjones, I finally got it! I knew it was much easier than I was making it out to be. I was missing the kernel! Yeah, a crucial part in the process, I know
I first ran CWM and flashed the ROM over and ran the .zip through recovery (which I couldn't understand at first as I could never find it in the directory) but the installer would only go 50% and would fail... makes sense why now lol
I later flashed TWRP and backed up again after recovering from the fail. I flashed over the kernel and voila! So simple... Had to slap myself.
Thanks again! Case solved.
REV3NT3CH, that is sweet!! I have been hoping there is a way to gain s-off with Windows. I have 7 at work and 8.1 (which I can't get anything to work on) at home. I actually have to focus on work today haha so I'll look into the method and try it out tomorrow if I can. Thanks for all of the help.
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Sorry, don't know anything about that phone.
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Did you try this first? (Right from Moto's site)
Perform a factory reset using external keys
1. Power off the phone, press and hold volume down button, press power button
2. Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", then press Vol up key
3. Wait for the "triangle ! / Android" screen then go on to step 4
4. Press both Vol up and Vol down key simultaneously. A menu will come up
5. Tap on Vol down key until "wipe data/factory reset" is highlighted, and tap Power key. Another Confirmation screen will come. Tap on Vol down key until coming to Yes and tap Power key
6. After userdata is cleared, the "reboot system now" option will be highlighted by Default. Tap Power key
7. Phone will reboot to initial setup screen.
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
not working
hariom.gupta11 said:
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
Click to expand...
Click to collapse
not working on my 4c. write successful but when reboot is completed it goes to previous state.
"the user data partition can no longer be used"
zb602kl_x00tdb
L0RDZ3RO said:
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
Click to expand...
Click to collapse
I have same problem on asus zenfone max pro m1 I bought it online said used and now working
can't boot into recovery.
can't boot into system.
Only EDL Mode and Fastboot Mode, but fastboot is Locked whic I cant unlock because I cannot boot into system to toggle USB Debugging and allow OEM unlocking
Qualcomm is harder to flash than MTK that can use SP FlashTool.
on this I use QFIL but keeps "sahara error". I tried searching and try moving firmware file to bin but no Luck. I'm currently trying different version of QFIL Tool.
If it FAILS my only HOPE is to use MUT-QCfire which will Require a "SmartCardReader" Which is a bit pricey and I don't even know if it will work on my device.
Hello
i managed to unlock my bootloader, flashed twrp recovery, flashed super user.
Tried to install dirty unicorn and got status 7 error.
And now i dont have a rom/os installed.
I tried to move over .zip files through twrp but cant mount drives.
Any help?!?
I TRIED TO PUSH ZIP WITH SIDELOAD AND NO LUCK
BUMP!
i really need to get this fixed please help
xr1charxx said:
BUMP!
i really need to get this fixed please help
Click to expand...
Click to collapse
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
dsf767 said:
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
Click to expand...
Click to collapse
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
xr1charxx said:
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
Click to expand...
Click to collapse
I would try to plug in the USB after your already in recovery.
If you cant get that to work you can always buy this:
https://shopmeenova.appspot.com/st/order.html
its a microusb to microsd its a good worst case and will get you up and running.
do you still have the rom that errored out on you on your internal storage? if so you can always try a fresh wipe and try to install again.
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.