yashsingh1/xdaforums huggingface dataset:
[Android] :
So you need to edit apks to add "values-**" folders.

What about the older version is this problem solved with them?.

Try to re-add the the arm* folders to framework after finish deodex from the original rom then try again.
[Android] NZnewbie:
I also have an issue when editing a 7.1.1 rom, flash the rom and the phone gets hot and random FC's- clean flash or dirty. IT never happened on the previous version rom kitchen.
[Android] :
This changes in oat2dex, you can back to old files if it better with you.
[Android] diabolicalprophecy:
Noob here. Does this helps to port rom? If yes, where can i find step by step guide? please let me know
[Android] :
No this is not for porting roms you can find guides for that by searching in google "how to port roms".
[Android] diabolicalprophecy:
Yes there are, but I want to use your kitchen as it allows to mod framework, unpack, modify bootimg and create flashable zips.
[Android] :
Port roms is not supported yet, sorry
[Android] asafyry:
[MENTION=6350858]ASSAYYED[/MENTION]

great work bro... i allready created so many files and all okey specialley whish i add root but i have small issue after created official file without root..then canot make reste factory default

any idea?:):)
[Android] :
I think this from checking dm-verity, i don't have any solutions sorry.
[Android] RealWelder:
I have a tab3 T210. The kitchen is an awesome tool, but for some reason regardless of which method I use (.tar, raw, .zip) the ROM will boot, but mtp connection no longer works and adb will only work every once in a while. I reverted back to my original ROM, but was wondering if anyone knew why or how to fix this issue.
[Android] Ram121:
This seems to be related to either build.prop or default.prop

Try adding following in default.prop of your kernel ramdisk

persist.sys.usb.config=mtp,adb
[Android] RealWelder:
Ok. I'll give that a shot.
[Android] RealWelder:
That didn't seem to do it...any other ideas? It has to be something on the system partition because I flashed the stock kernel on with the new system and same problem.
[Android] Ram121:
Check following commit for changes to be done in ramdisk

https://github.com/Ram121/RamKernel_N4/blob/master/bootimg/patches/N910.default.prop.patch

Otherwise try ROM without deodexing or any changes and check what creates the problem

Deodexing may also create problem
[Android] madsurfer1:
hi

thanks for your work

In this version, you may have fixed the nougat bootloop wen deodexing, but on marshmellow it started to bootloop after deodex, do you stiil have the deodex files from the last release?

thanks
[Android] dixmer1998:
How do I add applications to select in the installer Aroma?

I use translator, sorry for bad english
[Android] :
Which version of the kitchen worked with you to deodex MM?

http://xdaforums.com/showthread.php?t=1461712
[Android] :
In the last there are some changes on the oat2dex.jar.

After finish from deodexing try to re-add arm* folders to system/framework from the original odexed rom then try build and flash again.
[Android] madsurfer1:
So, basically you want me to try to deodex 2 times and see if it works, is that correct?

Did you changed deodex jar files in this version?

thanks for your help
[Android] :
Not 2 times.

Just one time deodex and extract the original "arm*" folders from the original rom and copy them to the deodexed rom and zip then flash.

In the v 1.82 there is no change but in the older versions updated oat2dex to support android N.
[Android] :
Thanks for feedback

But can you tell me what the android version?

Is lollipop 5.x.x or m 6.x.x i don't know if the metadata of the installer support mm roms can you tell me please?
[Android] pendor24:
Hello

910F(MM) for me on there are only metadata that has allowed my rom demarer .
[Android] edzamber:
6.0.1 MM [emoji6]
[Android] jackq:
maybe i doing something wrong then point me to the right way.

I take stock ftf rom, extracted system.sin and kernel.sin, with flashtool extracted system.ext4 and kernel to .elf,

then copied 2 img files to kitchen PLACE folder, next i start kitchen choose 1, start new project from stock img system file, when

kitchen want to mount i have error - can't mounting

then i have to extract system manually, copied system.img and imgextractor.exe to WORK folder, take system.img and drop it to exe, system folder is created with all files but this extract never ending - nothing in window was changes still presenting info about extracting, like on screen

so i watch to system folder and when i see that is everything unpacked then close this window manually.

then i finally have system folder with all files, deodexed and zipalignet it, debloated then want to build rom using first DAT method, build was succesfull but when i flash it to device, doesnt boot, stil goes to recovery...

about 7zip, sure you can extract ext4, even with symlinks, using latest 7zip

thanks for your effort, maybe finally i was able to work without problems using your kitchen. cheers
[Android] :
Imgextractor can't unpack files more than 4GB

Mount problem from you picture i see this problem from harddisk or from the high size of you rom i will test and fix it

And about 7zip thats great maybe will make the kitchen do that

Thanks for feedback
[Android] jackq:
Thanks for answer. Now i tried with smalest rom file, start was promissing but stuck about 10mins at:

extracting symlinks from new sparsed image..

should i wait more or something goes bad? How long it should take? i have i7 and 16gb ram.
[Android] :
No don't continue this stage (extracting symlinks.....) should not take more than 1 minute....it is an error

Sorry for that i will try to fix it using 7zip this week
[Android] gvmiguez:
Hi, I´m using the kitchen on Windows 10, but drag and drop system.img into ImageExtractor.exe is not working for me
[Android] :
Imgextractor can't unpack system more than 4GB

You can (after converting from sparse to raw ext4) unpack the system.img using latest realase from 7zip

I will work on fix this week.....

Sorry for that
[Android] jackq:
For Z5 ROMs 5GB+ size this kitchen doesn't work as it should. Extracted all files with symlinks using latest 7zip.

Tried two creating ROM methods, DAT and RAW, after flash bootloop, looks like created files are broken. I check and open system.img and inside wasn't even 20% of necessary files.

Sorry dude but you have to work a little bit more at this project. Maybe you have to find a way which allows correct rebuild big ROMs.
[Android] :
Ok the version 3 now work in progress

I will improve it and fix all detected bugs
[Android] s5610:
Seems like it doesn't work with Motorola multiple chunk sparse images. Add support, please.
[Android] :
The kitchen supports sparsechunk...

These files must be in zip file i have tested that

The files look like (system_sparsechunk.1) or something like that......

Any way please open the zip file then take screenshot and attach it so i can see the files types to add support for them and give me the link for your rom
[Android] s5610:
Ah, my bad! I Now it works! Thank you for quick answering ) It was VICTARA_TMO_XT1095_6.0_MPE24.49-18_cid9_CFC.xml.zip. Looks like sparses unpacked correctly into system folder - just what I needed for now. Thanks, great "end-user" tool )

---------- Post added 19th July 2016 at 12:01 AM ---------- Previous post was 18th July 2016 at 11:58 PM ----------

Peace to your country and people :(
[Android] jackq:
looks promising, waiting ;)
[Android] pendor24:
Hello

I work from my mobile system Estre the kichen and once made ​​my rom , flash ca said corompu zip error . an idea ?
[Android] :
Try to re-build zip manually in GUI winrar or 7zip

pulling rom doesn't cause this problem

Sorry for late
[Android] pendor24:
Hello . already tried , same result . excuse my bad english , I'm french and use a translator

thank you
[Android] :
No problem

Try to reduce size of file or build it on other PC

or try change compression level to

in the worest status search for this problem in google
[Android] :
NO

It supports Windows only
[Android] madsurfer1:
after deodex in the arm folders, is created 2 more folders inside DEX and DEODEX, those files/folders arent in the original arm folder, should I also delete the dex and deodex folders?

our just replace the files that were in the original arm folders and leave those that are created after the deodex?

edit, nevermind, those were temp files, I'm installing the rom now to try if it boots with the arm folders

---------- Post added at 01:55 AM ---------- Previous post was at 01:36 AM ----------

Sorry for the double post, just try'ed it, and it works as you said

Just on the kitchen it still shows that the rom isnt deodexed, despite all the apks are deodex'ed

Thanks
[Android] RealWelder:
I figured it out. It was the sdcardreadahead init.d script that was preventing the mtp. Figured I post in case anyone else has the issue.
[Android] dixmer1998:
To add applications apk to the ROM installation is in \ WORK \ META-INF \ ADD-ONS \ DATA? I'm not sure
[Android] :
Good.

Ignore the kitchen message, it needs to update but the developing is stopped for this kind of programming.

Yes, create "app" folder and add in it the apks you want and don't forget to create folders for them if you are running android 5.x.x+.
[Android] Yzord:
Trojan:Win32/Detplock detected in ASSAYYED.exe

How can i use this tool safely? For now i have placed it back and authorized it. Hopefully it is ok :(

Is there a tutorial how to use this tool?
[Android] RealWelder:
Not sure about a tutorial, but it is safe. I had to disable my antivirus. It's actually a pretty awesome tool!

If I helped you, please hit the "like" button. Thank you.
[Android] Yzord:
Ok, i am starting to learn this tool. Pretty nifty tool it is :)

