Develop Bugs

[Q] Creating a Kernel update zip file

Ok I'm a bit confused. After hours upon hours of trying, I have yet to successfully create a WORKING update.zip file for flashing a kernel.
I'm trying to create an update.zip file for the 2.6.35.10 kernel from the leaked T-Mobile US Gingerbread 2.13.531.5 ROM.
I properly unpacked the boot.img from the ROM, and my updater-script file seems correct, then I create the zip, sign it and flash thru CWM. The update completes without errors, however, when I reboot the phone, it still says I have 2.6.32.28. I'm stuck. My updater-script is as follows:
Code:
ui_print("");
ui_print("T-Mobile US - G2 Kernel Update");
ui_print("Kernel Version: 2.6.35.10");
ui_print("Prepared by: spyral");
ui_print("");
ui_print("Using: AnyKernel Updater by Koush.");
ui_print("");
set_progress(1.000000);
ui_print("Clearing dalvik and boot cache ...");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/boot-cache");
ui_print("Extracting System Files...");
set_progress(2.000000);
mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("system", "/system");
unmount("/system");
set_progress(5.000000);
ui_print("");
ui_print("Extracting Kernel files...");
package_extract_dir("kernel", "/tmp");
ui_print("Installing kernel...");
set_progress(6.000000);
set_perm(0, 0, 0777, "/tmp/dump_image");
set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");
set_perm(0, 0, 0777, "/tmp/mkbootimg");
set_perm(0, 0, 0777, "/tmp/unpackbootimg");
run_program("/tmp/dump_image", "boot", "/tmp/boot.img");
run_program("/tmp/unpackbootimg", "-i", "/tmp/boot.img", "-o", "/tmp/");
run_program("/tmp/mkbootimg.sh");
write_raw_image("/tmp/newboot.img", "boot");
set_progress(10.000000);
ui_print("Done!");
I've tried multiple times, with no luck. Any ideas?

Btw, sorry if I posted this in the wrong forum Mods... feel free to move it if need be. I'm still learning the ropes of this place.
Sent from my HTC Vision using XDA Premium App

Nothin so far, huh?
Sent from my HTC Vision using XDA Premium App

Still nothin on this??
Sent from my HTC Vision using XDA Premium App

Question about HTC Kitchen

Messing around with the HTC Kitchen and I am getting an error when trying to build a ROM.
Error is:
Code:
format() expects 3 args, got 2
(status 7)
installation aborted
Any ideas?

Find the line it is referring to in the update(r) script. Should be the 7th line as it tells you that. There is probably a comma missing between the numbers in the parenthesis

