yashsingh1/xdaforums huggingface dataset:
[Android Development on Bada] hunktb:
I know Tigrouzen ROM's until now have not been GPL compliant (look here, here or here for example), but sharing this sources may allow XDA talk about it if it become GPL compliant:

Look at this from may 23th:

https://www.facebook.com/tigrouzen/posts/869017383124767

ICZen source 2.5GB compressed, 5GB uncompressed :

This is source not rom, you can modify and compile to make rom.

http://zendrokat.com/ICZen.tar.gz​

Edit1: I am afraid it is not GPL compliant, It seems he is just focusing on new project

-- not all sources have been shared ...

- "Of course i don't give it for free," ...

May 4th

https://www.facebook.com/tigrouzen/posts/856550224371483

If you are interesting from source & kernel pm me :

I make it 5GB full source and 2.4GB compressed, original source it is 20GB.

Support : 2 Weeks, also i support you if you need port Kitkat or Jelly Bean, explain how make it optimize.

Source ICS :

Ready to compile

Support if you have issue or need help and porting.

Very fast compile, 45min for my B960 2 core.

Rom file script :

Support for making it easy way and tweak

With last modification for make theme default.

Kernel source :

All script Nand, SD (bigmem...)

All tweak

Ready to compile, with bash script.

Recovery mode Integrated on kernel source :

I lost the source, but as you see it is complète

I added many thing on

Support for script making.

FBOOT : Multi boot source, like you can use it to boot under to 2 different rom with multi key code.

Kernel goes on 1 folder with 2 different name.

Example : boot ics kernel name : zIcs. Boot Kitkat kernel name zKitkat. Then with key holding you choose which rom you want boot.

I never do it because only support S8500

But it is work.

Of course i don't give it for free,there's more then 5 years experience work before making good kernel and good rom.

Ps : im on new project it is making file sharing next generation. zClouds...
[Android Development on Bada] black0000:
Zendrokat

Yesterday at 12:36am · Edited ·

ICZen source 2.5GB compressed, 5GB

uncompressed :

This is source not rom, you can modify and

compile to make rom.

http://zendrokat.com/ICZen.tar.gz

Use 7zip, already downloaded tested.
[Android Development on Bada] BenzoX:
Those are only ROM sources, but he says kernel sources will come later.
[Android Development on Bada] Fidelator:
Can the Nand version of the kernel work on Badadroid, more specifically unofficial CM by volk? Can I just flash it or are there any other necessary steps? (Aside from the usual clear dalvik and cache)
[Android Development on Bada] Taxidriver05:
Nope!

Tigrouzen's kernels are not compatible with volk204's ROMs.
[Android Development on Bada] Silkmeister1:
Hey [MENTION=4570762]Taxidriver05[/MENTION], Tigrouzen mentioned that you had broken video and asked me to give you zImage that makes the video work again.

here it is for Wave I (Nand)

http://speedy.sh/ppwBe/zImage

you'll also notice faster back button and recents window

Silkmeister1
[Android Development on Bada] Taxidriver05:
But I need kernel for Wave II...
[Verizon Samsung Galaxy S 4] BabelDev:
Hey everybody, I spent the last two days reading up and down the forum and simply cant find an solution to recover my soft bricked SCH-545.

I was on a MK2 firmware. I rooted my phone using the saferootmethod which worked fine. Than I wanted to flash Hiperdrive RLS 15 on my device using safestrap. Here the flash ran all the way through but my phone simply wouldnt boot anymore (boot freeze). At this point I still could go into safestrap recovery mode. So I decided to select another rom. Unfortunatelly I dont know anymore which one. Stupid me! The end of the story, it didnt work "Firmware upgrade encountred an issue. Please select recovery mode in Kies and try again". I cant go into recovery mode anymore and Kies wont detect the device. I only can go into download mode. This works still fine.

