yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] asc1977:
also what i see is that in the updater script mounting and formating system dont work. i always must replace with followed that work on s6 edge

---------- Post added at 20:13 ---------- Previous post was at 20:11 ----------

ok i will try and report

but if i choose set metadata it says to me its no lollipop rom. thats why i take setperm
[SuperR Kitchen] SuperR.:
Please send a link to the firmware. Make sure I don't need to register for anything to download. Thanks
[SuperR Kitchen] asc1977:
https://drive.google.com/file/d/0B8s5_g_D0wWZLU1COHZvX2dvdTA/view?pref=2&pli=1

Gesendet von meinem SM-G925F mit Tapatalk

---------- Post added at 20:32 ---------- Previous post was at 20:21 ----------

And i tested again and with your new 1.0.2.7 i can choose set metadata. Try to build a odex rom and if work a deodex. I will report asap

Gesendet von meinem SM-G925F mit Tapatalk

---------- Post added at 20:33 ---------- Previous post was at 20:32 ----------

And really really thx for your hard work and support. I am very thankful for that [emoji120] [emoji120] [emoji120] [emoji120] [emoji120] [emoji120] [emoji120] [emoji120] [emoji120] [emoji120] [emoji120]

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] JochenP:
[MENTION=718594]super[/MENTION]R

thanks for your explanations - it is all clear now and i've played a little bit with this point.

Not a great problem: Flag for '2 Custom Debloat' active/inactive is not working - it is always ( Current: Bloated)

SuperRs_Kitchen_v1.0.2.7
[SuperR Kitchen] SuperR.:
The flag is working fine. It will say "Bloated" as long as there are files in the rom that exist on the bloat list. Options 1 and 2 have their own flags so debloating with option 1 does not change the flag for option 2 unless the bloat_custom file only has files that already exist in the standard bloat file.

Additionally, adding files to the bloat_custom file is not enough. You must then choose option 2 and let it move the files out of the rom. After that, it will say "Debloated".

If you still have trouble, paste your bloat_custom file contents so I can have a look.
[SuperR Kitchen] JochenP:
Hmm. i left Option 1 untouched and have added some files to bloat_custom file:

system/app/ExactCalc*

system/app/facebook*

system/app/Hangouts*

Option 2 moves these files 00_project_files directory - i have checked this.

should option 2 show now 'debloated'? It shows always red Bloated for me :eek:

Thank you for your support
[SuperR Kitchen] SuperR.:
It should say Debloated in green after doing the custom debloat. Sadly I am not able to reproduce the issue. At least it is doing it :)
[SuperR Kitchen] asc1977:
[MENTION=5787964]SuperR.[/MENTION]

now my test results

odex: boot up, no forcecloses but wifi dont work

deodex: boot up, forceclose of syscope and smardcardmanager apks, after freezing this two apk, setup wizard works but no wifi

did you have any ideas about wifi? in one thread by a dev with self problem he posted that he must set the right permissions and than work. i asked him what he has done. waiting for answer. but nothing till now. hope you have an idea

cheers
[SuperR Kitchen] 9282gkg:
Which Linux version you guys are using?
[SuperR Kitchen] :
Think most people are using linux mint or Ubuntu. If you haven't used linux before I'd try linux mint as the desktop is very similar to Windows
[SuperR Kitchen] allurba:
Hi I have the TWRP 2.8.7.0 and gives me error to flash the Huawei G8

""error executing updater binary""

What can I do?
[SuperR Kitchen] shoey63:
[MENTION=718594]superR[/MENTION]

Apparently toybox is borked for 32 bit devices, as pointed out by [MENTION=4544860]osm0sis[/MENTION] http://xdaforums.com/showthread.php?p=65149012

Maybe he could help?
[SuperR Kitchen] JochenP:
this (my custom debloat) problem only occurs under Ubuntu 14.

I have installed Linux Mint now (for convenience) and here it shows after custom debloat the expected green 'Debloated' :o

