Database Develop

Help!!!! My htc wont connect to fastboot

Hey guys my htc is stuck on a boot loop so i try to connect fast boot to flash a new boot.img but my fastboot just says usb device not recognized please guys i really need help
My symptoms
Stuck on htc boot logo
Cannot access Recovery
Fastboot wont connect

Locky123 said:
Hey guys my htc is stuck on a boot loop so i try to connect fast boot to flash a new boot.img but my fastboot just says usb device not recognized please guys i really need help
My symptoms
Stuck on htc boot logo
Cannot access Recovery
Fastboot wont connect
Click to expand...
Click to collapse
Put the stock ROM on your sdcard and rename it from ROM.zip to ph39IMG.zip and go to bootloader.

mohamed_moscow said:
Put the stock ROM on your sdcard and rename it from ROM.zip to ph39IMG.zip and go to bootloader.
Click to expand...
Click to collapse
No luck it just goes through and says no image found

U got the HTC USB drivers?
Sent from my Vivid 4G using Tapatalk 2

ZeRo2o9 said:
U got the HTC USB drivers?
Sent from my Vivid 4G using Tapatalk 2
Click to expand...
Click to collapse
ok yes i can acess it but no matter what rom i install it is just stuck on the htc logo but i can access recovery

Locky123 said:
ok yes i can acess it but no matter what rom i install it is just stuck on the htc logo but i can access recovery
Click to expand...
Click to collapse
Did you ever find a solution to this? I am in the same boat now. I managed to flash carbon rom and used fastboot to flash boot.img but now I can't go back, fastboot seems broken. USB works fine within the ROM, just not from fastboot. USB Device Not Recognized. Not a driver issue, it's before it even tries to load the drivers.

rewen said:
Did you ever find a solution to this? I am in the same boat now. I managed to flash carbon rom and used fastboot to flash boot.img but now I can't go back, fastboot seems broken. USB works fine within the ROM, just not from fastboot. USB Device Not Recognized. Not a driver issue, it's before it even tries to load the drivers.
Click to expand...
Click to collapse
Are you using Windows 8? I found it does the same with my Sony phone. It sucks!

rewen said:
Did you ever find a solution to this? I am in the same boat now. I managed to flash carbon rom and used fastboot to flash boot.img but now I can't go back, fastboot seems broken. USB works fine within the ROM, just not from fastboot. USB Device Not Recognized. Not a driver issue, it's before it even tries to load the drivers.
Click to expand...
Click to collapse
Yea I fixed it I ended up flashing the kernal then flashing the rom then flashed the kernal once again and it works fine after that but i dont know how i could help any other way

Locky123 said:
No luck it just goes through and says no image found
Click to expand...
Click to collapse
Remember to put all letters in capital and also to relock your bootloader before using the zip file.

My 'USB Device Not Recognized' issue turned out to be Windows 8. I originally flashed my boot.img using Windows 7 at work and forgot that I'd done it from there, so I'd been under the impression that it worked once for me on Windows 8 so it should work again. But in fact, it never worked on Windows 8.
I installed Windows 7 on a second partition at home and it worked without issue. FYI I wasn't using USB 3.0 or anything and I tried a couple of Windows 8 PCs before resorting to installing Windows 7. It's also worth noting that the error in Windows 8 seems to happen before the actual drivers are installed/loaded, so it's not just a matter of picking the proper driver afaik. I did have the proper drivers and HTC Sync Manager, and tried forcing the driver install, but it didn't help. This also means you can't use a virtual machine to work around the issue.
Hope this helps others who run into the 'USB Device Not Recognized' error on Windows 8...
---------- Post added at 11:45 AM ---------- Previous post was at 11:45 AM ----------
Locky123 said:
Yea I fixed it I ended up flashing the kernal then flashing the rom then flashed the kernal once again and it works fine after that but i dont know how i could help any other way
Click to expand...
Click to collapse
Did you wipe data/factory reset after flashing? I didn't see you mention that anywhere. Also, are you sure you're using the right ROMs for the One XL (evita) and not the regular One X? Or the other way around in case you're in the wrong forum?

