Database Develop

Cannot load 'Access' bootloader

I am new to rooting and unlocking my new HTC One. I have had great pleasure in doing the same to my galaxy nexus in the past but this one has got me beat.
I have unlocked the bootloader via the HTC site. I have the latest drivers installed and showing OK in the device manager.
I am trying to load a TWRP on my phone without any succes. I can see it listed in the HTC tool kit I have. Its listed as 'SH****** fastboot device. I click install recovery but nothing happens.
I have tried it through the CMD prompt also but get the error 'cannot load'
Can someone please help as I'm desperate to root and install a custom Rom on my phone.
Thanks in advance.

potsykate said:
I am new to rooting and unlocking my new HTC One. I have had great pleasure in doing the same to my galaxy nexus in the past but this one has got me beat.
I have unlocked the bootloader via the HTC site. I have the latest drivers installed and showing OK in the device manager.
I am trying to load a TWRP on my phone without any succes. I can see it listed in the HTC tool kit I have. Its listed as 'SH****** fastboot device. I click install recovery but nothing happens.
I have tried it through the CMD prompt also but get the error 'cannot load'
Can someone please help as I'm desperate to root and install a custom Rom on my phone.
Thanks in advance.
Click to expand...
Click to collapse
download the correct twrp for your device then put it on your fastboot folder and flash via cmd prompt (fastboot flash recovery [twrp file name].img)

[email protected] said:
download the correct twrp for your device then put it on your fastboot folder and flash via cmd prompt (fastboot flash recovery [twrp file name].img)
Click to expand...
Click to collapse
I tried that.
I get the error message 'cannot load image'
I'm at a loss at the moment

potsykate said:
I tried that.
I get the error message 'cannot load image'
I'm at a loss at the moment
Click to expand...
Click to collapse
what happens when you do fastboot devices

I get
SH******** fastboot
then c:|Android

potsykate said:
I get
SH******** fastboot
then c:|Android
Click to expand...
Click to collapse
Are you sure you have the right recovery .img file? What's the file size of the recovery? Should be around 8MB.

It should be its 8.43MB in size.
I got it from here.
http://forum.xda-developers.com/showpost.php?p=38933080&postcount=1

potsykate said:
I get
SH******** fastboot
then c:|Android
Click to expand...
Click to collapse
try to do fastboot erase cache first then flash the recovery again.

This is the message I get

potsykate said:
This is the message I get
Click to expand...
Click to collapse
you're forgetting ".img" in the file name, "DIR" on your computer and then use the full file name of the recovery, that's all
EDIT: I think it's called "openrecovery-twrp-2.6.3.0-m7.img" (unless you saved it under a different name)
so fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
EDIT 2: just saw you folder
fastboot flash recovery twrp-2.6.3.0.img

Thanks for that,I've finally been able to install a recovery and also install my first ROM as well.
Thanks a lot

potsykate said:
Thanks for that,I've finally been able to install a recovery and also install my first ROM as well.
Thanks a lot
Click to expand...
Click to collapse
Congratz mate.
Hit the thanks button if I helped

Still no OTA but you want KitKat AND keep your data?

Hello friends!
I want to share some information for the beginners here:
While there is the Nexus 4 factory image for KitKat available, there still are non known OTA urls.
But you can flash KitKat anyway AND keep your data (as long as you have an unlocked bootloader):
1. Download the factory image from here:
https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
2. extract ALL the files contained into the same directory where your fastboot.exe is saved, for unpacking I recommend using 7zip
3. boot your phone into bootloader
4. type in the following commands:
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
You're done, KitKat on your Nexus 4, your apps and data still available!
Note: Your phone has to be full stock!!!!
UPDATE:
I'm really sorry for the mistakes I made in this thread.
I corrected them all by now, I think.
To make it more easy for you: You can rename the radio and the bootloader files let's say to radio.img and bootloader.img. Then use the fastboot commands with these new names. So you're a bit more safe not to make spelling errors.
Once again: I am sorry and I hope nobody got stuck due to my mistakes!!!

Some errors here.
random hero said:
fastboot flash bootloader bootloader-mako-makoz10o.img
Click to expand...
Click to collapse
Should be
fastboot flash bootloader bootloader-mako-makoz20i.img
random hero said:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
Click to expand...
Click to collapse
Should be
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84
random hero said:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Skip this if you dont want your custom recovery to be stock again. :good:

