Develop Bugs

rom cooking - unyaffs

I'm not daily Linux user but I'm usually savvy enough to figure things out; however unyaffs is giving me quite some trouble.
I have downloaded unyaffs from Lox's Rom cooking thread and placed it in the /bin/ folder but when I type /bin/unyaffs system.img I get "cannot get execute binary file". Help please?

did you chmod +x it?

kendong2 said:
did you chmod +x it?
Click to expand...
Click to collapse
No, didn't know I needed to. So now I have am getting "syntax error: ")" unexpected.
I am brand new to Rom cooking; sorry if this seems simple or stupid.

It needs to be in your computer's /bin/, not your phone's. Actually, it can be anywhere as long as it's on your $PATH. It's usually suggested that you create a /bin/ directory at your home folder (~) and then run all your personal binaries from there, then you can include that /bin/ in your .bashrc so that it gets loaded on every new terminal.
Open up a terminal window and do either
Code:
~$ gedit ~/.bashrc
or
Code:
~$ nano ~/.bashrc
depending on which editor you're comfortable with. Add the following to the end of your .bashrc
Code:
PATH=$PATH:/path-to-home/bin/
export PATH
where path-to-home is, ofcourse, the path to your home folder (usually /home/username), you can't use the ~ wildcard in the .bashrc script.
After you have your ~/bin set up, restart the terminal then move the unyaffs binary to ~/bin/ and then chmod a+x it, that way you can run the tool from any location.
To run the tool, just pass an image file as a parameter, note that the contents will be output to the directory where the image file is stored, so say I have a hero system file on my Desktop:
Code:
~$ cd ~/Desktop
~/Desktop$ mkdir HeroSystem
~/Desktop$ mv system.img HeroSystem
~/Desktop$ cd HeroSystem
~/Desktop/HeroSystem$ unyaffs system.img
end of file.
~/Desktop/Herosystem$_
The contents, along with the system.img will be in ~/Desktop/HeroSystem

Okay so added the following to bottom of my bashrc:
PATH=$PATH:/home/tito/bin/
export PATH
New terminal:
Code:
cd ~/bin
chmod a+x unyaffs
cd ~/Desktop/HeroSystem
unyaffs system.img
bash /home/tito/bin/unyaffs: cannot execute binary file
Followed all directions but still getting this error.

Found this site: hotrobots.blogspot.com/2009/07/useful-tool-unyaffs.html
Managed to unyaff my system.img; thanks for the help.

Hi, I am getting the "cannot execute binary file" error aswell..
I copied unyaffs in /bin and it is executable for everyone.
Yet and still it won't work. Any ideas?
Or do I really have to put unyaffs in a seperate bin folder and then edit bashrc?
Oh, and I'm running Mac OS X, if that's of any importance.. Bash is bash I think, or are there any differences I'm not aware of?

royalmitkaese said:
Hi, I am getting the "cannot execute binary file" error aswell..
I copied unyaffs in /bin and it is executable for everyone.
Yet and still it won't work. Any ideas?
Or do I really have to put unyaffs in a seperate bin folder and then edit bashrc?
Oh, and I'm running Mac OS X, if that's of any importance.. Bash is bash I think, or are there any differences I'm not aware of?
Click to expand...
Click to collapse
in this case you need the binary for osx, but the rest of the instructions should apply AFAIK (i have never used macos myself).

Thanks, but where can I get a binary for OSX?
The code.google.com page only offers one version of the binary..

royalmitkaese said:
Thanks, but where can I get a binary for OSX?
The code.google.com page only offers one version of the binary..
Click to expand...
Click to collapse
it is probably easier to compile it yourself...

download xcode from apple developer site for free
download source unyaffs from google site
and run gcc -o unyaffs unyaffs.c.
thats it ur done

Thanks for everyone's help. Almost done with my rom.

royalmitkaese said:
Thanks, but where can I get a binary for OSX?
The code.google.com page only offers one version of the binary..
Click to expand...
Click to collapse
I've attached version i compiled for OSX 10.6

jabbslad said:
I've attached version i compiled for OSX 10.6
Click to expand...
Click to collapse
sorry for reviving a dead thread but i was getting the "cannot execute binary file" so i used your attached compiled unyaffs and now i'm getting "Bad CPU type in executable"
I'm not registered on apple as a developer and can't download xcode :/