[Q] ADB doesnt recognize HTC One in Recovery

I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.

Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium

shrex said:
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes fastboot usb is shown and all fastboot commands work, its just that adb doesnt work when its in bootloader or recovery.
I did some more digging around and found that when the phone is connected while in recovery, the computer recognizes it as a "HTC MTP device"..and thats it. I cant upgrade the drivers of the said device or essentially do anything with it.
What am i missing?

ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would start with these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe

TygerByte said:
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would startpage these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
Click to expand...
Click to collapse
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.

Bhavpreet said:
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Click to expand...
Click to collapse
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109

EddyOS said:
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
Click to expand...
Click to collapse
installed the 3 series driver, still the same problem. Heres some photos (which i should have attached originally) of whats happening.
The pictures are while the phone is normally booted, and then when the phone is in recovery.
Edit: Uninstalled all of the HTC drivers and devices inside the device manager, and only installed the Universal Naked Driver, the phone now shows up with a different name in device manager, but STILL does not work while in recovery.
Another pictures attached of how device manager looks with just the Universal Driver while in recovery.

anyone?

i have the same problem as u.. I tried both my missus Windowss PC now.. It used to detect it before. Now it suddenly doesn´t anymore. On my mac, same deal. Nothing detected.
Been googling around and i have found threads but they all end unsolved. ADB returns ADB devices blank. Kill-server or adb remount does nothing. in Fastboot USB its totally a ghost.
found any fixes?

I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.

Me too...
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)

bretula said:
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
Click to expand...
Click to collapse
In case this helps someone else: The reason I lost adb was that I'd installed the drivers on my mac for EasyTether. There's a note about this on the EasyTether FAQ page. When I disabled the EasyTether driver, I was able to use adb again.

TygerByte said:
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Click to expand...
Click to collapse
have you tied all-in-one-tool-kit ???

Not sure if this will help, but I had an issue like this with my asus tab - adb worked fine in android os but not in twrp recovery, device manager showing it as other device.
While in recovery with device connected to pc I followed this how-to from the device manager part on and got adb working in recovery.

ADB not connecting
Bhavpreet said:
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Click to expand...
Click to collapse
Re Install HTC drivers manually, windows sees HTC until you boot into recovery mode and try to use ADB, It worked for me.

HTC One(M7) not recognized by adb
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.

TonyDEV said:
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
Click to expand...
Click to collapse
Take a look at this FAQ post and see if this doesn't help solve your problems. I would also recommend updating your CWM recovery to the latest.

having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb... I can't install the naked drivers it just says that the file is incompatible

blu422 said:
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb...
Click to expand...
Click to collapse
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.

clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
thanks! did what you said i installed the drivers and the installation crashed the first time, then the second time it game me the option to remove or repair and i repaired and it worked thank you!!!
---------- Post added at 02:55 PM ---------- Previous post was at 02:37 PM ----------
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
so i have adb... but now it wont let me flash cyanogenmod... error executing updater binary in zip.... just fails.... help? updated to twrp 2.7.1.1. that fixed the problem

[Q] HELP - Bricked HTC One m7vzw (Verizon)

