Jeff's Kitchen message means what? - MDA, XDA, 1010 Software Upgrading

Anybody could kindly explain to me the following message received after cooking a rom:
Creating ROM... Please be patient.
Copying ROM files
Running mkrom
Warning: shell_exec(): Unable to execute '/usr/local/bin/bash ./mkrom.sh rom.exe 2>&1' in /home/jsummers/public_html/ROMkitchen/processor.php on line 100
Warning: system(): Unable to fork [rm -rf /home/jsummers/public_html/ROMkitchen/download/zhyyqiip] in /home/jsummers/public_html/ROMkitchen/processor.php on line 106
Your ROM is done. (click here to view the log)
Is my ROM correct or should I try again?
THX
Gear

Try again, I would say...

XDA developer Peter Poelman said:
Try again, I would say...
Click to expand...
Click to collapse
Second try was clear....
THX
Gear

Related

[HSPL/SSPL][DISCUSSION] Hacking SPL [SSPL works - now flashing HSPL/closed testing]

Well this is just my second HTC device.. But has anybody ever wondered why information on creating HardSPL and stuff is seeded sparely? We're just waiting until olipro, cmonex (bless their work!!! ) or some other mod finishes the Hard-SPL.
If this is an illegal talk or something then just delete my thread..
I find this is an interesting topic.. So why not colaborate with each other and report status on this, so that we eventually could hack something together..? At least for the sake of interest.. I ever liked hacking embedded devices, but my knowledge in these things is not so good. Would like to dig more into this and solve this kind of mystery
I have found interesting bits of information at the following places:
http://wiki.xda-developers.com/index.php?pagename=Wizard_ROM_Layout
http://forum.xda-developers.com/showthread.php?t=334667
http://www.xs4all.nl/~itsme/projects/xda/tools.html
http://wiki.xda-developers.com/index.php?pagename=SPL%20Questions%3F
http://forum.xda-developers.com/showthread.php?t=501871
The first step seems to be extracting the stock SPL.. I read something about pmemmap, a tool to show the memory map of the phone and pmemdump, a tool to dump memory areas of the phone to disk.
This rises the question of how to find out the address, where the SPL lies in our LEOs and then how to dump it?
If there are any constructive comments on this, everybody is invited to add his thoughts here, or point out the right way
Update:
SPL seems to be dumped, credits go to cmonex. - Now it's time to investigate further steps. Currently looking into it.
Okay.. You can read the SPL from your LEOs with the following command:
pmemdump 0x8ff00000 0x80000 dump.bin
But i have attached it here for your convenience.
Update 2:
For all those people that are curious about the technical background behind SPL hacking i am giving an update of my research now (of course cmonex will finish that work, and she will do it good, but as you probably know, i want to get into that kind of stuff):
I managed to get an MFG SPL (the SPL that isn't shipped with stock ROMs and that is used by HTC to debug) now. This type of SPL is needed to do any further steps regarding flashing Hard-SPL.
This may not be complete or even correct, so if you have any information to add, please share it with us.
As far as i understood the rough procedure now would be to relocate the SPL and its .data section in RAM (that means all the data referenced by code) to a new address. This is needed because the address where the SPL and its data section lie now is protected by the MPU (Memory Protection Unit?), which is set up by the radio bootloader, which is running on another CPU (the ARM9). Every write there will lead to nowhere and as our SPL would execute, it would crash, because of missing data. This is why we need to relocate our SPL to a new address by changing all the hard coded references to data (such as strings etc.) in code.
I need someone to comment on the process of changing all the hard coded addresses to another one. I don't know how to do it yet.
If this is done and all code runs well (there could be further glitches, such as the NAND write/read issue - please comment on that) we would use JumpSPL to load our SPL in RAM into an unused address and execute it. This would give us all the tools needed for flashing HSPL.
I have attached a copy of the MFG SPL i obtained (if this is against any rules, please remove it) together with an analysis in IDA32, which i just made (for the lazy ones).
It would be nice, if we could get some further info here.
Btw.: I found this funky stuff on the PSAS forum. It is a tool that actually simulates an ARM processor and let's you step through the instructions. Really nice, if you want to understand what's going on.
If you want to flash another language ROM to your HTC device you can go here. Please don't use this thread for such requests. Let's keep it about SPL talking. Thanks
Thanks to share this information with the comunity.
Feel free to investigate and and have a go for it.
The itsme utils are extremely useful,
You could also read the posts from Pof, Des, jockeyw2001 regarding this subject.
After you got your SPL, you can read Jockyw2001's posts regarding bootloaders dissembling in IDA pro.
The actual patching of the SPL isn't the hardest part, Cmonex once told that the development of the Soft SPL was trickiest part.
Regards, and good luck.
EqX
Thank you.. I will have a go for it, when i have more time. It's over for today..
Very interesting thread. I would like to know how they are trying to hack the SPL. With due respect to Olinex, we rely on them but there must be also people around who can give a hand to accelerate the process. No ?
on a related note i tried to make my hd2 supercid without using QMAT so that i could flash wwe official rom...
i followed these steps and i got to Ad.7) part where i needed to run this command:
perl typhoonnbfdecode.pl -p cardid=<cardid> -p keys=tornado -p seclevel=0 -d goldcard.img
when i hit enter i get this message:
C:\itsutilsbin>perl typhoonnbfdecode.pl -p cardid=0085007b9394eb0000000000000000
00 -p keys=tornado -p seclevel=0 -d goldcard.img
Can't locate XdaDevelopers/NbfUtils.pm in @INC (@INC contains: C:/Perl/site/lib
C:/Perl/lib .) at typhoonnbfdecode.pl line 81.
BEGIN failed--compilation aborted at typhoonnbfdecode.pl line 81
if anybody can point me to the right direction or tell me what am i doing wrong i would be very grateful.
mr.vandalay said:
on a related note i tried to make my hd2 supercid without using QMAT so that i could flash wwe official rom...
i followed these steps and i got to Ad.7) part where i needed to run this command:
perl typhoonnbfdecode.pl -p cardid=<cardid> -p keys=tornado -p seclevel=0 -d goldcard.img
when i hit enter i get this message:
C:\itsutilsbin>perl typhoonnbfdecode.pl -p cardid=0085007b9394eb0000000000000000
00 -p keys=tornado -p seclevel=0 -d goldcard.img
Can't locate XdaDevelopers/NbfUtils.pm in @INC (@INC contains: C:/Perl/site/lib
C:/Perl/lib .) at typhoonnbfdecode.pl line 81.
BEGIN failed--compilation aborted at typhoonnbfdecode.pl line 81
if anybody can point me to the right direction or tell me what am i doing wrong i would be very grateful.
Click to expand...
Click to collapse
Did you install activeperl ?
yes , however now i see that packages Crypt-DES and XdaDevelopers-NbfUtils are not installed and i can't find them...
i select "all packages" but i can't find those two, and i tried by adding repositories but it doesn't download anything.
can i somehow add them manually?
mr.vandalay said:
yes , however now i see that packages Crypt-DES and XdaDevelopers-NbfUtils are not installed and i can't find them...
i select "all packages" but i can't find those two, and i tried by adding repositories but it doesn't download anything.
can i somehow add them manually?
Click to expand...
Click to collapse
You need to use the exact version of ActivePerl as stated on that page and you must use Windows.
You should also know that you cant use this goldcard image for your LEO with the typhoon option. This is for another HTC device.. If you look into that pl file you see that there is no entry for LEO. We need the LEO key.
I replied to your PM about dumping SPL 0x95000000
mr.vandalay said:
on a related note i tried to make my hd2 supercid without using QMAT so that i could flash wwe official rom...
i followed these steps and i got to Ad.7) part where i needed to run this command:
perl typhoonnbfdecode.pl -p cardid=<cardid> -p keys=tornado -p seclevel=0 -d goldcard.img
when i hit enter i get this message:
C:\itsutilsbin>perl typhoonnbfdecode.pl -p cardid=0085007b9394eb0000000000000000
00 -p keys=tornado -p seclevel=0 -d goldcard.img
Can't locate XdaDevelopers/NbfUtils.pm in @INC (@INC contains: C:/Perl/site/lib
C:/Perl/lib .) at typhoonnbfdecode.pl line 81.
BEGIN failed--compilation aborted at typhoonnbfdecode.pl line 81
if anybody can point me to the right direction or tell me what am i doing wrong i would be very grateful.
Click to expand...
Click to collapse
sorry this will never work on Leo. I can make the goldcard for you though (for a small donation)
Thanks a lot cmonex, for your PM, hope to flash my Holand device onto a WWE device to better understud.
just wondering, based on this, is it possible for me to flash my o2 branded device with the stock wwe rom?
Tung_meister said:
just wondering, based on this, is it possible for me to flash my o2 branded device with the stock wwe rom?
Click to expand...
Click to collapse
Yes, it should be
umh... I can't dump... I'm wondering ...why?
If I enter "pmemdump 0x95000000 0x80000 spl.nb" I get a 0bytes file, but if I don't enter the file name I'm seeing the errors that it gets.
Anyway, this is what I'm getting:
Code:
G:\itsutilsbin>pmemdump.exe 0x95000000 0x80000
ERROR: ITReadProcessMemory - Invalid access to memory location.
95000000: * * * * *
ERROR: ITReadProcessMemory - Invalid access to memory location.
ERROR: ITReadProcessMemory - Invalid access to memory location.
ERROR: ITReadProcessMemory - Invalid access to memory location.
ERROR: ITReadProcessMemory - Invalid access to memory location.
ERROR: ITReadProcessMemory - Invalid access to memory location.
ERROR: ITReadProcessMemory - Invalid access to memory location.
ERROR: ITReadProcessMemory - Invalid access to memory location.
Someone can help?
kholk said:
umh... I can't dump... I'm wondering ...why?
If I enter "pmemdump 0x95000000 0x80000 spl.nb" I get a 0bytes file, but if I don't enter the file name I'm seeing the errors that it gets.
Anyway, this is what I'm getting:
Someone can help?
Click to expand...
Click to collapse
You're not the only one. Currently working it out with cmonex.
just wanna say that cmonex helped me and i just flashed wwe rom on my german hd2
mr.vandalay said:
just wanna say that cmonex helped me and i just flashed wwe rom on my german hd2
Click to expand...
Click to collapse
Welcome to the club of dutch rom refugees
cmonex helped me and i just finish to flash my NEW WWE ROM.
Thank you mate.
To all who want to flash now, be in touch with this guy, he is going to help you really fast.
cidriver said:
cmonex helped me and i just finish to flash my NEW WWE ROM.
Thank you mate.
To all who want to flash now, be in touch with this guy, he is going to help you really fast.
Click to expand...
Click to collapse
She.. She's female!