i'm getting "Bad CPU type in executable"
Click to expand...
Click to collapse
Are you running a 32 or 64 bit kernel on osx. You need a compile binary that is correct for your cpu. Let me know I will attach the right one in a reply. Check under apple menu >> about this mac >> more info >> software >> 64 bit kernel and extensions, yes or no.

anika200 said:
Are you running a 32 or 64 bit kernel on osx. You need a compile binary that is correct for your cpu. Let me know I will attach the right one in a reply. Check under apple menu >> about this mac >> more info >> software >> 64 bit kernel and extensions, yes or no.
Click to expand...
Click to collapse
@anika200 I'm also getting "Bad CPU type in executable". Mine is a 32bit one...
64-bit Kernel and Extensions: No
Could you please build one for 32bit kernel?

I got a hold of xcode (i love torrents ) and compiled it myself.
Heres the attached compiled OSX 32 bit unyaffs
Extract it and place it wherever you want, and to use it in another directory make sure you append it to your .bash_profile

Hey alright. You got it done before I could even check the thread again. I figured it was a 64 bit. Now we have both on here, nice.

Anyone familiar with doing this on windows?
I tried a couple of binaries, but i get errors.
Microsoft Windows XP [Version 5.1.2600]
C:\g2orgsys>unyaffs systemg2.img
28852 [main] unyaffs 3212 _cygtls::handle_exceptions: Exception: STATUS_ACCESS
_VIOLATION
30677 [main] unyaffs 3212 open_stackdumpfile: Dumping stack trace to unyaffs.e
xe.stackdump
348883 [main] unyaffs 3212 _cygtls::handle_exceptions: Exception: STATUS_ACCESS
_VIOLATION
375003 [main] unyaffs 3212 _cygtls::handle_exceptions: Error while dumping stat
e (probably corrupted stack)
Perhaps windows just sucks with this. I've never really used bash, but I got some LiveCDs around. :/

I use the attached file, works fine on windows. I think you need cygwin installed but not sure.

Ubuntu/Debian install for Slide

Ok so the ubuntu install now works on slide credit goes to eratosthene he updated all the files to make it work all other credit goes to the dev’s listed on the links provided. FYI this was tested on eugenes latest froyo rom.
1. Go to http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/ download the ubuntu.zip file .
2. Unzip to a location on your pc to a folder named ubuntu.
3. Download the ubuntu-slide-v2 from here.
4. Unzip the ubuntu-slide-v2 to the same folder you used in step 2.
5. Create a ubuntu folder on the root of your sdcard .
6. Connect your Slide to the pc verify debugging enabled and storage disabled.
7. Adb push the files in the ubuntu folder to the /sdcard/ubuntu.
8. Then adb shell.
9. cd /sdcard then sh ubuntu.sh
Note: At this point, the scripts are now located in /data/local/bin and the mount point is /data/local/mnt
10. sh /data/local/bin/bootubuntu
11. you should now see [email protected]:/#
Note : install completed only do the following if you want to access ubuntu from android vnc app.
12. apt-get update
13. apt-get install tightvncserver
14. export USER=root
15. vncserver -geometry 480x320
16. • Run the android-vnc-viewer app and specify localhost port 5901 .
UPDATE: This is not working on CM 6 , I'm not sure why please help if you know .

That would be sooooo coool
Sent From My HTC Espresso Running Froyo Thanks to eugene373

Tried it but the install fails , may be the script or may be rights to edit the files im not that good with linux yet so im not sure .

Ok thanks, any help would be apriciated . If we can get a procedure that works ill write up a step by step for everyone and maybe make a video how to also.

Just guessing but it's probably because we don't have rw access to /system.
Until we get an unlocked bootloader it ain't happenin...
I could be completely way off though

I think you are right , if i rember most the errors where do to access issue's with files in the system folder. If it is the bootloader what would need to be done to " unlock " it ?

bled82 said:
I think you are right , if i rember most the errors where do to access issue's with files in the system folder. If it is the bootloader what would need to be done to " unlock " it ?
Click to expand...
Click to collapse
An OTA update would unlock it.

So once we get the froyo ota we should be able to follow the same process as the nexus one then ?

