When using the only available pre-rooted ROM on a North American Galaxy Player 3.6 the capacitive home button doesn't work. I'm guessing it's a driver issue and we just need to find it in either the source or the stock ROM. This thread will be dedicated to finding the solution to this problem. :fingers-crossed:
Here are the partitions mmcblk0 of pre-rooted Korean Rom with the cf-root kernel :
Pre-rooted Korean Rom :
hundz said:
Okay im uploading it right now, takes a while though.
Will edit this post later :good:
link
Click to expand...
Click to collapse
Cf-root kernel :
zaclimon said:
I don't gurantee anything but here's the Cf-root kernel :
Link: 2nd (old) kernel download
Instructions: flash with either odin or heimdall.
Click to expand...
Click to collapse
Download :
https://www.dropbox.com/sh/9ci002b4ywbqkxz/gCKNx8DC3J
Click to expand...
Click to collapse
Quentinga said:
Here are the partitions mmcblk0 of pre-rooted Korean Rom with the cf-root kernel :
Pre-rooted Korean Rom :
Cf-root kernel :
Download :
Click to expand...
Click to collapse
Okay, does the US home button work with these?
Mars11_ said:
Okay, does the US home button work with these?
Click to expand...
Click to collapse
No it's for developpers.
Sent from my YP-GS1 using xda app-developers app
Why just don't someone with a us player (stock us rom) flash the unfinished cf-root kernel and dump the system partition so you can flash the US stock rom?
zaclimon said:
Why just don't someone with a us player (stock us rom) flash the unfinished cf-root kernel and dump the system partition so you can flash the US stock rom?
Click to expand...
Click to collapse
Because using that kernel breaks the home button also, it's a driver that's in the kernel, I'm sure of it. I've spent hours searching through the kernel and haven't found anything that looks like it belongs to the home button, I have no idea where it would be.
Mars11_ said:
Because using that kernel breaks the home button also, it's a driver that's in the kernel, I'm sure of it. I've spent hours searching through the kernel and haven't found anything that looks like it belongs to the home button, I have no idea where it would be.
Click to expand...
Click to collapse
Alright so I'll build a US kernel on top of the modified ramdisk then. Or you want the modified ramdisk and you build a kernel on top of it?
zaclimon said:
Alright so I'll build a US kernel on top of the modified ramdisk then. Or you want the modified ramdisk and you build a kernel on top of it?
Click to expand...
Click to collapse
I have no idea how to do any of that, so it would be best if you did it.
How to upload the 2 gb file (mmcblk0p9) ?
---------- Post added at 10:25 AM ---------- Previous post was at 10:10 AM ----------
I cut into pieces of 10 mb (65) and collected in four tar file. I currently following the upload.
still there's no way to fix the home button? :/
No idea if this will work for the 3.6 but it works for the 5.0
The key layouts are stored in /system/usr/keylayout and the korean rom probably has the correct key layout for a physical home key. Here is my idea:
Extract the files in /system/usr/keylayout in the stock rom for devices with the capacitive button
Compare these files with the files in /system/usr/keylayout in the korean rom
If any files are different, delete the files from the korean rom and replace with the files from the stock rom and your button should now work
Can you do this for me? cause i cant understand what you are talking about. Sorry. :/
Sent from my YP-GS1 using xda app-developers app
zephy09 said:
Can you do this for me? cause i cant understand what you are talking about. Sorry. :/
Sent from my YP-GS1 using xda app-developers app
Click to expand...
Click to collapse
I'll try to help. Can you navigate to /system/usr/keylayout in a file browser and extract all the files there onto your computer. Then put those files in a zip file and upload them and send me the link. You'll also have to do the same thing while running the stock rom. Is there anywhere I can download your stock rom?
Where can i navigate that?
Sent from my YP-GS1 using xda app-developers app
zephy09 said:
Where can i navigate that?
Sent from my YP-GS1 using xda app-developers app
Click to expand...
Click to collapse
Download a file browser from the Play Store. I recommend Root Browser.
Then open the app and use it like windows explorer or whatever. Go to /system/usr
Long press on the folder called keylayout and then press archive and press ok.
Long press on the archive and press Move
Press the home key in the top left corner and then go to sdcard
Press paste at the bottom
Then copy the archive to your computer and upload it to mediafire or somewhere and send me the link
Supermaster34 said:
Download a file browser from the Play Store. I recommend Root Browser.
Then open the app and use it like windows explorer or whatever. Go to /system/usr
Long press on the folder called keylayout and then press archive and press ok.
Long press on the archive and press Move
Press the home key in the top left corner and then go to sdcard
Press paste at the bottom
Then copy the archive to your computer and upload it to mediafire or somewhere and send me the link
Click to expand...
Click to collapse
keylayout right? here you go.
http://www.4shared.com/zip/X6mWxv58/keylayout.html?
Take the file from the US rom to paste it in the korean rom.
ps : I'm going on vacation tomorrow, I can not test anything until I return.
How will i do that? Please give me a instructions.
Sent from my YP-GS1 using xda app-developers app
zephy09 said:
How will i do that? Please give me a instructions.
Sent from my YP-GS1 using xda app-developers app
Click to expand...
Click to collapse
Someone who does not install the korean rom. It should download an application file manager (Astro file, File Expert). He copy the file and upload on the internet in hopes that the file is read permissions.
zephy09 said:
How will i do that? Please give me a instructions.
Sent from my YP-GS1 using xda app-developers app
Click to expand...
Click to collapse
You need to install the stock rom or find someone who is still running the stock rom. Then you need to use adb:
Code:
adb pull /system/usr/keylayout c:\AFolderWhereYouCanStoreTheFiles
Related
Hi,
since I don't really like the Glass lockscreen on YP-G1,I wanna change it to AOSP style.
However,UOT kitchen can't make it though I've tried many times uploading files
So,I searched for way to mod these files manually in forum.Like:
http://forum.xda-developers.com/showthread.php?t=969354
Stuck ROM's is fully odexed,so I got android.policy.jar and android.policy.odex.After decompiling android.policy.odex(340KB),editing codes,recompiling,I got a dex file(296KB).It was smaller than before,making me confused...
Then I renamed it to 'classes.dex' putting into android.policy.jar,and made a CWM zip and flashed it as usual.
Reboot,ah,just got a bootloop
Anyone could give me a hand?This stuff almost made me mad...
If AOSP lockscreen's codes were not exist in firmware,then what I've done was just in vain...
But Klin has succeed in changing lock style via UOT.So there should be sth wrong in editing these codes for me.
Keep working on it.
fromnowon said:
If AOSP lockscreen's codes were not exist in firmware,then what I've done was just in vain...
But Klin has succeed in changing lock style via UOT.So there should be sth wrong in editing these codes for me.
Keep working on it.
Click to expand...
Click to collapse
You have to change a method in android.policy.jar. I think it was in class lockpatternkeyguardview.
Sent using Tapatalk
klin1344 said:
You have to change a method in android.policy.jar. I think it was in class lockpatternkeyguardview.
Sent using Tapatalk
Click to expand...
Click to collapse
Hi,Klin.
Could you please send me your android.policy.jar and android.policy.odex?I downloaded your custom ROM R5,but couldn't be unpacked by UltraISO,even failed to mount the rfs file in Linux
Thax!
Ok, I'll give it to you when I get home this afternoon. But my rom is deodexed, so it doesn't have android.policy.jar.odex.
And also, the reason you can't mount the factoryfs.rfs is because it is an extremely image in an Odin flashable format. If you want it sooner, you could download r4 and mount it and take the file you need.
Sent using Tapatalk
klin1344 said:
Ok, I'll give it to you when I get home this afternoon. But my rom is deodexed, so it doesn't have android.policy.jar.odex.
And also, the reason you can't mount the factoryfs.rfs is because it is an extremely image in an Odin flashable format. If you want it sooner, you could download r4 and mount it and take the file you need.
Sent using Tapatalk
Click to expand...
Click to collapse
Thank you~
Starting to learn Android,I'm interested in everything about it.
Sorry for the delay, but here ya go.
There is no odex version because it is already deodexed.
So, would using a deodexed android.policy.jar on a stock odexed rom not work?
Sent using Tapatalk
iJimaniac said:
So, would using a deodexed android.policy.jar on a stock odexed rom not work?
Sent using Tapatalk
Click to expand...
Click to collapse
Probably not. But you could try it if you want, and if it boot loops just adb push the original one to your phone. But if your rom is a different framework other than 2.3.6 than this definitely won't work.
Sent using Tapatalk
klin1344 said:
Sorry for the delay, but here ya go.
There is no odex version because it is already deodexed.
Click to expand...
Click to collapse
Thx.
In fact I got lots of bootloop while testing such things,haha
I would investigate this file and hope to find sth.
Thx again!
Hi everyone!
I hope someone here will have an asnwer for my question...
So , the question is, How can I know for sure, which Android version runs on my device, if I don't trust the information
provided in "build.prop" file.
Specifically, how can I be sure I have an ICS and not GB ?
Thank you in advance!
System settings > about phone
Sent from my SPH-D710 using Tapatalk 2
Furthermore if your running ICS for android version it should have a number ranging from 4-4.04.
Sent from my SCH-I535 using xda premium
Thanks, but both answers don't help in my case, as they do use the contents of "build.prop".
In my case, I don't trust "build.prop" , and hence looking for alternative ways to determine the Android version.
f_mulder said:
Thanks, but both answers don't help in my case, as they do use the contents of "build.prop".
In my case, I don't trust "build.prop" , and hence looking for alternative ways to determine the Android version.
Click to expand...
Click to collapse
What's your beef with build.prop? The only other way I know is to download a ROM of your choice, unzip it, Look in META-INF>com>android> and open up the metadata file and you should be able to see it in there. But, I suppose that could be fudged as well. Is someone launching some sort of Android conspiracy against you?
0dBu said:
What's your beef with build.prop? The only other way I know is to download a ROM of your choice, unzip it, Look in META-INF>com>android> and open up the metadata file and you should be able to see it in there. But, I suppose that could be fudged as well. Is someone launching some sort of Android conspiracy against you?
Click to expand...
Click to collapse
+1
Sent from my SPH-D710 using Tapatalk 2
If Google Chrome is available to you on the play store, you have ICS. If its not you have GB. Furthermore you could download an ICS only app and if it says there is an error parsing the package then you have GB
Sent from my DROID2 using xda premium
0dBu said:
What's your beef with build.prop? The only other way I know is to download a ROM of your choice, unzip it, Look in META-INF>com>android> and open up the metadata file and you should be able to see it in there. But, I suppose that could be fudged as well. Is someone launching some sort of Android conspiracy against you?
Click to expand...
Click to collapse
LOL .
OK I'll explain myself...
I have a chinese phone, which runs Android.
Manufacturer , releases new ROMs from time to time.
Last few ROMs, were "4.0.3", as it was written in "build.prop", but after installation,
I saw there is no Right to Left support, and for me , that is a sign, that the ROM isn't really 4.0.3,
as (AFAIK) 4.0.3 supports RTL out ofthe box...
Now, I still hope they will release real 4.0.X ROM some day, but till then, I don't want
to install every ROM they release. I want to identify whether ROM is 2.3.6 or 4.0.X before I Install it,
and not based on "build.prop".
So, I hope now you have full explanation, and will be able to help.
Thanks!
f_mulder said:
LOL .
OK I'll explain myself...
I have a chinese phone, which runs Android.
Manufacturer , releases new ROMs from time to time.
Last few ROMs, were "4.0.3", as it was written in "build.prop", but after installation,
I saw there is no Right to Left support, and for me , that is a sign, that the ROM isn't really 4.0.3,
as (AFAIK) 4.0.3 supports RTL out ofthe box...
Now, I still hope they will release real 4.0.X ROM some day, but till then, I don't want
to install every ROM they release. I want to identify whether ROM is 2.3.6 or 4.0.X before I Install it,
and not based on "build.prop".
So, I hope now you have full explanation, and will be able to help.
Thanks!
Click to expand...
Click to collapse
Yes I figured this
gagdude said:
If Google Chrome is available to you on the play store, you have ICS. If its not you have GB. Furthermore you could download an ICS only app and if it says there is an error parsing the package then you have GB
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
and here was my help you didn't notice. More apps include the Google now for ICS project, apex, nova, etc.
Sent from my DROID2 using xda premium
posible soluction
I thing that if you go to Settings/ about phone/ and in android version you do a lot of clicks you will force to saw a picture with the version of android loock this:
http://www.youtube.com/watch?v=o_PBIw7j4S4
werty100 said:
I thing that if you go to Settings/ about phone/ and in android version you do a lot of clicks you will force to saw a picture with the version of android loock this:
http://www.youtube.com/watch?v=o_PBIw7j4S4
Click to expand...
Click to collapse
But maybe he thinks that's been modified too?!!
Sent from my MB525 using xda app-developers app
werty100 said:
I thing that if you go to Settings/ about phone/ and in android version you do a lot of clicks you will force to saw a picture with the version of android loock this:
http://www.youtube.com/watch?v=o_PBIw7j4S4
Click to expand...
Click to collapse
Wow, that is really nice trick!
I wasn't aware of it. Thanks!
Though, the problem is to know ROM's Android version , before I install it on the device.
So it is not a solution to my problem...
Ah, and that phone has an iPhone look menus , so there is no way to perform that trick, unfortunately...
gagdude said:
If Google Chrome is available to you on the play store, you have ICS. If its not you have GB. Furthermore you could download an ICS only app and if it says there is an error parsing the package then you have GB
Click to expand...
Click to collapse
I did notice your post, thank you.
But the whole point of my question/problem , to identify the Android version on ROM,
without installing it to device.
Thanks!
f_mulder said:
I did notice your post, thank you.
But the whole point of my question/problem , to identify the Android version on ROM,
without installing it to device.
Thanks!
Click to expand...
Click to collapse
I can make app that will say if you are running ICS or JB or GB!
I'll send you it tomorrow!
It checks api level of the system.
If its 16=JB , 15= ICS, 11 or 12=GB
Sent from my MB525 using xda app-developers app
ppero196 said:
I can make app that will say if you are running ICS or JB or GB!
I'll send you it tomorrow!
It checks api level of the system.
If its 16=JB , 15= ICS, 11 or 12=GB
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
Can you please explain what should be checked ?
I mean what can I check in ROM (it is CWM installable ZIP file ) , in order to know
which Android version it has?
But again, I don't want to install it! I want to know that from inspecting the ROM itself!
Thanks!
f_mulder said:
Can you please explain what should be checked ?
I mean what can I check in ROM (it is CWM installable ZIP file ) , in order to know
which Android version it has?
But again, I don't want to install it! I want to know that from inspecting the ROM itself!
Thanks!
Click to expand...
Click to collapse
You can't check it....only apps can!
Sent from my MB525 using xda app-developers app
f_mulder said:
Can you please explain what should be checked ?
I mean what can I check in ROM (it is CWM installable ZIP file ) , in order to know
which Android version it has?
But again, I don't want to install it! I want to know that from inspecting the ROM itself!
Thanks!
Click to expand...
Click to collapse
Download the rom open it with 7zip and go to system-SW_configuration.xml
Open it with notepad++ and check the firmware.
The same thing you can do it with root explorer in your phone.
I don't believe he changed all the xml's just to make users believe is an ICS rom
To check for ICS:
Look at the file's /system/bin .
If it contains a binary called sh it's Gingerbread .
If it contains a binary called mksh then it's ICS .
Sent from a Samsung Galaxy Ace
CallMeVentus said:
To check for ICS:
Look at the file's /system/bin .
If it contains a binary called sh it's Gingerbread .
If it contains a binary called mksh then it's ICS .
Sent from a Samsung Galaxy Ace
Click to expand...
Click to collapse
On JB its also called mksh
Sent from my MB525 using xda app-developers app
CallMeVentus said:
To check for ICS:
Look at the file's /system/bin .
If it contains a binary called sh it's Gingerbread .
If it contains a binary called mksh then it's ICS .
Sent from a Samsung Galaxy Ace
Click to expand...
Click to collapse
As long as you live you learn
Thanks CallMeVentus!!!
Greetings,
This is my first thread and post here at this community.
I have a Samsung Galaxy SIII with the beta firmware I9300XXELK4_I9300OJKELK5_ILO. I've read at this forum about an APK that can be used to add more programs to the native MutiWindow View that this FW has. At the same topic it is written that you have to use some odexe or deodexe.
Actually i dont know what is odexe or deodexe and i dont know how to install it on my device.
Can someone please help me and guide about how to install it properly.
Thank you very much!
Acaeg said:
Greetings,
This is my first thread and post here at this community.
I have a Samsung Galaxy SIII with the beta firmware I9300XXELK4_I9300OJKELK5_ILO. I've read at this forum about an APK that can be used to add more programs to the native MutiWindow View that this FW has. At the same topic it is written that you have to use some odexe or deodexe.
Actually i dont know what is odexe or deodexe and i dont know how to install it on my device.
Can someone please help me and guide about how to install it properly.
Thank you very much!
Click to expand...
Click to collapse
If you did flash the original leak it will be most likely odexed (as mine is), deodext are usually all the custom roms (stock and others) as it is easier for modifications. You can also Google and will find a lot of explanations.
Sent from my GT-I9300 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1363749
Its odex vs deodex roms..
Sent from my GT-I9300 using xda premium
chrismast said:
If you did flash the original leak it will be most likely odexed (as mine is), deodext are usually all the custom roms (stock and others) as it is easier for modifications. You can also Google and will find a lot of explanations.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thank you very much, now how can i install those files inside the odexed.zip (META-INF and system folders) into my phone in order to run the MW Control APK.
Thank you!
Acaeg said:
Thank you very much, now how can i install those files inside the odexed.zip (META-INF and system folders) into my phone in order to run the MW Control APK.
Thank you!
Click to expand...
Click to collapse
download the odex file from the MW threat and flash it in CWM. Do NOT extract the files (e.g. meta-inf etc.)
chrismast said:
download the odex file from the MW threat and flash it in CWM. Do NOT extract the files (e.g. meta-inf etc.)
Click to expand...
Click to collapse
Finally, thanks! now i have the MWC correctly installed.
Mr. Moderator you can close the topic.
Hello,
I want to make a custom ROM based on a stock i9001 ROM. However when I extracted the tar file there were IMG and ext4 files. I know how to make a rom via cygwin when i have: 1) system folder
2) META-INF folder
And 3) boot.img
I don't know what to do to the stock ROM
(.tar) to be like this
*** sorry for my bad english
Sent from my Galaxy Nexus using xda premium
kagouro said:
Hello,
I want to make a custom ROM based on a stock i9001 ROM. However when I extracted the tar file there were IMG and ext4 files. I know how to make a rom via cygwin when i have: 1) system folder
2) META-INF folder
And 3) boot.img
I don't know what to do to the stock ROM
(.tar) to be like this
*** sorry for my bad english
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
explain more
Help Building a CUSTOM(from STOCK ROM)
Newbie here---
- I have downloaded the HTC stock RUU for my device.
- I used Android Kitchen cygwin to extract the files, setup the working folder.
- Added root permissions,BusyBox
- Built the rom from working folder.
Wanted to test whether this works or not... But Phone Got stuck on HTC logo .. Not even BOOTANIMATION.
What did i miss or DO wrong here??
Where in these steps worked flawlessly when i took a custom rom? What else should be done here?? Help would be Appreciated!!!
Learn More About Kitchen. Add Root, Busybox, Put apk files in System/aps etc. What do you want to do?
cheqolada said:
Learn More About Kitchen. Add Root, Busybox, Put apk files in System/aps etc. What do you want to do?
Click to expand...
Click to collapse
I'm Sorry, The ROM i built from the working folder did not boot. My question was what went wrong?
kagouro said:
Hello,
I want to make a custom ROM based on a stock i9001 ROM. However when I extracted the tar file there were IMG and ext4 files. I know how to make a rom via cygwin when i have: 1) system folder
2) META-INF folder
And 3) boot.img
I don't know what to do to the stock ROM
(.tar) to be like this
*** sorry for my bad english
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Maybe this is what you search:
http://forum.xda-developers.com/showthread.php?t=1976412
yashwantpiduru said:
I'm Sorry, The ROM i built from the working folder did not boot. My question was what went wrong?
Click to expand...
Click to collapse
My Answer is for kagouro - Becouse i Don't see your post when I write.
If Your Phone is dedected in adb you can use logcat (adb logcat in windows cmd) if phone don't dedected in adb - flash recovery via fastboot, join in recovery , instal working rom and found bad files in rom (try add modyfication singly - first root, second busybox etc - in this metod you can see whad mod don't work - probably stupid method but work :cyclops
yashwantpiduru said:
Newbie here---
- I have downloaded the HTC stock RUU for my device.
- I used Android Kitchen cygwin to extract the files, setup the working folder.
- Added root permissions,BusyBox
- Built the rom from working folder.
Wanted to test whether this works or not... But Phone Got stuck on HTC logo .. Not even BOOTANIMATION.
What did i miss or DO wrong here??
Where in these steps worked flawlessly when i took a custom rom? What else should be done here?? Help would be Appreciated!!!
Click to expand...
Click to collapse
Kitchen will replace certain necessary parts of your ROM if it isn't compatible with the kitchen, it puts them back when you compile. When you compiled your ROM did you take the guided option? Also, and probably the first thing I should have asked, is your phone compatible with kitchen?
Sent from my SPH-D710 using xda premium
Stryke_the_Orc said:
Kitchen will replace certain necessary parts of your ROM if it isn't compatible with the kitchen, it puts them back when you compile. When you compiled your ROM did you take the guided option? Also, and probably the first thing I should have asked, is your phone compatible with kitchen?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
My phone is compatible with the kitchen.
Yeah I took the guided step! Still no luck
sent from my oc'd incS
yashwantpiduru said:
My phone is compatible with the kitchen.
Yeah I took the guided step! Still no luck
sent from my oc'd incS
Click to expand...
Click to collapse
OK, just for giggles try this, take the meta-inf folder from a rom you know works and using 7zip replace the one in your rom. Let me know if that helped at all:beer:
Sent from my SPH-D710 using xda premium
Stryke_the_Orc said:
OK, just for giggles try this, take the meta-inf folder from a rom you know works and using 7zip replace the one in your rom. Let me know if that helped at all:beer:
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Sure! its late! I will try and let you know asap!
P.S: actually I tried this as well adding aroma installer to the rom! That had some ext3 error ! Dont have a clue what's that?
sent from my oc'd incS
yashwantpiduru said:
Sure! its late! I will try and let you know asap!
P.S: actually I tried this as well adding aroma installer to the rom! That had some ext3 error ! Dont have a clue what's that?
sent from my oc'd incS
Click to expand...
Click to collapse
Ext3 is a mount point, I'm not sure what it would be specific to your device, but it tells me there's an error in your updater script
Sent from my SPH-D710 using xda premium
Stryke_the_Orc said:
Ext3 is a mount point, I'm not sure what it would be specific to your device, but it tells me there's an error in your updater script
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thanks for the heads up... I am gonna check the updater script.
sent from my oc'd incS
Hi guys,
I'm trying to set up Aroma Installer for my own Custom ROM. When I try to flash the ROM, it shows all but when i had nearly finished it let me choose Installation Demo and other options. This will flash the ROM or it will show me what will happen without flashing it?
If it is only a demostration, what I have to do to flash the ROM definetly?
Thank you!!!
TenKoX said:
Hi guys,
I'm trying to set up Aroma Installer for my own Custom ROM. When I try to flash the ROM, it shows all but when i had nearly finished it let me choose Installation Demo and other options. This will flash the ROM or it will show me what will happen without flashing it?
If it is only a demostration, what I have to do to flash the ROM definetly?
Thank you!!!
Click to expand...
Click to collapse
By the looks of it, it's just a demo
To flash a ROM, go to its thread, download it(it won't be 5 mb, it would be probably bigger than 100 mb or around it) and follow the instructions on how to flash it.
Sent from my GT-S5830i using xda app-developers app
How about posting your meta-inf folder here so someone can see where you went wrong as in its hard to give you an answer without more detail
Sent from my Nexus 4 using xda premium
demkantor said:
How about posting your meta-inf folder here so someone can see where you went wrong as in its hard to give you an answer without more detail
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I don't think that there is a problem in my meta-inf folder. I just ask what I have to do to skip the demo and flash the ROM.
Thank you for answering!
iamareebjamal said:
By the looks of it, it's just a demo
To flash a ROM, go to its thread, download it(it won't be 5 mb, it would be probably bigger than 100 mb or around it) and follow the instructions on how to flash it.
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
I don't want to flash other's ROM. I want to install Aroma for MY ROM so when someone try to flash my rom, he'll be able to choose what he want to install or not.
Thank you for answering!!
TenKoX said:
I don't want to flash other's ROM. I want to install Aroma for MY ROM so when someone try to flash my rom, he'll be able to choose what he want to install or not.
Thank you for answering!!
Click to expand...
Click to collapse
Then you need to modify Aroma-Config (Uses C as language) and updater-script to make the package behave as you want.
If you don't want options in Aroma, just a simple installer of ROM
Then, follow this guide
http://forum.xda-developers.com/showthread.php?t=2223368
iamareebjamal said:
Then you need to modify Aroma-Config (Uses C as language) and updater-script to make the package behave as you want.
If you don't want options in Aroma, just a simple installer of ROM
Then, follow this guide
http://forum.xda-developers.com/showthread.php?t=2223368
Click to expand...
Click to collapse
I have done all of this before but it continues taking me to the demo.
Here is my aroma-config and udapter-script files.
The reason the demo keeps playing is because you haven't set things up right, that's why I'm asking for your meta-inf folder and all its contents, if you would like to have aroma flash your ROM and not play a demo that is.... Choice is yours
Sent from my Nexus 4 using xda premium
demkantor said:
The reason the demo keeps playing is because you haven't set things up right, that's why I'm asking for your meta-inf folder and all its contents, if you would like to have aroma flash your ROM and not play a demo that is.... Choice is yours
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Here is my meta-inf folder
Sorry, my phone is being a **** and won't let me extract .rar, can you either upload it as a .zip or you could use pastebin to post your updater-script and aroma-binary otherwise it will have to wait until I can get near a PC (few more hours)
Sent from my Nexus 4 using xda premium
demkantor said:
Sorry, my phone is being a **** and won't let me extract .rar, can you either upload it as a .zip or you could use pastebin to post your updater-script and aroma-binary otherwise it will have to wait until I can get near a PC (few more hours)
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Here is the meta-inf as .zip.
Thank you for helping me!!
TenKoX said:
Here is the meta-inf as .zip.
Thank you for helping me!!
Click to expand...
Click to collapse
No problem, just busy right now so sorry if it takes a bit to answer.
Right now all you did was swap updater scripts, you need to edit your aroma-config to have it select what you want.
If you need some help with it I'll be home in maybe 5hours and can lend a hand then, in the meantime take a look at some of my (or others) aroma packaged and see how they matched aromaconfigs to updater scripts
Sent from my Nexus 4 using xda premium
ok this is just a quick sloppy job but should get you what your after, feel free to ask any more questions on how to pretty it up for your installers
View attachment META-INF.zip
demkantor said:
ok this is just a quick sloppy job but should get you what your after, feel free to ask any more questions on how to pretty it up for your installers
View attachment 2099972
Click to expand...
Click to collapse
Thank you!!! It works!!!
Can you tell me how you did it?
Now, how I can put different options? For example, if someone installs my ROM I would like them to choose what kernel or app they want to install or not. How can I do that and where I must place the .apk files (for the apps) or the .zip files (for the kernels)?
Thank you again!!!
I'm seeing that the installer does not install the ROM, how I can do that?
@demkantor
Dear mate!
Could you plz help me to correct my rom aroma installer, i configured aroma-config and updater script but during flash process it show (Status 1) error on line 187 col 4 or something like this.
TenKoX said:
I'm seeing that the installer does not install the ROM, how I can do that?
Click to expand...
Click to collapse
all i did was fix aroma, you need to put the files in the proper place, as in open root folder, there should be two inside (more if needed for other purposes) meta-inf and system, put all rom info organized properly in system and then flash
you can always save aroma logs if you have questions
and yes i can help you add kernel choices and such but i need to know what all options you need or want
ab-samy said:
@demkantor
Dear mate!
Could you plz help me to correct my rom aroma installer, i configured aroma-config and updater script but during flash process it show (Status 1) error on line 187 col 4 or something like this.
Click to expand...
Click to collapse
change
"Touchwiz Launcher","It's the Default (Stock) Launcher of the Samsung Galaxy S2 with some cool Features and transitions",0, #--selected.1 = 3
Click to expand...
Click to collapse
to
"Touchwiz Launcher","It's the Default (Stock) Launcher of the Samsung Galaxy S2 with some cool Features and transitions",0 #--selected.1 = 3
Click to expand...
Click to collapse
no comma after the 0
I have added the system and meta-inf folders and packed all of this as a .zip before. Do i have to modify any other aroma files?
Sorry for being so noob...
Sent from my GT-I9001 using xda app-developers app
No need to apologize, we all learn new thongs every day!
You shouldn't have to edit any script, just take your system folder and meta-inf (and anything else needed) zip them up and sign, when you flash in aroma be sure to save logs so you can check it later for errors
Sent from my Nexus 4 using xda premium
demkantor said:
No need to apologize, we all learn new thongs every day!
You shouldn't have to edit any script, just take your system folder and meta-inf (and anything else needed) zip them up and sign, when you flash in aroma be sure to save logs so you can check it later for errors
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I have signed it with ROM kitchen and packed all as zip. When i try to start Aroma with the recovery, it says:
Code:
E:Can't copy META-INF/com/google/android/update-binary
Installation aborted.