This is what the script is
Code:
format("MTD", "cache");
format("MTD", "boot");
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
format("MTD", "userdata");
mount("MTD", "userdata", "/data");
package_extract_dir("data", "/data");
set_perm(1000, 1000, 0771, "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
format("MTD", "system");
mount("MTD", "system", "/system");
package_extract_dir("system", "/system");
I try taking out the format lines, and I get the same error except on mount() this time.

Did you run the script checker?

Don't remove the lines manually... open your kitchen and change " the wipe status if your ROM"

Vinchenzop said:
Did you run the script checker?
Click to expand...
Click to collapse
Script checker only works for update-scripts' not updater-scripts. At least to my understanding... unless there is another one out there ? I am running HTC Android Kitchen, v0.161 on Ubuntu btw.

Flashable ZIP How To?

How do you make flashable zip?
i have alot of mods on my arc s and i want them all in one and flashable..

http://forum.xda-developers.com/showthread.php?t=1374394
Flashable Zip

In few words:
You make a zip file with the order of how the files go.
You make an updater-script which are the instructions for CWM to flash the correct order.
You sign it and that's it.
Everything is in the tutorial XperienceD posted.

XperienceD said:
http://forum.xda-developers.com/showthread.php?t=1374394
Flashable Zip
Click to expand...
Click to collapse
IM sorry but im kinda slow... in the "Flashable Clockwork Mod (CWM) zip:"
TO UNDERSTAND UR GUIDE I OPEN SOME SCRIPT TO GET AN IDEA BUT I FOUND SOME LINES THAT IS NOT INCLUDED IN YOUR EXAMPLE.
LIKE THESE:
show_progress(1.000000, 0);
set_progress(0.125000);
mount("MTD", "system", "/system");
package_extract_file("fix_permissions", "/tmp/fix_permissions");
set_perm(0, 0, 0777, "/tmp/fix_permissions");
WHAT IS show_progress(1.000000, 0); AND set_progress(0.125000); ??
I GUESS mount("MTD", "system", "/system") IS THE SAME AS run_program("/sbin/mount", "/system"); ??
AND ALSO GUESS THAT package_extract_file("fix_permissions", "/tmp/fix_permissions"); AND set_perm(0, 0, 0777, "/tmp/fix_permissions"); IS FOR THE PERMISSIONS, IF U HAVE IN UR ZIP RIGHT?
I DONT REALLY UNDERSTAND THOSE OR I CAN JUST IGNORE THEM?

[Q] - Impossible to flash stock rom

I have been using CM-based roms since I first got my i9195 in September and left TW stock rom behind. But I now decided to go back to stock and I just can't.
My phone has no Knox.
Each time I try to flash ANY recent stock rom with Odin, I get this:
The phone displays
Code:
ODIN : Invalid ext4 image
Odin 3.07 and 3.09 gives
Code:
<ID:0/013> Added!!
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> SingleDownload.
<ID:0/013> rpm.mbn
<ID:0/013> NAND Write Start!!
<ID:0/013> tz.mbn
<ID:0/013> boot.img
<ID:0/013> recovery.img
<ID:0/013> system.img.ext4
<ID:0/013> NON-HLOS.bin
<ID:0/013> cache.img.ext4
<ID:0/013> hidden.img.ext4
<ID:0/013> FAIL! (Ext4)
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Heimdall
Code:
Downloading device's PIT file...
PIT file download successful.
Uploading HIDDEN
62%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: HIDDEN upload failed!
It ALWAYS happens on hidden.img.ext4.
I tried different stock roms (after removing KNOX) - every time it's the same thing.
I tried removing this hidden partition from the rom - rom flashed, but got stuck on Samsung logo.
I tried converting stick Odin format to flashable CWM zip - rom flashed, but got stuck on Samsung logo.
Non-stock roms flash and work perfectly fine.
I am out of ideas. Do you have any?

Here is Odin guide. It should help.
http://forum.xda-developers.com/showthread.php?t=1372414
Sent from my Hudl HT7S3 using Tapatalk
---------- Post added at 09:47 PM ---------- Previous post was at 09:47 PM ----------
I'd like to know how to do this myself. If you figure it out. Let us know in thread please.
Sent from my Hudl HT7S3 using Tapatalk

same problem here.
can't flash stock rom..
1.
and this is what odin says
2. St*pid anti spam
I flashed couple of times, and with out any problem.
just to add, no help with Kies. tried to do firmware upgrade, but when i enter model number GT-I9195
and then in next screen s/n number, says 'GT-I9195' dose not support initialising
the only way i was able to bring it back to life was to flash a CWM. (don't know how i think of that)
after that phone booted normally, but still can't flash rom via odin.
and Kies is waste of time because it even won't recognise my phone. no connection what so ever. Win pop's up auto play window, and I'm already browsing internal storage, but Kies is still trying to recognise phone.. after about 15 min it says to reboot my phone, because it can't connect :laugh:
Samsung and their stuff. Pffff...
but to be back with real problem. haven't figure out this problem yet. but will try to re flash same stock rom, to see if it's a rom problem or phone it self. I'm guessing the partition table is changed for this new builds of rom's so it can't be flashed. or some other wired stuff.
if someone has some good advice, or even better, has an answer how to flash this new stock rom..

wizard.no.84 said:
just to add, no help with Kies. tried to do firmware upgrade, but when i enter model number GT-I9195
and then in next screen s/n number, says 'GT-I9195' dose not support initialising
Click to expand...
Click to collapse
Don't use Kies. It will punch you in the face with KNOX. Oh, wait... I see form you screenshots It already did...
Anyway, I also thought it might be changed partition layout, but that would be strange because it would also prevent other people to upgrade form stock to newer stock... Hmm...
In the meantime, I tried CWM-flashing this http://forum.xda-developers.com/showthread.php?t=2552363 and, unlike my modded stock roms based on newer bases, this did work (not on PhilZ though). I am running it now, but as I said - this is a bit outdated and does not solve the main problem.

Knox is a least of my problem.. i can remove it after, but i don't know whats the deal..
I'm downloading free region rom "X.." and the one I already have in the phone and try to flash them.
but knowing server down limit, it will take a while.

wizard.no.84 said:
Knox is a least of my problem.. i can remove it after, but i don't know whats the deal..
Click to expand...
Click to collapse
No, you can't. You can remove apps but Knox is there to stay and your Void Warranty flag is already tripped. Just look at your bootloader screenshot.
But on the bright side - you have nothing more to lose at this point

impactor said:
But on the bright side - you have nothing more to lose at this point
Click to expand...
Click to collapse
:laugh::laugh::laugh::crying: that's true :good:

OK, I see that you are using a PIT file. Was there the "Re-Partition" also enabled?
I never tried the scenario above I always flash new stock FW as a single-file package and browse it via Odin AP button.

ladislav.heller said:
OK, I see that you are using a PIT file. Was there the "Re-Partition" also enabled?
Click to expand...
Click to collapse
I don't think I am using a PIT file. Where do you see it? Re-Partition was always disabled.
ladislav.heller said:
I never tried the scenario above I always flash new stock FW as a single-file package and browse it via Odin AP button.
Click to expand...
Click to collapse
Which is what I am doing in the part describing Odin flashing.

Here's some more specifics:
ladislav.heller said:
Easily:
You did not say nothing about Odin version you used.
Click to expand...
Click to collapse
impactor said:
Odin 3.07 and 3.09 gives
Click to expand...
Click to collapse
ladislav.heller said:
Nothing about Samsung drivers version, Kies presence, etc.
Click to expand...
Click to collapse
As indicated, I did that in Windows and in Linux and the process stops at the same stage, which suggests driver version irrelevant.
In case this assumption is wrong: on Windows it is Kies 2.6.2.14014_7 and driver 2.11.7.
ladislav.heller said:
You did not specify WHAT firmwares you exactly tried, from where you downloaded them.
Click to expand...
Click to collapse
FTM I9195XXUBNB3
EVR I9195XXUBNB3
and one of the old I9195XXUBMJ7
Downloaded from here: http://samsung-updates.com/device/?id=GT-I9195 and samfirmware.com
ladislav.heller said:
Were the downloaded firmwares corrupt or not? Did you try to unpack them manually?
Click to expand...
Click to collapse
Not corrupt, as suggested by several different firmwares tried.
Yes, I unpacked them manually in order to remove knox. Like so: http://forum.xda-developers.com/showthread.php?t=2549357
Also, author of that guide did the whole rom-deknoxing by himself for me, too, and the result was the same.
The rest of your questions relate to CWM flashing method.
ladislav.heller said:
You did not say, how you built your modded ROM in Kitchen.
Click to expand...
Click to collapse
I tried some, and I tried no modifications. Same result.
ladislav.heller said:
You did not send me the update script for you modded ROM.
Click to expand...
Click to collapse
update, or updater? Here is the later one:
Code:
show_progress(0.1, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p21");
mount("ext4", "EMMC", "/dev/block/mmcblk0p21", "/system");
package_extract_dir("system", "/system");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/chcon");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/cmp");
symlink("toolbox", "/system/bin/cp");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/dmesg");
symlink("toolbox", "/system/bin/du");
symlink("toolbox", "/system/bin/freshsebool");
symlink("toolbox", "/system/bin/getenforce");
symlink("toolbox", "/system/bin/getevent");
symlink("toolbox", "/system/bin/getprop");
symlink("toolbox", "/system/bin/getsebool");
symlink("toolbox", "/system/bin/grep");
symlink("toolbox", "/system/bin/hd");
symlink("toolbox", "/system/bin/id");
symlink("toolbox", "/system/bin/ifconfig");
symlink("toolbox", "/system/bin/iftop");
symlink("toolbox", "/system/bin/insmod");
symlink("toolbox", "/system/bin/ioctl");
symlink("toolbox", "/system/bin/ionice");
symlink("toolbox", "/system/bin/kill");
symlink("toolbox", "/system/bin/ln");
symlink("toolbox", "/system/bin/load_policy");
symlink("toolbox", "/system/bin/log");
symlink("toolbox", "/system/bin/ls");
symlink("toolbox", "/system/bin/lsmod");
symlink("toolbox", "/system/bin/lsof");
symlink("toolbox", "/system/bin/md5");
symlink("toolbox", "/system/bin/mkdir");
symlink("toolbox", "/system/bin/mount");
symlink("toolbox", "/system/bin/mv");
symlink("toolbox", "/system/bin/nandread");
symlink("toolbox", "/system/bin/netstat");
symlink("toolbox", "/system/bin/newfs_msdos");
symlink("toolbox", "/system/bin/notify");
symlink("toolbox", "/system/bin/printenv");
symlink("toolbox", "/system/bin/ps");
symlink("toolbox", "/system/bin/reboot");
symlink("toolbox", "/system/bin/renice");
symlink("toolbox", "/system/bin/restorecon");
symlink("toolbox", "/system/bin/rm");
symlink("toolbox", "/system/bin/rmdir");
symlink("toolbox", "/system/bin/rmmod");
symlink("toolbox", "/system/bin/route");
symlink("toolbox", "/system/bin/runcon");
symlink("toolbox", "/system/bin/schedtop");
symlink("toolbox", "/system/bin/sendevent");
symlink("toolbox", "/system/bin/setconsole");
symlink("toolbox", "/system/bin/setenforce");
symlink("toolbox", "/system/bin/setprop");
symlink("toolbox", "/system/bin/setsebool");
symlink("mksh", "/system/bin/sh");
symlink("toolbox", "/system/bin/sleep");
symlink("toolbox", "/system/bin/smd");
symlink("toolbox", "/system/bin/start");
symlink("toolbox", "/system/bin/stop");
symlink("toolbox", "/system/bin/sync");
symlink("toolbox", "/system/bin/top");
symlink("toolbox", "/system/bin/touch");
symlink("toolbox", "/system/bin/umount");
symlink("toolbox", "/system/bin/uptime");
symlink("toolbox", "/system/bin/vmstat");
symlink("toolbox", "/system/bin/watchprops");
symlink("toolbox", "/system/bin/wipe");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 06755, "/system/bin/ip");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pair_devlist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm_recursive(0, 0, 0755, 0644, "/system/vendor/firmware");
set_perm(0, 2000, 0755, "/system/vendor/firmware");
set_perm(0, 2000, 0755, "/system/vendor/lib");
set_perm(0, 2000, 0755, "/system/vendor/lib/hw");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
show_progress(0.1, 10);
show_progress(0.2, 0);
package_extract_file("boot.img", "/dev/block/mmcblk0p13");
show_progress(0.2, 10);
unmount("/system");
ladislav.heller said:
Bootloop maybe caused by kernel. Which kernel you are using?
Click to expand...
Click to collapse
Stock.
Thanks for taking the interest in it.

Odin part:
Did you UNPACKED the original stock FW and removed the Knox bootloader files?
What did you do next? Repacked them into TAR with MD5 checksum? If yes, what commands you used?
Kitchen part:
Have you replaced the kernel (boot.img) + needed modules in the result ZIP package to Arco's one or another modded kernel? Because with the stock kernel it won't work.

X.. rome worked
i just flashed open region rom and got PASS
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
wtf?

ladislav.heller said:
Odin part:
Did you UNPACKED the original stock FW and removed the Knox bootloader files?
What did you do next? Repacked them into TAR with MD5 checksum? If yes, what commands you used?
Click to expand...
Click to collapse
Code:
unzip *.zip
rm -rf SS_DL.dll
tar -xvf *.tar.md5
rm -rf aboot.mbn
rm -rf sbl1.mbn
rm -rf sbl2.mbn
rm -rf sbl3.mbn
rm -rf *.tar.md5
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > name.tar
And then I flash, because if I add md5, Odin will display some error message in Korean while loading it.
ladislav.heller said:
Kitchen part:
Have you replaced the kernel (boot.img) + needed modules in the result ZIP package to Arco's one or another modded kernel? Because with the stock kernel it won't work.
Click to expand...
Click to collapse
You mean I need to replace the stock kernel, because it will not work if flashing with CWM?
If that's the case, then can I use the JB version from here? http://forum.xda-developers.com/showthread.php?t=2568479

impactor said:
Code:
unzip *.zip
rm -rf SS_DL.dll
tar -xvf *.tar.md5
rm -rf aboot.mbn
rm -rf sbl1.mbn
rm -rf sbl2.mbn
rm -rf sbl3.mbn
rm -rf *.tar.md5
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > name.tar
And then I flash, because if I add md5, Odin will display some error message in Korean while loading it.
You mean I need to replace the stock kernel, because it will not work if flashing with CWM?
If that's the case, then can I use the JB version from here? http://forum.xda-developers.com/showthread.php?t=2568479
Click to expand...
Click to collapse
Odin part - try these commands:
Code:
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > name.tar
md5sum -t name.tar >> name.tar
mv name.tar name.tar.md5
And use name.tar.md5 in Odin.
Kitchen part:
Use this kernel.

ladislav.heller said:
Odin part - try these commands:
Code:
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > name.tar
md5sum -t name.tar >> name.tar
mv name.tar name.tar.md5
And use name.tar.md5 in Odin.
Click to expand...
Click to collapse
As I said, if I do this, Odin won't even open file, just return an error in Korean. Tried it already on several roms.
ladislav.heller said:
Kitchen part:
Use this kernel.
Click to expand...
Click to collapse
Thanks. Do I just replace files form the zip in the kitchen's work folder, or do I need to do it some other way?

impactor said:
As I said, if I do this, Odin won't even open file, just return an error in Korean. Tried it already on several roms.
Thanks. Do I just replace files form the zip in the kitchen's work folder, or do I need to do it some other way?
Click to expand...
Click to collapse
Odin part:
Are you using Odin v3.09 ?
BTW I have no idea
Kitchen part:
Yes, replace in working folder before the build of final ROM.
Replace everything and when there is something extra in f4k kernel, also add those files to the correct directories.

I had this to make sure the Stock one you are flashing with ODIN is for your device as I tried a few here in the UK
And only the BTU ones work on my device for some reason as tried EE (Orange who is my sim card with) and doesnt work
Failing that then use Recovery via Kies
Similar to this as I dont have the right link handy :LINK

If you will face this "hidden.ext.img4" problem again, solution is simple. The complete firmware was correctly written and u just need to boot it for the first time.
When the error happens, dont reboot the phone. Just unplug and replug the usb cable and flash a stock recovery image (just the recovery.img file packed in a *.tar.md5 file) with odin. Flashing will complete and when the phone will reboot, you have to go in recovery mode with the 3 button trick. Your phone will automatically complete the flashing procedure and firmware will be installed and booted.

I dont think that will work. Because when i got that "hiddent.ext" error, and when i flashed the CWM and rebooted, i was back at the beginig. Didn't check build in "settings-about" but im prety sure i was on old rom, (not the new flash) because root was still present.
Only now when i flashed it successfully the root is gone
Sent from iPhone

It work, surely. Tried it several times on my i9195 the file you need to flash is the stock recovery file extracted from the firmware image you are installing.
I've modified my previous post adding more details. I don't know if i can upload and post an example recovery image for copyright issues.

error 6 while trying to use set_perm in updater-script

Heloo, i have hard times finding a solution to my problem, here my script :
Code:
ui_print("Starting...");
mount("ext4", "EMMC", "/dev/block/mmcblk0p41", "/system");
ui_print("...system mounted");
package_extract_dir("modifiedframework", "/system/framework");
ui_print("...framework-res.apk transfered");
set_perm(0, 0, 0644, "/system/framework/framework-res.apk");
ui_print("...permissions set");
unmount("/system");
ui_print("...system unmounted");
it return : Updater process ended with ERROR: 6
and the script is working fine if i remove the line
Code:
set_perm(0, 0, 0644, "/system/framework/framework-res.apk");
any help is welcome, thanks you

thanks for help... i have found the solution, https://github.com/mission-impossible-android/mission-impossible-android/issues/50. i'm using this update-binary and now it is working.

@linpinpin
I'm facing exactly the same issue with TWRP on Xiaomi. set_perm(...); causing error: 6 regardless it's syntactically fine.
Which updater binary can I use for my device?

i use this one https://github.com/mikeperry-tor/mi...ult/META-INF/com/google/android/update-binary click on download
i'm using a xiaomi also