i would say "unlikely," i dont see how an ota would unlock the bootloader in any fashion. but i guess he might have been referencing the possibility of someone using the new ota to create an unlocked bootloader. the whole "how could the bootloader be unlocked," question bothers me, i never seem to get a straight answer

aceraider4 said:
i would say "unlikely," i dont see how an ota would unlock the bootloader in any fashion. but i guess he might have been referencing the possibility of someone using the new ota to create an unlocked bootloader. the whole "how could the bootloader be unlocked," question bothers me, i never seem to get a straight answer
Click to expand...
Click to collapse
Once there is an official OTA devs will be able to extract the keys needed to properly sign files I believe.

I thought the engineering build had an unlocked boot loader on it and once we flashed it that was that ?

Here's an updated zip for you guys. The process is generally the same as on the above-linked nexus one version, I just changed the scripts to move a few files to different places. You'll need to download ubuntu.zip from that post as well. Summary:
unzip ubuntu.zip somewhere
unzip ubuntu-slide.zip in the same place, replace all the files
make a directory called 'ubuntu' on your sdcard
adb push all the files in the zip to that directory
adb shell
cd /sdcard/ubuntu
sh ubuntu.sh
At this point, the scripts are now located in /data/local/bin and the mount point is /data/local/mnt
sh /data/local/bin/bootubuntu
You're now chrooted into the ubuntu install. Have fun.

Thanks going to try it now !!!

Does not work get attached error.

bled82 said:
Does not work get attached error.
Click to expand...
Click to collapse
I haven't tried this but based on your error, try this from the shell:
mkdir /data/local/bin
then run the ubuntu.sh again

falken98 said:
I haven't tried this but based on your error, try this from the shell:
mkdir /data/local/bin
then run the ubuntu.sh again
Click to expand...
Click to collapse
I did cd /data/local then ls and bin is listed , ran mkdir /data/local/bin failed file exists . i cant cd /data/local/bin get error cant cd to /data/local/bin

bled82 said:
I did cd /data/local then ls and bin is listed , ran mkdir /data/local/bin failed file exists . i cant cd /data/local/bin get error cant cd to /data/local/bin
Click to expand...
Click to collapse
This is some other script messed up when bin wasn't there and ended up creating a file called bin instead of it being a directory.
rm /data/local/bin
mkdir /data/local/bin

falken98 said:
This is some other script messed up when bin wasn't there and ended up creating a file called bin instead of it being a directory.
rm /data/local/bin
mkdir /data/local/bin
Click to expand...
Click to collapse
Ok getting closer , Thank you very much . Now when i ran sh .data/local/bin/bootubuntu i get error attached .

bled82 said:
Ok getting closer , Thank you very much . Now when i ran sh .data/local/bin/bootubuntu i get error attached .
Click to expand...
Click to collapse
What rom are you using? It looks like you don't have the ext3 module built into your kernel. I set my scripts up to use ext3 (more reliable, I really don't care that it eats into the life of my sd card), but many roms only have ext2. You might try uncommenting the first line of bootubuntu, and changing the ext3 to ext2 on line 10.

eratosthene said:
What rom are you using? It looks like you don't have the ext3 module built into your kernel. I set my scripts up to use ext3 (more reliable, I really don't care that it eats into the life of my sd card), but many roms only have ext2. You might try uncommenting the first line of bootubuntu, and changing the ext3 to ext2 on line 10.
Click to expand...
Click to collapse
I am running froyo using Kanged CM6 newbuild.zip from eugene373 , http://forum.xda-developers.com/showthread.php?t=721515 .

[GUIDE] Beginner guide how to make your ROM *.img from Linux OS !!!