random hero said:
Hello friends!
I want to share some information for the beginners here:
While there is the Nexus 4 factory image for KitKat available, there still are non known OTA urls.
But you can flash KitKat anyway AND keep your data (as long as you have an unlocked bootloader):
1. Download the factory image from here:
https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
2. extract ALL the files contained into the same directory where your fastboot.exe is saved, for unpacking I recommend using 7zip
3. boot your phone into bootloader
4. type in the following commands:
fastboot flash bootloader bootloader-mako-makoz10o.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
You're done, KitKat on your Nexus 4, your apps and data still available!
Note: Your phone has to be full stock!!!!
Click to expand...
Click to collapse
If you're making a guide, make sure you give people the correct commands (the numbers of the bootloader and radio are wrong). Not to mention there already is a guide where flashing the update without losing data is explained.
http://forum.xda-developers.com/showthread.php?t=2527142

vanmarek said:
If you're making a guide, make sure you give people the correct commands (the numbers of the bootloader and radio are wrong). Not to mention there already is a guide where flashing the update without losing data is explained.
http://forum.xda-developers.com/showthread.php?t=2527142
Click to expand...
Click to collapse
The numbers of radio & bootloader in Factory image itself are wrong

I am sorry for the two "spelling errors". I corrected them, should be all fine now.
I did not notice that the other guide contains information about flashing KitKat without losing all your data...
sometimes it can be hard to keep an eye on all the threads in every detail...

fastboot flash bootloader bootloader-mako-makoz10i.img still wrong should be 20 instead of 10

Don't really want go threw all that ..
dose somebuy just have image I can flash without having to use the above
I want down load the Image
Boot into Recovery and Flash the Image with Team win Project
Then Reboot

Onknight said:
Don't really want go threw all that ..
dose somebuy just have image I can flash without having to use the above
I want down load the Image
Boot into Recovery and Flash the Image with Team win Project
Then Reboot
Click to expand...
Click to collapse
there are some stock images with root on android develop or orig android develop.
edit: can use dd command to flash images if u have root.
do dd if=/block of/img
like dd if=/dev/block/platform/by-name/system /data/media/0/download/images/zipextracted/system.img

opssemnik said:
fastboot flash bootloader bootloader-mako-makoz10i.img still wrong should be 20 instead of 10
Click to expand...
Click to collapse
Again sorry for that... updated. Thank you!

"I'm really sorry for the mistakes I made in this thread.
I corrected them all by now, I think.
To make it more easy for you: You can rename the radio and the bootloader files let's say to radio.img and bootloader.img. Then use the fastboot commands with these new names. So you're a bit more safe not to make spelling errors."
I thought it was excellent! Anyone who knows what they are doing in the Command Prompt/Terminal understands that they can hit the Tab key to auto-complete the filename. Its up to them to make sure they are accessing their correct folder/file name, not yours!

good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason

maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
7zip is free, winrar is not.

maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
In my opinion 7Zip looks slightly better and it doesn't spam you with that your trial is over every time you open it.

what to do with a custom rom?
I have PA on my N4 and was wondering what to do to get KitKat? is the procedure similar or different?
Thanks a lot!

maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
7zip is far more friendly towards archives other than rar and zip formats. it's also the only archive app I've found that will allow you to open a flashable zip or apk and replace files inside (like an icon's image file, for example) without having to actually decompile/recompile either the zip or apk (assuming you don't change too much with either file-type)
mad_zack said:
I have PA on my N4 and was wondering what to do to get KitKat? is the procedure similar or different?
Thanks a lot!
Click to expand...
Click to collapse
whether it's a custom or stock rom does not matter. the procedure will be the same either way

Upgrading 4.2>4.3>4.4 was always a piece of cake with Wug toolkit and never had to reinstall any application.
Keeping my settings and applications was important for me.
Sent from my NookColor using Tapatalk 4

how is this method different from if i just removed the -w wipe parameter?

maverickronny said:
how is this method different from if i just removed the -w wipe parameter?
Click to expand...
Click to collapse
the method you refer to will still install the userdata.img file, which will wipe your rom's userdata, as well as anything on your storage partition. The method mentioned in this thread's OP omits the userdata.img file and relies on the user manually wiping the rom data in n custom recovery, therefore wiping only rom data while leaving the storage partition untouched.

Confused as to why people take all these steps when its just unlock>flash recovery>Flash update rom of your choice and done. All these threads on the same thing makes no sense and lets be honest its not that hard to keep up with threads if you search extensively prior to making up a thread which at week three of KitKat you should of thought would be up already.
Not flaming anyone just trying to understand the thought process. Mistakes happen I get it but we got to do better especially with so many people destroying their phones over simple things.... Jus Sayin'