So I got carried away with trying to get rid of that three dot menu button at the bottom of the screen and I've slowly managed to work myself into a really bad problem. I'm not necessarily new to this, I've rooted my Droid 2, Droid 3, and GS3, but this has been more complicated for me.
Anyways, my problem is, I was trying to wipe my phone so that I could flash a ROM. This is because I couldn't access my settings (I overwrote the original in an attempt to get rid of the multitask button). But while I was in CWM I factory reset it but I also accidentally deleted the system. My bootloader is unlocked, but now my phone is on and I can't get into recovery, and I'm assuming it's because the whole system is gone so there's nothing to boot.
Another problem I had (while my phone was able to boot up completely), Android File Transfer wouldn't work, I downloaded a rom for the settings.apk but it wouldn't let me transfer files between my computer and phone. I emailed the .apk to myself but since I couldn't access settings I wasn't able to pick my usual email (although now I'm thinking I should have just used the email I first signed in with). Not as much of a concern but input is still welcome.
I've looked up RUU but it looks like it's not available yet for Verizon. Any possible solutions would be MUCH appreciated.

Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.

Gudio142 said:
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Click to expand...
Click to collapse
I'm stuck on the green HTC logo screen and the red warning about the bootloader. I can't boot into recovery anymore. By the way I'm using a Mac but I do have a PC running Windows 8 if there's solutions I could try

Gudio142 said:
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Click to expand...
Click to collapse
I tried flashing into recovery via fastboot but my computer doesn't recognize my device. And I'm pretty sure I had drivers installed since that's how I unlocked the bootloader in the first place..

xerhoffx said:
I tried flashing into recovery via fastboot but my computer doesn't recognize my device. And I'm pretty sure I had drivers installed since that's how I unlocked the bootloader in the first place..
Click to expand...
Click to collapse
Install the latest drivers and try from a windows 7 pc (or windows 8, win 8.1 doesn't work well)

Reinstall drivers if you haven't already and try the correct file for your 'Modelid' here. It's the only way I got mine to work again after i did the same thing.
Note: The file i used had a different software version but it still flashed ok.
After that, if you can find the right Nandroid you now have the ability to flash that

n1234d said:
Install the latest drivers and try from a windows 7 pc (or windows 8, win 8.1 doesn't work well)
Click to expand...
Click to collapse
I only have Windows 8 I believe...

xerhoffx said:
I only have Windows 8 I believe...
Click to expand...
Click to collapse
Try a different PC, worked for another guy whose pc wouldn't detect his phone. See if a pc with XP works..

ndulian increase
jingles98 said:
Reinstall drivers if you haven't already and try the correct file for your 'Modelid' here. It's the only way I got mine to work again after i did the same thing.
Note: The file i used had a different software version but it still flashed ok.
After that, if you can find the right Nandroid you now have the ability to flash that
Click to expand...
Click to collapse
Where could I find a nandroid for Verizon? I feel like Verizon is the most difficult to find.

FIXED
I was finally able to boot into recovery and thank goodness had a CWM backup. Thanks for your input guys.

HELP!!! I bricked my N3!!!

Ok. So rooted my Note 3 in Oct and ROMd in Jan with XNote 7. I had it all fine and everything since. Well, I upgraded to XNote 12 and realized I couldn't receive calls and a few other weird annoying bugs. So I attempted to downgrade back to MJ5 using the Restore tutorial in the General section.
Alright, well I did the whole tutorial I Heimdalled the MI9_Fix.img.ext4 file and then started flashing the ZIPs. I did the SEC_CSC then I tried the 2400845 and it failed with a message about system/vender/lib.camerafilter.whatever.so couldn't be found and quit. I figured it was normal so and now I'm stuck at the Samsung logo with a padlock. It will go into recovery and Odin mode fine.
It also deleted my Safestrap. So I cannot get into SS recovery. I have tried the tutorial again and now Heimdall quits with error 87 and something about a I/O error.
I have also tried to Odin the MJ5 stock flash files (AP, BL, CP and PIT) but it does nothing. I cannot install a ROM and cannot use my phone.
I desperately need my phone for work, so if someone can help me out ASAP, so I don't lose my job, I would be SO grateful! THANK YOU!!!!

533y4 said:
Ok. So rooted my Note 3 in Oct and ROMd in Jan with XNote 7. I had it all fine and everything since. Well, I upgraded to XNote 12 and realized I couldn't receive calls and a few other weird annoying bugs. So I attempted to downgrade back to MJ5 using the Restore tutorial in the General section.
Alright, well I did the whole tutorial and started flashing the ZIPs. I did the SEC_CSC then I tried the 2400845 and it failed with a message about system/vender/lib.camerafilter.whatever.so couldn't be found and quit. I figured it was normal so I Heimalled the MI9_Fix.img.ext4 file and now I'm stuck at the Samsung logo with a padlock. It will go into recovery and Odin mode fine.
It also deleted my Safestrap. So I cannot get into SS recovery. I have tried the tutorial again and now Heimall quits with error 87 and something about a I/O error.
I have also tried to Odin the MJ5 stock flash files (AP, BL, CP and PIT) but it does nothing. I cannot install a ROM and cannot use my phone.
I desperately need my phone for work, so if someone can help me out ASAP, so I don't lose my job, I would be SO grateful! THANK YOU!!!!
Click to expand...
Click to collapse
do the procedure again and follow it to the letter as i can see you can still get to dl mode, btw you're supposed to flash the sec_csc and 240058 AFTER you flash the system.img with heimdall.

posersk8r said:
do the procedure again and follow it to the letter as i can see you can still get to dl mode, btw you're supposed to flash the sec_csc and 240058 AFTER you flash the system.img with heimdall.
Click to expand...
Click to collapse
I can do the ODIN part, then when I try the Heimdall part, it comes up with an error. I have tried it 5 times over. To a T... : (
And yes, I know you flash those BEFORE. That's what I meant to say, but I was in a rush...

Im in a similar pickle but my problem is that I need a way to get those files to the SD card because the thing is bricked. I can't copy the files to a bricked phone and every device in my house refuses to read the micro SD card.

533y4 said:
I was in a rush...
Click to expand...
Click to collapse
That's the problem right there. Over in my thread about the kitkat update fix people are saying it's not working for them but they are missing steps because they're not reading everything. I've used that method 3 times so far and it worked all 3 times. Start from the beginning. Delete all the files from previous attemtps, go to step 1, read everything, you will get it.

mazdamiata210 said:
That's the problem right there. Over in my thread about the kitkat update fix people are saying it's not working for them but they are missing steps because they're not reading everything. I've used that method 3 times so far and it worked all 3 times. Start from the beginning. Delete all the files from previous attemtps, go to step 1, read everything, you will get it.
Click to expand...
Click to collapse
Again, I have done this 5 times. No joke. I have redownloaded everything 3 times.
1) Download and install Heimdall from here for windows. You'll need this and this to avoid missing .dll file errors
2) Download the following files;
MI9_fix.img.ext4
https://mega.co.nz/#F!icMTnSQY!bMBNFmUnn2_K8olSTYpwIA (mirror provided by drakeymcmb)
sec_csc.zip
rldv.zip
2400258.zip
Put everything except for the system.img on your external SD card
3) Download and install the MJ5 partions. Use Odin to flash these files (match the file names with the different upload slots)
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit
4) Now is the time to use Heimdall.
Reboot into Download Mode once Odin finishes.
Install the vcredist packages downloaded from step 1.
unzip the heimdall .zip file to c:/
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message
5) Navigate on your computer to c:/Heimdall Suite/ and open heimdall-frontend.exe.
IMPORTANT -- Go to the Utilities tab and click the "Detect" button
Go to the Flash tab on Heimdall, click Browse and select the HLTE_USA_ATT_32G.pit file downloaded from step 3
Click the 'add' button, then next to 'partition name' select system from the dropdown.
click the Browse button underneath the dropdown, and select the MI9_fix.img.ext4 image you downloaded from step 2.
6) Click Start. ***I usually check the 'No Reboot' box to prepare for booting into recovery
THIS IS WHERE I CAN NO LONGER GO ANY FURTHER!!! IT SPITS A I/O ERROR 87 AT THIS POINT! I CANNOT GET AROUND THIS! THIS IS WHAT I NEED HELP WITH!
7) Heimdall and your Note will report a bad flash at around 95% -- but don't worry -- your system.img got uploaded Reboot directly into recovery mode.
8) Once in recovery, select "Choose update from external" in the recovery, and select the sec_csc.zip you downloaded earlier (did you remember to put that file on your external SD card?). This will install the CSC files and run the preload checkin so you don't FC all over the place
9) IMPORTANT--After flashing the sec_csc, the Note will reboot.
Try to catch it in time to reboot BACK into recovery
Once in recovery, select "Choose update from external" in the recovery, and select the 2400258.zip you downloaded earlier.
This will give you a stock MJ5 system. You can choose to stop here if you don't want to root.
10) Extract rldv.zip to the root of your internal sdcard (NOTE **my script removes Knox apps). Reboot, then once SuperSu installs, Reboot again.
This leaves you with a rooted MJ5 device.

