Related
I've had this phone since its launch, but I'm now encountering this strange problem.
While I can get into Download Mode without difficulty, I have an issue with connecting it to my PC. While it'll pick it up fine while the phone is in recovery or normal modes, DL mode causes it to give me this error, thus blocking Odin and my chances of returning it to stock.
I desperately need to flash my way out of this battery-draining and unstable OC/UV kernel, but Odin won't recognize it because Windows won't recognize it.
I am using Win7 x64 and WinXP x86, both with appropriate drivers and both not working and having the same issue.
CWM is similarly failing to work, producing a "failed to chown" something or other. Is my phone basically gone at this point?
My suggestion is to reinstall the drivers for the device and if cwm is not working right then use rom manager to install another version of it and if that doesn't work im pretty sure in the development section u can dl the update file with cwm on it
Sent from my SAMSUNG-SGH-I897 using XDA App
I've done the former, I'll try the latter after work today.
Sent from my SAMSUNG-SGH-I897 using XDA App
command symlink
calling command set_perm_recursive
E:Can't chown/mod /data/
(I/O error)
E:Failure at line 69:
set_perm_recursive 0 0 0777 0777 DATA:
Installation aborted.
Failure at line 6:
install_zip SDCARD:/Perception-Build-8-non-oc-uv.zip
Here's my error message from CWM. This is after reinstalling both ROM Manager and CWM. This is preceded by a million "command symlink" commands, leading me to believe that something is failing to work here.
Aus_Azn said:
command symlink
calling command set_perm_recursive
E:Can't chown/mod /data/
(I/O error)
E:Failure at line 69:
set_perm_recursive 0 0 0777 0777 DATA:
Installation aborted.
Failure at line 6:
install_zip SDCARD:/Perception-Build-8-non-oc-uv.zip
Here's my error message from CWM. This is after reinstalling both ROM Manager and CWM. This is preceded by a million "command symlink" commands, leading me to believe that something is failing to work here.
Click to expand...
Click to collapse
If ur trying to flash a new rom I've had this problem before the reason it isn't working is u need to flash back to stock first before u can install a new rom but it will work if u want to flash the same rom over the one u have something to do with the kernel I believe not quite sure but the way I've fixed that is to flash back to stock before flashing a new rom
Edit:::: or u need to disable lagfix by putting a file in ur root folder named disable-lagfix
Sent from my SAMSUNG-SGH-I897 using XDA App
okay thanks unhelpful guy
if you read his original post, he can't get his pc to recognize the phone in download mode. big problem.
same problem i've got.
Have your tried different usb ports. If you are using a pc try the port in the rear of your tower.
Are you using oem usb cord?
Have you tried running odin as administrator
Where did you get the drivers from
Sent from my SAMSUNG-SGH-I897 using XDA App
I've had this happen and I was pissed. No matter what I did, my computer would not see this phone and the phone was bricked with cognition. So I don't know exactly what I did BUT this comes close. Uninstall keys and go to control panel and unistall any samsung drivers. Restart computer. Install only the samsung drivers found on the samsung support page at the official samsung website. And then try putting it in download mode again. I seriously spent 7 hours on getting this to work. If this doesn't work.then you need to find the right drivers. I know there's like 3 different driver packages and kies that have the ring one, but some just completely mess you up. So.find the right one with the right drivers. Good luck! Oh and have patience, that's key.
Sent from my SAMSUNG-SGH-I897 using XDA App
Okay, I'll take your advice. I thought I tried every combination of installing and uninstalling until I nearly ripped my hair out. I tried patching the GPS and it totally boned all GPS functionality, so reverting to stock is apparently my only option... and my phone isn't recognized in download mode. So I guess a few more uninstalls and restarts and we'll see if I blow my brains out today...
Yeah. I just uninstalled Kies, Samsung Drivers, and Samsung New PC Studio. I rebooted twice, and then reinstalled the drivers (from the OP, which are identical to the ones on the Samsung site) and rebooted.
Guess what? No effing luck. Nothing shows up in Odin (remove battery, run odin, plug cable in, plug phone in, return battery and enter download mode) and my taskbar tells me that "A USB Device has malfunctioned and is not recognized."
What the HELL is going on? There are several people with this problem and nobody seems to have an answer that isn't "buhhh you have the wrong drivers."
I had this issue, used a different computer and it worked. I did have to try multiple drivers to get it to work though.
What usb jack are you using
Have you tried running ofin as administrator
Sent from my SAMSUNG-SGH-I897 using XDA App
CHECK OUT THIS POST FROM SteveVHT ON THE ANDROID FORMS:
Had this problem this past week.
You need to uninstall all Samsung software and drivers completely. Do this the normal way through Control Panel.
After that, you need to go into your registry and delete all Samsung folders.
You open up Regedit in Windows
Then go to HKEY CURRENT USER, Expand that (+), expand Software
and delete the Samsung folder
Do the same for HKEY LOCAL MACHINE
When you simply uninstall Samsung stuff, it leaves a bunch of junk in the registry of the computer even after uninstall.
Reboot the computer with no phone attached.
Download the Samsung update from Sprint
http://www6.sprint.com/downloads/samsung/executables/SamsungMoment_Update.exe
Install the updater. After its installed, right click the SWUpgrade and run as administrator....Follow all on screen instructions, and you should be good.
If you do not need the updater, then you can skip the software install and just download the drivers for the phone from the SDX forum. Just do a search.
But I suggest you do it this way, it was the only thing that worked for me...
Running Windows 7 Ultimate 64
Hope this helps
Steve
Click to expand...
Click to collapse
I'm trying it right now.
edited:It was for a Samsung MOMENT, but imagine a company flubbing two series of drivers the same way.
FFS
it's still not working
Same problem here. Windows 7 will not detect my phone in download mode. I have tried every set of drivers out there. Detects it in regular (mass storage), and USB debugging mode though.
jtdroid said:
Same problem here. Windows 7 will not detect my phone in download mode. I have tried every set of drivers out there. Detects it in regular (mass storage), and USB debugging mode though.
Click to expand...
Click to collapse
If you are using a pc, are you using the rar usb port
Sent from my SAMSUNG-SGH-I897 using XDA App
Tried all 4 ports on the back of my computer
delugeofspam said:
FFS
it's still not working
Click to expand...
Click to collapse
mcord11758 said:
If you are using a pc, are you using the rar usb port
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I believe if you right click odin you can run as administrator. Some say this has helped
Sent from my SAMSUNG-SGH-I897 using XDA App
I don't believe this to be a problem with Odin (even though I tried that method). Odin picks it up perfectly fine while in USB debugging mode. Windows simply will not pick it up when it enters download mode.
Any other mode Windows will "chime" when the phone is connected. Download mode doesn't do anything. No sound, chime, icon, nothing....
mcord11758 said:
I believe if you right click odin you can run as administrator. Some say this has helped
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Did you try deleting all drivers then going into download mode and letting windows install the drivers by itself?
Sent from my SAMSUNG-SGH-I897 using XDA App
goob1284 said:
Did you try deleting all drivers then going into download mode and letting windows install the drivers by itself?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
You know, this might be the only thing I haven't tried.
Here goes.
Edit:
Exactly the same megafail.
Hi mates,
i crashed my GT-P1000.
Installed CWM via Heimdall and tried to flash to Paranoid 2.20.
Now I cant install anything because of "Status 7".
The only package which was possible to install was MiUi.
No WiFi, no GSM, etc. - thats why I think i must have touched the radio-partition
I can control the tab via adb, but odin and all those tools dont recognize the Tab (Just Samsung Composite Device). So no flashing via Odin.
Anybody here can tell me how to get the radio partition back?
Thanks a lot and all the best!
Jan
There is no radio partition on MTD based ROM.
it is just /radio/
Which ROM did you flash, maybe can find out if it is BML or MTD.
But WiFi isn't radio dependent.
Remove your sim card in case you have the WiFi channel / middle eastern tab WiFi issue.
your best bet is still to restock
Sent from my GT-P1000 using xda app-developers app
WilhelmDerTell said:
I can control the tab via adb, but odin and all those tools dont recognize the Tab (Just Samsung Composite Device). So no flashing via Odin.
Click to expand...
Click to collapse
priyana said:
your best bet is still to restock
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
As Priyana said it is not related to radio partition... are you sure you have p1000 tab.
Error status 7 occur when flashing noncompatible ROM.
Sent from my GT-P1000
Its definetly P1000.
I used a howto to install CWM.
Technomancer’s Kernel with ClockworkMod Recovery 5 (cwm-5-p1.tar, 5 MB, md5sum: e67e61a27741069e43bf9f790bf35b10)
Heimdall Suite 1.3.2 (heimdall-suite-1.3.2-win32-.zip, 9.6 MB)
Instructions
1. Extract the contents of Heimdall Suite 1.3.2 to obtain a folder named Heimdall Suite. Drivers and the Heimdall Suite application are found inside the folder.
2. Connect the other end of the USB cable to the computer. Do not connect the tablet just yet.
3. Switch off your tablet.
4. Reboot the tablet into Download Mode. To do this, press and hold the Power and Volume Down buttons as you connect the other end of the USB cable to your tablet.
5. On your PC, double-click the zadig.exe file found in the Heimdall Suite folder. This tool allows you to easily install the USB drivers needed for Heimdall to be able to communicate with your tablet.
6. Select Options and choose List All Devices from the menu. You will see a drop-down list.
7. From the drop-down list, select either Samsung USB Composite Device or Gadget Serial and choose Install Driver. After this, Heimdall can now be safely used on your computer.
NOTE: A prompt may appear saying that the installer is unable to verify the publisher of the driver. If this happens, select “Install this driver anyway.”
8. After installation of the drivers, unplug your tablet from the USB cable.
9. Turn your tablet off.
10. Reboot the tablet into Download Mode again (as in step 4).
11. Untar Technomancer’s Kernel. You will be getting a file named zImage. Copy the zImage file into the Heimdall Suite folder. The file should be inside the same folder as heimdall.exe.
12. On your PC, open a command prompt. Change directory to where heimdall.exe is located.
13. Enter the following at the command prompt:
heimdall flash --kernel zImage
14. The command above instructs Heimdall to flash the kernel to your tablet. You will see a blue progress indicator displayed on your tablet’s screen.
15. After flashing of the kernel is done, your tablet will boot automatically.
Click to expand...
Click to collapse
Step 15 didnt work
The Tab didnt boot anymore.
So I asked a friend to have a look at it.
First there was the problem that the tab seemed not to know "who" it was.
"assert failed: getprop(“ro.product.device”)..."
We tried several ROMs.
The only one which worked was the MiUi. But nor I can enable WiFi neither it recognizes my SIM Card.
Even without the SIM I cant enable WiFi.
I dont know how to restock, without being able to install any ROM because of status 7.
So far thanks for your effort!
If you are REALLY sure you have the right version of a ROM for your type of Tab, you can do the following. ROM's which can be flashed from the Recovery are zips with files and folders. One of these files, META-INF/com/google/android/updater-script, checks first of all if the Tab is the right type. It seems this check can fail even though the Tab is OK. In this case you can just remove the first two lines with the assert statement. Be careful, because the ROM doesn't have the type sanity check anymore! It should flash now.
The best way to do this is not to unzip the zip into a folder, edit the file, and rezip the folder, but to open the zip, edit the file, and update the zip. You'll have to use an editor that respects UNIX end-of-lines (line feed), and not replaces them with DOS end-of-lines (carriage return/line feed). Notepad++ will do that, but there are others as well.
Sorry, it might have been a bit incomprehensible.
The problem isnt "assert failed: getprop(“ro.product.device”)..." anymore.
Ive got the problem that i cant install anything because of "status 7".
Restock to overcome method.
Follow my signature. Even a p1000l/n will become p1000 assert wise.
Sent from my GT-P1000 using xda app-developers app
Its done
I dont know why Odin didnt recognize the Tab before, but with these tools it does.
Thanks a lot Priyana, you absolutely made my day!!
pls close this thread
Hi all, I got into issue with my Gear Live and now it's only showing Download/Upload/Recovery. In Recovery mode, my ADB on Mac can detect the watch, but when choosing Apply update from ADB, suddenly ADB can't detect the watch, so nothing to do here.
In Download mode, I am using Heimdall to flash the stock img from Adam's ones here. And it's dailed to obtain the PIT from the watch.
Using commend:
Code:
sudo heimdall print-pit --verbose --usb-log-level debug
And some errors from debug log:
Code:
[28.431346] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7fe69840bff0 has callback 0x103e89452
[28.431355] [00000513] libusbx: debug [bulk_transfer_cb] actual_length=0
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
[28.431399] [00000513] libusbx: debug [ep_to_pipeRef] converting ep address 0x01 to pipeRef and interface
Ok the problem is about libusb or related, but I have no idea how to fix.
I am not sure if my Mac running OS X 10.10 DP 5 is the problem or not. Right now, i need the PIT file to test to see how it goes further.
Please help, thank you so much.
Problem solved:
The Almost-Stock ROM KMV78Y is working well on mine now: http://forum.xda-developers.com/gear-live/general/rom-octamodwear-stock-root-busybox-t2834620
I'm not sure if it's truly stock or not but it's clean and stable. Flashing boot.img then system.img will go. The system.img from Adam package has problem, seriously doesn't work. Try octathorp's one.
Regards.
PS: We really don't need Odin or such. In case someone doesn't know how to get into the fastboot mode, try this: http://forum.xda-developers.com/gear-live/help/download-fastboot-debug-mode-guide-t2839323
Root note 4 on mac
robertfresno said:
Root note 4 on mac
Click to expand...
Click to collapse
Use Heimdall (ODIN equivalent for mac) to flash the files. http://mac.softpedia.com/get/Utilities/Heimdall.shtml
or use JOdin if you perfer the more user friendly approach https://builds.casual-dev.com/jodin3/
Hope this helps
crabtreebrandon29 said:
Use Heimdall (ODIN equivalent for mac) to flash the files. http://mac.softpedia.com/get/Utilities/Heimdall.shtml
or use JOdin if you perfer the more user friendly approach https://builds.casual-dev.com/jodin3/
Hope this helps
Click to expand...
Click to collapse
I need a pit file
robertfresno said:
I need a pit file
Click to expand...
Click to collapse
Use this guideas to get your file to be usable with heimdall http://www.all-things-android.com/content/how-root-samsung-mobile-device
I used Odin via a vmware fusion Windows 7 virtual machine.
Sent from my SM-P900 using Tapatalk
I just got a Macbook Pro and have not had a chance to try Heimdall yet. I know Note 4 and S5 users have been experiencing the same errors under Linux (and I believe OS X as well). Heimdall doesn't like something about newer Samsung devices.
I might give it a shot again soon. If I do, I will update my Linux Heimdall post, which documents some of the patches I tried.
http://forum.xda-developers.com/showthread.php?t=2919334
Sent from my SM-N910T using XDA Free mobile app
I am getting this error in Heimdall when I try to download my N910T's PIT:
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Can anyone help? Thanks!
Caveat: I tested this how-to with Ubuntu 14.04 and a Lenovo pc, I obviously don't know if it'll work for different linux versions, computers, note 4 phones. Just take everything as it is and please don't blame me if your phone gets bricked. Heimdall is as risky as Odin and you can void your warranty or even hard brick your phone if you don't know how to use it. I am a beginner myself with this software and don't ask me how to use it, just because I still have to learn most commands
Edit 1/12/16: I tested this software and I successfully flashed a TWRP recovery and eventually rooted my phone.
Most credit goes to Fattire and to the people at Github who are still mantaining and forking this software.(see why below).
I am a linux only user and I've been such for the latest 10 months at least. and, while I was previously a guy who played a lot with his own gadgets, the absolute lack of spare time and the lack of windows and Odin as well has prevented me from rooting and modding my last device.
As most of you should know, Heimdall is something like an open source versione of Odin, which works for Windows, Linux and Mac too. Anyway, Heimdall is this thing https://github.com/Benjamin-Dobell/Heimdall
Most threads here are very old and not very useful in order to get a fully functional Heimdall for Note 4 smartphones. I thought myself it was outdated and no more useful.
Yesterday I saw a post of @fattire http://forum.xda-developers.com/not...3-0-910f-g-t3243386/post64090942#post64090942 that linked to another post of his that linked to a thread of Github.
Well, I had some free time and it took not more than an hour to get everything working.
As Fattire himself wrote in the thread I linked, it is slightly technical, but it's not that difficult (I am a hobbyst, I am a lawyer and not a professional developer, and, as I said above, it took me less than a hour for everything to work).
So I want to share a simple how-to. It'll be not very well written since I have no spare time for now, but I hope it can be useful just the same.
First of all, the version of Heimdall that you can install this way
sudo apt-get install heimdall-flash
does not work
You need to clone the Github repo by SaburoJiro
Well, first of all, you've got to
sudo apt-get install git
then you have got to clone the repo but, unless you have already got a Github account or you want to join to it, you cannot type
git clone [email protected]/SaburoJiro/Heimdall.git
since you'll get a warning about your public key not beeing accepted
on the other side, you just have to use https instead of the previuos command this way (while being sure you are in your own user home directory)
git clone https://github.com/SaburoJiro/Heimdall.git
then it will took some time, also depending on the speed of your data connection and, after that time delay, you should have got the sources in /Heimdall
In any case, if the the path should be different, please look yourself for the directory where the sources are.
So, still as sudo su, type
cd Heimdall/libpit
Now you have got to compile the sources. If you have already compiled other biniaries, you should already have got the build essentials, if you have not compiled anything yet, you have very likely to
sudo apt-get install build-essential cmake zlib1g-dev qt5-default libusb-1.0-0-dev libgl1-mesa-glx libgl1-mesa-dev
then you just have got to type (see also here https://wiki.cyanogenmod.org/w/Install_and_compile_Heimdall)
cmake -DCMAKE_BUILD_TYPE=Release ..
make
sudo cp bin/* /usr/local/bin
Now you should have a working heimdall!
To check if it works, just put your phone in download mode, connect it to your computer via usb, and type
heimdall print-pit
that's what you should get
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
etc.
and finally
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Well, now it works and I should be able to flash a recovery or a kernel without any hassle but for now I've got to work, so I cannot go any further
Just a little update, though not many users seem to be interested: I flawlessly flashed a twrp recovery without using the frontend (i.e. by using the terminal) and everything went fine. Later on I rooted the phone by flashing from the recovery both the kernel and supersu 2.50.
This thing is reliable and much faster than Odin, especially if you give up to the Gui.
It is a very good choice for Linux users.
You just have to download the right recovery.img, open the terminal of your pc as
sudo su
connect your phone in download mode and type
heimdall flash --RECOVERY recovery.img
and that's all, your phone will reboot and the recovery will be ok.
No warranty void until you actually use the recovery, as usual. If you flash anything, knox will be triggered.
I flashed supersu 2.52 and one of the kernel Senforcing compiled by Phil379, BTW
Update booloader and modem
I have just downloaded modem and bootloader from Kyuby rom http://forum.xda-developers.com/note-4/snapdragon-dev/kyubi-rom-port-n5-n910f-coj3-v5-t3254964
Updating modem and bootloader is very easy, you just have to remove the .md5 extension an decompress the 2 tar files. My suggestion is to put all the files into a single folder (in my case I put them into Scaricati, which stands for Downloads in italian).
After that, you have just got to type
sudo su
and move to the folder where the files are stored, then type the command shown below, which flashes both the modem and the bl files. Very easy, 30 seconds at most
[email protected]:/home/luca/Scaricati/bootloader# heimdall flash --APNHLOS NON-HLOS.bin --MODEM modem.bin --ABOOT aboot.mbn --RPM rpm.mbn --SBL1 sbl1.mbn --DBI sdi.mbn --TZ tz.mbn
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading APNHLOS
100%
APNHLOS upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading ABOOT
100%
ABOOT upload successful
Uploading RPM
100%
RPM upload successful
Uploading SBL1
100%
SBL1 upload successful
Uploading DBI
100%
DBI upload successful
Uploading TZ
100%
TZ upload successful
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Video please
pedodroid said:
Video please
Click to expand...
Click to collapse
Well, I have no camera, apart from a couple of smartphones and I can't ask my wife to help me, she would say I am a nerd lol!
Do you want a video of the part where I compile the sources or about the flashing of modem and bootloader? Regarding the first one, maybe i could record the screen of my pc and share such video....
lucaoldb said:
Well, I have no camera, apart from a couple of smartphones and I can't ask my wife to help me, she would say I am a nerd lol!
Do you want a video of the part where I compile the sources or about the flashing of modem and bootloader? Regarding the first one, maybe i could record the screen of my pc and share such video....
Click to expand...
Click to collapse
WE ARE ALL NERDS!!!!!!! EMBRACE NERDOM!!!!
On topic you could use a screen recording app to get a video of what's going on on your phones screen then upload to youtube.
Yes, lol
But, when I use Heimdall, my phone is in download mode and there is nothing to be shown and there is no app that can record its screen. Anyway, during the week end, I will look for a way to make this how to as clear as possible and maybe I will share a little video. I was also thinking of making a deb package since Heimdall is an open source software and sharing a package should not break any rule, but I haven't made any deb package since the times of Nokia n900 (i.e. early 2011) and I need to brush up my skills
Thanks for taking the time to test this out.
One less reason to have a Windows partition.
Sent from my SM-N910F using Tapatalk
Thanks for this thread, been a Linux convert for about a year myself. Had to use my old windows machine for odin until now
Sent from my SM-N920C using Tapatalk
This all sounds interesting, i will try it.
Sorry for not sharing any video, but last week end I was very busy for work and I'd got some troubles with my pc due to a bad update of the javaws platform that I must rely on (the so called PCT: telematic trial... Garbage! Each update a bug, especially for poor linux users lol).
Anyway, I have checked and tried myself my own tutorial and found a little mistake: it's not Saburo Jiro's andoid.git, but Heimdall.git
Sorry for the mistake, but I had written this little guide very fast
The other steps do work.
Double post
@lucaoldb
Thank you,
Wow, I can't believe I've never seen this post. Ive searched for a verified working heimdall for the note 4, on and off for a year. Ive been trying to get rid of windows for over a year. Every search I've always done always showed unsuccessful results. And i never wanted to attempt it without knowing it could work. Don't want to brick my device.
So your saying, if i compile heimdall from source that it'll work. Can you or anyone please confirm this? And does it work for complete tar?
Thank you much!
You are welcome
It worked one year ago and I still have a working heimdall in my pc. In the meanwhile, the version you can install via apt-get could have been updated.... I would try this route first.
Regarding the full tar, you just have to extract the single files so as I wrote in the OP.
So, today 24th of September, Linux says:
remote: Repository not found.
fatal: repository 'https://github.com/SaburoJiro/Heimdall.git/' not found
Do you have the old repository or is there another way to compile the repository to flash the Note 4 with Heimdall?
So i found that you copied the old repository, can you change the old repository from SaburoJiro to https://github.com/fat-tire/Heimdall?
Heimdall is a very interesting choice, specially for linux users (like me) who don't have access to a windows computer or Odin itself. I've compiled the Command line version and saved it somewhere, so I can use it in every distro I got. It works very well and doesn't need any dependecies (except for libusb which comes with almost every distro).
It's just a bit more complicated when you have to flash a stock ROM that comes with many files at once and you have to know every single partition to flash. The command for it gets big and with a lot of parameters (I am not complaining about that) which makes complicated for most of common users.
Just yesterday I have flashed a stock ROM on my Grand Prime, that was complicated to figure out which file fitted on each partition. Even though it was hard, I still managed to get my phone working again.