Database Develop

Please Help!!I think I bricked my Phone "zImage" Error :((

****************************************************************************
FIXED IT MYSELF! PLEASE CLOSE THIS THREAD! THANKS AND SORRY FOR THE INCONVENIANCE!!
****************************************************************************
Hey guys...pretty big noob here,
I have a Samsung Galaxy S i1900 and wanted to get Cyanogen on there,
I had a custom rom(don't remember which one) with Gingerbread installed for quite some time, but i wanted something new.
I followed the instructions from the cyanogenWiki and wanted to install
the ClockMod Recovery.
\\instructions below
Power off the Samsung Galaxy S and connect the microUSB to the computer but not the Samsung Galaxy S.
Boot the Samsung Galaxy S into download mode by holding down Home & Volume Down while connecting the microUSB to it.
Untar hardcore's kernel into the Heimdall directory.
On the computer, open terminal and run the following command from the Heimdall directory:
heimdall flash --kernel zImage
\\I followed all the instructions above and get the following error
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised...
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to open file "zImage"
\\Then trying to run again:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is initialised.
ERROR: Failed to open file "ZImage"
-------------------------------------
If i reboot without download moade i'm stuck in cell to computer mode and odin doesn't seem to detect anything (tried with 1.7 and 1.85)
Any idea how/if I can fix this??
Thanks
****************************************************************************
FIXED IT MYSELF! PLEASE CLOSE THIS THREAD! THANKS AND SORRY FOR THE INCONVENIANCE!!

Now with what you running your cell?
Sent from my GT-I9000 using xda premium

I find it less disturbing to use heimdall-frontend while im on linux.
If you dont have it installed i would recommend you to use that if you are not to familiar with flashing.
Can you still get you'r phone in download mode?
if so you might have to grab a stock firmware and flash back to stock before re-trying (that is if you cant boot/read data from the partitions)
you can grab a binary file installer from heimdalls website and launch it by typing heimdall-frontend in a terminal window.
Hope this help you!
Edit: you can grab a stock rom from http://samfirmware.com
Edit 2: h***, you have allready fixed it, good for you!
Sent from my GT-I9000 using Tapatalk

That's the solution when I had this problem I solved in this way try it will fix
Sent from my GT-I9000 using xda premium

Rooting protection?

I have now successfully rooted my device by downloading the firmware, unpacking system.img.md5, adding the su binary, making an ext4 sparse image and installing that to the device using heimdall. Problem was, that on my first attempts the system became unstable, the UI restarted repeatedly, especially when manually switching WiFi and Data Mode. After double and triple checking everything I found that I could create a perfectly stable system image by following the same steps but just not adding the su binary. One further attempt placing the su binary in /system/usr/bin (does not exist) and using it as a backdoor to install the binary to /system/bin/su I now seem to have a stable and rooted system.
It appears that something has been detecting my initial and straightforward attempt to tamper with the system image and made the system to become unstable. I have seen a lot of errors from PackageManager in my logs but nothing conclusive.
Tom

RealBorg said:
I have now successfully rooted my device by downloading the firmware, unpacking system.img.md5, adding the su binary, making an ext4 sparse image and installing that to the device using heimdall. Problem was, that on my first attempts the system became unstable, the UI restarted repeatedly, especially when manually switching WiFi and Data Mode. After double and triple checking everything I found that I could create a perfectly stable system image by following the same steps but just not adding the su binary. One further attempt placing the su binary in /system/usr/bin (does not exist) and using it as a backdoor to install the binary to /system/bin/su I now seem to have a stable and rooted system.
It appears that something has been detecting my initial and straightforward attempt to tamper with the system image and made the system to become unstable. I have seen a lot of errors from PackageManager in my logs but nothing conclusive.
Tom
Click to expand...
Click to collapse
Hi Tom! I managed to root my s advance with this method, but in guide that I have read, was said that I should put the su binary on "/system/xbin/". I used that steps, by Xanonus. Over here everything gone right and after flashing, I got Supersu from Play store. If help you, please thanks Xanonus.
Sorry for bad English

johnnybr said:
Hi Tom! I managed to root my s advance with this method, but in guide that I have read, was said that I should put the su binary on "/system/xbin/". I used that steps, by Xanonus. Over here everything gone right and after flashing, I got Supersu from Play store. If help you, please thanks Xanonus.
Click to expand...
Click to collapse
Xanonus unnecessarily copies everything out from system to new_system, you can just add the su binary to the loop mounted image.
/bin/su is the location of the su binary on every Unix system and Superuser also installs the su binary to /system/bin/su. I wonder if it would make a difference (avoid instability) to place it in /system/xbin/su.
Tom

RealBorg said:
Xanonus unnecessarily copies everything out from system to new_system, you can just add the su binary to the loop mounted image.
Click to expand...
Click to collapse
I really suspected that, like you said, part of all that stuff was unnecessary.
About the place of su binary, well, I just wanna to help. I don't know nothing about linux and less of unix. But normally, while you are dealing with this kind of stuff, you should try. Cause things sometimes work when they shouldn't and don't work like they should. I can only say: God knows why...:silly:

Thread moved to General section, post in the relevant section next time.

Why use Heimdall to flash ? Odin3 works better
"None forget the bite.....of Viper...."

CallMeVentus said:
Why use Heimdall to flash ? Odin3 works better
Click to expand...
Click to collapse
heimdall is the method of choice when you are on linux and works like a charm
much easier than Odin which needs the image to be put into a .tar.md5 file
Tom

RealBorg said:
heimdall is the method of choice when you are on linux and works like a charm
much easier than Odin which needs the image to be put into a .tar.md5 file
Tom
Click to expand...
Click to collapse
I have tried heimdall but I can't make it work on Windows (7 X64, it never get to comunicate between pc and mobile). So when I was messing with my rom I have to try zillions of ways to make a image to work with Odin. In the end, make the image with ext4_utils and compress with tar on my virtual machine running ubuntu did the trick. If you don't put any md5sum verification or "md5" in the name of the file, Odin never check the file.
This was me trying to root hahhaa!!
I guess everyone that want play with Android should learn to use linux. ubuntu at least. I intend to learn linux, but I can't right now.
Sorry, crap english from google translator!

johnnybr said:
I have tried heimdall but I can't make it work on Windows (7 X64, it never get to comunicate between pc and mobile). So when I was messing with my rom I have to try zillions of ways to make a image to work with Odin. In the end, make the image with ext4_utils and compress with tar on my virtual machine running ubuntu did the trick. If you don't put any md5sum verification or "md5" in the name of the file, Odin never check the file.
This was me trying to root hahhaa!!
I guess everyone that want play with Android should learn to use linux. ubuntu at least. I intend to learn linux, but I can't right now.
Sorry, crap english from google translator!
Click to expand...
Click to collapse
Seriously?
How can hemidall work on windows when its designed for linux!
Sent from my GT-I9070 using xda premium

Shaaan said:
Seriously?
How can hemidall work on windows when its designed for linux!
Click to expand...
Click to collapse
Actually it has a windows version. Even Mac has a version of Heimdall. Take a look: http://www.glassechidna.com.au/products/heimdall/
Indeed I can't make it work... Perhaps on windows x86 it can work...

Samsung galaxy gear

Can anybody tell me if there is a method of rooting the Galaxy gear via a Mac.
All the vids that are currently talking about rooting are using Windows.
There must be a Mac version surely???
Sent from my SM-N9005 using xda app-developers app

I had to use parallels worked great
Sent from my SAMSUNG-SM-N900A using xda app-developers app

Sweetboy220466 said:
Can anybody tell me if there is a method of rooting the Galaxy gear via a Mac.
All the vids that are currently talking about rooting are using Windows.
There must be a Mac version surely???
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
You can search for the same app name and you will find the website with a mac version you can download. Let me know if you can't find it and will post a link.
Sent from my SM-N900V using Tapatalk

Mac owner here - First, a more descriptive title would have helped your thread - simply posting the name of the device garners no attention. Take the time to think about a good title that will gain people's curiosity or assistance.
Second, I had to use a windows machine to first root it, but since then I can push anything to it using the Terminal on my Mac.
ODIN is Windows Only. There is a Mac alternative called Hiemdall (notice the trend of using mythical character names?) It is found here: http://forum.xda-developers.com/showthread.php?t=834195
However, I have seen a lot of people having issues with Heimdall. I would suggest using a friend's Windows machine to initially root it properly, then you will be fine using terminal.
You have a few choices for getting the adb and fastboot binaries:
1. Download the SDK
2. google for the files
3. http://www.2shared.com/file/w2mue84a/adb-fastboot.html
If you need to learn to use these, then search the boards.
Good luck!

therealduckie said:
Mac owner here - First, a more descriptive title would have helped your thread - simply posting the name of the device garners no attention. Take the time to think about a good title that will gain people's curiosity or assistance.
Second, I had to use a windows machine to first root it, but since then I can push anything to it using the Terminal on my Mac.
ODIN is Windows Only. There is a Mac alternative called Hiemdall (notice the trend of using mythical character names?) It is found here: http://forum.xda-developers.com/showthread.php?t=834195
However, I have seen a lot of people having issues with Heimdall. I would suggest using a friend's Windows machine to initially root it properly, then you will be fine using terminal.
You have a few choices for getting the adb and fastboot binaries:
1. Download the SDK
2. google for the files
3. http://www.2shared.com/file/w2mue84a/adb-fastboot.html
If you need to learn to use these, then search the boards.
Good luck!
Click to expand...
Click to collapse
Odin is windows only but that is to flash a rom. There is another program you can use to just root the gear and only root. To root on the Mac the program is called impactor and it has both a windows version and a Mac version.
see this link for information about cydia impactor to root. Go here to download
http://www.cydiaimpactor.com
It has links for mac, Windows, linux 32 or 64 bit.
If you want to flash a new rom you need odin which is windows only.
To sideload apps use terminal on your mac and install adb then it is as easy as ./adb install app-name. Apk
Sent from my SM-N900V using Tapatalk

Please help getting the PIT file fỏ Gear Live

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

How to compile Heimdall for Linux Ubuntu 14.04 - works for Samsung note 4

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.