hp420 said:
the method you refer to will still install the userdata.img file, which will wipe your rom's userdata, as well as anything on your storage partition. The method mentioned in this thread's OP omits the userdata.img file and relies on the user manually wiping the rom data in n custom recovery, therefore wiping only rom data while leaving the storage partition untouched.
Click to expand...
Click to collapse
I updated from 4.3 to KRT16O (and later, KRT16S) by omitting the "-w" from the batch file, and I didn't lose a byte of userdata. My bootloader is unlocked, but everything else is stock.
It was so painless, I wonder why I ever bothered waiting for OTAs in the first place.

[Q] HTC One Brick?

Hi guys. Was just trying to install a 4.4 custom rom on my HTC One using CWM. I got into rrecovery mode and started trying to install the rom but it came up with an error saying it had aborted. I realised I hadn't made a backup so I thought I best do it in case anything goes wrong. I tried doing that and rebooting the phone. Now the HTC logo flashes on screen before flashing off and then the phone puts me back in recovery. Have I bricked this phone? If anyone can help me I can answer any more necessary questions.

krisdeaco said:
Hi guys. Was just trying to install a 4.4 custom rom on my HTC One using CWM. I got into rrecovery mode and started trying to install the rom but it came up with an error saying it had aborted. I realised I hadn't made a backup so I thought I best do it in case anything goes wrong. I tried doing that and rebooting the phone. Now the HTC logo flashes on screen before flashing off and then the phone puts me back in recovery. Have I bricked this phone? If anyone can help me I can answer any more necessary questions.
Click to expand...
Click to collapse
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and install the ROM again.

nkk71 said:
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and install the ROM again.
Click to expand...
Click to collapse
Sorrry if I seem like a complete fool but how to I flash the recovery image. I'm in the fastboot usb menu now but there doesn't appear to be any option to flash.

krisdeaco said:
Sorrry if I seem like a complete fool but how to I flash the recovery image. I'm in the fastboot usb menu now but there doesn't appear to be any option to flash.
Click to expand...
Click to collapse
from you PC
open a command prompt, go to the folder where adb is (also put the downloaded recovery there), then on your PC, type commands in bold above.

nkk71 said:
from you PC
open a command prompt, go to the folder where adb is (also put the downloaded recovery there), then on your PC, type commands in bold above.
Click to expand...
Click to collapse
Again, rreally sorry. Where will I find ADB? Where would it typically be?
EDIT: I've downloaded minimal ADB and Fastboot and out the recovery image in there. I've tried typing in the top command but had no luck. A little more help, please? Thank you for your help so far by the way

krisdeaco said:
Again, rreally sorry. Where will I find ADB? Where would it typically be?
Click to expand...
Click to collapse
wherever you put it, didnt you unlock your phone using "fastboot flash unlocktoken Unlock_code.bin"? that would be the folder (often referred to the adb sdk)

nkk71 said:
wherever you put it, didnt you unlock your phone using "fastboot flash unlocktoken Unlock_code.bin"? that would be the folder (often referred to the adb sdk)
Click to expand...
Click to collapse
Ah yes thanks. I've found it all and put it where you said. I've tried to flashing it but I'm getting the message:
"unknown partition 'fastboot flash openrecovery-twrp-2.6.3.3-m7.img'
error:cannot deterrmine image filename for 'fastboot flash openrecovery-twrp-2.6.3.3-m7.img'

krisdeaco said:
Ah yes thanks. I've found it all and put it where you said. I've tried to flashing it but I'm getting the message:
"unknown partition 'fastboot flash openrecovery-twrp-2.6.3.3-m7.img'
error:cannot deterrmine image filename for 'fastboot flash openrecovery-twrp-2.6.3.3-m7.img'
Click to expand...
Click to collapse
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
please be careful with things like these, you don't want to mess up your phone, reading and staying calm, not rushing things, IS A MUST!!

nkk71 said:
wherever you put it, didnt you unlock your phone using "fastboot flash unlocktoken Unlock_code.bin"? that would be the folder (often referred to the adb sdk)
Click to expand...
Click to collapse
nkk71 said:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
please be careful with things like these, you don't want to mess up your phone, reading and staying calm, not rushing things, IS A MUST!!
Click to expand...
Click to collapse
Sorry I'm just panicking an awful lot. I'm a bit calmer now though so I'll crack on. I've got TWRP back up and I've tried to install the ROM but it keeps saying failed. Is therre any way to make my phone available to transfer to so I can try a different ROM?
EDIT: It seems I did make a backup with TWRP, I'm assuming that wouldn't show up on CWM? That seems to be working so I'll count myself lucky. I would very much like to get stock android 4.4 though so do you know of any detailed guides for getting that with TWRP on HTC one?
By the way THANK YOU SO MUCH for everything. I completely panicked and I would never have figured any of this out without your help. Thank you.

