So i did a bit of searching and have not came up with anything.
I am trying to modify a rom to fit in a different hboot then it was originally developed for.
Could i just move the files around in the .zip to there appropriate places and update the updater-script or is it more complex? I know where all the files and folders are supposed to go (that belong in the system and Data).
I was just wandering if anyone has come accross the same thing and my have a tutorial or guide that may help? I have found one on porting a rom from one to another but nothing for diffrent size hboots.
Thanks
Related
I want to use the android kitchen to turn our recently leaked ICS update into a rom. On Dsixda's thread, he states that we need to create a file in the kitchen's /tools/edify_defs folder with the properties of our phone, in the templates file, it is kind of unclear for me how to do this.
Can anyone help me create a file for the HTC Amaze 4G? Thanks
HuskyHamburger said:
I want to use the android kitchen to turn our recently leaked ICS update into a rom. On Dsixda's thread, he states that we need to create a file in the kitchen's /tools/edify_defs folder with the properties of our phone, in the templates file, it is kind of unclear for me how to do this.
Can anyone help me create a file for the HTC Amaze 4G? Thanks
Click to expand...
Click to collapse
Sorry if I am reviving a not quite old thread, but it came up when I was searching for the kitchen to download on my new windows install..
If you want to create a rom you don't really need the kitchen, it can do certain things to a rom- deodex, zipalign, install superuser and busybox, etc.. but within a few days of the leak all of that is available. You can pm a developer as I did and get permission to use their files rather than recreate the wheel.
First, just run the zip file thru the kitchen, don't do anything special with it- we have a superuser zip file you can/should just unpack into the final setup.
Find the updater-script and the binaries(in the same folder), this is what tells it what to install and where, fix permissions, install the files needed for SU(look in the superuser zip files updater script for details) etc..
If you want a deodexed rom you can ask to borrow the system/app directory from a rom that already has deodexed theirs. Literally, this is the best way to do it.
What the kitchen IS better for is pulling apart the kernel, putting it back together, unpacking apks.. it has built in scripts which can be a real time saver than typing in backsmali this, smali that-- simply put a file in a folder, type a number, and magically it all happens for you.. but you won't need ANY of that until you get into the advanced stuff.
I don't know if you were still trying to figure it out or not, but at the very least this may give someone who happened across this thread SOME sort of answer-- I get sick of finding more unanswered posts or posts where people reply with "you should search".. I've searched so much I my fingers should be bleeding.
ok so im loving the svn and superlte and all that, can someone please give me some direction as an order to flash all the different mods and such? i understand different orders for different purposes im just looking to get mine as fast as possible and able to tweak the hell out of everything and . Also a follow up question when checking out and after exporting i add my apps and such what do i gotta do besides zipping up the file to make it flash right? has always i appreciate any feed back anyone can give me
BigTexastrev said:
ok so im loving the svn and superlte and all that, can someone please give me some direction as an order to flash all the different mods and such? i understand different orders for different purposes im just looking to get mine as fast as possible and able to tweak the hell out of everything and . Also a follow up question when checking out and after exporting i add my apps and such what do i gotta do besides zipping up the file to make it flash right? has always i appreciate any feed back anyone can give me
Click to expand...
Click to collapse
Not sure I'm quite up to date on the latest ROM slang lingo, but I'll do my best to provide some insight from a developers point of view.
In regards to creating a ROM .zip, which I think is what is referred to as, "checking out and after exporting I add my apps and such what do i gotta do besides zipping up the file to make it flash right?", the process is fairly generic. The ROM .zip (update.zip) file will be processed and loaded in the custom recovery.
The directions are generally all located in the updater-script file under META-INF/*. If the only action being done is adding apps to /system/app on a ROM .zip which already contains apps in /system/app, nothing should need to be changed in the updater-script file.
If apps are being added to /data/app, but nothing in the ROM currently installs to /data, might need to a copy_recursive to updater-script to make sure the /data directory from the ROM .zip is installed properly.
If there are other questions, the more detailed the links and question, the better we can answer! Hope some of the technical details help resolve the question!
Hi all!
Dont know if ill get flamed because this a noob post, but i searched all over, (xda, google) and i cant find a solution to my problem.
Im starting in this cooking deeds but i have problems setting up my kitchen.
I want to cook to an HTC ONE X, i got my dsixda kitchen setted up in a VM, everything works with no problem.
But i have this problem when flashing rom
QUESTION: When flashing my ROM I get the error "mount expects 4 args got 3" or similar.
This refers to the fact your mount command takes 4 parameters (e.g. ext4, EMMC, /dev/block/.., /system) and your update-binary file only checks for 3 parameters. You'll have to change the update-binary file to a compatible one, found under the /tools/update_files folder. Just copy the appropriate file and rename to update-binary. e.g. If you're going to be using MTD partitions, copy 'mtd-update-binary' to /META-INF/com/google/android as "update-binary".
Click to expand...
Click to collapse
i know this is an answered question on dsixda FAQ, but my english is not so good to understand the easy solution to fix it :\
i tryed some several ways to fix this but with no sucess.
i already tryed, copying the update-binary from my ROM.zip to /tools/update_files folder no sucess
i already tryed copying the update-binary from my ROM.zip to /META-INF/com/google/android before script conversion, but with no sucess
i even tryed to make the kitchen my device compatible, renaming the evita (HTC ONE XL) to enderavou (HTC ONE X) in /tools/edify-defs/ in a chance that will have the same "specs" .. but it outputs me another error when flashin :\
sorry for the noob question, i know the solution is in front of my eyes and its easy, but my english is weak and i cant figure this alone with the short explanation on FAQ.
so if anyone can give me a more detailed help, or maybe if anyone has the templates for HTC ONE X to make dsixda kitchen compatible, ill appreciate.
thanks all
I have replaced the updater script from a working rom with the one the kitchen comes up with. Depending on the changes you made in the kitchen that has worked well for me. Looks like your script needs to match the partition setup. Compare the 2 scripts, 1 from working and 1 from kitchen and you should be able to see the difference.
I am far from a dev, and I'm sure someone will chime in with better info. but maybe this will work for you.
onlychevys said:
I have replaced the updater script from a working rom with the one the kitchen comes up with. Depending on the changes you made in the kitchen that has worked well for me. Looks like your script needs to match the partition setup. Compare the 2 scripts, 1 from working and 1 from kitchen and you should be able to see the difference.
I am far from a dev, and I'm sure someone will chime in with better info. but maybe this will work for you.
Click to expand...
Click to collapse
that was my first solution ... no sucess... maybe if i try another updater from another rom ... hum but i dont see any logic .. its supose to work with update from any working rom
Hi guys,
Long time lurker first time poster. I've always been handy enough to follow the clues on xda forum to be able to work things out and google, but this time around I'm stuck and would appreciate a few leads... maybe I'm google-ing the wrong terms.
Anyways, I'm looking to get more info on directory structures on the phone and microsd card.
Let me explain: After rooting my phone and putting a new ROM on it, I noticed that the ROM does does not read my sd card. I looked it up and apparently the rom had a new structure on jb (or was it ics, I can't remember,) and there was a fix that I needed to run in recovery which fixed it, when I changed to a different ROM (was running sentinelRom and now slimrom) it didn't read again and I ran the file in recovery again.
This time I noticed that the kinda added extra directories and I'm not sure which one the rom is using.
As an example, I noticed that when I went into es explorer, there would be similar directories within each other (ie. device/0/0 .....)
and since I've gotten notice that I'm running low on space, I noticed under storage that the directory /0 is taking the most space.
Problem is I don't want to just delete it... the last time I tried to clear a directory I deleted some files that were being used. (luckily they were only sound files, ) so somehow, certain directories are being used by the rom, I'm just not sure which one....
Anyways, I would be much obliged if someone could point me in the right direction on where I can get info or be able to clean up my directories before I upgrade to the kitkat version of my ROM.
Thanks in advance folks!
grungypoo said:
Hi guys,
Long time lurker first time poster. I've always been handy enough to follow the clues on xda forum to be able to work things out and google, but this time around I'm stuck and would appreciate a few leads... maybe I'm google-ing the wrong terms.
Anyways, I'm looking to get more info on directory structures on the phone and microsd card.
Let me explain: After rooting my phone and putting a new ROM on it, I noticed that the ROM does does not read my sd card. I looked it up and apparently the rom had a new structure on jb (or was it ics, I can't remember,) and there was a fix that I needed to run in recovery which fixed it, when I changed to a different ROM (was running sentinelRom and now slimrom) it didn't read again and I ran the file in recovery again.
This time I noticed that the kinda added extra directories and I'm not sure which one the rom is using.
As an example, I noticed that when I went into es explorer, there would be similar directories within each other (ie. device/0/0 .....)
and since I've gotten notice that I'm running low on space, I noticed under storage that the directory /0 is taking the most space.
Problem is I don't want to just delete it... the last time I tried to clear a directory I deleted some files that were being used. (luckily they were only sound files, ) so somehow, certain directories are being used by the rom, I'm just not sure which one....
Anyways, I would be much obliged if someone could point me in the right direction on where I can get info or be able to clean up my directories before I upgrade to the kitkat version of my ROM.
Thanks in advance folks!
Click to expand...
Click to collapse
Have a look in the stickies thread. Described over there why there is a new structure and how to move files...
Sent from my GT-I9300 using xda app-developers app
Thanks for that! Much appreciated!
Hello I am kinda of new to rooting and I am following this tutorial, from my understanding I need the Factory image of SM-A526B/DS, I am having issues finding that file can someone point me in the right direction?
Correct me if I am wrong but, if I cant find this file does it mean It would be convinient to change my OS and then download the img file? I don't know If I am making sense, I apologize im kind of new to this.
ARCHANGELGABRIEL said:
Hello I am kinda of new to rooting and I am following this tutorial, from my understanding I need the Factory image of SM-A526B/DS, I am having issues finding that file can someone point me in the right direction?
Correct me if I am wrong but, if I cant find this file does it mean It would be convinient to change my OS and then download the img file? I don't know If I am making sense, I apologize im kind of new to this.
Click to expand...
Click to collapse
In the same Forum where you opened this thread there is someone saying that could be unlock and root the same device as yours https://forum.xda-developers.com/t/unlock-bootloader-magisk.4272797/post-85041029 a little research could bring you there.
For the firmware just adding to SM-A526B/DS, the word "firmware" you will find a lot of entries, also you can use some tool like Frija https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/
which rom ur phone running can u take a screenshot about phone section ?