Database Develop

[Q] 1,31 , no rom or adb

So basically the only thing working in fastboot
somehow i have managed to wipe everything off of my device so there is no rom installed what so ever...which means i am unable to turn on usb debugging to get adb working. I am also on 1.31 so the RUU method will not work. i am able to flash whatever recovery or Superuser i wish and root/unroot as i please.
the only solution i can think of would be to flash a signed stock zip using "fastboot update signedstock.zip" but the ones i found here -http://forum.xda-developers.com/showthread.php?t=2368907 dont seem to work. i get errors like no "boot.img" or "does not contain android-info.txt"
any suggestions?
thanks for your time

shadowtdt09 said:
So basically the only thing working in fastboot
somehow i have managed to wipe everything off of my device so there is no rom installed what so ever...which means i am unable to turn on usb debugging to get adb working. I am also on 1.31 so the RUU method will not work. i am able to flash whatever recovery or Superuser i wish and root/unroot as i please.
the only solution i can think of would be to flash a signed stock zip using "fastboot update signedstock.zip" but the ones i found here -http://forum.xda-developers.com/showthread.php?t=2368907 dont seem to work. i get errors like no "boot.img" or "does not contain android-info.txt"
any suggestions?
thanks for your time
Click to expand...
Click to collapse
Guide in General on how to downgrade. You'll be fine.
http://forum.xda-developers.com/showthread.php?t=2390821

Indirect said:
Guide in General on how to downgrade. You'll be fine.
http://forum.xda-developers.com/showthread.php?t=2390821
Click to expand...
Click to collapse
i have tried that for cwm recovery but that requires adb and usb debugging...which i dont have
i have also just tried it with the htc recovery where the screen just shows the HTC logo but "adb devices" says no devices are connected

shadowtdt09 said:
i have tried that for cwm recovery but that requires adb and usb debugging...which i dont have
i have also just tried it with the htc recovery where the screen just shows the HTC logo but "adb devices" says no devices are connected
Click to expand...
Click to collapse
Then oh well? There is no other way to fix it than using TWRP / CWM and adb / fastboot.

Indirect said:
Then oh well? There is no other way to fix it than using TWRP / CWM and adb / fastboot.
Click to expand...
Click to collapse
There are no signed stock zips out there that i can use fastboot update .zip ?

shadowtdt09 said:
There are no signed stock zips out there that i can use fastboot update .zip ?
Click to expand...
Click to collapse
http://teamviewer.com/download
Get that, pm me your id and password and I'll fix your phone. Have nothing better to do for a half hour anyway.

Indirect said:
http://teamviewer.com/download
Get that, pm me your id and password and I'll fix your phone. Have nothing better to do for a half hour anyway.
Click to expand...
Click to collapse
you're a hell of a man indirect!

Aldo101t said:
you're a hell of a man indirect!
Click to expand...
Click to collapse
Tis the benefit of having no job. Easily able to help everyone out if I'm bored.

shadowtdt09 said:
So basically the only thing working in fastboot
somehow i have managed to wipe everything off of my device so there is no rom installed what so ever...which means i am unable to turn on usb debugging to get adb working. I am also on 1.31 so the RUU method will not work. i am able to flash whatever recovery or Superuser i wish and root/unroot as i please.
the only solution i can think of would be to flash a signed stock zip using "fastboot update signedstock.zip" but the ones i found here -http://forum.xda-developers.com/showthread.php?t=2368907 dont seem to work. i get errors like no "boot.img" or "does not contain android-info.txt"
any suggestions?
thanks for your time
Click to expand...
Click to collapse
just a fyi you can use fastboot to flash a rom if you put it in the same folder as the platform tools folder of your sdk, All roms have a android-info.txt file that's how android knows how to flash what to the particular partition.
you can flash any zip file from fastboot as long as it has the android-info file
fastboot flash zip nameofzip.zip

Fixed his phone and found out he is in my area. Pretty small world.

Indirect said:
Fixed his phone and found out he is in my area. Pretty small world.
Click to expand...
Click to collapse
I'm in fort myers

ktu84m UpDater

Edit, your bootloader must be unlocked to use this. If your bootloader is not already unlocked, unlocking it will wipe your data and this method is not recommended.
This is a modified factory image that will not erase your user data or custom recovery. This can be used even if you’re rooted and with modified system files, xposed framework, or custom recovery. Once installed you will lose root, just flash supersu in your custom recovery. Xposed should still be on your device so just go into the app and re-install it. For any modified system files, you will have to re-modify those.
This is intended for those on the stock rom, rooted, and with a custom recovery. It’ll work if you have a custom rom but will put the stock system on.
I am not responsible for anything you do to your device so flash at your own risk. Always backup before doing any significant changes to your device. I would recommend off your device in case something happens
.
To use, download the modified factory image here http://d-h.st/OEl Use 7-zip or winrar to extract the files.
Mirror https://mega.co.nz/#!EVQyiaSR!sUIKUSR40EQSbL2p6OaOZq2NBxrWs0opbc6IbgbGVvI
Supersu by chainfire can be found here, CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
Boot into the bootloader. From a cmd window opened where the flash-all file is just type flash-all. You can use shift, right click on the hammerhead-ktu85m-Modified folder to open a command window in the correct folder.
You can also just double click on the flash-all.bat
This is tested on a windows machine; however it should work on a Mac too, flash the flash-all.sh.