Great - thank you
[SuperR Kitchen] SuperR.:
The wifi issue is probably due to some missing set_metadata lines in the updater-script. If you have a working updater-script for your device you can send it my way and I can find the parts the kitchen is missing and add them. Otherwise, if you figure out how to fix it on your own let me know and I will update the kitchen if possible.

Please send your recovery log after flashing the rom and getting the error. My guess is that you are getting an assert error saying the the rom is for a different device than you are flashing it on. Check post #4 for the solution if that is the case.

Not sure what you mean. Is something broken in the kitchen?
[SuperR Kitchen] Mentalmuso:
The WiFi issue for Samsung might not be a metadata issue. What I mean is that I have the no WiFi issue even when building a sparse dat zip.
[SuperR Kitchen] asc1977:
no it happen with sparse dat and set metadata

---------- Post added at 16:55 ---------- Previous post was at 16:54 ----------

i only can help you with a working rom of a other dev. but all inside is with system.img for example. dont know if it help
[SuperR Kitchen] Mentalmuso:
That's exactly what I mean. Because it happens with sparse dat and metadata, then it is probably not a permission issue. Sparse dat should eliminate a permission setting issue right? Or am I wrong?
[SuperR Kitchen] asc1977:
i dont know but it fu.. me up that i have this wifi problem and cant start with building rom and nobody have an idea for the problem. with lollipop all working so fine and now new system and new problems
[SuperR Kitchen] asc1977:
I will give it a try

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] thereassaad:
Only this way i found it to fix wifi issues with tw mm 6.0.1 doedexed so im sure it's will work my friend ,,

& about wifi issues im sure when we flashing rom as zip as old method way its by some permission & symlinks writed wrong don't know how i can fix it but will try to find a way to fix it & will ask some friends that have experts with this like Friedrich ( Echoe Roms Dev ) , i hope we can find a way to fix it ...

Good luck,,
[SuperR Kitchen] ambasadii:
definitely is bad permission & symlinks created by kitchen but don't forget that is dumped system.img of Android M (not official)
[SuperR Kitchen] thereassaad:
Yes but already try it with korean Official MM too & its same issues with wifi so i just did that way to skip this issues for now [emoji16][emoji17][emoji17]
[SuperR Kitchen] ambasadii:
did you try by flash new system.img or zip rom ?

[MENTION=5150393]_alexndr[/MENTION] is a guy that can help with this, He has the knowledge how to create them without kitchen
[SuperR Kitchen] russel5:
[MENTION=5787964]SuperR.[/MENTION] i can't update kitchen if i use your program's option. i don't know why, but several versions just gone after update.

i choose update - program download update - all done - do you want check updates? and i always say no - bam, your kitchen gone and if i enter in tool's folder i see only devices names folders and nothing more.
[SuperR Kitchen] asc1977:
thats right but also happen with 925k firmware official from samaung released. problem its not related to system dump beta

i hope you can find a solution. [MENTION=1649452]geiti94[/MENTION] found the solution. i am write him but no answer till now. in his sixperience rom it works after he has the same issue
[SuperR Kitchen] ambasadii:
if you want have wifi working you need to flash clean m then root and make changes by for example root explorer

then make a new system.img dump by adb like this:

#adb kill-servers

#adb devices

#adb shell

#su

#dd if=/dev/block/platform/15570000.ufs/by-name/SYSTEM bs=4096 of=/sdcard/system.img

before that remove file /system/xbin/su (becouse new image will be corupted)

when you create with succes new system.img by adb you find it in /sdcard/system.img

use this system.img by flashing in installation script by this command:

package_extract_file("system.img", "/dev/block/platform/15570000.ufs/by-name/SYSTEM");

This method works 100% i try it and wifi works.

good luck :)