533y4 said:
Again, I have done this 5 times. No joke. I have redownloaded everything 3 times.
Click to expand...
Click to collapse
Did you do this??
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message​

mazdamiata210 said:
Did you do this??
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message​
Click to expand...
Click to collapse
Yes. And everytime I try this again I have to delete and revert drivers, because ODIN won't see it afterwards. X_X
The drivers named "WinUSB 6.1.7600"

533y4 said:
Yes. And everytime I try this again I have to delete and revert drivers, because ODIN won't see it afterwards. X_X
Click to expand...
Click to collapse
Switch usb ports, switch usb cables, switch computers if possible.
Are you on an administrator account for windows?

mazdamiata210 said:
Switch usb ports, switch usb cables, switch computers if possible.
Are you on an administrator account for windows?
Click to expand...
Click to collapse
I will try this. I am on a ASUS G75 with Win 7 Ultimate X64 via USB 2.0 not USB 3.0. The account I am using is the Administrator. I'm also going to try and run Heimdall as Admin. I'll report back in about 10 mins.

533y4 said:
I will try this. I am on a ASUS G75 with Win 7 Ultimate X64 via USB 2.0 not USB 3.0. The account I am using is the Administrator. I'm also going to try and run Heimdall as Admin. I'll report back in about 10 mins.
Click to expand...
Click to collapse
If that doesn't work try this...
fire up zadig, connect phone while in download mode, install the driver for msm8960, fire up heimdall frontend, go to utilities tab, hit detect button, and then go to flash screen and check no reboot, then start...
I also did mine with usb 3.0 and it worked fine so I don't think that matters. Using the stock cable also.