krisdeaco said:
Sorry I'm just panicking an awful lot. I'm a bit calmer now though so I'll crack on. I've got TWRP back up and I've tried to install the ROM but it keeps saying failed. Is therre any way to make my phone available to transfer to so I can try a different ROM?
Click to expand...
Click to collapse
yes plenty, now please go get a glass of water and I'll post back in a minute, you need to relax, we'll have your phone up and running soon.
Which ROM would you like to have? post, then get that water/coffee/beer/scotch whatever makes you calm down :laugh:

krisdeaco said:
EDIT: It seems I did make a backup with TWRP, I'm assuming that wouldn't show up on CWM? That seems to be working so I'll count myself lucky. I would very much like to get stock android 4.4 though so do you know of any detailed guides for getting that with TWRP on HTC one?
Click to expand...
Click to collapse
Unfortunately, TWRP and CWM backups aren't interchangeable but you can always flash back the proper recovery for the backup, and restore.
krisdeaco said:
I would very much like to get stock android 4.4 though so do you know of any detailed guides for getting that with TWRP on HTC one?
Click to expand...
Click to collapse
Details please , GPE or Sense, any one in particular, best post a link to the one you'd like to have.
krisdeaco said:
By the way THANK YOU SO MUCH for everything. I completely panicked and I would never have figured any of this out without your help. Thank you.
Click to expand...
Click to collapse
Feel free to hit the thanks button

[Q] Can't unlock bootloader as there is no OS installed

Hi everyone,
I was in the process of installing the stock Android factory 5.1 image from Chroma -- During this process I wiped everything (System data, user data, cache, etc) in TWRP and then went to fastboot to start the factory image flashing process. However, I accidently relocked my bootloader by executing my commands in the wrong order. I am now in the position where I can't unlock my phone's bootloader, as I need to enable "Allow OEM Unlock" in the developer settings, however, I can't do that as my phone currently has no OS installed.
I am at a gridlock currently, not sure how to proceed. Any ideas as to how I can fix this?
Any help would be much appreciated, as at this point, I am totally locked out of my device

Format cache and userdata via fastboot.
Edit: TWRP for the win
Never relock your bootloader. See @rootSU a tool might have saved him
Sent from my Benzo'd Google N6 on VZ

DebianDog said:
See @rootSU a tool might have saved him
Click to expand...
Click to collapse
@DebianDog, I never need saving

DebianDog said:
Format cache and userdata via fastboot. If that doesn't work, nothing you can do.
Edit: no OS? Yeah....
Sorry bro RMA
Never relock your bootloader. See @rootSU a tool might have saved him
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
Formatting the cache and userdata with "fastboot -w" fixed my TWRP bootloop issue. At this point I was not able to write data to /data/media to try and restore one of my backups. So I ran a backup in TWRP, which worked, and also formatted the data partition, as I can now write to /data/media from my computer while in TWRP.
From here, I was able to copy a TWRP backup I had on my computer, and restore it. I was then able to boot into Android once again, Allow OEM unlock, and then successfully unlocked my bootloader.
Wow, what a headache. But all is working now -- I was unaware of the new low level security features with Android 5.1
If anyone wants me to clarify my fix for this, feel free to ask.
Thanks everyone for the help! <3

Ooohhh Nice! Nothing like having a backup Good job!
Sent from my Benzo'd Google N6 on VZ

curious as to how one relocks the bootloader by "accident" Isn't the only way by issuing the "Fastboot OEM LOCK" command?

BladeRunner said:
curious as to how one relocks the bootloader by "accident" Isn't the only way by issuing the "Fastboot OEM LOCK" command?
Click to expand...
Click to collapse
Cutting and pasting while not paying attention is what I figured.
Not something I've done on my phone but at work once or twice....
Sent from my Benzo'd Google N6 on VZ

Glad it's all sorted.
Just noticed the avatar, very appropriate

rootSU said:
Glad it's all sorted.
Just noticed the avatar, very appropriate
Click to expand...
Click to collapse
I was thinking the same thing actually haha