What i am trying to do is this. I want to edit the Nexus 5X Copperhead ROM so i can delete more apps from it (calenders/chromium/Email etc.). They will be all replaced with Torbrowser/k9-mail etc. Please tell me if i am doing ok before i can flash it...a find it a little bit scary for now. I have just my Nexus 5X :)

1. Downloaded the Copperhead ROM for the 5X

2. Placed the "image-bullhead-nmf26q" compressed file in PLACE

3. Opened up the .exe file which came up a menu.

4. Pressoption 1

5. Took the default folder for the image file

6. Took nr.1 as this is the image of Copperhead

7. Filled in all kinds of details (after it was extracting and converting)

8. I choose the AROMA installer (is this ok?) and filled in some more info

9. After that it is finished and need to press ENTER

Now i am back in my projects menu and as far as i have read i need to deodexing the apps. So i did the following (PLEASE tell me if i am doing something wrong here)

1. Pressed nr.2 and it checks for my JAVA which is ok.

2. Pressed ENTER to convert odex files (this took a while)

3. After it is finished i need to press ENTER

So again i am back in the projects menu. Now i am gonna debloat the ROM from the apps i don't want anymore

1. I press 11

2. and take option 1 to do it manually

3. I start removing the apk's from the apps which i don't want anymore

4. When i am done i press 0 to get back in the projects menu, but the DEBLOATED STATUS is still set to NO (how come?)

From this point i don't know what to do further. Let me ask a few questions which i have right now.

1. How can i add apk's which can be updated in the future though F-Droid?

2. How can i build this ROM without pushing it right away to the phone?

3. What can i do to get OTA updated from Copperhead or Google?

If anyone has some tips...please let me know.

EDIT: i have managed to build a ROM but when i look into the zipped file i see a different structure then the original ROM file. So i guess i cannot flash that?
[Android] kevintm78:
I might be able to help with some of your questions. First, don't worry about whether or not debloated says yes or no, as long as the apps are removed from your work\system\ folder, it is gone.

The reason your newly built ROM looks different than your original may be due to the fact that the new one is using a different format. Most roms are built using image files now instead of the old zip file structure that we used to see when we could unzip it and see everything in there. There is an option for that though, when you go to build the rom it is the zip option (3 I think).

The option that asks if you want this rom pushed to your phone is just asking to push to your memory card, it doesn't actually install anything at that point. A lot of times I'll just copy it from the ready folder to my phone using Windows just like you would anything else that you want to copy or move to your phone. In my case is a bit faster that way.

For user apps, if you go back a few posts you'll see the discussion about placing apps in a data folder, created by the kitchen, the goes into the meta-inf folder. You may want to follow that trail as I don't use that option a whole lot.

Last but not least, don't be nervous:). As long as you have a good backup you'll be ok, I used this kitchen countless times and have tried things I probably shouldn't have tried and so far so good. I finally tried the tar option the other day and it worked perfectly as well. As long as the files your trying to use are for your phone or you've made the necessary adjustments to port this kitchen won't let you down.
[Android] Yzord:
Thank you very much!! I have waited a day for this answer and it was worth it :)