So I decided to follow this threat (http://xdaforums.com/showthread.php?t=2578209) in order to recover the device. I tried both, full-wipe and no-wipe / with and without pit file. I also tried different USB cable (original samsung and other) and different USB hubs. But I always get following error:

<ID:0/003> Removed!!

<ID:0/003> Added!!

<ID:0/003> Removed!!

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> sbl1.mbn

<ID:0/003> NAND Write Start!!

<ID:0/003> sbl2.mbn

<ID:0/003> sbl3.mbn

<ID:0/003> rpm.mbn

<ID:0/003> aboot.mbn

<ID:0/003> tz.mbn

<ID:0/003> boot.img

<ID:0/003> recovery.img

<ID:0/003> persdata.img.ext4

<ID:0/003> system.img.ext4

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

The next end last attempt was to download the stock firmware from sammobile.com (I545VRUEMJ7, I545VRUEMK2, I545VRUFNC5). But also the same error. I know now that you cannot downgrade but I still gave it a shot thinking that I might was mistaken with the built number MK2. But when I bought the phone it came with 4.2.2 and I know that I upgraded it to 4.3 at some point later.

Also, In the downloading mode, in the top left corner it says:

Write protection: enabled

eMMC Burst Mode: enabled

Now I simply dont know what I can do anymore. Is there somebody else you experiences / experienced similar issues or somebody who could point me in the right direction. Any help would be greatly appreciated. Thanks a thousand times!!!
[Verizon Samsung Galaxy S 4] k1mu:
Well, this is different. Normally, the "Complete (Write) operation failed." has some info displayed on the phone that says why it failed.

I'd start with installing Samsung Kies and trying to recover using that.
[Verizon Samsung Galaxy S 4] BabelDev:
Hi thank for your quick response. I get this message on Odin. In the screen of the device you only see a progress bar that stops. Thats It.

I also tried installing / reinstalling Kies and the samsung driver but it wont detect my device. So it seems that this is not an option either.
[Verizon Samsung Galaxy S 4] BabelDev:
PS: Odin detects the device but Kies does not.
[Verizon Samsung Galaxy S 4] Surge1223:
This is what you should do;

1. First boot in to linux (google "dual-boot linux and windows 7" or "boot linux live cd" if you dont know how to get linux)

2. Download this file and this file

3. Next, open terminal emulator (google "how to open terminal emulator in linux" if you dont know how to open terminal emulator.) and then copy and paste the following into terminal:

find . -name "Heimdall1.4c2debian.sh" -exec cp {} ~/ \;
find ~/ -name "Heimdall1.4c2debian.sh" -type f -exec chmod 755 {} \;
sh ~/Heimdall1.4c2debian.sh

4. Type in your password (dont worry if it looks like no characters are being entered when you type your password, this is normal hit enter after your done typing your password) if all went well heimdall-frontend should open up.

5. In the "flash" tab under "PIT" select browse and find the pit file i had you download in step 2.

6. Under "Partitions (Files)" select add then change the Partition type to SYSTEM and choose the system.img.ext4 file that you can get from the ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5 you downloaded earlier (rename the end of the file from tar.md5 to .tar then extract it) then click "Add" and then "Remove"

7. Go over to the "Utilities" tab and select "detect" then go back to the flash tab and select "start". If all goes well this should recover your device.

Sorry about telling you to google this or that, but if I had to type out the whole process I think I would've just given up typing a response at all.
[Verizon Samsung Galaxy S 4] BabelDev:
find . -name "Heimdall1.4c2debian.sh" -exec cp {} ~/ \;
find ~/ -name "Heimdall1.4c2debian.sh" -type f -exec chmod 755 {} \;
sh ~/Heimdall1.4c2debian.sh

Hey and thank you. I am installing Ubuntu right now. Just for clarity, you want me to copy and paste the exact code including ";" or do I need to modify it in any way?

I will keep the forum updated on my "progress". :p

Thank you guys a thousand times.
[Verizon Samsung Galaxy S 4] BabelDev:
So I installed Ubuntu via VMware on my OSX, copied all the files on my virtual machine and opened the terminal. So far, so good.

But when I entered the commands I get following error "missing argument to `-exec'" (see screenshot).

Help would be greatly appreciated. Thank you!
[Verizon Samsung Galaxy S 4] Surge1223:
you removed both semi-colons. Literally copy and paste what I typed.
[Verizon Samsung Galaxy S 4] BabelDev:
I did that to but receive an "Syntax error: redirection unexpected"

Thanks for you quick response!!
[Verizon Samsung Galaxy S 4] Surge1223:
try typing this in terminal:

bash ~/Heimdall1.4c2debian.sh

and if that doesnt work try:

cd ~/
chmod 777 Heimdall1.4c2debian.sh
./Heimdall1.4c2debian.sh
[Verizon Samsung Galaxy S 4] BabelDev:
I tried both commands now and both seem to work. I type in the passwords and it runs. Than it asks me a second time for the pass and than I get an "Authentication failure". Tried it multiple times with both commands, always the same (see screenshot)

If it doesnt work with ubuntu, do you think I just should tried it with the OSX version of Heimdall?

Thank you!
[Verizon Samsung Galaxy S 4] Surge1223:
ok open terminal and type this in, when it asks for the password just hit enter, dont actually type a password.

sudo su

then finally copy and paste the below:

find . -name "Heimdall1.4c2debian.sh" -exec cp {} ~/ \;
find ~/ -name "Heimdall1.4c2debian.sh" -type f -exec chmod 755 {} \;
bash ~/Heimdall1.4c2debian.sh

you can replace the last line with the below if it the above doesnt work.

cd ~/
chmod 777 Heimdall1.4c2debian.sh
./Heimdall1.4c2debian.sh
[Verizon Samsung Galaxy S 4] BabelDev:
Thanks again surge1223. This time Heimdall fronted started but after following your instructions I get a "Failed to begin session!". I attached again a screenshot. Any leads on went wrong? Thank you.
[Verizon Samsung Galaxy S 4] BabelDev:
PS: Here the full status description from Heimdall:

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...

ERROR: Failed to begin session!

Releasing device interface...

Re-attaching kernel driver...
[Verizon Samsung Galaxy S 4] Surge1223:
connect the phone to a different usb port, then type this in terminal hit enter when it asks for pass

sudo su

then:

sudo apt-get update && sudo apt-get upgrade

if you're not using a live cd then I would recommend rebooting here but if you are using a live cd dont reboot then in the same terminal window type the following (if you didnt reboot)

heimdall-frontend

and try again
[Verizon Samsung Galaxy S 4] BabelDev:
I followed your instructions and rebooted ubuntu. Afterwards I started heimdall-fronted again and followed the your initial instructions. I made sure that my S4 is in download mode.

Now I receive follwoing error however:

Initialising connection...

Detecting device...

ERROR: Failed to access device. libusb error: -3
[Verizon Samsung Galaxy S 4] BabelDev:
I meanwhile installed libusb on ubuntu using following commands:

sudo apt-get install libusb-dev

sudo bash -c "apt-get update && apt-get upgrade"​

After rebooting I still get the same error on Heimdall as before

Initialising connection...

Detecting device...

ERROR: Failed to access device. libusb error: -3​

Any leads on whats going on? Thanks!
[Verizon Samsung Galaxy S 4] Surge1223:
ok now in terminal, type the following and hit enter when it asks for pass

sudo su

Then copy and paste all of the below into terminal and reboot once they're done installing and try again (we're almost there!)

