[4.4 ROM Flash] bypass set_metadata_xxx fails - Android Software/Hacking General [Developers Only]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before we can take a bite on the new KitKat, some of us may encounter the set_metadata.. error at flashing.
Problem:
The new updater-scritpt use set_metadata and set_metadata_recursive to assign the permissions to the newly copied files.
Most of the existing /system partition doesn't support the "capabilities" option. Script in android/build would assign 0x00 to "capabilities".
However, assigning a "capabilities" with 0x00 to the unsuported partition also cause error!
If you are lucky, you might find an updated custom recovery to solve that.
For those who don't have a workable recovey or don't want to update the recovery yet. Here is a solution
Solution:
I patched the script when building my 4.4 rom for GT-7.7. The included "update-binary" would solve that problem at flashing.
Open the zip of the ROM or gapps. Replace the file in /META-INF/com/google/android with this one.
Now you can flash the 4.4 rom and gapps without an recovery update..
It works for cm11 & aosp based ROMs and gapps.
Cheers!
Edit:
Silly me, how can it be hardware independent... This one is compiled for armv7. Different cpu surely need a recompile.
Here is the change in the source: http://forum.xda-developers.com/showpost.php?p=47692333&postcount=15

Thanks dude
Sent from my LG-P500 using xda premium

Thanks daniel_hk
It works fine on my SGS :good:

@daniel_hk
Thanks for this. But it does not work for my armv6 device (lg p500). Could you please tell us what you changed, so that it can be "ported" to older devices. I have read that some recoveries have merged changes to source, but these devices do not yet have a ported version. So if you have time, this would be much appreciated by my device community.
Sent from my LG-P500 using Tapatalk 2

ibub said:
@daniel_hk
Thanks for this. But it does not work for my armv6 device (lg p500). Could you please tell us what you changed, so that it can be "ported" to older devices. I have read that some recoveries have merged changes to source, but these devices do not yet have a ported version. So if you have time, this would be much appreciated by my device community.
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
The theory of what I have done is already mentioned in the thread.
In details, I changed the file in the source of the recovery. The update-binary is generated there.
In the function ApplyParsedPerms, when encounter a 0x0 for "capabilities", I drop the flag .
The attached file was from the rom I built.
For ROMs using the CyanogenMod cm-11 or AOSP 4.4 source, it should work.
Send me the link of your ROM which fail. Let me take a look.

Thank you so much. But I may have spoken too soon. I found an updated recovery (4.3), and new update binary for my phone. I will try it later to see if it works, before asking you to waste your time.
Sent from my LG-P500 using Tapatalk 2

Ok, I tried but had no success. So here is a link to the rom:
http://jenkins.androidarmv6.org/job/submission-test/755/
Again, thanks.
Sent from my LG-P500 using Tapatalk 2

ibub said:
Ok, I tried but had no success. So here is a link to the rom:
http://jenkins.androidarmv6.org/job/submission-test/755/
Again, thanks.
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
Is your error "set_metadata_recursive"... "fail"? Can you list the exact messages at flash. Take a photo to avoid typing.
I think you might get an assert error not set_metadata related

Yeah, it's set_metadata_recursive error or fail. I think my recovery will copy messages to SD. Will record soon. The devs for this device are now trying to add set_metadata tags in boardconfig.mk, and then use set metadata =false. But I'm not really sure if that would be an actual fix, or just a temporary work around to get it to flash. So I'd rather try to do it your way. Just wish my 32-bit system would compile newer Android.
Sent from my LG-P500 using Tapatalk 2
---------- Post added at 06:37 AM ---------- Previous post was at 06:06 AM ----------
Ok, here's my recovery log.
Sent from my LG-P500 using Tapatalk 2
---------- Post added at 06:38 AM ---------- Previous post was at 06:37 AM ----------
http://www.mediafire.com/view/?dddwi6vtbo3a1fg
Sent from my LG-P500 using Tapatalk 2

ibub said:
Yeah, it's set_metadata_recursive error or fail. I think my recovery will copy messages to SD. Will record soon. The devs for this device are now trying to add set_metadata tags in boardconfig.mk, and then use set metadata =false. But I'm not really sure if that would be an actual fix, or just a temporary work around to get it to flash. So I'd rather try to do it your way. Just wish my 32-bit system would compile newer Android.
Sent from my LG-P500 using Tapatalk 2
---------- Post added at 06:37 AM ---------- Previous post was at 06:06 AM ----------
Ok, here's my recovery log.
Sent from my LG-P500 using Tapatalk 2
---------- Post added at 06:38 AM ---------- Previous post was at 06:37 AM ----------
http://www.mediafire.com/view/?dddwi6vtbo3a1fg
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
in line 1260:
-> ApplyParsedPerms: removexattr of /system/xbin/su to 0 failed: Operation not supported on transport endpoint
seems the file system doesn't support XATTR, remove a non exsist attr probably cause error.
Did the log come from my update-binary?
If so, you need to tell the rom developer to check the kernel source:
if the kernel support selinux and file system is EXT, you need the following
CONFIG_EXT4_FS_XATTR=y
or
CONFIG_EXT3_FS_XATTR=y
Either one must be enabled dependent on the file system.
If kernel doesn't support selinux, disable it.
For YAFFS, there might be similar config for kernel need to enable or disable
Good luck!