What i mean about the apps is that i would like to install them in such a way they also will get updated by F-droid when a new update is available. Or is this always?
[Android] Yzord:
I tried to pull the ROM of my Nexus 5X, but it said it cannot get the kernel from it. I have made the ROM exactly how i would want it (with the appropriate apps) so now i want to pull it from my phone, debloat it further and make a flash able ROM of it. But it cannot pull the kernel from the phone. Anyone an idea how i can pull the full ROM from the phone? The kitchen says it can pull everything without a rooted phone, but at my phone it failed doing it, but maybe i am doing something wrong.
[Android] RealWelder:
You do have to have root to pull the kernel, because it is not an adb command that is being ran. It is using a shell command to diskdump the boot.img. You have to have root to run dd command.
[Android] dixmer1998:
Do I create the app folder inside the data folder?
[Android] RealWelder:
I've actually never done it myself, but yes the end result is you want to put the apks in the /data/app/ directory of the phone... so you have to create the same structure. At least that's my understanding.
[Android] Yzord:
When i try to build a rom with option 7 and then option 3 for RAW it always results in an ERROR (error in creating [system.img] can't continue). I am looking for the same structure as my original ROM, so i have read i have to use 3=RAW. When i use option 2 (ZIP) i get the same structure as when system.img is extracted, but i need to have a zipped ROM with system.img in it.
[Android] Yzord:
Ok, i am a little bit further now. But when i build the ROM with option 3=RAW and flash the system.img to the phone it always results that it is stuck at the Google boot image.

I am editing an excisting ROM, deleting some apps and change the bootanimation and make the ROM again. Then flash the system.img with Nexus Root Toolkit. Anyone has a tip how i can get this to work? I am using the Aroma installer.

---------- Post added at 02:30 AM ---------- Previous post was at 02:30 AM ----------

Ok, i am a little bit further now. But when i build the ROM with option 3=RAW and flash the system.img to the phone it always results that it is stuck at the Google boot image.

I am editing an excisting ROM, deleting some apps and change the bootanimation and make the ROM again. Then flash the system.img with Nexus Root Toolkit. Anyone has a tip how i can get this to work? I am using the Aroma installer.
[Android] :
Sorry i don't have any idea, i didn't work with google roms yet.
[Android] RealWelder:
This might be counter intuitive, but I was having an issue with mtp not working on the kitchen builds...so I used it on the kernel, then for the system I just did it manually. For example in tools/tweaks you will see the init.d scripts. I zipped them up and pushed them to my sdcard. Then extracted them with root browser and copied them to /etc/init.d/ and changed their permissions accordingly. (Some ROMs it could be 0755 and others it 0644)

Did the same for the build.prop tweaks. I used root browser to manually copy and paste them into my build.prop.

After all that was finished I ran dd command to make my system.img and then used it in my zip instead of the one generated by the kitchen.

For the command you will have to check your path because it is different depending on the chipset of the device, but you want to go all the way to "by-name."

Example (for my device this is the exact command in terminal or adb shell)

su

dd if=/dev/block/platform/sdhci-pxav3.2/by-name/SYSTEM of=/sdcard/system.img

Your paths will be different and possibly SYSTEM won't need to be all caps. It varies from device to device...but if you use root browser you can navigate to it and check before you run your command.
[Android] Yzord:
I tried it also with SuperR kitchen and that one didn't work also. What i did there was unzipping the original rom and rebuilding it right after that. So i didn't edit anything. Flash the outcome to my phone and hangs on the Google bootscreen. So i don't know what is going wrong here, but it looks like it is not the kitchens who are giving these problems.
[Android] anees02:
Try to grab the whole firmware you downloaded , not that you pulled it from your device.
[Android] Yzord:
Also tried that. I just remembered something...do i need to be root to flash a custom ROM? Because the Copperhead rom i can flash easily without root.
[Android] RealWelder:
You don't have to have root to flash a custom ROM. Most custom ROMs that you flash will be pre-rooted, though.

It's probably an error with the updater script or binary. If you PM me I can probably help. What I would try is extracting your stock ROM. Then putting your new image files in it. (That is if both are flashing a raw system image and boot image.) Then compare your updater script from the original to the new one.
[Android] Yzord:
Wow, thanks! I will send you a PM. Would be great to have some help with this, because i am doing this 5 days now and tried very much everything i have read on this forum and on Google, but it always sticks to the Google bootimage (does not seems to be relooping, it always sticks to that image).
[Android] cbtc:
Hi!

I have recorded a video compiling a Fenix ROM.

https://xdaforums.com/galaxy-tab-a/development/rom-galaxy-tab-series-t3514996

LANGUAGUE: SPANISH :p

VIDEO:

https://youtu.be/PcTI4mJ8Jjo

Enjoy it :)
[MENTION=5248695]gvmiguez[/MENTION]

Thanks to :
[MENTION=6350858]ASSAYYED[/MENTION]
[Android] cbtc:
[MENTION=6350858]ASSAYYED[/MENTION]

¿Do you plan to add any new features to the kitchen?

Thanks you very much :fingers-crossed:
[Android] :
I thinked about some new features like (poting roms, dump system partitions, root running android device, updating binaries.......)

But currently i stopped working on it.
[Android] cbtc:
Awesome!

Thank you very much for your work!!!!
[Android] borjaag:
Hi, I can't use this program with Parallels (Windows 8) on my Mac, as it gives me this message:
[Android] farookh:
Assayyed how do i fix my wifi not turing on on s6 if i use tar in odin and not zip file.
[Android] :
I didn't test it on cross system as you say so you need an original copy of windows

This from "make_ext4fs" binary, it doesn't support the new contexts and permissions for system files so you need to do this manually.
[Android] pendor24:
Hello