sudo apt-get update && sudo apt-get upgrade && sudo dpkg --configure -a && sudo dpkg --add-architecture i386 ; sudo apt-get update ; sudo apt-get --yes --force-yes install build-essential pkg-config zlib1g-dev libusb-dev libqt4-dev qt4-qmake autoconf libtool libusb-1.0-0-dev debhelper libusb-1.0-0 libgcc1 libc-bin tzdata libc-bin libdb1-compat initscripts libdb1-compat locales psmisc git-core ia32-libs libusb-ocaml libhpmud0 libdevice-usb-perl libusb-0.1-4 libusb-1.0-0-dev libusb-dev libusb-1.0-0 libusb++0.1-4c2 libusbprog-dev libusb++-dev libusbtc08-1 libusbmuxd-dev libusbmuxd1 libusbprog0
[Verizon Samsung Galaxy S 4] BabelDev:
Thank you. I followed your instruction but it seems that the "package is missing, has been obsoleted, or is only available from another source". I also attached a screenshot.

I tried to flash using heimdall again anyway but received the same libusb error.
[Verizon Samsung Galaxy S 4] BabelDev:
Thanks once again. I followed your last instructions but received following notice "package is missing, has been obsoleted, or is only available from another source". I rebooted and tried the to flash using heimdall again but received the same libusb error. I also attached a screenshot.
[Verizon Samsung Galaxy S 4] Surge1223:
ok lets try this in terminal:

sudo heimdall flash --SYSTEM /path_to_the_system.img.ext4_file/system.img.ext4
[Verizon Samsung Galaxy S 4] BabelDev:
Also, no success. "Error: failed to begin session!"

Uff...do you think I should try to flash the whole stock firmware or do you think I will encounter the same issue? I am stuck and really dont know what else to do. Thanks a thousand time for your support here.
[Verizon Samsung Galaxy S 4] BabelDev:
Anybody can give me any leads on how to get Heimdall running on umbuntu? I am always getting this error and cant find a solution it seems. Help would be reatly appreciated. Thank you!
[Verizon Samsung Galaxy S 4] BabelDev:
So, this is basically the root of the problem I believe.

With this command I tried to access my device. It detects it but seems that It has no write access. Someone has an idea, how I can perceid? Thanks!

$ heimdall print-pit --verbose

Initialising connection...

Detecting device...

libusbx: error [_get_usbfs_fd] libusbx couldn't open USB device /dev/bus/usb/001/003: Permission denied

libusbx: error [_get_usbfs_fd] libusbx requires write access to USB device nodes.

ERROR: Failed to access device. libusb error: -3
[Verizon Samsung Galaxy S 4] Surge1223:
You need to install android-sdk and java and add them to your path. So that adb usb rules can be set
[Verizon Samsung Galaxy S 4] BabelDev:
Ok, so I installed android-sdk and java following these instructions.

http://askubuntu.com/questions/3182...on-guide-for-android-sdk-adt-bundle-on-ubuntu

It seems that the AVD Manager can access my device but there is non of my personal data left on it. I also tried to flash it via heimdall again as you were initially suggesting. I received the same error again though.

ERROR: Failed to access device. libusb error: -3

Is there a way to restore the device with the AVD Manager or what do I need to do? Thank surge1223 a thousand times!
[Verizon Samsung Galaxy S 4] BabelDev:
So I followed the Android SDK instructions and set the undev rules.

Here the instructions if someone needs them.

Following that is used the command.

$ adb devices

It seems however that the terminal does not recognize my device. Heimdall on the other hand seems to recognize it but has no write access.

Dont know anymore...I am stuck.
[Verizon Samsung Galaxy S 4] BabelDev:
https://help.ubuntu.com/community/AndroidSDK
[Verizon Samsung Galaxy S 4] Surge1223:
you have to add the android-sdk/platform-tools dir to your PATH. It would be easier to google how to this.

heres an example of what I had to enter

export PATH=${PATH}:~/android-sdk/tools

export PATH=${PATH}:~/android-sdk/platform-tools

export PATH=${PATH}:~/bin

export JAVA_HOME=/usr/lib/jvm/jdk1.7.0
[Verizon Samsung Galaxy S 4] BabelDev:
I am sorry, I was not clear. I set the PATH. See here:

# export PATH=${PATH}:~/home/ubuntu/workspace/android/android-sdk-linux/sdk/tools

# export PATH=${PATH}:~/home/ubuntu/workspace/android/android-sdk-linux/sdk/platform-tools

I also created a rule file. See here:

# gksudo gedit /etc/udev/rules.d/51-android.rules

And than defined rules for my Samsung S4 (since I was not sure which one is the correct one I added a couple):

# SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="adbusers"

# SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0600", OWNER="<ubuntu>"

# SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"

# SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666", GROUP="plugdev"

When I type in the command (# adb devices) the terminal doesnt list any devices.

Heimdall however does detect it. I also dont get this error anymore:

ERROR: Failed to access device. libusb error: -3

But Instead when I try to flash the .pit and system.img.ext4 file, Heimdall gives me this error.

Initialising connection...

Detecting device...

Claiming interface...

Attempt failed. Detaching driver...

Claiming interface again...

Setting up interface...

Initialising protocol...

Protocol initialisation successful.

Beginning session...

ERROR: Failed to begin session!

Releasing device interface...

Re-attaching kernel driver...

Ufff, 4 days non stop now....my eyes heard and I still dont know what going on here. Any suggestions are very welcome. Thank you.
[Verizon Samsung Galaxy S 4] Surge1223:
install all of the below manually by typing

sudo apt-get install x

where "x" is replaced by each file in the list below.

libusb-ocaml

libhpmud0

libdevice-usb-perl

libusb-0.1-4

libusb-1.0-0-dev

libusb-dev

libusb-1.0-0

libusb++0.1-4c2

libusbprog-dev

libusb++-dev

libusbtc08-1

libusbmuxd-dev

libusbmuxd1

libusbprog0
[Verizon Samsung Galaxy S 4] BabelDev:
Thanks surge1223. I installed all the packages manually. I tried to flash via Heimdall again but receved the same error. Do you think there is still hope? Thanks for ur support.

Initialising connection...

Detecting device...

Claiming interface...

Attempt failed. Detaching driver...

Claiming interface again...

Setting up interface...

Initialising protocol...

Protocol initialisation successful.

Beginning session...

ERROR: Failed to begin session!

Releasing device interface...

Re-attaching kernel driver...
[Verizon Samsung Galaxy S 4] Surge1223:
Actually I think I figured out why you're getting that error!, im writing a fix into a script now. Ill update this post with a link.

I was getting the same error on my linux build too but was able to finally resolve it...itll take me an hour or so to post the script
[Verizon Samsung Galaxy S 4] BabelDev:
Thanks surge1223, its really a pain in the .... :)
[Verizon Samsung Galaxy S 4] Surge1223:
Okay download this and extract it anywhere.