First you must to install yaffs!!!
Download attached archive and unpack it to /usr/sbin/ folder with your File Manager or Terminal window. I preffered File Manager, it is simpliest way.
After copyed mkfs.yaffs2 and unyaffs, you must to change permissions on these two files.
Open Terminal if you don`t previously opened and write...
[email protected]_name:~$ sudo nautilus
Nautilus is File Explorer on Ubuntu Linux. On other Linux distribution you may have other File Explorer. Anyway... open it with sudo command.
Enter your root password and navigate to /usr/sbin folder.
Find these two files mkfs.yaffs2 and unyaffs.
Right click mouse on it then click to see "Properties".
In properties tab you will see "Permissions" tab.
Click on it and set "read and write" option for all users and group in this tab then close window and Terminal.
You can change permission in the Terminal window with this command if you want...
[email protected]_name:~$ sudo chmod 667 /usr/sbin/mkfs.yaffs2
[email protected]_name:~$ sudo chmod 667 /usr/sbin/unyaffs
This is it for install mkfs.yaffs2 and unyaffs.
After that, create new folders on your desktop named as "newrom".
Copy system.img from ROM instalation folder to newrom folder and run unyaffs.
Open terminal and type... Only type BOLD text.
[email protected]_name:~$ cd /home/your_name/Desktop/newrom
[email protected]_name:~/Desktop/newrom$ unyaffs /home/your_name/Desktop/newrom/system.img
Wait unyaffs to uncompress all files and folders from system.img
When unyaffs has been completed uncompress procedure, you will see something like that...
end of image
[email protected]_name:~/Desktop/newrom$
Close terminal window if you want to close.
Open folder newrom and delete system.img file. Folder "newrom" contains everything from your system.img file. You may to change, delete or something else to create your new Android build. Yes you may to be ROM cookers.
After your intervention on files and many other stuff in your "new rom", you will be prepare to create your new "system.img" file.
This process must to be in other folder with diference name. Not to be in same folder where is your previous uncopressed folders and files. In my case this folder is "newrom".
Folder for new "system.img is my Desktop.
Ok, let see what we must to do... In case when you previous closed Terminal window, you must be placed on Desktop uses CD command in Terminal.
[email protected]_name:~$ cd Desktop
You must see this...
[email protected]_name:~/Desktop$
Enter this...
[email protected]_name:~/Desktop$ mkfs.yaffs2 newrom/ system.img
And you must see this...
mkfs.yaffs2: Android YAFFS2 Tool,Build by PowerGUI
at http://www.openhandsetalliance.org.cn
Building...
Build Ok.
[email protected]_name:~/Desktop$
After that you will see new system.img on your Desktop.
For boot.img file, procedure is same except name of *.img file.
That`s it. I hope that is help.
Thanks to everyone who helped me to write this guide.
Enjoy.
FileFixer.

so much thanks. i'll have a try~

Ignore this

I have extracted the files in to the directories as suggested but when I run the command to extract the system.img I get access is denied. I have tried this as my standard user account and logged on as root any ideas?
Edit: modified the permissions on the two files I dumped in to sbin and resolved the issue!

Yes... If you don`t permission you can login as root and change rigts on this two files.
In my case i just copy these two files in /usr/sbin folder and everything work fine.
This is, maybe i think,for per user mod.
I would be to edit thread for this problem...

Works very well very nice thread man. I was able to fully extract the img file from a gingerbread build and play arround with it and rebuild it cheers!

Pictures or video's?

You will be free to create them. I have no much time for this. if you try my procedure step by step, you can learn something...

@FileFixer
Maybe you could also post a way for us to edit the initrd.gz files in the rom builds, so we can make some changes that are necessary for SD builds to work with MAGLDR "AD SD" option ourselves?
Thanks, Santroph.

Unpack initrd.gz on your desktop and open cpio archive. Inside is a few scripts and few elf files.
I am not developer but i will trying to learn more about this.

Pretty useful tutorial i will try that soon.

FileFixer said:
Unpack initrd.gz on your desktop and open cpio archive. Inside is a few scripts and few elf files.
I am not developer but i will trying to learn more about this.
Click to expand...
Click to collapse
Cool guide did you have any help you would like to credit

No, i don`t have any help about this. I just playing with some files.

FileFixer said:
No, i don`t have any help about this. I just playing with some files.
Click to expand...
Click to collapse
KillaHurtz said:
Cool guide did you have any help you would like to credit
Click to expand...
Click to collapse
hehe
(10 chars)

When I use the command unyaffs /home/your_name/Desktop/newrom/system.img I get an error open image file failed.
Why is this not working for me?
...
Never mind, it worked!
Very useful topic!

Yo MUST be placed in to your "newrom" folder before start unyaffs command.
[email protected]_name:~$ cd /home/your_name/Desktop/newrom
then type this...
[email protected]_name:~/Desktop/newrom$ unyaffs /home/your_name/Desktop/newrom/system.img
Only type BOLD text.
Never mind, it worked for you!

After repack - no root
I did unpack and repack system.img according this guide (without any changes - only for testing). After flash the ROM works fine, but is not rooted. Original ROM is rooted.
Why? I didn't make any changes in unpacked system.img.
Can anyone help me with this, please?
Thanks.

I think that you must set permissions to all before pack img file.

santroph said:
@FileFixer
Maybe you could also post a way for us to edit the initrd.gz files in the rom builds, so we can make some changes that are necessary for SD builds to work with MAGLDR "AD SD" option ourselves?
Thanks, Santroph.
Click to expand...
Click to collapse
Hi,
Here's a quick howto
* mkdir initrd-temp
* cp initrd.gz initrd-temp
* cd initrd-temp
* gunzip initrd.gz -c | cpio --extract --make-directories
* rm initrd.gz
* Make your changes
* find .|cpio -H newc -o|gzip -9 -c - > ../initrd.gz
I hope that helps

Hey,
thanks for this useful thread!
I have problems in this whole process of booting a custom rom ( in my case Miui) in the Emulator . I have compiled the whole rom on a Linux VM with your Guide and pushed it in a Windows system into android-9/images/system.img but it won't boot I don't know what I am doing wrong. My system.img is 2 GB big I think this is not normal. if i am replacing the system.img with the original out of the emulator, it is booting. I just want to boot the Miui rom to port some features to Cyanogenmod... Thanks in advance. I have a HTC Legend btw .

[Q] Mac equivalent to flashtool?

Is there a Mac equivalent to FlashTool?

I also have the same question.

Hi there mmzubair!
In the end the best solution I found was just to install windows XP with bootcamp! Or if your Macs newer than mine (using a 4 year old Mac Mini) you could install XP using parallels so you don't have to rebooting every time you want to flash your phone!
Sent from my R800i using Tapatalk 2

I'm wondering if you can install and run flashtool with Wine?
Sent from my R800x using Tapatalk 2

beez1717 said:
I'm wondering if you can install and run flashtool with Wine?
Sent from my R800x using Tapatalk 2
Click to expand...
Click to collapse
I believe you can't because wine can't install driver software.

flashtool linux
the flashtool site explains a method of installing it on linux based systems, but it all sounds gibberish to me (because im a noob) and i cannot understand it, has anybody done this? please explain in pure english if possible. thank you.

Flashtool on Mac instructions
!! UPDATE, ALL
There is a flashtool for mac on androxyde's github.
Basically...
You need (in this order):
1/ Xcode, Download and install it from App store/your mac's supplied DVD/Apple developer website
> If using version 3 and earlier, make sure the "UNIX Development", "System Tools", "Command Line Tools", or "Command Line Support" is selected during the installation process,
> If using version 3 and earlier, Apple's Command Line Developer Tools are found at the Apple Developer Connection site
2/ MacPorts, See section 2 on http://www.macports.org/install.php.
Then:
3/ Download and unzip flashtool from androxyde's github
More prep work for the USB stuff:
4/ Open Terminal and type/run code:
Code:
ls -la /opt/local/lib/libusb-1.0.dylib
If "no file or directory" found then run code:
Code:
sudo port install libusb
Now, to run Flashtool (ASSUMING YOU DID NOT RENAME THE FLASHTOOL FOLDER AND PROGRAM NAME SINCE UNZIP!):
5/ Open Terminal and type/run code:
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib; */Flashtool/FlashTool;
or
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib; ~/Downloads/Flashtool/FlashTool;
Alternatively:
> Open up the "Flashtool" Unix Executable File in TextEdit
> Copy and paste
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
the the line directly underneath export OS=$(uname -s)
> Save it, and from now on, double click the FlashTool executable file to open flashtool
6/ Flashtool window should pop up and a smile appears on your face
Maintenance
7/ To update MacPorts and installed ports, open terminal and run:
Code:
sudo port -v selfupdate; sudo port -v upgrade outdated;

Themindbuddah said:
Is there a Mac equivalent to FlashTool?
Click to expand...
Click to collapse
J0YU said:
There is a flashtool for mac on androxyde's github.
Basically...
You need (in this order):
1/ Xcode, Download and install it from App store/your mac's supplied DVD/Apple developer website
2/ MacPorts, See section 2 on http://www.macports.org/install.php.
Then:
3/ Download flashtool from androxyde's github
More prep work for the USB stuff:
5/ Open Terminal and type/run code:
Code:
ls -la /opt/local/lib/libusb-1.0.dylib
If "no file or directory" found then run code:
Code:
sudo port install libusb
6/ Last line of code to run in Terminal for prep:
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
Now run Flashtool:
7/ Open the Flashtool folder which you unzipped in 3/
8/ Double click on "Flashtool" (Unix Executable File)
Hopefully that helps, haven't tried it out personally because I'm too lazy for 1/ and 2/ but reply/thanks if it works out fine!
Maintenance
9/ To update MacPorts, open terminal and run:
Code:
sudo port -v selfupdate
Click to expand...
Click to collapse
That's right there is a FlashTool Mac Edition check it out: http://androxyde.github.com/

Thanks for the post. The LD_LIBRARY_PATH variable was the key for me. With the 2 mods for steps 6 & 8 in bold, these directions worked on my MacBook Air. FlashTool now comes up and runs!
-- Cronin
6/ Last line of code to run in Terminal for prep:
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
Becomes:
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
​
Now run Flashtool:
7/ Open the Flashtool folder which you unzipped in 3/
8/ Double click on "Flashtool" (Unix Executable File)
Becomes:
go to your FlashTool folder
Code:
cd ../FlashTool
​execute the FlashTool:
Code:
- ./Flashtool
​

J0YU said:
There is a flashtool for mac on androxyde's github.
Basically...
You need (in this order):
1/ Xcode, Download and install it from App store/your mac's supplied DVD/Apple developer website
2/ MacPorts, See section 2 on http://www.macports.org/install.php.
Then:
3/ Download flashtool from androxyde's github
More prep work for the USB stuff:
5/ Open Terminal and type/run code:
Code:
ls -la /opt/local/lib/libusb-1.0.dylib
If "no file or directory" found then run code:
Code:
sudo port install libusb
6/ Last line of code to run in Terminal for prep:
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
Now run Flashtool:
7/ Open the Flashtool folder which you unzipped in 3/
8/ Double click on "Flashtool" (Unix Executable File)
Hopefully that helps, haven't tried it out personally because I'm too lazy for 1/ and 2/ but reply/thanks if it works out fine!
EDIT: check out the post below for more info/stuff
Maintenance
9/ To update MacPorts, open terminal and run:
Code:
sudo port -v selfupdate
Click to expand...
Click to collapse
I followed this guide and tried the other variation but when i launch flashtool this happen:
Macbook:~ Suz$ /Users/Suz/Downloads/FlashTool/FlashTool ; exit;
Exception in thread "main" java.lang.UnsatisfiedLinkError: Unable to load library 'usb-1.0': dlopen(libusb-1.0.dylib, 9): image not found
at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:179)
at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:252)
at com.sun.jna.Library$Handler.<init>(Library.java:140)
at com.sun.jna.Native.loadLibrary(Native.java:368)
at com.sun.jna.Native.loadLibrary(Native.java:353)
at se.marell.libusb.jna.LibUsb.<clinit>(LibUsb.java:11)
at se.marell.libusb.LibUsbSystem.<init>(LibUsbSystem.java:36)
at se.marell.libusb.LibUsbSystem.<init>(LibUsbSystem.java:73)
at linuxlib.JUsb.init(JUsb.java:38)
at gui.FlasherGUI.main(FlasherGUI.java:170)
logout
[Processo completato]
nothing else! Where am I doing wrong?

smayor said:
I followed this guide and tried the other variation but when i launch flashtool this happen:
Macbook:~ Suz$ /Users/Suz/Downloads/FlashTool/FlashTool ; exit;
Exception in thread "main" java.lang.UnsatisfiedLinkError: Unable to load library 'usb-1.0': dlopen(libusb-1.0.dylib, 9): image not found
at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:179)
at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:252)
at com.sun.jna.Library$Handler.<init>(Library.java:140)
at com.sun.jna.Native.loadLibrary(Native.java:368)
at com.sun.jna.Native.loadLibrary(Native.java:353)
at se.marell.libusb.jna.LibUsb.<clinit>(LibUsb.java:11)
at se.marell.libusb.LibUsbSystem.<init>(LibUsbSystem.java:36)
at se.marell.libusb.LibUsbSystem.<init>(LibUsbSystem.java:73)
at linuxlib.JUsb.init(JUsb.java:38)
at gui.FlasherGUI.main(FlasherGUI.java:170)
logout
[Processo completato]
nothing else! Where am I doing wrong?
Click to expand...
Click to collapse
i have the same problem can someone help me?

currently trying to diagnose it, I got the same problem too xD

The problem is that instead of */Flashtool/Flashtool you should replace before * with the the path from root to the file.
On my system this was:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib; /Users/<username>/Downloads/Flashtool/FlashTool;
Was getting same error and then it loaded
edit--
In fact, just open FlashTool in text wrangler or another editor and paste this in:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
after line:
export OS=$(uname -s)
save that and it should work. I did this, then I got an app got Platypus and wrapped the whole thing into a .app file. I'd upload it but it is 80 megs and I have a quarter meg upload rate
You could probably put that jar on the same path as the other files and it would find it, and save others going through the other steps but I'm not sure. I've not had time to try.

brim4brim said:
The problem is that instead of */Flashtool/Flashtool you should replace before * with the the path from root to the file.
On my system this was:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib; /Users/<username>/Downloads/Flashtool/FlashTool;
Was getting same error and then it loaded
edit--
In fact, just open FlashTool in text wrangler or another editor and paste this in:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
after line:
export OS=$(uname -s)
save that and it should work. I did this, then I got an app got Platypus and wrapped the whole thing into a .app file. I'd upload it but it is 80 megs and I have a quarter meg upload rate
You could probably put that jar on the same path as the other files and it would find it, and save others going through the other steps but I'm not sure. I've not had time to try.
Click to expand...
Click to collapse
oops, did the unix wildcard " * " not work on your machine? yeah it's either that or
Code:
~/Downloads/Flashtool/FlashTool
should also work. Thanks for the heads up, might update my tutorial more to cover more stuff and maybe release a moded FlashTool executable, I'm not sure

J0YU said:
oops, did the unix wildcard " * " not work on your machine? yeah it's either that or
Code:
~/Downloads/Flashtool/FlashTool
should also work. Thanks for the heads up, might update my tutorial more to cover more stuff and maybe release a moded FlashTool executable, I'm not sure
Click to expand...
Click to collapse
I hope you guys can help, I tried using the methods you gave (exporting the var and updating the file in textwrangler) but I'm still getting the error below. Would you know how to get around this?
I checked and I do have the file:
Users-iMac:FlashTool user$ ls -la /opt/local/lib/libusb-1.0.dylib
lrwxr-xr-x 1 root admin 18 May 12 00:25 /opt/local/lib/libusb-1.0.dylib -> libusb-1.0.0.dylib
Error below:
Last login: Sat Nov 3 00:47:57 on ttys001
Users-iMac:~ user$ /Users/user/Downloads/FlashTool/FlashTool ; exit;
Exception in thread "main" java.lang.UnsatisfiedLinkError: Unable to load library 'usb-1.0': dlopen(libusb-1.0.dylib, 9): image not found
at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:179)
at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:252)
at com.sun.jna.Library$Handler.<init>(Library.java:140)
at com.sun.jna.Native.loadLibrary(Native.java:368)
at com.sun.jna.Native.loadLibrary(Native.java:353)
at se.marell.libusb.jna.LibUsb.<clinit>(LibUsb.java:11)
at se.marell.libusb.LibUsbSystem.<init>(LibUsbSystem.java:36)
at se.marell.libusb.LibUsbSystem.<init>(LibUsbSystem.java:73)
at linuxlib.JUsb.init(JUsb.java:38)
at gui.FlasherGUI.main(FlasherGUI.java:170)
logout
[Process completed]
---------- Post added at 01:21 AM ---------- Previous post was at 01:02 AM ----------
Somehow, double clicking on FlashTool gives me that error... But doing a ./FlashTool in the terminal works. Thanks!
Would you guys happen to know if a Mac version of the rooting toolkit is available?

Somehow, double clicking on FlashTool gives me that error... But doing a ./FlashTool in the terminal works. Thanks!
Would you guys happen to know if a Mac version of the rooting toolkit is available?
Click to expand...
Click to collapse
Are you talking about ADB and FlashTool for mac?
Or like the actual rooting stuff like Superuser.apk and BusyBox (root_tools.rar in the attached files)?

Use wine
Sent from my R800x using xda app-developers app

problems with libusb
Hi guys,
thank you so much for this guide,
I have a problem when i try to open flash tool with the
Code:
~/Downloads/Flashtool/FlashTool
this error shows up
Minimum libusb version is 1.0.14. Found 1.0.9
It can be downloaded on
i have tried everything and i really cannot updated :crying::crying:
Please help me i never done it before

Java 1.6 or 1.7
Hi!
Whenever I try to run the commands, I get the following error message:
"Java version must be 1.6 or 1.7"
I have the latest version of Java installed on my Mac, and I can actually see the Java icon from the Control Panel. Any ideas about the error I get?
Thanks!

Hi!
Whenever I try to run the commands, I get the following error message:
"Java version must be 1.6 or 1.7"
I have the latest version of Java installed on my Mac, and I can actually see the Java icon from the Control Panel. Any ideas about the error I get?
Thanks!
Click to expand...
Click to collapse
1// What version of Mac OS X are you running on?
2// What do you get when you run java -version in terminal?
Hi guys,
thank you so much for this guide,
I have a problem when i try to open flash tool with the
Code:
~/Downloads/Flashtool/FlashTool
this error shows up
Minimum libusb version is 1.0.14. Found 1.0.9
It can be downloaded on
i have tried everything and i really cannot updated
Please help me i never done it before
Click to expand...
Click to collapse
I'm looking into it...
btw are you trying to run flashtool version v0.9.9.0 or an older one?
I written the tutorial a while ago lol

[TUT][NOOB FRINDLY] Building Flashable On Device Rom-Kernel

Hello Guys
Iam Guiding you today to build your on device rom most Of u can do it but i belive somebudy doesn't know That is Noob Frindly Guide
Requirements
Code:
1-PC
2-Winrar/7zip
oR Root Explorer on Mobile
Part A (Rom Building)
METHOD1
Step1
Code:
Reboot To Recovery
Step2
Code:
Make Nandroid Backup
Step3
Code:
Open Your pc and connect via usb
Step4
Code:
Bull Your clockworkmod folder to pc
Step5
Code:
Extract Templete rom.zip attached below
Step6
Code:
Navigate to your cwm backup
Step7
Code:
Extract System(..).tar
Step8
Code:
Copy The files u extracted (inside system folder u extracted) To Template rom/ System/
[B]NOTE:DONT COPY WHOLE SYSTEM FOLDER - JUST ITS COMPONENTS[/B]
Step9
Code:
Go to Template Rom Folder Select Meta-inf
and system
then add them to new Archive with .zip extintion
Step10
Code:
Flash your rom and enjoy
METHOD 2
Code:
1. Go to treminal emulator
2. Type these commands dont copy that >"
[CODE]
1."su"
2."tar -c system/* >> sdcard/system.tar"
3.navigate to your sd root
4.extract system.tar
5.put its components to template rom>system (like method 1)
6.Enjoy
[/CODE]
Part B (On Device Kernel Packing)
Step 1
Code:
Follow Steps Up From 1-6
Step 2
Code:
Get Boot.img and put it in the root of zip attached (Kernel Template)
Credits
Myaservip
Marcussmith2626

you can also type in terminal emulator
su
tar -c system/* >> sdcard/system.tar
wait until the command promp returns (may take 5 mins so make sure screen timeout is set to at least 15mins to make it easier for you to keep an eye on it without the screen keep turning off)
once done you will have a file called system.tar on the root of your sd card
you can then load this file in android kitchen which is useful for deodexing
or you can just extract it and all your system files will be there to do with as you like - eg put in a flashable zip
note the above requires the following
root
terminal emulator (playstore)
busybox installed (get installer from playstore if not already installed)
my method in spoiler above added to op

How about my data.rfs.tar? Will I Flash again my Tweak on Phone, after reflashing the ROM backup?

U can push them by adb or wait untill i make data script

When I Flash my ROM Backup, It stucks on black screen But Heard the Boot Sound not the animation display.

Try fix premisions

I will update my template if it worked
Or u might deleted my fix premision binary
Be aware dont replace/delete it to avoid bootloops/breaks

myaservip said:
I will update my template if it worked
Or u might deleted my fix premision binary
Be aware dont replace/delete it to avoid bootloops/breaks
Click to expand...
Click to collapse
I'll Try again. *Report Later.