edit: [MENTION=1649452]geiti94[/MENTION] for sure use methond from above ;)
[SuperR Kitchen] SuperR.:
This is not a 6.0.1 Samsung wifi not working thread. If there is something you can provide to make the kitchen work better, please do so. Otherwise, please start a new thread on how to get wifi working on Samsung 6.0.1 roms. Thanks
[SuperR Kitchen] asc1977:
sorry for spamming but we only search a solution for the missing things in updater-script for your tool
[SuperR Kitchen] ambasadii:
soory mate for this little of topic, we definitely end this discusion.

I hope that we found where is the problem with making a custom rom with android m by your great kitchen.
[SuperR Kitchen] JochenP:
is it possible to include xposed-framework, maybe with its variants?
[SuperR Kitchen] dkionline:
No, theres to much problems with it.
[SuperR Kitchen] JochenP:
certainly, but that is the reason why I asked ;)
[SuperR Kitchen] geiti94:
i makes a little different ;) the image create the same way but mods and changes i are flashed with twrp.
[SuperR Kitchen] hohassan444:
any updates to support xperia kernels.
[SuperR Kitchen] JamFan05:
I used this tool to make a ROM for my Nexus 6P and it worked flawlessly. Many thanks to SuperR for making this wonderful kitchen for us. I'm gonna play around with it some more to see what all can be done with it. Donation coming your way ASAP!
[SuperR Kitchen] allurba:
Works in Huawei G8. Thanks

Enviado desde mi HUAWEI RIO-L01 mediante Tapatalk
[SuperR Kitchen] JochenP:
What Kitchen version? 1.0.2.5 - 1.02.7

What Linux are you running? Linux Mint

What device are you working on (make/model)? HTC one A9

What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.) system.img

What Android version? 6.01

What perm method (set_perm, set_metadata, sparse_dat, raw_img)? set_metadata

Hi

i have two issues -

the first: after extration for new rom it is not possible to manage BOOT/Recovery tools without root rights. OK little problem so i startet superr with sudo or edit BOOT before i will do ROM-extraction...

the second: only superKitchen v 1.0.2.5 generates valid deodexed roms for me (perfect) - 1.0.2.6 and 1.0.2.7 generated roms resulting in loops: system is optimizing apps and restarts/reboots after this and optimizes again...

p.s. can you give me a hint how to start flashing xposed as last process in updater-script? It is not similar like superuser and busiboy because of his flash-script.sh
[SuperR Kitchen] SuperR.:
Don't start the kitchen as root. The usage instructions do not mention doing that anywhere. The kitchen will ask for sudo password when it needs it.

I understand the possibility of 1.0.2.7 not deodexing M properly as the method has changed, but I do not understand 1.0.2.6 not working if 1.0.2.5 works. It may be again due to running the kitchen as root. I suggest trying again without running the kitchen as root.

I have not looked at it at all and have no intentions of adding support for it.
[SuperR Kitchen] allurba:
Zip all devices to share.

New Device Huawei G8
[SuperR Kitchen] ast11:
What Kitchen version? -- 1.0.2.5

What Linux are you running? -- mint 17.3 x64

What device are you working on (make/model)? -- htc one a9

What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.) -- system.img

What Android version? -- 6.0.0

What perm method (set_perm, set_metadata, sparse_dat, raw_img)? -- set_metadata

What did you do after extracting and before building? -- nothing. just testing full rom.zip

Were there errors on the screen if you scroll up in the terminal?:

Should we zipalign before building the ROM? y/n y

find: `./bootimg/ramdisk/data': Permission denied

find: `./bootimg/ramdisk/sbin': Permission denied

Preparing updater-script....

sed: -e expression #1, char 43: unterminated `s' command

Can you send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)? I can if you need it

I try to flash the generated full rom zip in twrp however I get an error "updater process ended with signal: 6"

I'm trying to create a deodex'ed version of the stock att rom. Been bashing my head against this all day.

***************

