Hello,
I'm developing my own ROM using the "XDA ROM Kitchen". However once Clicking "Build Rom" I obtain the error "All workspaces are busy now. Try again in 20 seconds or so..." I will list my setup.
------------------------------------------------
OS: SuSE Linux 10.0.0.42
kernel-default-2.6.16_rc1_git3-4
kernel-source-2.6.16_rc1_git3-4
kernel-syms-2.6.16_rc1_git3-4
------------------------------------------------
Webserver
XAMPP for Linux 1.5.1
Includes:
Apache 2.2.0
MySQL 5.0.18
PHP 4.4.1
PHP 5.1.1
Perl 5.8.7
Install directory = #/opt/lampp/
------------------------------------------------
RomKitchen date = 04/01/2005
Install directory = #/opt/lampp/htdocs/kitchen_template/
Rom used = 3.17.03ENG
MKROM date = 04/01/2005
Run locally via
"localhost/kitchen_template/"
I select any adequate options, and select build rom (tested on all three options) and error "All workspaces are busy now. Try again in 20 seconds or so..." Is displayed.
The Rom directory structure is as follows:
'/opt/lampp/htdocs/kitchen_template/'
'/opt/lampp/htdocs/kitchen_template/data'
'/opt/lampp/htdocs/kitchen_template/download'
'/opt/lampp/htdocs/kitchen_template/kitchen.local'
'/opt/lampp/htdocs/kitchen_template/workspace'
'/opt/lampp/htdocs/kitchen_template/workspaces'
The ROM location is as follows:
'/opt/lampp/htdocs/kitchen_template/data/00_Select your Base ROM/3.17.03 ENG O2-Euro/_/cfg/rom.nb1'
------------------------------------------------
Could anyone please help me evaluate the problem and perhaps correct this? such as after install configurations. I would greatly appreciate it also share my kitchen once complete.
Thanking in advance
John
*bump*
Hello,
Still no avail with this problem, I descovered php5 is not compatible and php4 fixes many issues, yet still no fix for the 20 second error.. please anyone?
John
Shadow_relm said:
However once Clicking "Build Rom" I obtain the error "All workspaces are busy now. Try again in 20 seconds or so..."
Click to expand...
Click to collapse
check the workspace directory. There have to be write access by you apache user, and it has to be empty. This error normally cames when it isn´t possible to create a workspace, or all workspaces are in use....
Stefan
LumpiStefan said:
Shadow_relm said:
However once Clicking "Build Rom" I obtain the error "All workspaces are busy now. Try again in 20 seconds or so..."
Click to expand...
Click to collapse
check the workspace directory. There have to be write access by you apache user, and it has to be empty. This error normally cames when it isn´t possible to create a workspace, or all workspaces are in use....
Stefan
Click to expand...
Click to collapse
Thankyou Works fine now , all i got to do is alter a few things, is it posible to obtain the WMP10 files and include into this rom? If not that is cool.
John
Hello,
Sorry, The error still appears now its constatly again. and i am incapable of compiling roms. any suggestions?
thankyou
Re: Hello,
Shadow_relm said:
Sorry, The error still appears now its constatly again. and i am incapable of compiling roms. any suggestions?
thankyou
Click to expand...
Click to collapse
Update, I can now creat NK.nb1 and NK.nbf files with the kitchen, the files flash perfectly and flawlessly. Yet when running installer EXE it displays the usual..
Creating ROM... Please be patient.
Copying ROM files
Why not using the time for donating? ;-)
Running mkrom
Your ROM is done. (click here to view the log)
But uppon downloading the rom its only 200-500kb the logg says as follows
no files for configid 26220739 2620749 27202 20404 20408 20412 23410write xip block starting at 81800000, with 27 fileswrite xip block starting at 81980000, with 0 filesthis rom seems to be 3.17.03 ENG 2003-05-15 o2eurothis bootloader seems to be V5.22 2003-05-15 17:46:5580000000 - 80040000 -- bootloader 0 files 1 modules80040000 - 8026a804 -- kernel 13 files 11 modules802c2000 - 8057d330 9 OS 15 files 32 modules80580000 - 8075a69c 8 SHELL 79 files 27 modules80780000 - 80a13b04 7 BROWSING 9 files 14 modules80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules80dc0000 - 80ebd150 5 SYNC 12 files 22 modules80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules81080000 - 81348248 3 24MCONSUMER 69 files 1 modules81400000 - 814019a4 -- xip chain 10 xip entries81440000 - 817f6f14 1 MISC 209 files 40 modules81800000 - 8189ec94 10 XDA_DEVELOPERS1 27 files 0 modules81900000 - 81925800 -- bitmap : 101a301a .. beb6fc8d81940000 - 81944000 -- operator rom 0 files81980000 - 81981054 11 XDA_DEVELOPERS2 0 files 0 modules../rom.exe: found a preamble of 31232 bytes adding: English/NK.nbfzip I/O error: No space left on devicezip error: Output file write failure (write error on zip file)
Related
I got a XDA new ROM which is 4.00.01. It's a BIN file. 32 MB. I don't know how to flash it. Anyone has ideas?
What's the exact size in bytes?
I have seen .bin files which start with the string 'B000FF'
you can use
Code:
perl splitrom.pl yourfile.bin -wo outfile.nb1 -t nb1
to convert it to nb1.
you can find splitrom.pl in the mkrom distribution archive.
splitrom understands several types of romimages.
Can I convert to NBF file? So that I can use PROGRAM A to install. Size is 33,555,995 bytes. It start with B000FF.
you must make sure there is either a bootloader in your .bin file,
or you get a bootloader from another source.
you can extract a bootloader from another nbf file using
Code:
perl splitrom.pl yournbf.nbf -wl bootloader.nb0
you must make very sure that your nbf really contains a bootloader, if it doesn't and programme a overwrites it with junk, you will have your self a brand new hightech paperweight.
a safer way to burn unknown images, is via an sd card + xdarit + bootloader mode.
What is the command to convert to NBF once I got the bootloader? When I try to extract the bootloader, I got the following message: "80000000 - 80040000 -- bootloader 0 files 1 modules". Does that mean no bootload information inside the NBF file?
that means you are looking at a file containing just a bootloader, no OS.
Code:
perl splitrom.pl yourfile.bin -rl bootloader.nb0 -wo outfile.nbf -t nbf -n PW10A1-ENG-3.17-001
to convert .bin + bootloader to .nbf
you can check the result again using
Code:
perl splitrom.pl outfile.nbf
Sorry about having so many questions. How can I make sure that the nbf really contains a bootloader? I use the NBF file from O2 UK RUU 3.17.03 to extract bootloader which under PROGRAM A folder. Can I use "perl splitrom.pl yourbin.bin -wl bootloader.nb0" to
extract the bootloader from my BIN file? I use UltraEdit to view the BIN file, I notice some information about bootloader 5.22 (not 5.17). The person give me this ROM said it's the PPC 2003 final. Actually I was given a HTC tool to flash the BIN file. But when I load the bin file, it checks my SD card and tells me invalid card. So I cannot flash directly.
well, that is a difficult question. in an ideal world we would have ready a list of bootloaders, and md5sums of these. for easy idendification. but not done that yet. su currently I look at the binary. and see if I see this line in the hexdump:
0000060: 4543 4543 0010 0a8c 0000 0000 0000 0000 ECEC............
and at about 0001580 there should be some lines with '*' and 'init debugserial...'
then it at least resembles something that looks like a bootloader, and not accidentally an os image. ( yes, that is a mistake we made fore you, leading us to abother intersting development : jtag flashing
5.22 is the latest I saw too.
so does your .bin file start with 'b000ff' ? can you maybe upload this file to
ftp://xda-developers.com ?
actually we noticed that somehow for recent roms the bootloader was not flashed by programme A. even though we managed to overwrite it with crap with one of our own experiments. possibly a different version of programme A. we have not researched this yet.
I would be interested in that htc program too.
you can only extract a bootloader from your .bin file if it contains one. .bin files may contain any memory region. so I don't know if yours does.
I saw the following information. So I believe it has bootloader.
0000060: 4543 4543 0010 0a8c 0000 0000 0000 0000 ECEC............
about 0001580 there should be some lines with '*' and 'init debugserial...'
I've done the following. I don't know if I'm right.
1. I run "perl splitrom.pl yourfile.bin -wl bootloader.nb0 -t nb0" to extracted the bootloader.
2. Run "perl splitrom.pl yourfile.bin -wo outfile.nb1 -t nb1" to extract OS.
3. Run "perl splitrom.pl yourfile.bin -rl bootloader.nb0 -wo outfile.nbf -t nbf -n PW10A1-ENG-4.00-001" to get NBF file. I got error message said romimage already has bootloader. So I run "perl splitrom.pl yourfile.bin -wo outfile.nbf -t nbf -n PW10A1-ENG-4.00-001" to convert to NBF file directly. I dont' know if this the right command to convert BIN to BNF file, but I didn't see any error.
4. I run "perl splitrom.pl outfile.nbf" to check and below is the result.
rommap: 80000000-81f00000
no xipchian found
no operator rim found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8015c5c8 -- kernel 5 files 5 modules
80180000 - 80376bd0 -- kernel 10 files 14 modules
80380000 - 8064306c -- kernel 20 files 36 modules
80670000 - 80be66a8 -- kernel 107 files 88 modules
80c80000 - 8102ce98 -- kernel 11 files 36 modules
81050000 - 813ef114 -- kernel 95 files 44 modules
81400000 - 815d2238 -- kernel 34 files 7 modules
815f0000 - 8171bc7c -- kernel 56 files 19 modules
817c0000 - 81adf390 -- kernel 109 files 40 modules
81980000 - 81925800 -- bitmap :30000be5 .. 010000ea
I tried to upload the file to your FTP. But no permission. Please PM your MSN Messenger ID, so that we can discuss more baout this ROM.
Thanks
I don't have msn, but you can find me on irc in #xda-developers on ircnet
( if you don't know a server: irc.nl.uu.net )
3: yes, that should work.
if you want to replace the exsisting bootloader, you can type "perl splitrom.pl outfile.nb1 -rl bootloader.nb0 -wo outfile.nbf -t nbf -n PW10A1-ENG-4.00-001"
4: ah, ppc2003 roms have a different structure splitrom cannot yet find
the xipchain in its new location. that is why it says 'kernel' on all lines.
also the bitmap it mentions is not the bitmap.
another issue may be that the nbf it creates has the wrong size, since
the xipchain in ppc2003 roms is in a location which was not originally
present in nbf files, I am not sure if programme a can write it correctly.
forgot to tell you the password: user=xdaftp pass=xdaftp
Replacing a corrupted bootloader via ActiveSync
I have a T-Mobile PPC Phone on which I have installed the AT&T radio stack and the XDA-Developers 1.1 ROM. All works well except for the fact that I appear to have corrupted the bootloader. The device now jumps directly into Windows CE and ignores any keys which I press when performing a soft reset.
From reading the rest of this thread it seems that I may be able to replace my corrupted bootloader via ActiveSync if I prepare an image file correctly. Is this true, or am I misunderstanding the ActiveSync upgrade process? As I can't reload from SD card, I'd be grateful for some expert advice before I go ahead - I can't afford to get it wrong!
Thanks,
Malcolm
Hi,
I've already upload the PPC2003 for XDA to your FTP. Please check your private message for the password for the ZIP file.
Thanks
Hello, there!
Today I was trying desperately to burn a custom version of the most recent German O2 ROM 3.19.01. For my experiments I used the freshly downloaded NK.nbf from http://www.o2online.de/o2/business/datenloesungen/xda/downloads/
setup.sh yields this ROM layout:
Code:
80000000 - 80040000 -- bootloader
80040000 - 8026dc78 -- kernel
802c2000 - 8057ef30 9 OS
80580000 - 8076118c 8 SHELL
80780000 - 80a15254 7 BROWSING
80a40000 - 80d948ac 6 COREAPPS
80dc0000 - 80ebd640 5 SYNC
80ec0000 - 81039258 4 24MAPPS
81080000 - 81348690 3 24MCONSUMER
81400000 - 81401484 -- xip chain
81440000 - 81833fb0 1 MISC
81900000 - 81925800 -- bitmap
81940000 - 81e3dcd7 -- operator rom
As one can see the MISC section reaches beyond the barrier of 0x8180000 where the ROM tools put the contents of the 'files1' subdirectory in a section called 'XDA_DEVELOPERS1'.
So I adjusted the appropriate variable in the shell scripts (namely 'start1') to 0x81833fb1 and the size accordingly.
However, when I try to run mkrom.sh afterwards I get this error message:
Code:
this rom seems to be 3.19.01 GER 2003-05-27 o2euro
this bootloader seems to be V5.22 2003-05-15 17:46:55
xip regions not found: 81833fb1=XDA_DEVELOPERS1
Error creating new rom
As far as I was able to find out it's splitrom.pl which issues this message. I think splitrom tries to extract the XDA_DEVELOPERS1 section from the original cfg/rom.nb1 image -- which of course does not contain no such section.
This makes me believe I've missed some important step in building a custom ROM.
Any hits would be greatly appreciated.
Christian, who's running the kitchen on a Win32 CygWin system
I don't take the responsibility for any damage caused by the information included.
This is not my intention to reveal any secrets of HTC Company. All this information was known earlier. I've just collected it in one place and used it for repairing my broken HTC device.
Although it was successfully tested on Herald from Dopod, it should work on any Herald and as far as I know this is the only hope, especially for Heralds with low SPL number, broken by flashing with HardSPL
If you find this tutorial useful, do it on your risk.
I've spent a lot of time in searching of a solution for my bricked Dopod C858. It has been bricked after Hard-SPL by Olipro. When this Hard-SPL was first introduced, there wasn't any warnings about minimum SPL and GSM versions requirements. That's why there is a lot of people with their Heralds stuck in the bootloader mode without a possibility of successful flashing in any way.
One of the symptoms was Invalid Update Tool 300 Error when I was trying to flash even with the official RUU. The other symptom was "GetDeviceCID: Error - InitDecoder" when getdevinfo command was typed at MTTY console.
Finally I was able to recover from this state. I successfully created the goldcard - a micro SD card with the special header, which gives us a temporary SuperCID status (security level 0). In this way we are able to flash the new ROM via SD card, instead of using the official RUU (ROM Update Utility). If it is not enough to flash successfully, we can use a wonderful service tool included in Herald's diagnostic image (heradiag.nbh).
All the credits goes to "itsme" and his hard work. It wouldn't be possible without his knowledge, his help and his great software. Willem agreed to make this tutorial and share this knowledge on the forum.
Thank you Willem!
I would also like to thank "pof" for his effort and although he couldn't find a solution, he tried to help me, so thank you Pau!
The other person I would like to thank is "canonyang_China". I know he is accused of stealing Olipro's ideas of Hard-SPL. I only want to thank him for posting heradiag.nbh file. This is the great tool which together with the goldcard can do a lot.
I would also like to mention one person. It's "jockyw". He has almost identical solution but he has found it by himself. If you find this tutorial too hard to deal with I recommend to contact "jockyw" and he will help you for a small paypal donation.
TUTORIAL:
***********************************************************
Requirements (not tested on other configurations):
1) Windows XP with SP3
2) ActiveSync 4.5
3) ActivePerl 5.8.8.822
4) Crypt-DES and XdaDevelopers-NbfUtils PERL packages
5) typhoonnbfdecode.pl PERL program
6) itsutils tools
7) working mobile device with any Windows mobile OS (2003, 5.0, 6.0)
8) any .nbh ROM file from the official Herald's RUU
9) heradiag.nbh file
10) micro SD card (tested on 512MB and 1GB)
Ad.2) download your language verion of ActiveSync and install it:
Ad.3) download and install MSI installer of ActivePerl 5.8.8.822 from http://www.activestate.com
http://www.activestate.com/store/download_file.aspx?binGUID=e5c71329-b7a6-4563-8199-e1483f751c4f
Ad.4) run Perl Package Manager from Windows Start Menu
change PPM Preferences (run Preferences from the Perl Package Manager menu and switch to the repository tab):
- Add repositories:
Name: itsme
Location: http://www.xs4all.nl/~itsme/projects/perl/ppm
- Add repository:
Name: theoryx
Location: http://theoryx5.uwinnipeg.ca/ppms/package.xml
After database synchronization install those packages (at the main window of Perl Package manager find those packages, mark them for install (the icon with green plus, next to the search bar) and run marked action(green arrow icon)):
-Crypt-DES
-XdaDevelopers-NbfUtils
If you can't find those packages on your list, please make sure you have selected "All packages" from "View" menu in Perl Package Manager main window.
Ad.5) download typhoonnbfdecode.pl from http://www.nah6.com/~itsme/cvs-xdadevtools/xda2nbftool/
Save it to "C:\itsutilsbin"
Ad.6) download itsutilsbin package from http://www.xs4all.nl/~itsme/projects/xda/tools.html. Unpack it to "C:\itsutilsbin"
http://nah6.com/~itsme/itsutilsbin-20080602.zip
Ad.7) Find a working Windows mobile device and use it to format your micro SD card as FAT32. It's important to do this on working mobile device with any Windows mobile OS (2003, 5.0, 6.0) because PC USB card readers causing troubles with making a goldcard because of a different MBR interpretation.
- Activesync your working Windows mobile device with SD card inside
- On your PC enter windows command mode (Start->Run... cmd)
- Choose your itsutilsbin directory (cd C:\itsutilsbin),
- Run this command (l means a letter 'el' - not a digit 'one'):
psdread -l
If you have problems with running psdread -l you probably have problems with the security configuration of your mobile device. There are many options to change it. In my case I was using Device Security Manager PowerToy for Windows Mobile 5.0
It is recommended to save your security configuration, then change it to the Security Off level and after the whole goldcard preparation process, load saved configuration preset if you don't want to leave your Windows mobile device Security Off. You should have your mobile device ActiveSync with your PC when you are using this tool.
- If everything went OK, look at the result at the cmd window after psdread -l and find something like that:
remote disk 1 has 1984000 sectors of 512 bytes - 968.75Mbyte
SerialNr: 75 63 00 49 8a f2 00 80 47 31 30 55 53 44 53 03
- in the next step you will have to replace the first byte ( in this case '75' ) with '00' and write this ID without spaces between numbers - this will be your modified cardid
In this example your modified cardid will be 006300498af200804731305553445303
(Thank you "hookcard" for reporting troubles in this step)
Run this command, where <cardid> is your modified cardid:
perl typhoonnbfdecode.pl -p cardid=<cardid> -p keys=tornado -p seclevel=0 -d goldcard.img
- Your goldcard image will be saved in your current directory (C:\itsutilsbin)
- If you have error message connected with msvcr71.dll file, please download this file or try to find it somewhere on your system partition and then copy it to the directory containing typhoonnbfdecode.pl (C:\itsutilsbin)
Then repeat the previous step with running typhoonnbfdecode.pl
If everything went OK, run this command, where <number> is a number under which you have your SD card during psdread -l command, for example, "remote disk 1 has 1984000 sectors of 512 bytes - 968.75Mbyte" means that your <number> is 1:
psdwrite -<number> goldcard.img 0 0x120
Now you have a card which gives you SuperCID - you can test it with MTTY and see that g_cKeyCardSecurityLevel = 0
Ad.8) Remember to have more than a half of the battery capacity available before you start this step!
- download any official Herald's RUU and extract it to the directory, where you should find RUU_signed.nbh ROM file. (It was tested with Dopod's ROM). Copy this .nbh file to your goldcard changing its name to heraimg.nbh
- Enter the bootloader mode. When you will see on your Herald's screen the question: "Update SD image?" you will have 10 seconds to press Volume Down button and this way to start flashing
Unfortunatelly, if something will go wrong and i.e. you will see SD update failed you will have to use heradiag.nbh file to enter special menu during the start of the bootloader mode. If you have problems with flashing, please read the step below:
Ad.9) download and unpack heradiag.zip file from this thread:
http://forum.xda-developers.com/showthread.php?t=332413&highlight=heradiag.nbh&page=6
Remember to have more than a half of the battery capacity available before you start!
- Copy heradiag.nbh on your goldcard together with any official .nbh ROM from ROM Update Utility from the previous step.
- boot your Herald in bootloader mode and you will see the diagnostic menu where you will have Reflash Image option. Choose Reflash Image and after the flashing process (about 5 minutes) please softreset your device.
That's all! You should see your Herald properly booting Windows OS.
Good luck!
Anyone had any luck with this?
I tried.
Everything is O.K.
ok first of all thank you very much for as a hope gain to bring our herald to live again.
but there is some point at this thread i didnt get it so plz if u could help me
1-
run Perl Package Manager from Windows Start Menu
change PPM Preferences:
- Add repository: itsme http://www.xs4all.nl/~itsme/projects/perl/ppm
- Add repository: theoryx http://theoryx5.uwinnipeg.ca/ppms/package.xml
After database synchronization install those packages (mark them for install and run marked action):
-Crypt-DES
-XdaDevelopers-NbfUtils
what is crypt -des
and when i open the link (add rep.by itsme )
there is too many files to download.
which one is that files u mean
i download them all but it seems they work on linux not in windows
so plz if u make that point more clear or at least post some pictures..
2-
does any official room will work .or it must be the exact cid room.
I've updated this tutorial and now it should be more clear.
According to your question about the ROMs - if you successfully create the Goldcard you will be able to flash any ROM, not only those matching your original CID.
halder said:
...............
what is crypt -des
and when i open the link (add rep.by itsme )
there is too many files to download.
which one is that files u mean
i download them all but it seems they work on linux not in windows
so plz if u make that point more clear or at least post some pictures..
2-
does any official room will work .or it must be the exact cid room.
Click to expand...
Click to collapse
how come i cant find XdaDevelelopers-NbfUtils package?
i have added the repository correctly.
i can see from the status screen:
Synchronizing Database ...
Downloading ActiveState Package Repository packlist ... done
Updating ActiveState Package Repository database ... done
Downloading itsme packlist ... redirect
Downloading itsme packlist ... done
Downloading itsme Win32-API-0.41WJ PPD ... done
Downloading itsme XdaDevelopers-CompressUtils PPD ... done
Downloading itsme XdaDevelopers-NbfUtils PPD ... done
Downloading theoryx packlist ... not modified
but i just can find the module (ie. XdaDevelopers-NbfUtils)
i have also tried the command line installation but no luck..
anyone??
maybe someone can post the perl folder, with the required modules installed?
Do you have "All Packages" chosen through View Menu?
klikman said:
how come i cant find XdaDevelelopers-NbfUtils package?
i have added the repository correctly.
i can see from the status screen:
Synchronizing Database ...
Downloading ActiveState Package Repository packlist ... done
Updating ActiveState Package Repository database ... done
Downloading itsme packlist ... redirect
Downloading itsme packlist ... done
Downloading itsme Win32-API-0.41WJ PPD ... done
Downloading itsme XdaDevelopers-CompressUtils PPD ... done
Downloading itsme XdaDevelopers-NbfUtils PPD ... done
Downloading theoryx packlist ... not modified
but i just can find the module (ie. XdaDevelopers-NbfUtils)
i have also tried the command line installation but no luck..
anyone??
Click to expand...
Click to collapse
Hi there! I also have a bricked Herald. I'm in Brazil and a store wants around 200 US dollars to fix the phone and it's too high.
I saw that the file itsme XdaDevelopers-NbfUtils PPD has just a text indicating an e-mail adress.
I saw in another site that this file has another content.
May be this is why we cannot find the package to install.
If i find a way to fix my Herald here i will do a very good donate!!
Thanks,
Alencar
alencarfr said:
Hi there! I also have a bricked Herald. I'm in Brazil and a store wants around 200 US dollars to fix the phone and it's too high.
I saw that the file itsme XdaDevelopers-NbfUtils PPD has just a text indicating an e-mail adress.
I saw in another site that this file has another content.
May be this is why we cannot find the package to install.
If i find a way to fix my Herald here i will do a very good donate!!
Thanks,
Alencar
Click to expand...
Click to collapse
Go to this thread, it will explain how to fix your phone....
http://forum.xda-developers.com/showthread.php?t=345411
Hi Mkoz,
Tried your procedure but when start bootloader it do not read the SDcard. I copied Heradiag to the card but it do not run. The bootloader remains the same as before.
No Signal. With MTTTy I gave the command set 32 1 and get the message:
================================================
+ SD Controller init
- SD Controller init
+StorageInit
SDInit+++
PL_SDSetSlotNumber() - MPUIO_SDIF_SEL1=0, MPUIO_SD_IF_SEL=0
SDCmd8 Command response time-out. MMC_STAT = 80
SDCmd8 Command response time-out. MMC_STAT = 80
SDCmd8 Command response time-out. MMC_STAT = 80
SDInit - SD ver1.0
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SD clock to 24MHz
***** user area size = 0x79280000 Bytes
SDInit---
SDInit OK
Unlimited time!
GetDeviceCID: Error - InitDecoder
g_cKeyCardSecurityLevel = 0
HTCE
=======================================================
So, please could you help me ? Thanks! Alencar
Hi,
Where did you format your SD card before preparing Goldcard? In Windows Mobile device or in laptop or PC card reader?
alencarfr said:
Hi Mkoz,
Tried your procedure but when start bootloader it do not read the SDcard. I copied Heradiag to the card but it do not run. The bootloader remains the same as before.
g_cKeyCardSecurityLevel = 0
So, please could you help me ? Thanks! Alencar
Click to expand...
Click to collapse
Hi Mkoz,
I formatted using Pocketmechanics in my HTC universal in mode FAT32.
I'm really looking forward to see the mobile working.
Thanks!! Alencar
please SIR how can i change cardid ?
and witch tool i use ?
Hi,
I've sent you my private message but you haven't answered so I have to ask you in this thread:
- What is the size of your SD card? I successfully tested it with 512MB and 1GB cards.
alencarfr said:
Hi Mkoz,
I formatted using Pocketmechanics in my HTC universal in mode FAT32.
I'm really looking forward to see the mobile working.
Thanks!! Alencar
Click to expand...
Click to collapse
Sucessfully tested with 2gb card
BTW, HardSPL'd devices doesn't want to load heradiag!
i can see from the status screen:
Synchronizing Database ...
Downloading ActiveState Package Repository packlist ... done
Updating ActiveState Package Repository database ... done
Downloading itsme packlist ... redirect
Downloading itsme packlist ... done
Downloading itsme Win32-API-0.41WJ PPD ... done
Downloading itsme XdaDevelopers-CompressUtils PPD ... done
Downloading itsme XdaDevelopers-NbfUtils PPD ... done
I found -Crypt-DES but not found -XdaDevelopers-NbfUtils
Please help me! Thanks
same here
already try restarting my windows still no luck
I guess you are doing something wrong because there are people who were successful with this tutorial. Maybe you don't have "All packages" chosen from the menu.
I have updated point 4 of my tutorial so please take a look.
I've also posted in this thread my answer to someone who had the same problem like you and he didn't answered anymore so I guess as a result he created Goldcard successfully.
If it will help you, please let us know.
TINDUNG10 said:
i can see from the status screen:
Synchronizing Database ...
Downloading ActiveState Package Repository packlist ... done
Updating ActiveState Package Repository database ... done
Downloading itsme packlist ... redirect
Downloading itsme packlist ... done
Downloading itsme Win32-API-0.41WJ PPD ... done
Downloading itsme XdaDevelopers-CompressUtils PPD ... done
Downloading itsme XdaDevelopers-NbfUtils PPD ... done
I found -Crypt-DES but not found -XdaDevelopers-NbfUtils
Please help me! Thanks
Click to expand...
Click to collapse
please help me delete 1 post
hello everyone, im using ervius kitchen 1.8.2
and getting error while compiling rom after picking all packages on executing
kitchen_build_rom.bat
ERROR: errorlevel:1
im running xpsp2, net3.5
can anyone help me with that?
rom is official, of course
this error appears on every compilation, even right after dumping official rom
aZzz.bZzz said:
hello everyone, im using ervius kitchen 1.8.2
and getting error while compiling rom after picking all packages on executing
kitchen_build_rom.bat
ERROR: errorlevel:1
im running xpsp2, net3.5
can anyone help me with that?
rom is official, of course
this error appears on every compilation, even right after dumping official rom
Click to expand...
Click to collapse
oh have u added new sources and new build...
if yes then check netcf and wince_nls must be in sys>shared>common
then still persist let us know....
yes, im trying to update build 21887 to 23549 and yes, both packages exist and included
NetCF and WinCENLS_WWE
aZzz.bZzz said:
hello everyone, im using ervius kitchen 1.8.2
and getting error while compiling rom after picking all packages on executing
kitchen_build_rom.bat
ERROR: errorlevel:1
im running xpsp2, net3.5
can anyone help me with that?
rom is official, of course
this error appears on every compilation, even right after dumping official rom
Click to expand...
Click to collapse
Open kitchen_build_rom.bat in the 'tools' folder of your kitchen with a text editor:
Search for this lines:
Code:
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
REM **************** TOOLS\platformrebuilder.exe
if not "%errorlevel%"=="0" goto error
And change it to be like this:
Code:
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
REM **************** TOOLS\platformrebuilder.exe
REM **************** if not "%errorlevel%"=="0" goto error
take care
YES, it works, thank you, dotcompt
I'm with this error on x1 kitchen:
Processing "AudioFilterTable.csv" as file
Processing "AudioPara.csv" as file
Processing "AudioPara3.csv" as file
Processing "AudioPara3_Boot.csv" as file
Processing "AudioPa
ERROR! (errorlevel: -1073741819)
ERROR executing: kitchen_build_rom.bat
ERROR!!!
Wait some seconds...
No ''SVN'' folders present...
Restored Original config.txt...
Temp config.txt Deleted!!!
Somebody know why?
I'm creating a cooked rom based on the stock rom ita LT9 4.1.2, you can change the battery in the status bar without Xposed? I would include the circular battery with percentage inside. decompiling an apk? which one?
stefano_te said:
I'm creating a cooked rom based on the stock rom ita LT9 4.1.2, you can change the battery in the status bar without Xposed? I would include the circular battery with percentage inside. decompiling an apk? which one?
Click to expand...
Click to collapse
I think it's enough that you throw it into the SystemUI.apk(have a look inside that apk, if it's not there then it is in secframework.apk) (/res/.../XHDPI). Open the apk in winrar (you might have to rename it from .apk to .zip) and drag and drop the new files. Decompiling isn't necessary for this sort of thing.
Also, check this out:
http://forum.xda-developers.com/showthread.php?t=1918500
I did this a long time ago so some of what I just said might be wrong, if you need more help then just say so.
I would like to use as a basis the stock rom 4.1.2 : N7000XXLT9_N7000ITVLT3_ITV.zip
I used the kitchen to create workfolder following all the steps suggested by the program , I found the following problems:
1 ) during the procedure appeared to me the following warning :
Warning : A valid boot.img is not found . You have the option to add a
' fake ' boot.img So THAT the features of the kitchen can still
function normally.
This boot.img will be automatically removed from your ROM 's
ZIP file When Is It built .
Add boot.img (y / n)? (default: y) "
is this normal? how to solve ?
2 ) Working folder information ( v)
Android OS version: 4.1.2
Device: GT- N7000
Model: GT- N7000
ROM Name : JZO54K.N7000XXLT9
CSC version: It 's normal that there is nothing written here ?
Rooted ( Superuser app + su) : NO
Rooted ( unsecured boot.img ) : UNKNOWN how I fix this ?
BusyBox installed : NO
BusyBox run-parts support: UNKNOWN UNKNOWN how I fix this ?
Apps2SD (Apps to EXT) enabled: NO
/ data / app enabled: NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support: NO
/ system / framework is deodexed : NO
/ system / app is deodexed : NO
modem.bin found: YES
ROM will wipe all data : NO
3) throughout the META-INF folder there are only 2 files: update-script; update-script.bak
4) scripts / get_api_level: line 18: more: command not found
5) I checked the update-script and there are 3 warning in the report:
7/101: copy_dir PACKAGEystem SYSTEM:
8/101: format PRELOAD:
>> WARNING: Partition not recognized
9/101: copy_dir PACKAGEreload PRELOAD:
>> WARNING: PRELOAD: not found in working folder
10/101: symlink dumpstate SYSTEM:bin/dumpcrash
11/101: symlink toolbox SYSTEM:bin/cat
82/101: set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
83/101: run_program PACKAGE:create_preload_symlinks
>> WARNING: create_preload_symlinks not found in working folder
84/101: set_perm 0 3003 06755 SYSTEM:bin/ip
How do I resolve this? I tried a lot of on-line but have not found anything. My goal is to make me a custom rom from the last stock (LT9) ... what should I do?
Check my old tutorial I used myself when cooking Custom Roms for the N7000 with the kitchen. Following the steps should avoid most problems.
ThaiDai said:
Check my old tutorial I used myself when cooking Custom Roms for the N7000 with the kitchen. Following the steps should avoid most problems.
Click to expand...
Click to collapse
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue?
Please wait ...
scripts/choose_rom: line 110: more: command not found
Enter selection number (default=1, cancel=0, r=refresh):
is a problem? I can go on with 1 (default)?
stefano_te said:
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue?
Please wait ...
scripts/choose_rom: line 110: more: command not found
Enter selection number (default=1, cancel=0, r=refresh):
is a problem? I can go on with 1 (default)?
Click to expand...
Click to collapse
Sorry, but only repeating the problems you actually have won't solve anything because it isn't really clear what you did before.
The error here seems to be a hint that your cygwin installation isn't correct.
So please try to follow the steps in my tutorial exactly. Start from scratch.
ThaiDai said:
Sorry, but only repeating the problems you actually have won't solve anything because it isn't really clear what you did before.
The error here seems to be a hint that your cygwin installation isn't correct.
So please try to follow the steps in my tutorial exactly. Start from scratch.
Click to expand...
Click to collapse
It works. I have re-installed windows ...
can you tell me how to add new info in device info? (rom name, rom maker, release date, build version ...)
stefano_te said:
It works. I have re-installed windows ...
can you tell me how to add new info in device info? (rom name, rom maker, release date, build version ...)
Click to expand...
Click to collapse
No. Because you do this partly when using the kitchen step by step. Or when changing your updater-script.
The kitchen is a great help and simplifies cooking a rom - but it still is a little bit more complicated than heating baby food in the microwave. And if you really want your "custom" rom you should start to learn what happens in each step. And this can't be done by revealing everything...