A concern with the kitchen 1. 82 on note4.

Ca bootloop without stops after the beginning of the rom.

I compiled the ROM by adding 1 step per compilation and it does not change anything. (I have seen nothing say that 1. 82 was a specific verssion)
[Android] jajk:
[MENTION=6350858]ASSAYYED[/MENTION] Thanks for this great tool. This deodexed an Android 5.1 ROM for Ulefone Be Touch 3 where all other tools failed repeatedly.

ROMs for MTK based phones are never easy but I had 100% success on first attempt and no bootloops or FCs after installing the result:good:
[Android] RealWelder:
They are scripts put into /system/etc/init.d that are commanded to run at boot by kernel-init.sh found in either the /system partition or in /sbin depending on if you do ROM init.d or kernel init.d.
[Android] nalas:
Always GPU rendering for normall usage not CPU.

Sd card cache from 256kb to 4096kb

Mount ext3 or 4 partition i think as Internal Storage ( for installing apps)

Dalvik menegmant for virtual machine

Internet speed up via change dns servers and better values for tcpip

Zipalgin apps on every device boot for faster run apps good if you dont have odex files.

Better touchness - more smooth and better touch

Wysłane z mojego SM-G930F przy użyciu Tapatalka
[Android] Er. Aditya:
hi dev when ever i try to pull system from device i get this error

DETECTING DEVICE RESPONSE

CHECKING IF WE CAN PULL KERNEL FROM DEVICE

ERROR: WE CAN'T PULL KERNEL FROM DEVICE

ERROR: FAILED PULLING KERNEL
[Android] RealWelder:
Are you on Gingerbread? I had this error before with an older gingerbread phone. What I did was made a backup and then copied the boot.img into the work folder.
[Android] kevintm78:
I had this error when I switched from win7 to win8. I had to put the program at the root of C drive and that solved it.
[Android] Er. Aditya:
strange thing is this happens just when i pull rom files from device
[Android] kevintm78:
Hmm, that is strange. Are you using win8 or 10? My win7 computer died about a month ago and it seems like i get permission errors with this and TMA on win8 unless installed directly to the C drive, but I got them on everything I tried to do. I wasnt even able to move a file to the work area without granting admin permission every time until I moved it.
[Android] Er. Aditya:
thanks bro il try tomorrow with moving it to C: and yes i am on win 10...i was thinking to moving to 7
[Android] Dovanchuc7521:
Thanks to your work! I have a bug: when deodex the Note5 stock rom and rebuild, then i flash it can't reboot by root app as Titaniumbackup or RootEssitiall

Gửi từ SM-N920S của tôi bằng cách sử dụng Tapatalk
[Android] :
This errors are simple and you can remove them by removing the lines that cause these errors like line [449] in file [E:\ASSAYYED_KITCHEN_V1.82_STABLE\WORK\apktool\working1\SecSettings_ESS.apk\res\values\styles.xml].

This maybe need to update the apps to make them compatible with the deodexed rom or try to rebuild the deodexed rom after adding the [WORK/system/framework/arm*] folders from the stock rom.
[Android] carlitobahsoun:
hi dear assayyed ....i pm u plz can u take a look..thanks

---------- Post added at 01:04 AM ---------- Previous post was at 12:54 AM ----------

how to make this step can u explan ( after build the rom rebuild the deodex rom with adding feom stock rom etc......) what should i put in place and in work and .......
[Android] Dovanchuc7521:
I flash and use good but can not be rebooted with Titanium. Even users with root rights and flash back by SuperSU. Help me
[Android] carlitobahsoun:
me too flashed ok but not boot try flash supersu not boot...flash custom kernel and not boot....hope we get help...
[Android] :
Before build flashable rom extract the original [arm*] folders from stock rom and copy them to [WORK/system/framework]
[Android] haifish9999:
What did you choose in root section while running the root process? Coz I have done to build a lot of N5 rom without any root issues. ..
[Android] Dovanchuc7521:
Inbox

Gửi từ SM-N920S của tôi bằng cách sử dụng Tapatalk
[Android] RealWelder:
Did you install all of the frameworks? SystemUI, framework-res, and tw-framework-res. (If Samsung)
[Android] JamFlux:
This tools is just... Amazing!

A mirror, no from me, just find i on google.

Now is over on Mega.

https://www.androidfilehost.com/?fid=529152257862695696
[Android] suanggi:
Thx... @ASSAYYED

Amazing....

Test Deodexed stock s7e Nougat DPLT