daniel_hk said:
in line 1260:
-> ApplyParsedPerms: removexattr of /system/xbin/su to 0 failed: Operation not supported on transport endpoint
seems the file system doesn't support XATTR, remove a non exsist attr probably cause error.
Did the log come from my update-binary?
If so, you need to tell the rom developer to check the kernel source:
if the kernel support selinux and file system is EXT, you need the following
CONFIG_EXT4_FS_XATTR=y
or
CONFIG_EXT3_FS_XATTR=y
Either one must be enabled dependent on the file system.
If kernel doesn't support selinux, disable it.
For YAFFS, there might be similar config for kernel need to enable or disable
Good luck!
Click to expand...
Click to collapse
No, that was the original update binary, built with the rom. I don't know for certain, but have read that the binary is specific to the chipset. Anyway, I'm gonna search through the commits to see if the xattr has been used. Remember seeing it... somewhere. Again thanks.
Sent from my LG-P500 using Tapatalk 2

ibub said:
No, that was the original update binary, built with the rom. I don't know for certain, but have read that the binary is specific to the chipset. Anyway, I'm gonna search through the commits to see if the xattr has been used. Remember seeing it... somewhere. Again thanks.
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
I think you haven't try my update-binary. I don't know why you said it fail?
You better try my update-binary again. "capacities" is one of the xattr. update-binary is just a set of functions calling the kernel's routine to do
things. I don't know who told you its hardware related. I already point you out where in the source creating it. Take a look at that part of the source is what you needed...
It would not waste our time if you have tried.I don't know how to help if you don't try it.
Good luck!

Thank you. I did try with your binary previously. But I will try again with an updated recovery and your binary. And then copy the recovery log again. Sorry for misunderstanding.
Sent from my LG-P500 using Tapatalk 2
---------- Post added at 09:56 PM ---------- Previous post was at 09:08 PM ----------
Ok, I tried again with no luck. And here is the log:
http://www.mediafire.com/view/?hcibdddd1vxtcr3
Again... thanks.
Sent from my LG-P500 using Tapatalk 2

Ok, I don't see any indication in the log as to what caused the error with binary. But I opened it in hex viewer. On line 044f21 the platform is listed as arm v7. I think my arm v6 device cannot use this. Anyway, thanks for helping. I guess I have MORE research to do.
Sent from my LG-P500 using Tapatalk 2