Gonna give this a shot

So far, so good. I just flashed jd1639's modified factory image using the provided instructions. Please note, there is a bit of a pause during the process, in all, it took around 78 seconds to complete. My N5 now says Android is upgrading. I'm in ART mode, so this will take a while. I will edit this post once it is completely up and running.
Thanks jd1639!
UPDATE: Everything seems to work fine, however my signal levels are not reporting as high as they were with the .17 baseband on Sprint. So I guess I won't have LTE in my office at all!

Any chance of a zip file to flash from custom recovery
Code_Blue N5

i'm getting fastboot is not recognized as internal or external command:??? Any ideas?
---------- Post added at 05:46 PM ---------- Previous post was at 05:30 PM ----------
Not working!... typed flash-all
fastboot is not rfecogniczed as internal or external command

MandoH said:
i'm getting fastboot is not recognized as internal or external command:??? Any ideas?
Click to expand...
Click to collapse
You don't have fastboot set up.
Edit, just double click on flash-all.bat. See if that works
Sent from my Nexus 5 using XDA Free mobile app

Does it work for D821 ?
When tried downloading, it says not available for my country..(India)
Sent from my Nexus 5 using XDA Free mobile app

double clicked and still samething persist.. any suggestions?

Is it okay to flash this with a custom kernel installed?

MandoH said:
double clicked and still samething persist.. any suggestions?
Click to expand...
Click to collapse
Install minimal adb & fastboot from this thread http://forum.xda-developers.com/showthread.php?t=2317790
Extract the rar folder of the ktu84m image to the install folder containing fastboot.exe
Run the flash-all.bat. It should now work

This will flash the stock 4.4.3 kernel.
Sent from my Nexus 5 using Tapatalk

confirmed working on Mac OS X, thanks jd1639!

trd360 said:
Is it okay to flash this with a custom kernel installed?
Click to expand...
Click to collapse
It'll work but will replace your kernel

worked perfectly on first try...window 8...thanks for this brother

trd360 said:
Is it okay to flash this with a custom kernel installed?
Click to expand...
Click to collapse
Same question (more specifically with Franco Kernel)?

Creed0 said:
Same question (more specifically with Franco Kernel)?
Click to expand...
Click to collapse
Yes, but it'll put the stock kernel on

hikarugo said:
Install minimal adb & fastboot from this thread http://forum.xda-developers.com/showthread.php?t=2317790
Extract the rar folder of the ktu84m image to the install folder containing fastboot.exe
Run the flash-all.bat. It should now work
Click to expand...
Click to collapse
This method worked well!!!! thanks a lot!!!:good::cyclops:

Great work. Thank you

Is it possible to use flashify for this?
Sent from my Nexus 5 using XDA Free mobile app

vipinbp said:
Is it possible to use flashify for this?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No
Sent from my Nexus 5 using XDA Free mobile app

[LOLLIPOP 5.1][STOCK] Cherry Mobile One H940 Official Links

Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.

do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks

Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.

intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you

Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/

OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.

erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.

intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.

erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.

intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance

Sir
can you capture ota for myphone uno

gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.

still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM

Working internal detect for pc and file ?

marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.

intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM

marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.

success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man

Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!

OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.

Nexus 6 stuck at google screen , Need Assistance.

So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you

I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app

faraz90 said:
So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you
Click to expand...
Click to collapse
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.

Evolution_Tech said:
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.
Click to expand...
Click to collapse
gee2012 said:
I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.

faraz90 said:
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.
Click to expand...
Click to collapse
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.

simms22 said:
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.
Click to expand...
Click to collapse
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/

faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
If your Android SDK is more than 6 months old, you may need to update it. Google updated fastboot to allow flashing these very large files.

faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
Click to expand...
Click to collapse
No, by using fastboot commands.. The location of the images you flash is irrelevant.
faraz90 said:
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
Either there is a problem with the system.img (redownload) or there is a problem with the flash memory on your device.
You could flash a custom recovery and use that to flash a zipped ROM to see.if that makes any difference.

faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.

Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.

simms22 said:
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.
Click to expand...
Click to collapse
gee2012 said:
Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.
Click to expand...
Click to collapse
I think he has already used fast boot to flash the system.img

rootSU said:
I think he has already used fast boot to flash the system.img
Click to expand...
Click to collapse
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem

I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052

gee2012 said:
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem
Click to expand...
Click to collapse
Nope. He used the correct commands. There is no correct folder.

Evolution_Tech said:
I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052
Click to expand...
Click to collapse
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks

faraz90 said:
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks
Click to expand...
Click to collapse
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.