I was in the same boat. I had to switch computers and it worked first time. Both of them were windows 8.1 btw.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Did you try changing ports for heimdall? Sounds like its not recognizing your n3, had that problem before too where after odin'ing the mj5 files heimdall wouldnt see my phone. Did a reboot on my laptop and changed ports had 7 different 2.0 cables. Just keep trying did this 5 times already and always had the same result.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

So is there no way to mount the card so that I can copy these files if I am bricked?

mazdamiata210 said:
If that doesn't work try this...
fire up zadig, connect phone while in download mode, install the driver for msm8960, fire up heimdall frontend, go to utilities tab, hit detect button, and then go to flash screen and check no reboot, then start...
I also did mine with usb 3.0 and it worked fine so I don't think that matters. Using the stock cable also.
Click to expand...
Click to collapse
Did this every single time. I also have tried all 4 USB ports. This program (Heimdall) worked the first time no problem. That's the weird part... The second and on time all is a no go.
I have attached pictures. 3.jpg is Heimdall with the error.

Have you tried rebooting your g75? Also make sure you're not running any anti malware antivirus firewall etc.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Dumb question but did you click on replace driver on the second picture you posted? The winusb driver is the one you need for heimdall frontend to detect your phone.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

posersk8r said:
Have you tried rebooting your g75? Also make sure you're not running any anti malware antivirus firewall etc.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Dumb question but did you click on replace driver on the second picture you posted? The winusb driver is the one you need for heimdall frontend to detect your phone.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Yes. I actually powered down the machine completely, removed the charger and battery, let it sit for 5 mins and retried.
Also, yes I did. That was before I did click replace tho. Good eyes. ^__^
{[EDIT]}
Does anyone have any input on the Hard Brick recovery method? The unbrick.img method? I tried it with (what I think was MJ5, but not 100% sure) a 64GB class10 UHS-1 Lexar MicroSD Card. I booted into download mode and nothing. Not sure if I did that wrong, or if the card isn't compatible, or the IMG isn't correct (anyone have any links to the unbrick.img for MJ5?)...