ibub said:
Thank you. I did try with your binary previously. But I will try again with an updated recovery and your binary. And then copy the recovery log again. Sorry for misunderstanding.
Sent from my LG-P500 using Tapatalk 2
---------- Post added at 09:56 PM ---------- Previous post was at 09:08 PM ----------
Ok, I tried again with no luck. And here is the log:
http://www.mediafire.com/view/?hcibdddd1vxtcr3
Again... thanks.
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
Just returned and studied your log. It is not set_metadata fail issue. The update-binary can not run on the devices
I found that p500 use Qualcomm MSM7227 (ARM11) on the web. I can't find the cm11 device tree for p500 nor the kernel source. However, I think the update-binary is not work on the kernel and/or cpu.
The easiest way would be including the following commit and rebuild again: (I simplify it for you, just change one line)
Change the file in (cm11 source):
<cm11 source dir>/bootable/recovery/updater/install.c
in line 694 (under the function ParsePermArgs(int argc, char** args):
694:- parsed.has_capabilities = true;
694:+ parsed.has_capabilities = false;
That is the simpliest way I can think of to fix the set_metadata fail in your device.
Good luck!

Thank you so much. I would have never found it. Now I just need to fork the repo, make the change, init repo, build/envsetup sh, sync, add to local manifest, and try to compile. ... Or just submit a pull request. That code is interesting. I think I'm gonna learn some more soon.
Sent from my LG-P500 using Tapatalk 2

I have a galaxy SIII (at&t). I have gotten this error instantly when trying to flash a 4.4 rom. Once I replace the aforementioned file with the contents of your zip, won't I need to re-zip the rom and somehow sign it? And if so, do you have a zip "signer"?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

thanks :good: working on my tab with CM11

Thanks bro.

Ahah too bad I saw the thread only today.
I had this error yesterday and had to waste a lot of time finding a solution. I finally had to flash a stock recovery , a stock system partition and adb sideload the update to resolve it without losing any data.
Sounds like your solution would have been a lot easier, I hope people can see it before attempting more complicated things like me

Related

bootanimation.zip

Are bootanimation.zip files os specific? I just found a few files on my old laptop that I used to throw in when I was running froyo. Can I use these in a gingerbread rom?
Sent from my SGH-T959V using XDA App
dbldown7 said:
Are bootanimation.zip files os specific? I just found a few files on my old laptop that I used to throw in when I was running froyo. Can I use these in a gingerbread rom?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
They'll work fine if you're using a kernel that supports them like bhudven's kernels.
Thanks man. I'll give em a shot.
Sent from my SGH-T959V using XDA App
What about poweron.wav? It doesn't want to play...
Sent from my SGH-T959V using XDA App
dbldown7 said:
What about poweron.wav? It doesn't want to play...
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Make sure the case & permissions are correct. It should be PowerOn.wav, the permissions should be -rw-r--r-- with root as the owner and group.
You guys are AWESOME!!! I truly appreciate the quick informative responses. Will slam the THANKS button when I get to a PC.
Sent from my SGH-T959V using XDA App
No worries, glad you got it working.
Sent from my SGH-T959V using XDA App
Custom Bootanimation
I am running The SlimSaber 4.4.2 Rom. I am trying to build my own custom bootanimation that will advertise my business when I boot the phone. I have found alot of great forums on here thatexplain how to build and install your custom animation. Everytime I try it I either get a blank bootscreen, or install failed. I there some thing different, or unique I need to do for the SGS4G?
I don't think there is anything special you need to do. You can look at what is there on the ROM itself -- /system/media/bootanimation.zip -- and compare it to what you have.
jeffsf said:
I don't think there is anything special you need to do. You can look at what is there on the ROM itself -- /system/media/bootanimation.zip -- and compare it to what you have.
Click to expand...
Click to collapse
I have taken those and built mine axactly like it, desc file, type of photoe format (png, jpg,etc etc) R zipped and get the failure. The only difference is the file size. Is there a specific file size to stay within?
AgainstTheFlow said:
I have taken those and built mine axactly like it, desc file, type of photoe format (png, jpg,etc etc) R zipped and get the failure. The only difference is the file size. Is there a specific file size to stay within?
Click to expand...
Click to collapse
If everything is the same as the existing bootanimation.zip, then it may be the way you are zipping it. Just a shot in the dark, but when zipping it and choosing the format/compression level, make sure to select "Store." This is what did it for me when mine wasn't working.
fingolfin14 said:
If everything is the same as the existing bootanimation.zip, then it may be the way you are zipping it. Just a shot in the dark, but when zipping it and choosing the format/compression level, make sure to select "Store." This is what did it for me when mine wasn't working.
Click to expand...
Click to collapse
Nope. Still fails. I dont know. I guess I will hit sites and see if I can get someone to look at it and build it for me
AgainstTheFlow said:
Nope. Still fails. I dont know. I guess I will hit sites and see if I can get someone to look at it and build it for me
Click to expand...
Click to collapse
Unless you want to post it here, then the only other thing I'd suggest is making sure you set permissions to rw-r-r and then restart. You've probably thought of that.
fingolfin14 said:
Unless you want to post it here, then the only other thing I'd suggest is making sure you set permissions to rw-r-r and then restart. You've probably thought of that.
Click to expand...
Click to collapse
No the permissions are wrong. Need to researh how to change them because they keep changing back Thanks
AgainstTheFlow said:
No the permissions are wrong. Need to researh how to change them because they keep changing back Thanks
Click to expand...
Click to collapse
Code:
# mount -o remount,rw /system
# chmod 644 /system/media/bootanimation.zip
# mount -o remount,ro /system
There might be something with SELinux as well, but I'd start with the above. Any clues in the output of dmesg at all? This would be before logcat would show anything.
If you're willing to attach the files here, I'll take a look at it. Also, I'll need the settings you wish to use.
sent from within the beast
I will have to load it to a URL when I get home.
Sent from my SGH-T959V using xda app-developers app
---------- Post added at 11:22 AM ---------- Previous post was at 11:14 AM ----------
This may be the proper one. If not then it will be when I get home. Try this link, of the pictures are of Terry's Computer Works , then it's the proper file.
https://www.dropbox.com/s/vr1it5ot1xr5rcm/bootanimation.zip
Sent from my SGH-T959V using xda app-developers app
Added to my DB. Will check it out when my PC is free. I'll post my findings shortly. Most likely will be a working bootanimation.zip.
sent from within the white knight
---------- Post added at 01:07 PM ---------- Previous post was at 12:30 PM ----------
Upon looking at the files, within the zip, I did notice one thing wrong. You had the folder bootanimation within the zip itself. That's what is causing you issues. Easy fix which I will do for you. Another thing I noticed is the image sizes. You're using 96 x 160. Normally with the SGS4G, the image size is 480 x 800 or you can use something larger. If you want, just send me the the original image you have in the center (the computer image) and what text you want on the top and bottom and I can re-do the images for you. Or, if you want, I can try and find something for you and you can provide me with the text you want and go from there. Either way, I'm here to help you out.
I will send you the originals when I get home. I have them at all sizes just trying to get a workable model to go from. Then I can tweek it with more animation.
Sent from my SGH-T959V using xda app-developers app
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
Thanks for looking at it
Sent from my SGH-T959V using xda app-developers app
AgainstTheFlow said:
I will send you the originals when I get home. I have them at all sizes just trying to get a workable model to go from. Then I can tweek it with more animation.
Sent from my SGH-T959V using xda app-developers app
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
Thanks for looking at it
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
No problem. Here's a little sample I have for you to show what I can do for you. Its a cleaner look IMO. If I could read what the bottom text says, I would have added that too. Let me know what you think though. Also, the image will appear smaller once it shows on your phone's screen which will also make it look cleaner than looking at it from a PC Monitor.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[TOOL]Kernel Flasher from Recovery Mode [V2.0] {Galaxy Y & Galaxy Y Duos}

Hi Guyz I compiled a script that can flash boot.img from CWM Recovery and it will not increaseCustom Bin Count.
You can Install Custom Kernel 1000000 times without increasing your Custom Bin Count.
Thanks to Koush for providing source: https://github.com/CyanogenMod/android_device_samsung_bmlunlock
Version 1.0
I have attached below a ZIP.
Replace the boot.img in the zip, with your boot.img, ZIP it and flash from CWM Recovery.
Download V1.0: http://forum.xda-developers.com/attachment.php?attachmentid=952982&stc=1&d=1332400029
I have tested it many times and it WORKS.
Version 2.0 is here with new features:
•Automatic backup of old boot.img/kernel when you flash a new boot.img/kernel.
The old boot.img can be found afterwards with OLDboot.img name.
•Automatic unmount of sdcard after flashing. (As requested by some users)
•No need to unzip and zip this version, just place this tool and boot.img on root of sdcard and flash tool from Recovery mode.
Instructions:
•To flash kernel/boot.img, just place Boot.img_flasher_V2.0_faqbly_2.zip and your boot.img on the root of your sdcard.
•Boot in CWM Recovery and flash Boot.ing_flasher_V2.0_faqbly_2.zip
•Your OLD boot.img will be backed up as OLDboot.img on your sdcard.
Download V2.0: http://forum.xda-developers.com/attachment.php?attachmentid=959669&d=1332425118
Both the versions are working perfectly you can use any version you like.
Confirmed by manojranjan2050 to be working on Galaxy Y Duos also.
PRESS THANKS IF YOU LIKE MY WORK.
...................Working just fine......
Is this kernel can be able to overclock
Sent from my GT-S5360 using xda premium
abhijitro said:
Is this kernel can be able to overclock
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
It is a flasher,not kernel.
Try it Yourself
abhijitro said:
Is this kernel can be able to overclock
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
It is not a KERNEL.
It is a tool to flash Kernel.
V 1.0 Place boot.img in my ZIP file to flash through CWM.
V2.0 Place boot.img and v2.0 ZIP in the root of sdcard and flash through CWM.
It works
Just used this to install "MerrukTechnology Kernel v.0.6 RC 80" and it works flawlessly!
now I'm overclocked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for this! this is great, soo we will have custom ROMs such as CM7/9 or hopefully MIUI
very GREAT job!!!
OC is not yet fully functioning,it has bugs till now
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
termagazis said:
very GREAT job!!!
Click to expand...
Click to collapse
Really good work,but any idea how do you explain coz it is so different than your perception
premolikeshtc said:
OC is not yet fully functioning,it has bugs till now
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
Really good work,but any idea how do you explain coz it is so different than your perception
Click to expand...
Click to collapse
ok i was wrong but i am not a dev.ALSO this is a different way than the roms zip we used.and i was talking for these zips and updater scripts.this tool here used some more file and different script to do this job.now if dev convert their zip with this tool options we will be able to flash rom and kernels together
great
great job sir.., i can using it to make a smple to working a2sd in my custom rom without odin flash tahnks sir
Great!
repencis said:
great job sir.., i can using it to make a smple to working a2sd in my custom rom without odin flash tahnks sir
Click to expand...
Click to collapse
More than 1000 Downloads but Thanks Meter still stuck at 100.
If you Like my work Press Thanks Guyzzz...
faqbly said:
More than 30 Downloads but just 3 Thanks.
If you Like my work Press Thanks Guyzzz.
Click to expand...
Click to collapse
I keep forgetting D:
Thanked!
<post deleted>
ronnieryan said:
thank you sir, anyways, can you provide a very accurate step by step procedure how to use this? its kinda difficult to understand if ur a newbie..
BTW, can i add this to page 2 of maroc-os kernel? this would be useful in flashing kernel, and all credits goes to you sir
can i?
Click to expand...
Click to collapse
you just open the zip(not exctract) delete the boot.img and drag and drop your boot.img.ready
ronnieryan said:
thank you sir, anyways, can you provide a very accurate step by step procedure how to use this? its kinda difficult to understand if ur a newbie..
BTW, can i add this to page 2 of maroc-os kernel? this would be useful in flashing kernel, and all credits goes to you sir
can i?
Click to expand...
Click to collapse
Yes, You can.
I would have used it myself and not uploaded but xda is a community of shareing and helping so I uploaded it.
This is all for you guyzzz.
i allready changed my rom and now its flashing kernel too.no more seperate flash with odin!!!!nice job!thanks again.
<post deleted>
faqbly said:
Hi Guyz I compiled a script that can flash boot.img from CWM Recovery and it will not increase Custom Bin Count.
Click to expand...
Click to collapse
for some odd reason I flashed many times already with ODIN: sometimes flash counter went up, often it remained the same. funny
ui_print("Boot.img flasher by faqbly @xda");
# copying files in ramdisk
package_extract_file("bmlunlock", "bmlunlock");
package_extract_file("boot.img", "boot.img");
set_perm(0, 0, 0755, "bmlunlock");
# mounting the sdcard
mount("vfat", "/dev/block/mmcblk0p1", "/sdcard", "rw");
ui_print("Flashing Boot.img");
# flashing
run_program("bmlunlock");
# back up old kernel to sd card before writing new one
run_program("/system/bin/dd", "if=/dev/block/bml7"), "of=/sdcard/old-boot.img";
unmount("/sdcard");
run_program("/system/bin/dd", "if=boot.img", "of=/dev/block/bml7");
ui_print("Done! Reboot system now!");
that's pretty decent. why no edify-script, which exchanges a kernel: backs up the old one to sd-card and dd's the new one (see above).
it was handily set to rw already ...
at the end of the day we should integrate it into temporary CWM if we have the sources.
Doky73 is thinking about doing that: http://forum.xda-developers.com/showpost.php?p=23766670&postcount=41
nobody could tell me wether the CWM modding sources by Skin1980 or motafoca are available, so we can integrate it with CWM.
a full nandroid should be a bit more automatic than separate fiddling with boot.img . but I think in CWM it inside some C++ binary or sth.
anyhow - this makes kernel testing a real ease, dude ! way cool
---------- Post added at 11:17 PM ---------- Previous post was at 10:31 PM ----------
premolikeshtc said:
that's good. Then what about Terma saying that kernel can't be flashed from CWM, as recovery is inside boot.img
Click to expand...
Click to collapse
a tough theoretical & philosophical challenge, if you follow his line of argument.
You deserve a "thank you" buddy. Awesome work!
Sent from my GT-S5360 using XDA
@mai77
Bin count does not increase if you flashed stock files. I've only ever used Odin once, to get back to stock. Count is still 0.
Anyway thanks to faqbly. Haven't tried yet but will come in handy soon. Pressed the button too.
Sent from my GT-S5360 using xda premium

[MOD] TeamViewer Quick Support 7.0.719 for Cyanogenmod / AOKP / AOSP ROMs

Hey :good:
I patched Teamviewer Quick Support APK (originally for Samsung ROMs) and signed it with Cyanogenmod platform keys.
Runs flawlessly on my SGS i9000 running CM9!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download (CWM flashable ZIP)
* Remember, you need at least 4+ MB of free space on /system to flash those ZIPs!
v7.0.719 ARMv7: http://d-h.st/BAF
Getting FC (force close) when app starts? Try this ARMv7 ZIP!
v7.0.719 ARMv6: http://d-h.st/NpF
Older builds: here​
How-to patch it yourself
http://forum.xda-developers.com/showpost.php?p=32375573&postcount=187​
Enjoy!
Why not sign it with your own key like a regular app dev so everyone can use it?
bradgog said:
Why not sign it with your own key like a regular app dev so everyone can use it?
Click to expand...
Click to collapse
Because this app requires some permissions that are granted only to applications that are signed with the same key as the platform (ROM).
What you're asking is impossible unfortunately.
"signature" A permission that the system grants only if the requesting application is signed with the same certificate as the application that declared the permission. If the certificates match, the system automatically grants the permission without notifying the user or asking for the user's explicit approval.
Click to expand...
Click to collapse
http://developer.android.com/guide/topics/manifest/permission-element.html
That being the case can you sign it with the platform key that Pete Alfonso is using on Bugless Beast?
theos0o said:
Because this app requires some permissions that are granted only to applications that are signed with the same key as the platform (ROM).
What you're asking is impossible unfortunately.
http://developer.android.com/guide/topics/manifest/permission-element.html
Click to expand...
Click to collapse
bradgog said:
That being the case can you sign it with the platform key that Pete Alfonso is using on Bugless Beast?
Click to expand...
Click to collapse
Did you try it and it's not working?
Keys look the same as CM
https://github.com/peteralfonso/platform_build/tree/jb/target/product/security
OP updated with ARMv6 flashable ZIP
thanks a lot!
works great with CM10 on my SGSII.
I am glad I can use this app now
hey i downloaded the zip to my galaxy tab (i know this is the sgs iii forum) and renamed the extension to apk, but i cant install it, the apk seems to be invalid. i am running cm10 do they not share the same signature?
edit: wait, those are cwm flashable?
Localhorst86 said:
hey i downloaded the zip to my galaxy tab (i know this is the sgs iii forum) and renamed the extension to apk, but i cant install it, the apk seems to be invalid. i am running cm10 do they not share the same signature?
edit: wait, those are cwm flashable?
Click to expand...
Click to collapse
Yep, CWM flashable.
And this is the general Android section not the GS3 one
Yeah, i just realized. Unfortunatelly it wont work on my gtab. The app fcs on launch (armv7 binary)
Sent from my GT-P7510 using xda app-developers app
Localhorst86 said:
Yeah, i just realized. Unfortunatelly it wont work on my gtab. The app fcs on launch (armv7 binary)
Sent from my GT-P7510 using xda app-developers app
Click to expand...
Click to collapse
If you can get & upload a logcat of the FC, I will check it tomorrow
Will do so when i am at home
Sent from my GT-P7510 using xda app-developers app
---------- Post added at 10:47 PM ---------- Previous post was at 09:59 PM ----------
here's the logcat.
uname -a
Linux localhost 2.6.36.4-cyanogenmod+ #1 SMP PREEMPT Mon Aug 13 09:42:21 EDT 2012 armv7l GNU/Linux
mine crashed too, usiing CM7. logcat:
https://www.box.com/shared/57f6353adde0bb2733ad
oh one more thing: the app FCs when someone has connected... they can see me for one sec, then the app crashes
EDIT: nevermind, i forgot to fix the libs permissions... ii didn't flash the zip, i extracted and copied, then changed permissions, but i miissed one .so file
———————————————————
i didn't mean to mock you or to offend you in any kind of way
The apk block JB rom, this is possible to modify too?
Ty.
i tried both versions and on my computer is coming out a black screen any ideas?
SGS II CM 10 Working!
Thanks!
Localhorst86 said:
Will do so when i am at home
Sent from my GT-P7510 using xda app-developers app
---------- Post added at 10:47 PM ---------- Previous post was at 09:59 PM ----------
here's the logcat.
uname -a
Linux localhost 2.6.36.4-cyanogenmod+ #1 SMP PREEMPT Mon Aug 13 09:42:21 EDT 2012 armv7l GNU/Linux
Click to expand...
Click to collapse
could not load needed library 'libsurfaceflinger_client.so' for 'libjniscreenshot23.so'
Maybe you should get a copy of libsurfaceflinger_client.so and push it to /system/lib ?
Ask your ROM dev for more info.
---------------------------------------------------
For those of you who get the firmware incompatible message, ROM name / link please.
If we can get your ROM's platform keys, we can fix it.
theos0o said:
could not load needed library 'libsurfaceflinger_client.so' for 'libjniscreenshot23.so'
Maybe you should get a copy of libsurfaceflinger_client.so and push it to /system/lib ?
Ask your ROM dev for more info.
Click to expand...
Click to collapse
Grabbed that lib (from goo.im), dropped it to system/lib, and changed the permissions, the app still crashes.
Sent from my GT-P7510 using xda app-developers app
Localhorst86 said:
Grabbed that lib (from goo.im), dropped it to system/lib, and changed the permissions, the app still crashes.
Sent from my GT-P7510 using xda app-developers app
Click to expand...
Click to collapse
extract the lib from the zip file from OP... and do the ssame thing.
i didn't flash the zip, i exctracted it and copied each file and changed the permissions
———————————————————
i didn't mean to mock you or to offend you in any kind of way
Riro Zizo said:
extract the lib from the zip file from OP... and do the ssame thing.
i didn't flash the zip, i exctracted it and copied each file and changed the permissions
———————————————————
i didn't mean to mock you or to offend you in any kind of way
Click to expand...
Click to collapse
hm... the libsurfaceflinger_client.so lib is not in that zipfile. Can you upload yours?
Localhorst86 said:
Grabbed that lib (from goo.im), dropped it to system/lib, and changed the permissions, the app still crashes.
Sent from my GT-P7510 using xda app-developers app
Click to expand...
Click to collapse
Looks like that lib you got is not compatible..
Here's mine from CM9, I don't think it'll work but try it.
http://www.mediafire.com/download.php?5c4u3qt33jb0a5o

[DIS] MXK - MinoochX Kernel - Discussion Thread - TEST 2 OUT

Since 4 weeks ago, i released a failure.
I'm utterly disappointed in myself and am very apologetic.
Because of that, i've used the 28 days testing and testing and testing.
Now, i've finally solved my issue, which is packing up the zImage.
I thank you if you still believe me
As for packaging the kernel, this is what i've found:
Code:
################################################################################
HOW TO BUILD KERNEL FOR GT-I8160_EUR
1. How to Build
- get Toolchain
download and install arm-eabi-4.4.3 toolchain for ARM EABI.
Extract kernel source and move into the top directory.
$ export CROSS_COMPILE=/opt/toolchains/arm-eabi-4.4.3/bin/arm-eabi-
$ make GT-I8160_defconfig
$ make
2. Output files
- Kernel : Kernel/arch/arm/boot/zImage
- module : Kernel/drivers/*/*.ko
3. How to Clean
$ make clean
[COLOR=Red]4. How to make .tar binary for downloading into target.
- change current directory to Kernel/arch/arm/boot
- type following command
$ tar cvf GT-I8160_EUR.tar zImage[/COLOR]
################################################################################
Those in red is the cure for my problems XD
With that, i now shall build the kernel.
The first test build will be here. If it boots, i will release it in the devment section.
And i'm very sorry for not replying PMs for 4 weeks
If you have any other queries, head to my twitter
Source Code
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOADS BELOW ARE DEVELOPMENTAL RELEASES!
FLASH WITH ODIN
===========================================
MXK Test REL 1 - GT-I8160_EUR.tar - 4.41 MB
MXK Test REL 2 =NOW TAR.MD5= - kernel.tar.md5 - 4.41 MB
YOU MUST BE ON JELLYBEAN
TEST RELEASE ONE
================
Initial Build
Implement Dynamic voltaging
Next build:
Includes
- SIO Scheduler
- I/O Tweaks
- GPU Voltage Control from Mali 400MP
- Various new governors
- CFlags optimizations
Im first ))) it work??... or need test?
Sent from my GT-I8160 using xda premium
kokiss said:
Im first ))) it work??... or need test?
Sent from my GT-I8160 using xda premium
Click to expand...
Click to collapse
Needs to test
Sent from my GT-N7105 using Tapatalk 2
As you can see, my ace 2 was traded in for a note 2 LTE. So I need willing people to try
It flash in Odin as PDA? I can bricked my phone?
Sory for my bad english...
Sent from my GT-I8160 using xda premium
kokiss said:
It flash in Odin as PDA? I can bricked my phone?
Sory for my bad english...
Sent from my GT-I8160 using xda premium
Click to expand...
Click to collapse
Yep PDA. Most probably no as this are the instructions by samsung.
Sent from my GT-N7105 using Tapatalk 2
If it doesnt work, I think I should make the image into bin.md5
Also there is a wish and it is pricked))) Terribly however...
Sent from my GT-I8160 using xda premium
kokiss said:
Also there is a wish and it is pricked))) Terribly however...
Sent from my GT-I8160 using xda premium
Click to expand...
Click to collapse
Are you success dude??
Sent from my GT-I9100 using Tapatalk 2
Nevertheless, im gonna make a kernel.bin.md5, same as D-Kernel's format.
I can not flash this kernel. The Odin write FAILED.
Sent from my GT-I8160 using xda premium
Ok. i think i know why. Im gonna add md5 for the next release.
I think zImage has to written as kernel.bin. IDK but maybe it will work.
Sent from my GT-I8160 using xda app-developers app
Released a new one. If it fails, im following the post above, renaming zImage into kernel.bin
and then md5ing it.
Which is the same format as D-kernel? I guess so XD
I made all that in the instruction for compilation and successed but I'm afraid to try it. Compiled stock kernel without any modification to source just for test. Also tried the linaro toolchain and it works but still afraid to test the result.
To the autor - keep up with the good work.
Test2 --> Odin --> PDA --> is FAIL too...
this is the next one.
you can use the dd method from terminal emulator to push it.
next build is a tar.md5
i really hate it when odin wants to verify the package. make thingss whole lot more complicated.
kernel.bin.md5 - 4.41 MB
This has SIO Scheduler and many more. see the github commits
Can i use Universal Kernel Flash?
---------- Post added at 05:39 AM ---------- Previous post was at 05:36 AM ----------
Do you only rename file?
yes. UKF works.
No. i did two commands that is required to md5 the file.
MinoochX said:
this is the next one.
you can use the dd method from terminal emulator to push it.
next build is a tar.md5
i really hate it when odin wants to verify the package. make thingss whole lot more complicated.
kernel.bin.md5 - 4.41 MB
This has SIO Scheduler and many more. see the github commits
Click to expand...
Click to collapse
Are you has been test it on your own ace 2???
Sent from my GT-I9100 using Tapatalk 2
Nope.
I can't. my codina is gone. i already said that.
I would be glad if you joined us to help in testing

[ROM]MIUI V5 Kitkat EN GNote2

What's Working:
- Touchscreen and hardware keys
- Touch key lights
- 3G
- SMS
- MMS
- Calls
- Wifi
- Sound
- Cameras
- Internal / external storage
- GPS
- Wifi Hotspot
- Bluetooth
- Recorder
- Torch
Installation:
- Download ROM and gapps
- Place on SDCARD
- Wipe factory rest 2x
- Flash MIUI rom
- Reboot into rom
- Then Reboot into recovery
- Flash gapps
- Reboot
- Enjoy
Bug:
Black background after full wipe. (Reboot then it will be ok. )
ScreenShot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOAD LINK:
Mod Edit link removed
Thanks to SuperNexus
Contributors
jing95916, Faryaab
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Last Updated 2014-07-02
Thanks for the ROM dev. Will a custom kernel work. On this
mohit141785 said:
Thanks for the ROM dev. Will a custom kernel work. On this
Click to expand...
Click to collapse
you dont waste time bud...................was just gonna mention in group :laugh:
---------- Post added at 02:55 PM ---------- Previous post was at 02:51 PM ----------
quick question
download says i777 so will this work on gt-n7100 gsm like what i have? sh*t not as i just read OP. oh well thanks for post anyway
quick question
download says i777 so will this work on gt-n7100 gsm like what i have? sh*t not as i just read OP. oh well thanks for post anyway
Click to expand...
Click to collapse
I have the same question. The file is "i777-4.6.29-4.4.zip". Since it is posted in Galaxy Note 2 it may be for note2 but can someone please confirm? I am excited to try Kitkat based MIUI
I downloaded the zip as quickly as i could and yes i did notice i777. I thought maybe it works , because another MIUI dev had multiple names and still could run.
The build.prop says i777 too. I'm not sure what to do next. Any help would be appreciated.
Exited to try this new baby
The op says for s2 i777, might he be mistaken by the forum lol
Sent from my GT-N7100 using Tapatalk
I suppose there are not a lot of languages in rom, only chinese and english?
abhishek0821 said:
I downloaded the zip as quickly as i could and yes i did notice i777. I thought maybe it works , because another MIUI dev had multiple names and still could run.
The build.prop says i777 too. I'm not sure what to do next. Any help would be appreciated.
Exited to try this new baby
Click to expand...
Click to collapse
edit build.prop and remove line relating to i777..............will be first 4 lines up to EMMC bit. rom should now flash without device get prop check
might run
shingers5 said:
edit build.prop and remove line relating to i777..............will be first 4 lines up to EMMC bit. rom should now flash without device get prop check
might run
Click to expand...
Click to collapse
Oh I'm not sure if I'm brave enough to do that. If its safe let me know , I'm not sure how these things actually work . I just download and flash
Attaching build.prop with txt exp becuase xda wont let me post another format.
abhishek0821 said:
Oh I'm not sure if I'm brave enough to do that. If its safe let me know , I'm not sure how these things actually work . I just download and flash
Attaching build.prop with txt exp becuase xda wont let me post another format.
Click to expand...
Click to collapse
actually looking at the updater script it all looks fine so it will flash. device will however be notted as i777 as per build.prop. can edit to gt-n7100
shingers5 said:
actually looking at the updater script it all looks fine so it will flash. device will however be notted as i777 as per build.prop. can edit to gt-n7100
Click to expand...
Click to collapse
Thanks a ton for such quick reply. I'll go ahead then and flash it. Would report it asap how it goes.
Thanks again
EDIT :
With philz it gave stats 7 error. Tried with latest twrp , it gives "Failed".
abhishek0821 said:
Thanks a ton for such quick reply. I'll go ahead then and flash it. Would report it asap how it goes.
Thanks again
Click to expand...
Click to collapse
it may not obviously work right as wifi and also signal may be broken..............its virtually impossible to brick samsung with tools like ODIN available ..............if you get symlink errors it doesn't like recovery used
---------- Post added at 04:41 PM ---------- Previous post was at 04:35 PM ----------
abhishek0821 said:
Thanks a ton for such quick reply. I'll go ahead then and flash it. Would report it asap how it goes.
Thanks again
EDIT :
With philz it gave stats 7 error. Tried with latest twrp , it gives "Failed".
Click to expand...
Click to collapse
yep build.prop needs edit as all relates to i777. pretty sure system board is different from n7100. you could try replace build.prop from another N7100 KK rom with one in rom zip as that could help!
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
also some really good and more knowledgable people on here than me so if they feel to might advise you on edits needed...............if can be done for i777 so n7100 might not be far behind.
shingers5 said:
it may not obviously work right as wifi and also signal may be broken..............its virtually impossible to brick samsung with tools like ODIN available ..............if you get symlink errors it doesn't like recovery used
---------- Post added at 04:41 PM ---------- Previous post was at 04:35 PM ----------
yep build.prop needs edit as all relates to i777. pretty sure system board is different from n7100. you could try replace build.prop from another N7100 KK rom with one in rom zip as that could help!
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
also some really good and more knowledgable people on here than me so if they feel to might advise you on edits needed...............if can be done for i777 so n7100 might not be far behind.
Click to expand...
Click to collapse
Sorry if I'm being stupid, but i also tried replacing the build.prop.. Thank you for your time and replying back. Getting back to my previous rom.
I guess we'll have to wait until the op decides to respond or someone else has some definite say on this.
sly.cooper said:
I have the same question. The file is "i777-4.6.29-4.4.zip". Since it is posted in Galaxy Note 2 it may be for note2 but can someone please confirm? I am excited to try Kitkat based MIUI
Click to expand...
Click to collapse
N7100-4.7.2-4.4.zip
jing95916 said:
N7100-4.7.2-4.4.zip
Click to expand...
Click to collapse
Where do you see N7100xx? The mega link still shows i777xx
Good to see MIUI V5 kitkat version for note 2 but please provide the proper link. BTW is it based on TW or CM?
friend as I think you got the wrong rom hehe
Maybe thread should be temporarily closed before someone damage their device in experimentation.
jing95916 said:
N7100-4.7.2-4.4.zip
Click to expand...
Click to collapse
Nooooooooo!
dunno whats going on here :laugh:
no new zip so dont get previous post by OP

Categories

Resources