EDIT: I deleted the superr folder and extracted a fresh copy. I can now get an unmodified rom to flash and boot fine. However I freeze at boot if I try to flash a deodexed rom. Any ideas?
[SuperR Kitchen] SuperR.:
Maybe [MENTION=1162986]Captain_Throwback[/MENTION] can help out with the A9 deodexing. Sadly I don't have that device so I won't be much help.
[SuperR Kitchen] ast11:
[MENTION=1162986]Captain_Throwback[/MENTION], could you look over my steps and let me know if I'm missing anything?

htc one a9 - AT&T branded model, unlocked and s-off

I start by flashing the stock att ruu (6.0.0 -- 1.27.502.5) and then flashing twrp. No other modifications.

I am using 1.0.2.5 of kitchen. I make a new project and have kitchen pull the rom files from twrp directly.

I get a system.img, boot.img, and recovery.img

It extracts system.img. I say NO to sparse dat images, then select set_metadata

At this point I can create a full ROM zip and it'll boot fine.

But I want to deodex it, so I select the deodex option and I let it finish.

I then go into the boot/recovery menu and try to disable dm-verity and forcencrypt. But it gives me an error "grep: fstab.qcom: permission denied"

I restart kitchen as root and try again. this time it works

I build the full rom zip, zip align both apps and framework, and then flash in twrp

But when I boot I get kicked into bootloader mode and I get an error up top. "init fs_mgr_mount_all failed"

Also. I'm trying to deodex this rom so I can install xposed on it. I get a bootloop if I install it on the stock odex rom. I know I can use the unlocked 6.0.1, but I want to use the stock att rom for carrier specific features. Will deodexing help at all?
[SuperR Kitchen] JochenP:
i have success only with kitchen v1.0.2.5 this way (no root):

create new project

fresch copy of boot.img and system.img (from twrp backup of untouched ROM: pull boot.emmc.win and system_image.emmc.win and rename)

1. unpack boot.img and disable dm-verity and forcencrypt - repack later (they will appear green)

2. use ROM-Tools for extracting System (by name with boot.img) and deodex and root system (spares_dat no -> set_metadata)

3. repack now boot.img

4. build now your full ROM zip

you have to check during deodexing process if there are errors (file not found etc. - with kitchen v1.0.2.6 happens more often for me)

this way it works perfect for me
[SuperR Kitchen] Captain_Throwback:
I don't have the device anymore either.

But I do recall having issues with the boot.img unpacking the last time I tried doing it with the kitchen. I think the issue is related to that somehow. It seems that the kitchen was unable to modify the fstab to remove dm-verity and forced encryption. Is the kitchen using sudo to make those edits? If not, that would explain the error.
[SuperR Kitchen] JochenP:
kitchen is able to modify/remove dm-verity and forced encryption only if system is not extracted yet - after extraction it is only possible with using sudo (otherwise you get red errors) but in that case i get a nonworking ROM .

that is why i have my special order
[SuperR Kitchen] vegetaleb:
While building the Rom it's stucked in the:

Determining system partition size...

Yes ADB USB is enabled and authenticated
[SuperR Kitchen] SuperR.:
v1.0.2.8

Changes:

Added requirement for build.prop to access Boot/Recovery tools menu.

Fixed some harmless but ugly errors when zipaligning if bootimg or recoveryimg directories for M exist.

The kitchen will no longer allow being run as root.

NOTE: Since M boot.img requires root to unpack/repack, we must now determine Android version before allowing any boot/recovery modification. That is why build.prop is now required to enter Boot/Recovery Tools menu. It can be located in /system or in the main rom directory with the boot.img if you don't want to work on a whole rom, but it must exist in one of those locations to enter the menu.

NOTE2: The kitchen is not intended to be run as root. There are things that could cause major problems if run as root. The kitchen uses sudo when root privelage is required for certain tasks. Therefore, the kitchen will now check if it is run as root and if so abort with an error message. If something doesn't work properly while running as a normal user, post your issues and I will do my best to sort them out.
[SuperR Kitchen] vegetaleb:
Thanks!