533y4 said:
Yes. I actually powered down the machine completely, removed the charger and battery, let it sit for 5 mins and retried.
Also, yes I did. That was before I did click replace tho. Good eyes. ^__^
{[EDIT]}
Does anyone have any input on the Hard Brick recovery method? The unbrick.img method? I tried it with (what I think was MJ5, but not 100% sure) a 64GB class10 UHS-1 Lexar MicroSD Card. I booted into download mode and nothing. Not sure if I did that wrong, or if the card isn't compatible, or the IMG isn't correct (anyone have any links to the unbrick.img for MJ5?)...
Click to expand...
Click to collapse
Well it's not bricked because you can boot into download and recovery mode. It sounds like it's just a driver issue with heimdall.

mazdamiata210 said:
Well it's not bricked because you can boot into download and recovery mode. It sounds like it's just a driver issue with heimdall.
Click to expand...
Click to collapse
I'm going to try my girls computer tomorrow after work. See if her crappy Toshiba can do any better.

My Phone is DEAD
I was talking on my phone yesterday and it just shut off and hasn't been back on since. It is not responding to anything i try. Power + Vol down + Home. When i plug it up, there is no sounds or vibration no response. The phone is in a permanent off state. Any thought or suggestion on how to repair. I did the OTA update last week SM-N900A.

Weird fastboot issue.

Alright guys, I'll get right to the point with this one. So I was flashing a stock image to get back to Marshmallow from N preview 3, and for whatever reason, I couldn't get my system partition to flash! It would begin, and then just finish early. When I tried again, it kept telling me that the file was in use in another program. I made a new copy of my platform tools and the stock image I needed, and it did the same thing! My first thought was a corrupted system partition, and I was really hoping it wasn't that. I got it to work using my sister's really really slow Windows Vista laptop (not kidding, took an HOUR to flash) and that worked. Since then I reinstalled windows on my main laptop, but was wondering just what could have caused that? It kept partially flashing the image, and then saying it was in use right after when I tried to do it again. Sorry this isn't too much to go on, I don't have screens or logs or anything to help the case, but suggestions? Thanks all!

H4X0R46 said:
.... I got it to work using my sister's really really slow Windows Vista laptop (not kidding, took an HOUR to flash) and that worked.
Click to expand...
Click to collapse
Hardware issue or wrong drivers. Your PC - USB port - USB cable - drivers or drivers not correct/installed wrong drivers.
Before fastboot check PC in device manager if your phone is recognized.
Download toolkit of wugfresh. After installing there is a sub folder with drivers and also as a sub folder with fastboot and adb.
Install the drivers and use the fastboot/adb and check/try again.

NLBeev said:
Hardware issue or wrong drivers. Your PC - USB port - USB cable - drivers or drivers not correct/installed wrong drivers.
Before fastboot check PC in device manager if your phone is recognized.
Download toolkit of wugfresh. After installing there is a sub folder with drivers and also as a sub folder with fastboot and adb.
Install the drivers and use the fastboot/adb and check/try again.
Click to expand...
Click to collapse
Sure hope it wasn't hardware. That would be bad. My sister's did it without problem despite the amount of time it took lol. I always use my laptop to flash images, it just chose today to do that. It's really weird at that, never seen that happen before. Fastboot devices command showed that it was connect and seen, so that's even more strange.

Also, does anyone know a sure fire way to check if my system partition is actually getting corrupted? Or is that much more extensive?

H4X0R46 said:
Also, does anyone know a sure fire way to check if my system partition is actually getting corrupted? Or is that much more extensive?
Click to expand...
Click to collapse
In case the system partition is corrupted the phone will not boot. And the partition will not mount in TWRP recovery.

NLBeev said:
In case the system partition is corrupted the phone will not boot. And the partition will not mount in TWRP recovery.
Click to expand...
Click to collapse
Well, my device boots and I as able to flash xposed with out and issues so that's not the case. Might have just been my computer acting up. Thanks for your input! It helps a lot!