No TWRP backup...
p011uX said:
Formatting the cache and userdata with "fastboot -w" fixed my TWRP bootloop issue. At this point I was not able to write data to /data/media to try and restore one of my backups. So I ran a backup in TWRP, which worked, and also formatted the data partition, as I can now write to /data/media from my computer while in TWRP.
From here, I was able to copy a TWRP backup I had on my computer, and restore it. I was then able to boot into Android once again, Allow OEM unlock, and then successfully unlocked my bootloader.
Wow, what a headache. But all is working now -- I was unaware of the new low level security features with Android 5.1
If anyone wants me to clarify my fix for this, feel free to ask.
Thanks everyone for the help! <3
Click to expand...
Click to collapse
First time poster, please be gentle
I'm in the same position, however I do not have a TWRP back-up on my computer to overwrite the one I just created. Is there anyway to get a standard system copy of a backup just to allow installation of OS and subsequent re-unlocking of the bootloader and at that point re-wipe and start from scratch?

NDAMT said:
First time poster, please be gentle
I'm in the same position, however I do not have a TWRP back-up on my computer to overwrite the one I just created. Is there anyway to get a standard system copy of a backup just to allow installation of OS and subsequent re-unlocking of the bootloader and at that point re-wipe and start from scratch?
Click to expand...
Click to collapse
Do you have TWRP recovery installed?

rootSU said:
Do you have TWRP recovery installed?
Click to expand...
Click to collapse
Yes. Luckily. :good:

NDAMT said:
Yes. Luckily. :good:
Click to expand...
Click to collapse
Just download a stock rom.zip and put it on your sdcard.

rootSU said:
Just download a stock rom.zip and put it on your sdcard.
Click to expand...
Click to collapse
I tried that, but I keep getting a failed message: " Error flashing zip '/sdcard/image-shamu-lmy47e.zip' "

NDAMT said:
I tried that, but I keep getting a failed message: " Error flashing zip '/sdcard/image-shamu-lmy47e.zip' "
Click to expand...
Click to collapse
Where did you get that? Got a link?

NDAMT said:
I tried that, but I keep getting a failed message: " Error flashing zip '/sdcard/image-shamu-lmy47e.zip' "
Click to expand...
Click to collapse
I don't think that's a flashable zip. View the contents of the zip.
Sent from my Nexus 6 using Tapatalk

rootSU said:
Where did you get that? Got a link?
Click to expand...
Click to collapse
I used the download from the official Google Nexus Factory Images page. The forum wont let me post an external link yet.
From there I decompressed the .tar, and copied the resulting files onto the Nexus 6 internal SD.
zephiK said:
I don't think that's a flashable zip. View the contents of the zip.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
What should I be looking for in particular?
"bootloader-shamu-moto-apq8084-7108"
"flash-all"
"flash-all.sh"
"flash-base.sh"
"image-shamu-lmy47e"
--> contains: android.info, boot, cache, recovery, system, userdata
"radio-shamu-d4.0-9625.02.98"

NDAMT said:
I used the download from the official Google Nexus Factory Images page. The forum wont let me post an external link yet.
From there I decompressed the .tar, and copied the resulting files onto the Nexus 6 internal SD.
What should I be looking for in particular?
"bootloader-shamu-moto-apq8084-7108"
"flash-all"
"flash-all.sh"
"flash-base.sh"
"image-shamu-lmy47e"
--> contains: android.info, boot, cache, recovery, system, userdata
"radio-shamu-d4.0-9625.02.98"
Click to expand...
Click to collapse
No you need a flashable rom.zip from XDA.

NDAMT said:
I used the download from the official Google Nexus Factory Images page. The forum wont let me post an external link yet.
From there I decompressed the .tar, and copied the resulting files onto the Nexus 6 internal SD.
What should I be looking for in particular?
"bootloader-shamu-moto-apq8084-7108"
"flash-all"
"flash-all.sh"
"flash-base.sh"
"image-shamu-lmy47e"
--> contains: android.info, boot, cache, recovery, system, userdata
"radio-shamu-d4.0-9625.02.98"
Click to expand...
Click to collapse
That's not a flashable zip. Those are fastboot images meant to be flashed in bootloader mode, not in recovery mode.
Sent from my Nexus 6 using Tapatalk

rootSU said:
No you need a flashable rom.zip from XDA.
Click to expand...
Click to collapse
zephiK said:
That's not a flashable zip. Those are fastboot images meant to be flashed in bootloader mode, not in recovery mode.
Click to expand...
Click to collapse
OK, at this point treat me like a noob. What rom.zip would you recommend for someone who is trying to get their phone back to factory?

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.