Can you help me with my error?

It looks like Superr is searching for an ADB device (Daemon restart....) but whatever I plug or not the HTC A9 it won't detect it and get stuck

ADB USB is enabled on the A9

Could it be ADB drivers on PC? I have latest minimal adb installed
[SuperR Kitchen] SuperR.:
Drivers are not the issue as this is not Windows. The kitchen includes adb and uses it instead of what you may have installed. It is possible I need to update it but I don't think that is the issue here. There are two more likely things going on. 1) Your device must be rooted to do what you are trying to do. 2) It is possible your device has a different response to the adb shell commands than the kitchen expects.

To resolve the issue, you can do a couple things. 1) Use one of the other options to determine the partition sizes. You can use 3791650816 if you want to enter it manually - credit to [MENTION=1162986]Captain_Throwback[/MENTION] for the A9 device tree. 2) Do some leg work for me to figure out how to get the info we need from your device. Let me know if you are interested in option 2. For now I suppose the easiest is to enter the number above manually when it asks :)
[SuperR Kitchen] JochenP:
Have you select 'use usb for data transfers?' on the device? Otherwise you get no communication via adb
[SuperR Kitchen] 3to4:
My rom zip is empty with 0 byte...

First, thank you for this tool. I am not a developer, but I always try to use rooted, deodexed deknoxed stock rom for all my devices. So, this tool is very precious.

I am now testing on Samsung stock firmware N7105XXUFNE3_N7105OXXFNE1_XEF (Android 4.4.2) downloaded from Sammobile with Kitchen v1.0.2.8.

I am using Linux Lite 2.6 (64bit)

My problem is the rom zip created is empty!! (I mean o byte)

I maybe doing something wrong. So, I will describe what I did.

1)	I created a folder named "superr) in my home directory, and extracted Super'R Kitchen to this folder. Then, I started the kitchen from the folder. The kitchen prompts me to install dependencies and 64 bit binaries. So, I installed them.

2)	Then, I created a project, and copied boot.img, cache.img, system.img and recovery.img in the project folder.

-	Selected 4) to extract rom – selected 2) system – then when prompted, extracted cache

-	Partition information – 4) and 1) set_metadata. Here I got an error. So, I need to enter manually in updater-script. (I have this information. So, that's ok.)

-	Rom Tools: I did – 1) deodex 1), 2) root, 3) busy box. Then, in debloat menu 7), I did 1) debloat and 3) knox.

3)	Then, I went to 8) Build Rom and selected 1) Build Full Rom zip

- First, zip aligned (zip aligned framework, too)

- Then, it displayed "preparing" – "building"

- When prompted if I wanted to sign the zip, I selected "y", then it said there was no memory, but I tried anyway. Then, to my surprise, it went through and it said "signed.zip has been created… "

I found a zip named "-signed.zip" in the project folder.

But, when I tried to check the inside of the zip, I got an error. Then, I saw that this zip had 0 byte data…. (I got the same problem with v1.0.2.7)

Maybe, this is because I have only 4GB of ram. How much ram should I have?

(But, I have read that rom flashes fine even when it is not signed.)

Or maybe, I am doing something wrong. Could you please help me?
[SuperR Kitchen] JochenP:
Thats too little - I needed 7-8gb
[SuperR Kitchen] Androidwizzard:
I don't agree, 4 GB is fairly enough to work with - my experience on my old pc.

Anyway - for Samsung devices beneath Android 5.0 - I'd suggest to go for an old tool/kitchen.

Please don't regard this as disrespect for [MENTION=5787964]SuperR.[/MENTION] and this great tool here, as it is state of the art on Lollipop and Marshmallow.
[SuperR Kitchen] vegetaleb:
Yep of course, I will try the Superr's solution with the magic number :good:

BTW all I want to do is to deodex my stock rom so I can finally use xposed, doing a custom app+private app is enough or I need to build a full rom?
[SuperR Kitchen] 3to4:
Thank you!! I will use SuperR's Kitchen when I upgrade to Lollopop.

Anyway, as I have a dual boot with Windows 7 and Linux, and Windows 7 is still 32bit. So, I don't feel like adding more ram for this purpose only.
[SuperR Kitchen] vegetaleb:
I am noob with Linux on virtualbox, what's the easiest way to add a folder (where superr kitchen is) to work with?
[SuperR Kitchen] JochenP:
extract downloaded zipped folder and move it to desktop :)

[MENTION=718594]super[/MENTION]R: version 1.0.2.8 doesn't work for HTC one A9 because kitchen doesn'tallow to extract boot.img before ROM is exctracted. After extraction i'm not able to change dm-verity and forcencrypt.

Please have a look my post: #2143
[SuperR Kitchen] vegetaleb:
I am using Mint Linux in Virtual Box, so HDD is virtual, I have to mount the folder where Superr is but it's a pain in the a** everytime
[SuperR Kitchen] SuperR.:
Please send a link to the A9 firmware you are using so I can have a look.

edit: If you are starting with RUU, please extract the system.img/boot.img first and send a link to that. I have no experience with RUU and don't have time to research and learn at the moment. Additionally, please make sure I don't need to register for anything to download the link you send. Thanks

edit2: I did a quick search and found the DECRYPT RUU tool from [MENTION=1162986]Captain_Throwback[/MENTION]. Going to give it a try with the AT&T A9 RUU.

edit3: Awesome tool [MENTION=1162986]Captain_Throwback[/MENTION]. Worked flawlessly :)

I found the issue with forceencrypt and dm verity. Will be pushing an update as soon as I get a chance.
[SuperR Kitchen] SuperR.:
v1.0.2.9

Changes:

Fixed dm verity and forceencrypt not being allowed to be removed.

Cleaned up code for M based roms using sudo.
[SuperR Kitchen] JochenP:
WOW - that was fast !

Boot Tools Menu now without errors.

only blemishes during cleanup:

----------------------------------------------------

Cleaning up ...

----------------------------------------------------

find: "/home/jogy/Schreibtisch/SuperRs_Kitchen_v1.0.2.9/superr_1.029/bootimg/ramdisk/sbin": Keine Berechtigung

find: "/home/jogy/Schreibtisch/SuperRs_Kitchen_v1.0.2.9/superr_1.029/bootimg/ramdisk/data": Keine Berechtigung

i will test now flashing the new ROM.zip (and hope for no loops)

Edit:

No success - A9 loops after optimizing apps - is it possible to workaround this?

Deodexing in kitchen v1.0.2.5/v1.0.2.6 works for this device... :crying:

[MENTION=2390514]vegetaleb[/MENTION]

i'm using Mint 64bit also in a VirtualBox but everything happens in this box
[SuperR Kitchen] jivany:
Hi im a noob to linux and tried googleing and reading previous post but still lost.... can u tell me what steps to star the program ? I installed ubuntu 15.10 gnome downloaded the superr newsest file. Extracted in downloads. Now i open terminal and type cd home/downloads/supperr .... and its says superr is not in location. Should i extract it somewhere else in system or do i type a different cmd. Lol i need help. Rusty on ubuntu its been a while
[SuperR Kitchen] jivany:
My situation
[SuperR Kitchen] Androidwizzard:
Just double tap the terminal symbol in extracted kitchen folder
[SuperR Kitchen] The Sickness:
Just navigate to where the superr script is...open terminal and type

./superr
[SuperR Kitchen] jivany:
Im doing that and gedit pops up
[SuperR Kitchen] jivany:
See look
[SuperR Kitchen] jivany:
I got it it was the . Period i had to put infront of slash

---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------

Sudo password?

Nvrmind got password lol...... edit how do i port a rom on this im reading just not sure what im reading lol