Now were doing the same steps of typing sudo su, then enter when it asks for your pass enter but instead of using the"Heimdall1.4c2debian.sh" script, we're going to use the newly extracted script named "Heimdall1.4.1debian.sh" and pray that this works. Godspeed.
[Verizon Samsung Galaxy S 4] BabelDev:
Hey surge1223, thanks for the script. I really appreciate that. I extracted the file and put Heimdall1.4.1debian.sh and external.zip on the desktop. Than isntalled using following commands.

sudo su
bash ~/Heimdall1.4.1debian.sh

At the bottom of the terminal output I receive following output, does this mean anything?

http://pastebin.com/2qCqNZJF

In either way, Heimdall opened and an tried to flash the device but received again the same error.

Godspeed! Really stuck here. Just doesnt want to it duty Mr. Heimdall
[Verizon Samsung Galaxy S 4] Hashbang173:
I think this has to be with running Ubuntu on a virtual machine.

The USB drivers and stuff gets all messed up
[Verizon Samsung Galaxy S 4] BabelDev:
Thanks for the comment. So do you think I should run Heimdall on OSX?
[Verizon Samsung Galaxy S 4] BabelDev:
So, I also tried not to flash via Heimdall on OSX. Thats what it says.

It detects the device but than simply thats do anything. Do you think there is still hope or what might be the reason? Thanks guys.
[Verizon Samsung Galaxy S 4] BabelDev:
Here also a screenshot. Its funny because it says "Flash completed successfully".
[Verizon Samsung Galaxy S 4] Hashbang173:
Could you try to run Ubuntu from live usb drive/DVD?

Or could you dualboot Ubuntu and Mac osx
[Verizon Samsung Galaxy S 4] BabelDev:
I am running now Heimdall on my native OSX Mavericks. Heimdall says it detects my device but when is use following command I get following info. I believe this to be the root of all evil. Any experiences with that? Thanks.

sudo heimdall print-pit --verbose --stdout-errors
[Verizon Samsung Galaxy S 4] BabelDev:
just to be clear, I uninstalled Kies prior to this.
[Verizon Samsung Galaxy S 4] Surge1223:
adb kill-server

then retry
[Verizon Samsung Galaxy S 4] BabelDev:
Nope, unfortunatelly this doesnt work.
[Verizon Samsung Galaxy S 4] Surge1223:
you said youre using mavericks right? you have to install brew and macports for it to work on osx...thats why I said to use linux. I have a new macbook pro (2014) dual booting linux and osx mavericks i was able to fix my libusb errors
[Verizon Samsung Galaxy S 4] BabelDev:
Thanks surge. I first used Ubuntu on a virtual machine. Since I didnt progess, I tried it via Maverics. I installed, Xcode and brew.

While I get a libusb error in ubuntu I get a libusbx error in OSX. Now I ll try to figure out what u meant witg the macports. Thanks for the comment.
[Verizon Samsung Galaxy S 4] Surge1223:
oh now I see why it failed using the last script I uploaded...its using two different directories for Heimdall

/home/ubuntu/Heimdall and /root/Heimdall

open the script and close to the bottom try to find the line in bold and delete it. then save the script

cd ../

cd ../libusb-1.0

./autogen.sh

./configure

make

su -c 'make install'

echo "installing Heimdall from source..."

cd ../heimdall-frontend/

qmake-qt4 heimdall-frontend.pro

make

su -c 'make install'

cd ~/Heimdall

heimdall-frontend
[Verizon Samsung Galaxy S 4] BabelDev:
cd ../

cd ../libusb-1.0

./autogen.sh

./configure

make

su -c 'make install'

echo "installing Heimdall from source..."

cd ../heimdall-frontend/

qmake-qt4 heimdall-frontend.pro

make

su -c 'make install'

cd ~/Heimdall

heimdall-frontend

I deleted the part of the script as u advised. However doesnt seal the deal...still not working.
[Verizon Samsung Galaxy S 4] BabelDev:
So, finally I was able to flash the system.img.ext4 on the device. The screen shows now the Samsung Logo and an open lock saying "custom".

I installed, uninstalled and reinstalled different versions of Heimdall on OSX. The one that it was working with was the latest one, 1.4.0. I cant really tell why it finally worked, unfortunately.

Since I don't to mess around with it, I was wondering if some could tell me which other files I need to flash in order to get it up and running again. Thanks a thousand times for your support here.