Evolution_Tech said:
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.
Click to expand...
Click to collapse
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!

faraz90 said:
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!
Click to expand...
Click to collapse
*ahem*

rootSU said:
*ahem*
Click to expand...
Click to collapse
haha ofcourse thanks alot to you for suggesting that idea

faraz90 said:
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
!
Click to expand...
Click to collapse
Possibly because your Android SDK tools are out of date(specifically fastboot).

Nexus 6, Deleted System Partition- Cannot Recover

The system partition was deleted and the phone has TWRP. The mac recognizes the ADB device and the MTP. Tried toggling the MTP, no success. Currently android file transfer fails every time due to a missing MD5 file in the android 6.0.1 zip, although all that is being attempted is a drag and drop. ADB sideload says it has completed but no files appear on the phone to flash, or in the file explorer, and so does ADB push. Tried re-downloading the rom, rebooting the phone and everything else.
Any help is appreciated.

evan7899 said:
The system partition was deleted and the phone has TWRP. The mac recognizes the ADB device and the MTP. Tried toggling the MTP, no success. Currently android file transfer fails every time due to a missing MD5 file in the android 6.0.1 zip, although all that is being attempted is a drag and drop. ADB sideload says it has completed but no files appear on the phone to flash, or in the file explorer, and so does ADB push. Tried re-downloading the rom, rebooting the phone and everything else.
Any help is appreciated.
Click to expand...
Click to collapse
flash the factory image, reflash twrp, reflash your ROM and SuperSU.

simms22 said:
flash the factory image, reflash twrp, reflash your ROM and SuperSU.
Click to expand...
Click to collapse
That is what is being attempted. All data has been wiped from the phone and there is an issue getting the ROM and a new TWRP to the phone. The only available computer is a mac and Android File transfer keeps reporting a MD5 file error whenever the rom is tried to be moved over.

evan7899 said:
That is what is being attempted. All data has been wiped from the phone and there is an issue getting the ROM and a new TWRP to the phone. The only available computer is a mac and Android File transfer keeps reporting a MD5 file error whenever the rom is tried to be moved over.
Click to expand...
Click to collapse
thats not how you flash a factory image. you boot into the bootloader, and use fastboot to flash it, via your computer. you dont download it to your phone http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

simms22 said:
thats not how you flash a factory image. you boot into the bootloader, and use fastboot to flash it, via your computer. you dont download it to your phone http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
The factory image is the .TGZ file? Or one in there. I am accustomed to just flashing zip files from TWRP on a OnePlus One but this is a friends Nexus 6 and in a very odd state.

evan7899 said:
The factory image is the .TGZ file? Or one in there. I am accustomed to just flashing zip files from TWRP on a OnePlus One but this is a friends Nexus 6 and in a very odd state.
Click to expand...
Click to collapse
yup, its a .tgz file. download it, "unzip" it, then flash each partition separately instead of all together using fastboot. its the only way to get everything back. then you can flash twrp after, and SuperSU.

simms22 said:
yup, its a .tgz file. download it, "unzip" it, then flash each partition separately instead of all together using fastboot. its the only way to get everything back. then you can flash twrp after, and SuperSU.
Click to expand...
Click to collapse
Sorry this is very simple but everything is going wrong...flashing the system.img exceeded partition limits. Do I rename files or just type them as is. Sorry many guides are contradicting and I'm very confused.
EDIT: The phone isnt being recognized by the computer in fastboot mode.

evan7899 said:
Sorry this is very simple but everything is going wrong...flashing the system.img exceeded partition limits. Do I rename files or just type them as is. Sorry many guides are contradicting and I'm very confused.
EDIT: The phone isnt being recognized by the computer in fastboot mode.
Click to expand...
Click to collapse
just type in the names, like system.img or boot.img.
and did you install the driver for adb.fastboot?

simms22 said:
just type in the names, like system.img or boot.img.
and did you install the driver for adb.fastboot?
Click to expand...
Click to collapse
This is on a mac and ADB was recognizing the device beforehand but fastboot is not. I am not sure if he has the fastboot drivers installed. I will check that

evan7899 said:
This is on a mac and ADB was recognizing the device beforehand but fastboot is not. I am not sure if he has the fastboot drivers installed. I will check that
Click to expand...
Click to collapse
honestly, I wouldn't know what you need on a Mac to get it working :angel:

simms22 said:
honestly, I wouldn't know what you need on a Mac to get it working :angel:
Click to expand...
Click to collapse
Yup thats my same issue. On my PC it could have been done easily but I'll keep trying. Thanks for all of the help!

evan7899 said:
Yup thats my same issue. On my PC it could have been done easily but I'll keep trying. Thanks for all of the help!
Click to expand...
Click to collapse
maybe this will help? http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/

You need to run sudo fastboot insertcomand on Mac. good luck.

simms22 said:
maybe this will help? http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Click to expand...
Click to collapse
Thanks but we have tired that. Due to distance this has all had to be over the phone which hasnt helped either. I will update this with how we got it working when we do.