yashsingh1/xdaforums huggingface dataset:
[Android] jm0077:
Hello,

I was analyzing the "adb logcat" of the HTC Desire again and comparate it with the respective "adb logcat" from the HTC Nexus One... and all result very similar.. but the last part of the log of the HTC Desire shows:

I/power ( 87): *** set_screen_state 0

D/SurfaceFlinger( 87): About to give-up screen, flinger = 0x121458

D/AK8973 ( 64): Compass CLOSE

D/SntpClient( 87): request time failed: java.net.UnknownHostException: north-america.pool.ntp.org

D/SntpClient( 87): request time failed: java.net.UnknownHostException: north-america.pool.ntp.org

D/SntpClient( 87): request time failed: java.net.UnknownHostException: north-america.pool.ntp.org

And cant found the reason why the phone gets stuck :confused:
[Android] dsixda:
You're flashing a Nexus One ROM to your Desire?? I don't understand.
[Android] jm0077:
No! I compiled another version for the Nexus One, just to clarify that the process that I'm making is ok.. and actually works fine..

But is not the same when I compile the AOSP for the HTC Desire (original case)..

I compared the logs generated and there are not much differences just in the last part where the HTC Desire gets stuck over the splash screen...

Hope can help me with this issue..
[Android] adrianh85:
ok this is my first time using this kitchen for my thunderbolt but i have run into problems on every rom i cook ie being stuck at the boot image i have pulled the logcat and the recovery files but i havent learned to read them to find my problem ! can someone help? both posted below
[Android] dsixda:
This is not a correct recovery.log. the instructions said to dump it after you flash and BEFORE you reboot. This is otherwise an empty log.

You can debug a recovery log easily by just looking at it yourself.
[Android] adrianh85:
Ok will try it agian
[Android] AngelDeath:
Any idea of my issue on post #4213?

Does the logs show you anything that I might have missed? Sorry to re-ask.
[Android] TMartin:
If you need help just pm me man.

Posted from my HTC Evo 4G on Tapatalk Pro!
[Android] adrianh85:
here is the correct recovery log (i hope) funny thing is the log says its a gingerbread rom but the ruu i pulled it from was a leaked thunderbolt offical one!
[Android] hroberts89436:
/system/framework files

I was told that these files in /system/framework are not to be resigned because they loose some required signatures, however I notice that your app resigned them, does it use HTC's signatures or did you find a way around this?
[Android] adrianh85:
Long time Thanks tmartin
[Android] TMartin:
Hey would you upload your build.prop??

Hey dsixda,

This is coming from his recovery log. No go on check data program for the Thunderbolt??

format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25about to run program [/tmp/check_data_app] with 1 args
[Android] jm0077:
Oh, sorry to post again but somebody have an idea about the problem that I have when I flash the AOSP compiled over the HTC Desire ?

Any help is welcome...
[Android] dsixda:
I think it's still fine despite that error, but the end of the log has issues with the sd-ext partition.
[Android] dsixda:
The update.zip gets signed.

I don't know how they're signed.. you'll have to ask the person who made the Java app.
[Android] TMartin:
I'm trying to get his update script & build.prop since I saw all the sd-ext issues & there were some partition errors too.
[Android] DearTanker:
Kitchen v0.153,Desire HD

1.data/app didn't work. apk names 'com.*.*.apk'/'*.apk'

2.just a suggestion,will you consider to remove 'installbusybox'and'check_data_app'.and fix those in other way.
[Android] adrianh85:
here are all of the files im looking threw them trying to see what i actually did wrong.
[Android] TMartin:
Try starting fresh and don't add app2sd at all.
[Android] dsixda:
They both worked on my Desire HD. Why remove install_busybox???
[Android] adrianh85:
ok doing it now
[Android] TMartin:
Hey dsixda,

Those sd-ext issues appear to be from the dtinstall in the /system/bin. Using sd-ext possibly an issue for the Thunderbolt??
[Android] twopumpchump:
i'm pretty sure you are right, i had the same issue with sd-ext on DHD on an older version of the kitchen.
[Android] dsixda:
That's likely a darktremor apps2sd issue then. But why use apps2sd on a device with such a large internal memory?
[Android] TMartin:
I don't...I refuse to use it on my Evo. adrianh85 was trying to use it which was causing all those sd-ext issues.
[Android] dsixda:
Yeah sorry, it wasn't meant for you ;)

But for that issue it needs to be addressed to rtkirton so that he can update his scripts.... but really, there is no reason to use apps2sd on the newer devices if someone knows what he's doing.
[Android] hroberts89436:
Any thoughts on this?
[Android] adrianh85:
im still learning this android kitchen i havent really been cooking since winmo but im trying to get it together im just having problems getting roms to boot
[Android] dsixda:
My thought is I just answered it a couple of hours ago
[Android] dsixda:
No problem, just start out small by using only the options on the basic menu (first screen) and make sure you can successfully get a working ROM first.
[Android] adrianh85:
yeah thats what im doing now
[Android] adrianh85:
ok i have a booting rom ! i did all the basic things like root , wirless tether. but this is what i wantto know every time i swap out a file so there another file i have to update? like i have a framework-res.apk i made using the online kitchen, do i just simply replace my file with the one already in the sys/framework, or do i also need some of the other files that where inside the zip ie there was a folder named meta-inf
[Android] scar45:
Hi dsixda, first off, thanks a bunch for this incredible set of tools, you've done a great job!

I've tried to search this thread before posting, but it seems the XDA Search functionality is currently down (it's too late at night for me to wait now!)

I have a bit of an issue in regards to unpacking, editing, recreating boot.img files, specifically from LeeDrOiD 2.4 (Desire Sense ROM). Basically all I want to do is edit a few lines in init.rc, rebuild the boot.img file, and flash it back to my currently running version of the ROM on my Desire. I was able to do each step properly (even verified by extracting my new boot.img with edits and saw them there). I flashed it back via fastboot, and also tried just temporarily booting it using 'fastboot boot d:\boot.img", but I run into an issue where the phone will not boot and just sits at the splash screen (before bootanimation runs).

I know that the lines I've added in init.rc are proper, so it's nothing like a malformed text file, as I've edited it in notepad. The lines in question are related to creating a temporary dir for Market Downloads since I'm using an HBOOT with a 5mb cache (original post which explains the overall goal of my boot.img edits - look under "Fixing Market Downloads", there's even a reference to your "wonderful" kitchen :)):

export DOWNLOAD_CACHE /mnt/asec/download

# Market downloads
mkdir /mnt/asec/download 0777 root system
mount tmpfs tmpfs /mnt/asec/download mode=0777,gid=1000

so again, I don't believe the actual edits that I'm making is causing the system not to boot.

I'm using the latest version of the kitchen (0.153), running within Cygwin in Win7-x64.

Just looking for a bit of advice, I've done much searching but can't come up with anything...

Thanks in advance for any insight!
[Android] dsixda:
Didn't you do a logcat as suggested in FAQ?

Try not to use Notepad for Windows because it inserts special characters for the carriage return... this may mess up your init.rc since it is Linux-based. Just download GVim or something similar and edit your init.rc with that.
[Android] DearTanker:
How did you names your apk?

These what i do:

base wee1.73.405.3

add root

add busy box

add data/app function

add com.speedsoft.rootexplorer.apk to data/app

packed it

flash rom

not do other things

and i am sure the apk i add can install.

consider to remove 'installbusybox'and'check_data_app'

because i found some recovery will have problem with this two script.
[Android] cal2011:
Ok Ive set up virtual box for windows now how do I install Ubuntu,

Do i need a ubuntu dvd or download iso or can i install it from internet ?

thanks :)
[Android] dsixda:
Which recovery and what problem with busybox? I'm not removing something that has been there since day 1.
[Android] dscott23:
Instructions are listed with a step by step guide at the beginning of the thread, download links and all.
[Android] dsixda:
Come on man, read the FAQ.
[Android] anhtuank15:
Thansk you so must ^^!
[Android] cal2011:
thanks for the help dsixda i did read the faq twice and again

i am new at this , thats how i setup virtual box, i know it says setup virtualbox and install ubuntu, i didnt realize i needed a copy, it didnt exactly say that or supply link so i thought it came with virtual box, im downloading ubuntu as we speak , i just thought i could get help on installing it from net or network as that was an option :)

ok after reading faq again there is link for ubuntu in how to install on linux section, why would i read that if installing on windows?
[Android] cal2011:
the reason i tried this

•Those who are brand new to creating custom ROMs and want an easy place to start

•Those who just want to modify shipped ROMs or someone else's custom ROMs to their liking

•Those who are confused by all those scripts and complex commands required for building and extracting

I am all 3

next read FAQ 3

What operating systems are supported, and how do I set them up for the kitchen?

I use windows so i choose windows,next choice cygwin or virtual machine,

I choose virtual machine because i used one when i made my bootable windows usb, next step

download a virtual machine (e.g. the free VirtualBox, or pay for VMWare) and inside of it, install Ubuntu Linux. Follow the instructions in the next section ("Ubuntu Linux") for setting up Ubuntu for the kitchen

I read this as , step 1: install virtualBox

step 2:install ubuntu, i got this far

step 3:go to Ubuntu linux section to setup ubuntu for kitchen,i didnt get this far.

next i ask Question about installing ubuntu, told read faq (how did i get to step 2 without reading faq)and also told downlinks provided, this got me thinking i only need Karmic Koala, i didn't get to step 3 so i didnt realize Karmic Koala is provided

Next question do i forget step 2 install ubuntu and just install Karmic Koala on virtual machine (although it says it doesnt have to be installed on virtual machine) This makes me think step 2 is needed
[Android] vetvito:
Dsixda, your kitchen works perfectly with the Dell Streak 7.
[Android] dsixda:
Cool, what items did you build, and from what base ROM?
[Android] cal2011:
Dsixda so I followed steps in windows section , downloaded ubunto 10.10, karmic koala wasnt mentioned, then in linux section it says use karmic koala, is the karmic koala for the windows version as well because if i follow faq properly i would have already installed ubuntu 10.10

ok so i was wrong the download links were there, i just tried following faq like stated setup virtualbox then install ubunto in it, then move on to linux section and set it up for kitchen, just needed some simple advice

if i knew how to i would delete previous posts , you can if u want

and even though i did take your advice and read the faq 10 times , windows section only said ubunto so i still dont know which version i need , great advice
[Android] vetvito:
I used the Dell update they just released as a base. I'll provide details when I get home.

edit

Ok, I used the latest Dell update. However the updater -> update script conversion doesn't properly work. So if any changes need to be did, the user must do it manually. Perfect example, I get assert write error "boot.img". We need "write_boot_raw_image", in the updater script in order for it to write. I don't know if its the recovery, or if its the device. I do know all updater script changes must be done manually, unless I'm overlooking something.

Your kitchen has been a time saver. I have published a themed 2.2 rom with your kitchen.
[Android] dsixda:
Can you tell me all the changes that need to be done? Or better yet, send me links to the stock ROM and your version that works. I could try to get it working without manual intervention.

EDIT: Nevermind, found the links

Thanks
[Android] atifsh:
Why it can't open new leaked desire gb test Rom. Error somthing like no system.......while starting to make working folder. All other roms work fine.
[Android] twopumpchump:
are you trying to dump the .zip file from the gb rom? if so, try unizipping it and place the boot.img and system.img in the "original_update" folder...worked for me.
[Android] atifsh:
yes the zip, as the it doesnt have any img files inside just folders for system and boot.

the file i got was named.....

Bravo_Gingerbread_hTC_Asia_WWE_3.06.707.0_Radio_32.56.00.32U_5.17.05.08_test_183945

but it doesnt have any img's except radio img.
[Android] dsixda:
You didn't read the instructions in the kitchen.

From the kitchen (see the required format for the ZIP file):

Ensure the ROM is under the original_update folder. The format
may be one of the following:

- A ZIP file for a custom ROM (e.g. update.zip)
- A ZIP file containing *.img (e.g. rom.zip from shipped ROM)
- system.img + boot.img (e.g. from shipped ROM or Nandroid)
- An APP file from Huawei (e.g. UPDATE.APP from software update)

File listing of Bravo_Gingerbread_hTC_Asia_WWE_3.06.707.0_Radio_32.56.00.32U_5.17.05.08_test_183945.zip:

$ ls
BOOT META OTA RADIO RECOVERY SYSTEM

This is neither a custom ROM or a ZIP file containing *.img.
[Android] atifsh:
I know that's different, figured out that part ;) but few ppl have rooted it, and I'm not familiar of anything else than this kitchen. Been using this kitchen for some time. :)
[Android] dsixda:
I think I can figure out how to do this one, but it will take me some time. It's a new format so it'll take a bit of hacking up.. doesn't look too bad though. Going to bed now though.
[Android] leith51:
Just a bit of info the new release I found a good download it was the .exe file I downloaded it got the Rom zip when extracted the boot.img was named boot_signed.img kitchen would not recognise the boot.img so renamed it to boot.img worked fine also kitchen worked fine to root with chains dd not used the Rom yet as it needs more work to make it run on dhd

Sent from Pluto
[Android] dsixda:
Like I asked you before, can you use punctuation, because I cannot completely follow what you are saying there. The kitchen already renames boot_signed.img if it is given inside a zip file.
[Android] xHausx:
Linux is case sensitive. I also had to create the META-INF/google/android folder (I think that was the one) or it would give a file not found error and cancel out.
[Android] dsixda:
The real problem is the ROM does not have a normal boot.img, and thus it needs to be converted to proper recognizable format. Not a big deal though, I'll do it when I have some time.
[Android] TMartin:
The new Sensation, Evo & Desire leaks aren't in any certain format. 911sniper refers to this as "Folder form" because it's just all the partitions dumped into folders. I don't think this will become the standard or anything.
[Android] dsixda:
I hope so :-)

One problem I'm having is determining the page size for the boot.img that will need to be created from the BOOT folder. The page size is equal to the offset of the kernel from the start of the boot.img (open boot.img in a hex editor and you'll notice). If I don't know the correct location of the kernel in the boot.img then the device may not boot.

On older devices, this page size is 2048 (0x800 in hex) bytes, and on most newer HTC devices it's 4096 (0x1000 in hex), but it's hard to determine this value by just looking at these new folders, since there is no boot.img from which to do the calculation.
[Android] leith51:
I never passed my English exams sorry

In a zip file maybe didn't try. But as taking just boot_signed.img and system.img it does not it will add its own boot.img.

I wasn't complaining, just pointing out to new comers to rename boot_signed.img if they use that method.

Sent from Pluto
[Android] dsixda:
That is not even funny, if you meant it that way. Anyways, this is a place to help others and share information, let's keep it civil.
[Android] leith51:
Not being funny I really didn't pass my English exams, maths and science no problem. But punctuation was never a strong point

Sent from Pluto
[Android] TMartin:
I have been compiling it into a boot.img and its been working fine for on my Evo.

Posted from my HTC Evo 4G on Tapatalk Pro!
[Android] dsixda:
That's because the script is defaulted to pageSize=2048, which is what the Evo uses. The newer HTC devices use 4096.
[Android] Newt:
ive searched everywhere and cant find an answer. i added the data app function to my rom but when i flash my rom none of the apps show up that i placed in the folder. do you know what i might have missed to cause this?
[Android] dsixda:
Read the FAQ to see how to get a recovery log after flashing
[Android] TMartin:
I'll check the script I used. It wasn't your kitchen.

Posted from my HTC Evo 4G on Tapatalk Pro!
[Android] dsixda:
Yes, please let me know, that would be appreciated!

BTW I'm talking about the kernel offset, not base address offset.
[Android] DearTanker:
How did you names your apk?

These what i do:

base wee1.73.405.3

add root

add busy box

add data/app function

add com.speedsoft.rootexplorer.apk to data/app

packed it

flash rom

not do other things

and i am sure the apk i add can install manual.
[Android] dsixda:
I don't understand your post. You also didn't answer my questions.
[Android] izzy001:
works great with the myTouch 3G Slide
[Android] dsixda:
Android Kitchen 0.154 is now up. Please see Release Notes for details. Enjoy.
[Android] neudof:
I am not only new to cooking, I am also new to Mac. With that said I am trying to set up the kitchen on my Mac, and I keep getting the following error:

Welcome to the HTC Android Kitchen

Please wait .....sed: illegal option -- -

usage: sed script [-Ealn] [-i extension] [file ...]

sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]

Error: You do not have the correct version of 'sed' installed.

Refer to the FAQ for the HTC Android Kitchen at

xda-developers.com to ensure you have installed the GNU

version of sed.

I have downloaded and installed the version of SED in the OP, but I am still missing something..

Any ideas?

Thanks in advance :)
[Android] xHausx:
Look for the META/misc_info.txt file, the page size is in there for the supersonic.

recovery_api_version=2
tool_extensions=device/htc/supersonic/../common/fake
mkyaffs2_extra_flags=-c 2048 -s 64

It also has all of the permissions for the rom in the filesystem_config.txt file. To build the boot.img with your kitchen I just extracted an older boot.img and replaced everything with the new files, worked great.

I think DearTanker is talking about adding apps to a ROM in the kitchen, when building a ROM you have to add it in the update script for it to flash the data partition. Although when I tried it I didn't use the data app function so I'm not sure if that adds that in there or not.
[Android] dsixda:
Ya I'm aware of the settings in the misc_info.txt, those two last numbers refer to the spare and chunk size for the yaffs partition, which is not relevant in our case.

I was thinking of your idea of using an existing boot.img but thought it may be too complicated for some users, so I did some other method... but we'll see how it goes. Maybe I can have a menu to select the method if the script cannot figure it out automatically.
[Android] DearTanker:
About 'installbusybox'and'check_data_app' this two script,i have some problem when i was flash zip into hero using some recovery.I did not remember so well.

Maybe i misremembered.

Now,there is no problem about this two script.

Other problem is,when i add /data/app to my desirehd rom.it seems not work.

this is what i do(just step by step using kitchen):

base ACE.wee1.73.405.3

first,i add root permissions by input 2,

then i add busybox by input 3,

then add data/app function by inout 0 and 13,

then i add apk to data/app folder,

then input 99 to build the rom.

but.when i flash it,the apk didn't install.

i have using names like 'com.*.*.apk'and'*.apk'.

'*' means some word.

but i can install the apk manual.
[Android] dsixda:
Again, if you have a problem with your flash then dump the recovery log. Read the FAQ for help. Attach it in your reply.
[Android] marcnvidic:
Great work on kitchen :cool:, very cool
[Android] klquicksall:
Love this tool. One question. I want to completely debrand my rom. I debranded the market but, i havent found in the rom where to remove att from the settings menu. Any help would be appreciated.
[Android] hroberts89436:
Who made the java app by chance?
[Android] TMartin:
Here is the perl script I used. Just remove the .txt extension.
[Android] dsixda:
It's similar to what I use.. it's also calling mkbootimg which hard-codes the page size to 2048 unless you change it manually or through my kitchen.
[Android] dsixda:
I don't remember anymore, sorry. I got it a year ago. Just Google it.
[Android] howtomen:
mmk fixed it after so many failed trys zomg yes!!!!!!!!!!!
[Android] Droidzone:
Hi..I saw that 0.154 has support for the leaked Gingersense Desire Rom. But when I cook it, the boot just fails. It gets stuck on the initial logo, and hence I cant get any useful info out of it. Even if I add nothing at all and just cook with the update-script, it fails to boot. Flashing doesnt give any errors at all. It is before logcat kicks in so that doesnt help either. I may have missed any discussion on this subject, in that case, just point me along the right way.. Or regarding any useful info I may be able to provide.
[Android] dsixda:
Could you paste the build.prop?
[Android] dsixda:
Looks fine to me, I don't have any idea. When you open tools/mkboot/mkbootimg.c, what is the value for pageSize? Is it 2048?

Edit: By the way, what is the "kernel offset" shown on the screen when you rebuild the boot.img? Is it the same as the value in another Desire ROM? It should also be the same as that stored in BOOT/base.

Edit: I think I know what the problem may be. It could be a parsing issue on my part. When I was grabbing the BOOT/base and BOOT/cmdline files, I didn't consider carriage returns or any other special characters in there that may mess up the values I wanted to use into the new boot.img. I will have to debug this when I get home later tonight. Are you using Ubuntu?
[Android] danarama:
I'm really sorry for the noob question.

I have searched the thread but I'm stuck on the simplest of things and I'm sure its something stupid I am doing.

I have set up cygwin and the kitchen.

I used option 20 to unpack the boot.img and have made the changes I need.

However, Option 20 only has an unpack or exit option but I thought I could repack from there too?

Boot image tools
----------------

Enter a choice:

a = Extract kernel+ramdisk (regular format) from boot.img in any folder
x = Exit

?

I can press b and get the following:

No working folder found!

Found BOOT-EXTRACTED folder, checking contents ...
Found boot.img-ramdisk
Found zImage
Working folder not found!

Press Enter to continue

Not sure how to progress.

I made the boot-extracted folder myself manually as it was complaining it couldnt find it and I dropped my extracted files in there

Once again, I do apologise for my noob question, please go easy on me. This is my first time delving in such things, but generally I do think myself technically minded.

Many thanks.
[Android] dsixda:
It will only have the re-pack option if you have the BOOT-EXTRACTED folder and Working folder.

It can't re-pack it to a boot.img if it doesnt know the parameters of a working boot.img, specifically the page size, command line and kernel base offset. The working folder should contain a boot.img so that the repacking script can use it to calculate these parameters when it makes the new boot.img.