[SOLVED] problem compiling rom in ervius kitchen

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?

Trying to make an update.zip for Titanium Backup... what's wrong ?

Hi all,
I'm trying to make an update.zip for users to install my app easily in recovery mode. It sounds trivial, and should basically just copy the apk into /data/app/.
Before I sign it, the zip contains (as shown by "unzip -t"):
Code:
data/app/com.keramidas.TitaniumBackup.apk
META-INF/com/google/android/update-script/update-script
The update-script is as follows:
Code:
show_progress 0.1 0
copy_dir PACKAGE:data DATA:
show_progress 0.1 10
Then I signed the update.zip with:
jarsigner -verbose -keystore my_keystore update.zip my_key
When I launch:
jarsigner -verify update.zip
I get "jar verified".
But in Clockwork recovery, my update.zip does not work - and signature verification is disabled, afaik.
EDIT: I have uploaded the update.zip there:
http://matrixrewriter.com/android/files/update.zip
Any ideas ?
Thanx in advance for any help
joel.bourquard said:
Hi all,
I'm trying to make an update.zip for users to install my app easily in recovery mode. It sounds trivial, and should basically just copy the apk into /data/app/.
Before I sign it, the zip contains (as shown by "unzip -t"):
Code:
data/app/com.keramidas.TitaniumBackup.apk
META-INF/com/google/android/update-script/update-script
The update-script is as follows:
Code:
show_progress 0.1 0
copy_dir PACKAGE:data DATA:
show_progress 0.1 10
Then I signed the update.zip with:
jarsigner -verbose -keystore my_keystore update.zip my_key
When I launch:
jarsigner -verify update.zip
I get "jar verified".
But in Clockwork recovery, my update.zip does not work - and signature verification is disabled, afaik.
EDIT: I have uploaded the update.zip there:
http://matrixrewriter.com/android/files/update.zip
Any ideas ?
Thanx in advance for any help
Click to expand...
Click to collapse
Hey Joel
Just curious has this been sorted yet? I would love a .zip so I can flash it after a new ROM when I don't have data.
FHL09 said:
Hey Joel
Just curious has this been sorted yet? I would love a .zip so I can flash it after a new ROM when I don't have data.
Click to expand...
Click to collapse
Hi dear Androlute overlord
Unfortunately no, I haven't got any hint on how to fix the zip file. Looking forward to having a working file!
I tweeted about it today, so I'm hoping someone will help...
Thanks
It's okay, the zip file works now. The update-script was misplaced
Hi Joel,
DO we have to sign the zip file created or would it be possible for your app to sign the file?
Thanks NSCXP2005
nscxp2005 said:
Hi Joel,
DO we have to sign the zip file created or would it be possible for your app to sign the file?
Thanks NSCXP2005
Click to expand...
Click to collapse
Hi,
The generated zip files are not signed - sorry.
I would love to incorporate the necessary signing code into my app, but unfortunately the signapk tool seems to require several Sun-only crypto classes, which don't exist on Android. If you know of a java implementation that can sign a zip file without using these Sun-only imports, please let me know and (as long as it's in the public domain) I'd be glad to include it in my app.
Thanks!
ok, Thanks.
Could you tell me how to sign the Update.zip that has been created by your app?
nscxp2005 said:
ok, Thanks.
Could you tell me how to sign the Update.zip that has been created by your app?
Click to expand...
Click to collapse
I have never really done it (or succeeded to do it), to be honest.
You need to use the "signapk" tool. I tried with Sun's standard "jarsigner" tool that comes with the JDK, but it wasn't considered as properly signed by the recovery image I have (Clockwork).
If you have more success than me, please let me know...
ok, thanks Joe, I hope you manage to find a way to sign the update.zip in the future.
Keep up the great work!!
EDIT Joel, I finally managed to flash your app in Recovery!!
Go here and look at the Update Maker made by DMzda
Update Maker
I hope you manage to implement this in to your update generator
I hope this helps
All the best
NSCXP2005

[Q] Help needed to dump the original rom

Hi everybody! I bought some weeks ago a Shift and my first priority is to change the language from Italian to English. But before going ahead in flashing a new rom I thought it is wise to make a back-up of the original rom.
So in my attempt to dump the original italian rom of my Shift I've come to an error status I don't know how to overcome, therefore any help would be very much appreciated:
Following pof's How to dump HTC Shift ROM at
http://forum.xda-developers.com/showthread.php?t=382609
I downloaded itsutils, unzipped on the pc and placed all the itsutils files in the c:\users\HTC User folder, (as I just did not know how to change the path in cmd to go to the c root with the itsutil folder).
Further on, with the WinMob connected to Vista with USB Tool, I introduced the first command line for pdocread
pdocread.exe -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw
and I got the answer
Copying c:\users\HTC User\itsutils.dll to WCE:\Windows\itsutils.dll (which I think it's OK) and then
rapi reinitializing (is it normal?)
and then
ERROR: CeProcessConfig – r=002349d0 ce=00000002 le=00000000 hr=80070005
– Access is denied
I have no idea on what the cause of the error could be, probably I must have done something wrong and I am stuck at this first dump step.
Can somebody please help me further to get unstuck?
Thank you very much!
Are you connected using activesync?
Also, try this guide:
http://forum.xda-developers.com/showthread.php?t=427507
and use pdocread -l first.
thaihugo said:
Are you connected using activesync?
Also, try this guide:
http://forum.xda-developers.com/showthread.php?t=427507
and use pdocread -l first.
Click to expand...
Click to collapse
THANK YOU THAIHUGO for taking the glove of answering me on this dead forum, I really need help! I find it fantastic that you are still so active, maybe in time some other senior members will take again the challenge to support the newcomers.
Yes, WM was connected to Vista side using the USB Tool and the Windows Mobile Device Center.
Looking back, I think I opened cmd as user and not as admin (now I know how to do it), this might have been the mistake, I will try again this afternoon.
1. So far I understood that the main reading process is running under Vista using the command lines and the itsutils, which is ok.
Does it matter where the unzipped folder <itsutilsbin-20100324> is placed? I mean should it be placed obligatory in the root of the c:\ drive?
If YES, how do I do that in the cmd line, I mean change the directory? Normally the cmd screen opens to the folder c:\users\HTC User when starting as user and to c:\Windows\system32 when doing it as administrator. Is it wise to copy all the itsutils files to system 32?
Of all those itsutils files, which are the absolutely necessary files to do the dump? Are these pdocread.exe and itsutils.dll only? This is because I'd like to handle as less files as possible to the system 32 folder.
2. If I got this right, the link that you pointed to shows for the Raphael ROM how to do the dump entirely on the WM side and should be applicable to the Shift WM as well if not managing it from Vista side, is that what you were trying to say?
3. Is this way of dumping the rom covering also the radio part and the bootloader, I mean all the 4 raw files contain the whole initial memory of the WM?
Sorry to raise such beginners question, but I did not find these things explained in any of the Shift threads and without answers I cannot progress with this dump job and furtehr proceed with flashing a custom rom in English. I did search in the Shift forums and googles for answers, but maybe I did not use the right keywords.
Looking forward to receive the enlighting answers, thanks in advance!
Admin cmd mode should help yes.
1) it doesn't matter where your zip is. Just uncompress the files somewhere in a folder (c:\itsutils if you want), open you command line in admin mode, navigate from system32 folder to the itsutils folder and try again with the pdocread -l then the command from POF post.
2) do not use raphael numbers. I linked to the post for the general procedure. Proper numbers are in the POF post.
3) you will not have the radio, nor the bootloader. But you have to jump if you want to use custom roms. Bootloader is available somwhere, and radio also I think.
Still getting errors
thaihugo said:
Admin cmd mode should help yes.
1) it doesn't matter where your zip is. Just uncompress the files somewhere in a folder (c:\itsutils if you want), open you command line in admin mode, navigate from system32 folder to the itsutils folder and try again with the pdocread -l then the command from POF post.
Click to expand...
Click to collapse
Thank you again Thaihugo!
I gave it another try to pof's commands as you recommended this time first with pdocread -l and it doens't work, BUT I'm getting the similar error messages. While accessing cmd as administrator and running the cmd line from c:\itsutils:
pdocread.exe -l
rapi reinitializing
and then after about 35 sec
ERROR: CeProcessConfig – r=002349d0 ce=00000002 le=00000000 hr=80070005 – Access is denied
At different runs I got different addresses for r and ce, but the same for le and hr (no idea what those mean).
It doesn't change if launching as administrator or user.
I even downloaded a previous version of itsutils directly on the Vista computer and unzipped it with Total Commander and the result is the same.
Have also tried another command from pof with the same error result:
pmemdump.exe 0x8c000000 262144 SPL.nb
Of course the WM side was connected to Vista via USB Tool and I also checked if from the Vista side the WM folders were accessible.
I'm completely stuck, don't know what to do further, please help!!!
Thank you!
P.S. Have copied the itsutils.dll to the Windows folder in WM via e-mail, just like in the liberalization process in order to avoid copying it via Active sync (as recommended for Raphael). This time at the first run of the pdocread.exe I was asked to accept installing itsutils.dll on the WM side, which I did.
But I'm still getting the error messages when launching pdocread.exe -l, this time running very fast in a few seconds and after 4 turns it stops with the final message
ERROR loading itsutil.dll - probably denied by policy restrictions
Does it ring any bell to you?
My guess is that I have to relax the security policy on the WM side, but I don't know how.
I am amaized that nobody raised all these before.
I've finally done it! HowTo......
OK, I finally managed to dump the ROM thanks to the support of Thaihugo and the info in various threads on this forum (with credit to the authors), I have now the ROM and bootloader dump files, but not the radio rom.
There were several detailed steps important for beginners that were not included in POF's thread "How to dump HTC Shift ROM" at http://forum.xda-developers.com/showthread.php?t=382609 that prevented me to do the dump from the first go.
In order to spare other newcomers time, here they are:
-On the WinMob side change the Security Policies setting by installing a registry editor like PHM Registry Editor, TotalCommander, etc. (I used the cab files downloaded in Vista and moved to WinMob via the Windows Mobile Device Center);
Go to HKLM\Security\Policies\Policies and change the valuename '00001001' from dword:2 to dword:1. Save the change and soft reset your WM device.
If in doubt check this: http://forum.xda-developers.com/showthread.php?t=427507
Note: After finishing the dump operation do not forget to revert back to the initial dword:2 value
-Download itsutils from POF's site to Vista and unzip the package to a new folder "c:\itsutils".
-To be on the safe side disconnect all network connections (3G modem, wifi, BT, LAN) and all USB external devices.
-Connect the WinMob side of the liberated Shift to Vista using the USB Tool and check in the Windows Mobile Device Center that the folders and files of WinMob are indeed accessible from Vista
-Open the command line screen and go to the folder where you unzipped the itsutils tool by typing "cd c:\itsutils" (without the quotes).
-From within the folder itutils type the command "pdocread -l" (without the quotes).
At this point, with pdocread.exe started, go to the WinMob side and
you will find a message asking you to accept installing the itsutils.dll on the WM side, say Yes to it and wait until it is instelled.
Then go back to Vista side and carry on as described in POF's thread mentioned above by:
- using "pdocread.exe -l" to list the NAND PARTITIONS (which have to do also with the radio side as I understood from one of cmonex posts)
- using "pdocread.exe -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw" and the other 3 commnads to generate the 4 raw files in the same folder c:\itsutils; keep them for reconstructing the original ROM
- using "pmemdump.exe 0x8c000000 262144 SPL.nb" to dump the bootloader file to the same folder c:\itsutils; keep that too.
That's it for now.
I have to deal further with dumping the radio rom, but I don't know how to do it, I must search the forums.
A big THANK YOU to all who helped me!
I never dumped a Radio. I think the experts keep this as secret because it's quite dangerous. Isuggest you have a look at your radio version and try and fin the same radioin the forum already dumped.
Otherwise, there are roms for each radio, so you could just simply apply the one that works wth your radio. No phone call though if you don't use the right one.
thaihugo said:
I never dumped a Radio. I think the experts keep this as secret because it's quite dangerous. Isuggest you have a look at your radio version and try and fin the same radioin the forum already dumped.
Otherwise, there are roms for each radio, so you could just simply apply the one that works wth your radio. No phone call though if you don't use the right one.
Click to expand...
Click to collapse
Thank you again Thaihugo, it seems that you are the only senior left on duty on this dead forum....yet the counter shows 238 views of this thread. Hm, strange....Anyway, thank you for all the good hints given one way or another during the past days, I wouldn't have made it without it.
I got the message, I will not bother with dumping the Radio. I know that a particular Rom is matched with a certain radio. I will flash one of your roms, most probably Age of Reasons and the associated radio. I am not looking for tens of programs on the WM side, it is enough to have the basic things in English and instant-on. I will let you know!

kitchen rom

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

Categories

Resources