mmh, I'm not very used to Gdebi. I usually don't use it. So I had to read a bit in uBuntu forums. Now I uninstalled nbhCreator and reinstalled it. I get to choose the output folder, but he output actually get on the desktop folder and is simply nmed froyo (no date stamp).
As I previously installed the new version without uninstalling the previous one, it may be possible that using synaptic to uninstall doesn't work completly and correctly.
I'll try to find a way to completly remove all nbhcreator remains before reinstalling one. this might be tricky if I really mess up using Gdebi.
maybe try uninstalling new version... then re-install old version... then "completely remove" old version... then reinstall new version.
that's exactly what I think the problem is. But I didn't save the previous version. Do you have a link to where you keep the old version (sourceforge ? )
As for my strange issue, I tried to rename the zimage file I use (it is named zimage-froyo). I still get a file called froyo on desktop. If I choose a donut android version, I get 'froyo' either... 8°
Could it be that I use a localized (french) uBuntu setup. (could be confusing the software depending how it is made, but I doubt it)
I really think the problem comes from me messing up with gdebi...
I confirm it works fine when the zimage is on the desktop and the output folder is the desktop. It's also working with the zimage and the output.nbh in any folder that is not on the desktop (meaning that don't have the desktop in its pathname).
I'm going to flash my phone
Well, I don't think there's a lack of interest in your job, simply it works.
Well, I don't think there's a lack of interest in your job, simply it works.
Now for a question that may be out of the subject. If I'd like to change the key mapping, is it the Zimage that have to be changed ? If so, may be would it be possible to add it to NBHCreator option...
Actually I have noticed that some tools are like that, they work so well that the author does not receive much feedback, since 90% of the time feedback is in the form of bug reports or support questions.
/home/armalota/.nbh/work/tinboot.s: Assembler messages:
/home/armalota/.nbh/work/tinboot.s:92: Error: attempt to move .org backwards
/usr/share/nbhcreator/bin/arm-2010q1/objcopy: '/home/armalota/.nbh/work/tinboot.o': No such file
cat: /home/armalota/.nbh/work/tinboot: No such file or directory
NBMerge 2.1rc2
Executing Z:\usr\share\nbhcreator\bin\kitchen\NBMerge.exe with data chunk size = 0x800 and extra chunk size = 0x8
on file /home/armalota/.nbh/work/output.nb
Partition 0: start sector: 0x00000002, total: 0x000005be
first used: 0x00000002, used: 0x000005be
Partition 1: start sector: 0x000005c0, total: 0x00000000
first used: 0x000005c0, used: 0x00000000
Partition 2: start sector: 0x000005c0, total: 0x00000040
first used: 0x000005c0, used: 0x00000007
Partition 3: start sector: 0x00000600, total: 0x00000000
first used: 0x00000600, used: 0x00000000
Checking /home/armalota/.nbh/work/output.nb for bad NAND block marker
-------> Found BAD BLOCK marker! <------
Do not flash this file!
Sector: 0x601
All extra bytes:
0x0000
0x0000
0x0000
0x0000
0x0000
0x0000
0x0000
0x0000
=== yang v1.1: Yet Another NBH Generator
=== (c) 2008 Pau Oliva Fora - pof @ XDA-Developers
[] Output NBH file: /home/armalota/appinstall/vogue-kernel//VOGUIMG.NBH-9-8-2010_13.48.32
[] Input files: /home/armalota/.nbh/work/output.nb
[] Input types: 0x400
[] SignMaxChunkSize: 64
[] Device: VOGU100
[] CID: 11111111
[] Version: 1.0.MARTIN
[] Language: WWE
[] 0x400 --> /home/armalota/.nbh/work/output.nb
Done!
Having trouble with NBH creator on Kubuntu 10.04.1
The big problem is that with most recent kernel builds, I'm not able to package everything: