Related
Hi all,
Can someone point out what is wrong with this updater script?
vaibhavknockout said:
Hi all,
Can someone point out what is wrong with this updater script?
Click to expand...
Click to collapse
I can tell you what is wrong with this thread, it belongs in Q&A.
Luckily, I took care of that for you.
Secondly, I don't know if there are more mistakes, but this line:
Code:
package_extract_file("boot.img", "/tmp/boot.img");write_raw_image("/tmp/boot.img", "boot");
is for flashing kernel via recovery which is not possible with Xperia phones.
What are you trying to do and what error does recovery give?
iridaki said:
I can tell you what is wrong with this thread, it belongs in Q&A.
Click to expand...
Click to collapse
LOLMAX!
iridaki said:
I can tell you what is wrong with this thread, it belongs in Q&A.
Luckily, I took care of that for you.
Secondly, I don't know if there are more mistakes, but this line:
Code:
package_extract_file("boot.img", "/tmp/boot.img");write_raw_image("/tmp/boot.img", "boot");
is for flashing kernel via recovery which is not possible with Xperia phones.
What are you trying to do and what error does recovery give?
Click to expand...
Click to collapse
Sorry madam for posting this in wrong thread. How stupid of me........I am trying to learn writing updater scripts and I am modifying CM9's script to do that. Recovery gives me Error 6. I am modifying this in notepad++, I had already checked for newline characters. Since I am a newbie in porting and stuff, I don't even know whether I need to make a new update-binary for every change I make in updater-script. I searched for hours on google about this problem but with no sucess. I never felt this miserable...
Sorry again for the wrong section.
vaibhavknockout said:
Sorry madam for posting this in wrong thread. How stupid of me........I am trying to learn writing updater scripts and I am modifying CM9's script to do that. Recovery gives me Error 6. I am modifying this in notepad++, I had already checked for newline characters. Since I am a newbie in porting and stuff, I don't even know whether I need to make a new update-binary for every change I make in updater-script. I searched for hours on google about this problem but with no sucess. I never felt this miserable...
Sorry again for the wrong section.
Click to expand...
Click to collapse
First of all, there is much more to updater-script than you appear to have knowledge of, and I am only saying this to point you to the right direction.
You need to do a little reading in order to really understand what each line does.
Otherwise, chances are, you will not be able to make a bootable ROM.
Update-binary does not need any changing though.
You should not feel miserable, just search and look in the right places.
iridaki said:
First of all, there is much more to updater-script than you appear to have knowledge of, and I am only saying this to point you to the right direction.
You need to do a little reading in order to really understand what each line does.
Otherwise, chances are, you will not be able to make a bootable ROM.
Update-binary does not need any changing though.
You should not feel miserable, just search and look in the right places.
Click to expand...
Click to collapse
I read the link you gave, it is informative indeed. But still doesn't solve my problem. The link is for syntax used in update-scripts. Since I am a Perl programmer by hobby, I do understand quite a lot of those commands in both update-script and updater-script and correct syntax associated with them (mostly based on linux). My questions are -
1. Do we have to write an update-script or an updater-script to flash a zip?
2. Updater-script is associated with an update-binary. What is it's role? Can we copy it from anywhere? If yes, then why is this binary encoded file of different size?
3. Can I write an update-script and use kitchen to convert it to updater-script? If yes, then why is kitchen giving me padded zeroes at the end of updater script?
4. If my build.prop has "ro.product.device="anzu"" and if my updater-script asserts for it using correct syntax, then why on earth is recovery giving me error 6 at the assert step?
5. If I don't have a file (say /system/lib/hw/abc) and if my updater-script calls it (say symlink toolbox /system/lib/hw/abc), then will the updater-script execution fail completely or does it skip it and move forward?
6. How would I know whether I can write boot image in xperia phones or not? Is there any list?
So in sum, I know and have found many guides to write syntax in updater-script and update-script but I couldn't find any guide which could explain all the above question clearly. Since android community (especially at xda) believes in helping out each other, I am astonished by the fact that what is the purpose of keeping this secrecy in instructions on how to make a proper bootable zip or port a ROM. I wanted to learn all this so that I could bridge this gap of knowledge like I did with my Namaste guide.
PS: You have something with colors. You have an elegant way of choosing colors in things as complex as themes and as trivial as fonts. I am a fan.
Ciao,
Vaibhav
vaibhavknockout said:
1. Do we have to write an update-script or an updater-script to flash a zip?
Click to expand...
Click to collapse
update-script is for "Amend Scripting" used in CWM prior to 3.0. update-script (and binary associated) is for "Edify Scripting" used in CWM 3.0 +. Both have different syntax. Basically use updater-script as it is latest.
vaibhavknockout said:
2. Updater-script is associated with an update-binary. What is it's role? Can we copy it from anywhere? If yes, then why is this binary encoded file of different size?
Click to expand...
Click to collapse
As mentioned above! updater script requires update-binary to work as all functions are defined in the binary.
vaibhavknockout said:
3. Can I write an update-script and use kitchen to convert it to updater-script? If yes, then why is kitchen giving me padded zeroes at the end of updater script?
Click to expand...
Click to collapse
Yes, you can! Probably kitchen's converter is messed-up. You can manually remove the zeroes.
vaibhavknockout said:
4. If my build.prop has "ro.product.device="anzu"" and if my updater-script asserts for it using correct syntax, then why on earth is recovery giving me error 6 at the assert step?
Click to expand...
Click to collapse
What error is it giving? Also, make sure to use the correct update-binary as there are different versions floating around.
vaibhavknockout said:
5. If I don't have a file (say /system/lib/hw/abc) and if my updater-script calls it (say symlink toolbox /system/lib/hw/abc), then will the updater-script execution fail completely or does it skip it and move forward?
Click to expand...
Click to collapse
Yet to try!
vaibhavknockout said:
6. How would I know whether I can write boot image in xperia phones or not? Is there any list?
Click to expand...
Click to collapse
boot image cannot be written in recovery for all Xperia phones. Basically boot partition is locked when phone is turned on, in all Xperia phones.
ameer1234567890 said:
update-script is for "Amend Scripting" used in CWM prior to 3.0. update-script (and binary associated) is for "Edify Scripting" used in CWM 3.0 +. Both have different syntax. Basically use updater-script as it is latest.
As mentioned above! updater script requires update-binary to work as all functions are defined in the binary.
Yes, you can! Probably kitchen's converter is messed-up. You can manually remove the zeroes.
What error is it giving? Also, make sure to use the correct update-binary as there are different versions floating around.
Yet to try!
boot image cannot be written in recovery for all Xperia phones. Basically boot partition is locked when phone is turned on, in all Xperia phones.
Click to expand...
Click to collapse
Thanks for answering some of my doubts and clearing the difference between update-script and updater-script. Your pointing my attention towards update-binary and it's importance caused me to read in that direction and ultimately solving it. It turns out that update-binaries are made chipset specific and if we don't use mogami specific update-binary (e.g. from CM9 for xperia arc), then assert check will fail. Hope this will help a lot of people.
PS: And this time I will try and compile another guide (like Namaste guide) to explain making flashable update.zip's, avoiding the commonly followed syntax part and focusing more on importance and functions of each component in the process.
Cheers,
Vaibhav
Hello, starting to get comfortable with Cygwin/Kitchen but still new at it. After repackaging and trying to flash Wicked Sensations, TWRP gives me an error (paraphrasing) "format, expect 3 args got 4".
I'm allowing the kitchen at the outset to convert updater script to "update" script, and allowing it to reconvert when it repackages. I'm accepting all defaults when repackaging.
I wonder if the kitchen is incompatible with some custom ROM's depending on what was used to create it in the first place? Or does somebody know where I'm going wrong? Thanks a million
Switch out the update binary with the original file from META-INF/com/google/android
CNexus said:
Switch out the update binary with the original file from META-INF/com/google/android
Click to expand...
Click to collapse
could you give me a little more detail? I see where the update-binary file is in the working ROM folder, but I don't see what to replace it with or where to paste that one?
SanDiegoHB said:
could you give me a little more detail? I see where the update-binary file is in the working ROM folder, but I don't see what to replace it with or where to paste that one?
Click to expand...
Click to collapse
It seems like the mayhem replaced the original update-binary...so replace it with the original update-binary from the Wicked Sensations rom zip
CNexus said:
It seems like the mayhem replaced the original update-binary...so replace it with the original update-binary from the Wicked Sensations rom zip
Click to expand...
Click to collapse
Sorry for the bother, I hate sounding dense, I'm just not following you because the only decompiled copy I have of the "update-binary" is the one in the Working ROM folder which was created from the original wicked sensations zip....
Huh...ok, post the "format(...." code that you have in your new updater-script
CNexus said:
Huh...ok, post the "format(...." code that you have in your new updater-script
Click to expand...
Click to collapse
thanks for your patience.
Here's what the "working rom" updater-script.orig says (note there are 3 arguments)
format("ext4", "EMMC", "/dev/block/mmcblk0p14");
But here's the error I get when I try to flash the rom with TWRP,
format () expects 3 args, got 4
E:Error executing updater binary in zip '/extern (it cuts off there)
Error flashing zip '/external_sd/(name of rom)
So I decided to decompile this output rom that gave me the error, and here's what the final updater-script says re: format:
format("ext4", "EMMC", "/dev/block/mmcblk0p14", "0");
As you said, it looks like something happens in the repackaging
Yeah, just use the original "format" command that only takes three arguments
And by "use" I mean copy it over to the new updater script
I also just found this http://forum.xda-developers.com/showthread.php?t=1906605 so I'll do some experimenting. What do you make of this:
"The problem is the Kitchen update to updater conversion. The kitchen doesnt make correctly the conversion. So the solution is: not give any script to kitchen for conversion, remove META-INF folder from original zip and let kitchen create a fresh updater.."
What is it that yoy are editing/changing with the kitchen? Because as long as you are not removing any files, you can use the entire META-INF folder from the original ROM in your edited ROM
CNexus said:
What is it that yoy are editing/changing with the kitchen? Because as long as you are not removing any files, you can use the entire META-INF folder from the original ROM in your edited ROM
Click to expand...
Click to collapse
Thanks for the tip! I was extracting (again) and decided to tell the kitchen to NOT do any update/updater conversion. Made my minor wallpaper edits. Repackaged. And everything worked like a charm.
Thank you very much!
SanDiegoHB said:
Thanks for the tip! I was extracting (again) and decided to tell the kitchen to NOT do any update/updater conversion. Made my minor wallpaper edits. Repackaged. And everything worked like a charm.
Thank you very much!
Click to expand...
Click to collapse
No problem
Whenever I try and flash Super Nexus, PA I get the same error Binary yada yada any general fix?
UPDATE: I added screenshot to the power menu for anyone who is interested.
Hello all!
I recently saw a pretty cool advanced power menu mod for the Nexus 7 and really wanted it for our Nexus 4. Unfortunately, the developer did not have time to make a version for the Nexus 4. I modified the framework-res.apk and androidpolicy.jar from the zip on the Nexus 7 thread to work on the Nexus 4. The result is pretty close to the original mod and it looks great. I've only tested it on a stock deodexed JWR66Y build. This won't work on odex ROMs. If you have any modifications to your framework-res.apk or androidpolicy.jar this modification will overwrite your current one.
I personally like to use the stock ROM and having this advanced power menu is really nice. I just wanted to share this with everyone!
All credit goes to scrosler for his awesome mod so go give him some thanks on the original thread:
http://forum.xda-developers.com/showthread.php?t=2380413
Instructions:
1. Reboot to recovery
2. Mount system
3. Flash zip
4. Reboot
Enjoy!!
With "Screenshot" in the power menu:
https://dl.dropboxusercontent.com/u/43701045/APM - 4.3 - DE-ODEX -(With Screenshot).zip
Without "Screenshot" in the power menu:
https://dl.dropboxusercontent.com/u/43701045/APM - 4.3 - DE-ODEX - (Without Screenshot).zip
Could you make a version for stock/odex please?
I have this stock, deodexed JWR66Y rom installed,
http://forum.xda-developers.com/showthread.php?t=2010887
I'm trying to flash your mod. It appears to flash successfully in TWRP, but it is not working. Neither android.policy.jar or framework-res.apk are modified when I reboot after flashing this. I'm using ziddey's kernel based off franco's kernel, and there have been changes to framework-res.apk. Could that be the reason that nothing gets installed?
EDIT: I decided to manually install the 2 files, and that works fine. So I'm guessing that the mount command in the updater-script is incorrect? Did you actually get your zip file to install successfully on the Nexus 4? Or did you just install the files manually?
EDIT2: A couple of hours later, I changed the mount command in your updater-script (to be like one I have in another Nexus 4 update.zip), and it flashes just fine! But another person has reported that this works fine for him, so I'm very confused.
EDIT3: Well, here are my conclusions, some of which are the same as already described above. (I do know that I can use an app to get the advanced power menu, but I'm trying to figure out why this mod works for some but not for me).
1. Flashing this zip as-is does not install either file (android.policy.jar and framework-res.apk). I believe it's due to the mount.
2. Manually installing the 2 files DOES work, i.e. the advanced power menu displays when holding down the power button.
3. Changing the mount command in the updater-script DOES work.
original mount (fails?): mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
modified mount (works): mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
4. I found another mod for the advanced power menu which only modifies android.policy.jar and NOT framework-res.apk, and it DOES work. See this thread. http://forum.xda-developers.com/showthread.php?t=2383509
By the way, it has a completely different way of mounting, i.e. run_program("/sbin/busybox", "mount", "/system");
I'm hoping babalonius508 (or anyone else who says this mod is working) can help me figure out why the mount works for them and not for me!
EDIT4: I'm using TWRP. I booted into recovery and used ADB. I tried a mount similar to the "tegra" one that is in this mod's updater-script (see 3. above). It failed. Then I did one with the "sdcc" one (again, see 3. above). It worked.
So...does this have something to do with which recovery is used? I'm wondering if those who are failing to get this to install are running TWRP (like me), while those who are successful are running CWM. I could try installing CWM and test this myself, but it's late, and maybe some others can chime in here and see if I'm on the right track. Well, if I really think about it, I don't think recovery has anything to do with it. I don't see how this could possibly be working with that mount command. Anyone who has this working on the Nexus 4, please post here and tell me how!
random hero said:
Could you make a version for stock/odex please?
Click to expand...
Click to collapse
I'm searching stock / odex, too! Would be great! :good:
alfiriel said:
I'm searching stock / odex, too! Would be great! :good:
Click to expand...
Click to collapse
Here!
http://forum.xda-developers.com/showthread.php?t=2383509
Very useful . Thanks
Sent from my Nexus 4 using xda app-developers app
random hero said:
Could you make a version for stock/odex please?
Click to expand...
Click to collapse
alfiriel said:
I'm searching stock / odex, too! Would be great! :good:
Click to expand...
Click to collapse
I'll definitely try and do an odex version as soon as I can!
sga999 said:
I have this stock, deodexed JWR66Y rom installed,
http://forum.xda-developers.com/showthread.php?t=2010887
I'm trying to flash your mod. It appears to flash successfully in TWRP, but it is not working. Neither android.policy.jar or framework-res.apk are modified when I reboot after flashing this. I'm using ziddey's kernel based off franco's kernel, and there have been changes to framework-res.apk. Could that be the reason that nothing gets installed?
EDIT: I decided to manually install the 2 files, and that works fine. So I'm guessing that the mount command in the updater-script is incorrect? Did you actually get your zip file to install successfully on the Nexus 4? Or did you just install the files manually?
EDIT2: A couple of hours later, I changed the mount command in your updater-script (to be like one I have in another Nexus 4 update.zip), and it flashes just fine! But another person has reported that this works fine for him, so I'm very confused.
EDIT3: Well, here are my conclusions, some of which are the same as already described above. (I do know that I can use an app to get the advanced power menu, but I'm trying to figure out why this mod works for some but not for me).
1. Flashing this zip as-is does not install either file (android.policy.jar and framework-res.apk). I believe it's due to the mount.
2. Manually installing the 2 files DOES work, i.e. the advanced power menu displays when holding down the power button.
3. Changing the mount command in the updater-script DOES work.
original mount (fails?): mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
modified mount (works): mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
4. I found another mod for the advanced power menu which only modifies android.policy.jar and NOT framework-res.apk, and it DOES work. See this thread. http://forum.xda-developers.com/showthread.php?t=2383509
By the way, it has a completely different way of mounting, i.e. run_program("/sbin/busybox", "mount", "/system");
I'm hoping babalonius508 (or anyone else who says this mod is working) can help me figure out why the mount works for them and not for me!
EDIT4: I'm using TWRP. I booted into recovery and used ADB. I tried a mount similar to the "tegra" one that is in this mod's updater-script (see 3. above). It failed. Then I did one with the "sdcc" one (again, see 3. above). It worked.
So...does this have something to do with which recovery is used? I'm wondering if those who are failing to get this to install are running TWRP (like me), while those who are successful are running CWM. I could try installing CWM and test this myself, but it's late, and maybe some others can chime in here and see if I'm on the right track. Well, if I really think about it, I don't think recovery has anything to do with it. I don't see how this could possibly be working with that mount command. Anyone who has this working on the Nexus 4, please post here and tell me how!
Click to expand...
Click to collapse
I actually don't use TWRP so its hard for me to guide you on that because I have very little experience with it. When flashing this mod in ClockworkMod recovery, I simply mount system before I flash.
If all else fails just take the framework-res.apk and androidpolicy.jar out of the flashable zip, put it in system/framework, and change the permissions of both the files to rw-rw-r-- and reboot. Don't forget to make a backup of your current framework-res.apk and androidpolicy.jar. I hope you can get it working!
Not bad, i'll give a try!
babalonius508 said:
I actually don't use TWRP so its hard for me to guide you on that because I have very little experience with it. When flashing this mod in ClockworkMod recovery, I simply mount system before I flash.
If all else fails just take the framework-res.apk and androidpolicy.jar out of the flashable zip, put it in system/framework, and change the permissions of both the files to rw-rw-r-- and reboot. Don't forget to make a backup of your current framework-res.apk and androidpolicy.jar. I hope you can get it working!
Click to expand...
Click to collapse
If you look at my first EDIT comment, you'll see that I did do each part manually, and it worked fine. But the issue was how to get your zip file to work "as is", i.e. without issuing a mount command during recovery (whether CWM or TWRP). With other zip files that I flash, the mount is done correctly in the script. I've moved on to using Xposed with either GravityBox or Xblast, which means no more flashing.
Hello,
I am starting to modify the stock rom for N5120. For now, I have Dsixda Kitchen running under Windows XP SP3, and successfully (at least without errors) added root, busybox, deodexed, etc. Now , all I need to do is to build a new rom, right?
Then, there comes my question. N5120 is not listed in the supported devices of Dsixda Kitchen.
If I understand well (I am not sure, though), adding a new device means adding mount points (?) etc, right?
I am just modding some features in the same rom (I am not porting to a different device). Should I still need to add N5120 support?
If yes, could someone please lead me to a concrete tutorial? There is some instructions on the original thread of Dsixda kitchen, but the instructions are not very clear for me. I am just starting to learn. So, there are many things I don't know or I don't understand. So, please forgive my lack of knowledge.
Thank you in advance.
PS: I thought asking this question in the original thread, but the original thread is closed now.
3to4 said:
Hello,
I am starting to modify the stock rom for N5120. For now, I have Dsixda Kitchen running under Windows XP SP3, and successfully (at least without errors) added root, busybox, deodexed, etc. Now , all I need to do is to build a new rom, right?
Then, there comes my question. N5120 is not listed in the supported devices of Dsixda Kitchen.
If I understand well (I am not sure, though), adding a new device means adding mount points (?) etc, right?
I am just modding some features in the same rom (I am not porting to a different device). Should I still need to add N5120 support?
If yes, could someone please lead me to a concrete tutorial? There is some instructions on the original thread of Dsixda kitchen, but the instructions are not very clear for me. I am just starting to learn. So, there are many things I don't know or I don't understand. So, please forgive my lack of knowledge.
Thank you in advance.
PS: I thought asking this question in the original thread, but the original thread is closed now.
Click to expand...
Click to collapse
PS2: I found and obrained Recovery.img from Stock rom, and made a file for Edify_Defs. As I don't understand anything, I duplicated the file for N7100, renamed it as GT-5120 and changed the mount point numbers(?).
Can anyone tell me if it is OK? Is there a risk of a brick if I go ahead with this file?
PS: I think the Edify_Defs file must be renamed to konalte. That's what is in ro.product.device.in build.prop.
PS2: I built a rom with "konalte". and it seems that the mount points are set correctly, but CWM fails to flash (Error status 6)... Can anyone help?
3to4 said:
PS2: I found and obrained Recovery.img from Stock rom, and made a file for Edify_Defs. As I don't understand anything, I duplicated the file for N7100, renamed it as GT-5120 and changed the mount point numbers(?).
Can anyone tell me if it is OK? Is there a risk of a brick if I go ahead with this file?
PS: I think the Edify_Defs file must be renamed to konalte. That's what is in ro.product.device.in build.prop.
PS2: I built a rom with "konalte". and it seems that the mount points are set correctly, but CWM fails to flash (Error status 6)... Can anyone help?
Click to expand...
Click to collapse
Its because the mount points are incorrect.
Just try and understand the work done on this thread..............m sure it will help out!
Thank him @BHARDIK
How To set Device Mount Points in Cygwin Android Kitchen for Any Android Device
m_jani said:
Its because the mount points are incorrect.
Just try and understand the work done on this thread..............m sure it will help out!
Thank him @BHARDIK
How To set Device Mount Points in Cygwin Android Kitchen for Any Android Device
Click to expand...
Click to collapse
However, someone gave me a hint from another thread, and I was able to flash two or three roms for testing.
I deleted META-INF folder before building a rom, and then, I deleted two lines in the script. And, everything went well.
The mount points I set in the files were correct.
I appreciate your comments. Thank you.
5120 mount points:
mount("ext4", "EMMC", "/dev/block/mmcblk0p20", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p21", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p19", "/cache");
package_extract_file("boot.img", "/dev/block/mmcblk0p9");
package_extract_file("modem.bin", "/dev/block/mmcblk0p13");
THL T200 Help
I am stuck in add device.
this is my recovery.fstab content:
/boot emmc /dev/bootimg
/cache ext4 /[email protected]
/data ext4 /[email protected]
/misc emmc /dev/misc
/recovery emmc /dev/recovery
/emmc vfat /[email protected]
/system ext4 /[email protected]
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
This sould? be my edify dev scrip?
THL
# THL T200
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD??????
sys_mnt=\/dev\/block\/mmcblk0p25???????????
cache_mnt=\/dev\/block\/mmcblk0p27?????????
boot_mnt=\/dev\/block\/mmcblk0p22??????????
data_mnt=\/dev\/block\/mmcblk0p26??????????
sdcard_mnt=\/dev\/block\/mmcblk1p1?????????
please help
I have the same problem always mount to MTD ,I really want Emmc Does anyone know please help me
hello ,
how can i remove starting verizon logo??? and i don,t want any other logos,
i just need like stock samsung boot, for note 4
remember i have not .zip file in media folder
Mr Hassan said:
hello ,
how can i remove starting verizon logo??? and i don,t want any other logos,
i just need like stock samsung boot, for note 4
Click to expand...
Click to collapse
You can use a app like this: https://play.google.com/store/apps/details?id=tkstudio.sboot to change boot animation or some ROMS like jasmine rom 7.0 have the original samsung logo boot sequence, for the app to work you need root and read carefully before doing anything. Hope this helps.
-spektor- said:
You can use a app like this: https://play.google.com/store/apps/details?id=tkstudio.sboot to change boot animation or some ROMS like jasmine rom 7.0 have the original samsung logo boot sequence, for the app to work you need root and read carefully before doing anything. Hope this helps.
Click to expand...
Click to collapse
thanks brother for reply i fixed this problem, now i,m in another project , i successfully extract the system,img,ext file,,,,now i edited somethings,
now i want to create again in same file, img,ext4
have you any idea about it?
Mr Hassan said:
thanks brother for reply i fixed this problem, now i,m in another project , i successfully extract the system,img,ext file,,,,now i edited somethings,
now i want to create again in same file, img,ext4
have you any idea about it?
Click to expand...
Click to collapse
Well if you mean like accessing and editing system files I'm not how to do edit them but I know that you can use a app like root explore: https://play.google.com/store/apps/details?id=com.speedsoftware.explorer that's the free version the paid one is $3.99 in the US. With that you can move and add files to system folder you can edit permission of files and things of that nature.
-spektor- said:
Well if you mean like accessing and editing system files I'm not how to do edit them but I know that you can use a app like root explore: https://play.google.com/store/apps/details?id=com.speedsoftware.explorer that's the free version the paid one is $3.99 in the US. With that you can move and add files to system folder you can edit permission of files and things of that nature.
Click to expand...
Click to collapse
ok brother thanks alot,
but i,m talking about stock rom, i already extracted and edit now its need to repack again
Mr Hassan said:
ok brother thanks alot,
but i,m talking about stock rom, i already extracted and edit now its need to repack again
Click to expand...
Click to collapse
Ah ok, so I found these two threads related to the subject one is for repackaging ODIN files if your using a Samsung: https://forum.xda-developers.com/showthread.php?t=2549712&page=5 and the other is a general tutorial on custom roms https://forum.xda-developers.com/showthread.php?t=2195858 Also this article covers mostly everything about creating and installing ROMS http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/ I hope this information helps I do not know much about creating or repackaging roms
-spektor- said:
Ah ok, so I found these two threads related to the subject one is for repackaging ODIN files if your using a Samsung: https://forum.xda-developers.com/showthread.php?t=2549712&page=5 and the other is a general tutorial on custom roms https://forum.xda-developers.com/showthread.php?t=2195858 Also this article covers mostly everything about creating and installing ROMS http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/ I hope this information helps I do not know much about creating or repackaging roms
Click to expand...
Click to collapse
ok again thanks,
i,m in samsung note 4 , and i found lot of threads to repack but not success, coz i,m counfuse about where i start?
and how, is that need just system folder or all file like hidden ,cache etc etc
Mr Hassan said:
ok again thanks,
i,m in samsung note 4 , and i found lot of threads to repack but not success, coz i,m counfuse about where i start?
and how, is that need just system folder or all file like hidden ,cache etc etc
Click to expand...
Click to collapse
Well system file is where all the data and software is at basically everything visible on the phone. Maybe this article could help it deals with modifying samsung rom and flashing it. If you want to read more on it here's the link: http://android.stackexchange.com/questions/85703/modifying-samsung-rom-and-flashing-it-on-a-device if you wanted to remove apps or add custom apps to your phone you would modify system file.
But what I thought was important was this;
(I did not write this thread)
< "You should be able to use an archive program on PC and recompress to .tar, .gz, and others. Dont forget to re-sign the archive. Keep a copy of your untouched ROM until you have the modified ROM tested and running.
The ROMs are signed with a signature. When repacking if they don't get signed they will fail in flashing. This link will help explain it.
So basically after downloading the firmware you have to rename it so you can extract the files, change them as you need, recompress them again and re-sign them, so you can flash them using Odin." >
This thread was dealing with modifying CM rom;
< "There are multiple solutions available:
Re-Zip the Image
Advantage: You do it once, and can use the resulting image for multiple devices. That's what I did with CM7.2 for my Milestone 2. Easy enough to do:
create a temporary (empty) folder
unzip the zip file to it
remove unwanted *.apk files from /system/apps (be careful of what you remove, of course)
zip up the directory contents again
Using a graphical ZIP manager (like WinZip or the like), steps would be even easier:
open the zip file with the archive manager
remove the unwanted .apk files
if the ZIP manager requires it, save the manipulated zip
Manually cleanup after flashing, using the shell
This is what ce4 recommended in the comments. It requires you using a terminal emulator on your device:
Flash the image as-is
remove superfluous stuff from the system partition by hand (like rm /system/big/junk/example.mp4)
Manually cleanup after flashing, using other tools
Almost the same as the previous method, but a bit more user-friendly. Disadvantage: this won't do for superflous ringtones and the like:
Flash the image as-is
Use a tool like Titanium Backup or Root Uninstaller to remove unwanted system apps" >
Edit: this link explains the signature of the file: (from google) https://code.google.com/archive/p/zip-signer/
-spektor- said:
Well system file is where all the data and software is at basically everything visible on the phone. Maybe this article could
Edit: this link explains the signature of the file: (from google) https://code.google.com/archive/p/zip-signer/
Click to expand...
Click to collapse
yes brother i want to remove some apps,. in system
even some edits in bulid prop
and after repack it for odin , thats it,
i create zip and trying to install the via twrp, during installation in end its give some error like this
setup finish with error 7 etc etc
so i reboot ,.....its reboot normal but after boot base band is unknown
i,m working on verizon devise.
in very simple words i,m trying to create rom without verizon apps and some more edits
and that all work in stock rom
Mr Hassan said:
yes brother i want to remove some apps,. in system
even some edits in bulid prop
and after repack it for odin , thats it,
i create zip and trying to install the via twrp, during installation in end its give some error like this
setup finish with error 7 etc etc
so i reboot ,.....its reboot normal but after boot base band is unknown
i,m working on verizon devise.
in very simple words i,m trying to create rom without verizon apps and some more edits
and that all work in stock rom
Click to expand...
Click to collapse
Ok so I may have found a solution for you it requires a pc and to download a program. You'll need your rom and any apps you would like to insert into it. The program is as simple as right click and delete for any apps you want to remove. The program is made by a developer on XDA named "_Logie" here's the link to the Web page: http://m.tech.firstpost.com/news-analysis/how-to-add-or-remove-apps-from-a-custom-rom-101986.html and the link to the program is on there or here's the direct link: http://www.solidfiles.com/d/da2dd6335d/
This program compiles the ROM into a .zip if you have TWRP recovery you could do a backup of your previous rom before flashing your current one because you'll have to completely wipe every main partition before flashing new rom to ensure you don't run into problems
Edit: backup system, data, and cache because those are the ones you'll need to wipe also before wiping them just in case I would remove any password that locks your phone because if you try to flash a new rom and fails and your left with the recovery file it'll mess up the password, fingerprints will be forget and backup password will be unchangeable and will require a factory reset to be able to change it.
-spektor- said:
.
Click to expand...
Click to collapse
Who its looking cool. I'll try tomorrow
But for now brother i want to know its remove the apps. OK and what about bulid.prop? I need to edit it also. And after edit i don't want root anymore .after edit i need in tar format
I know you think I'm made but i know it's possible
Mr Hassan said:
Who its looking cool. I'll try tomorrow
But for now brother i want to know its remove the apps. OK and what about bulid.prop? I need to edit it also. And after edit i don't want root anymore .after edit i need in tar format
I know you think I'm made but i know it's possible
Click to expand...
Click to collapse
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
-spektor- said:
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
Click to expand...
Click to collapse
Ok apps done
Bulid done
Now final thing need . repack in ext4 format
I'll check these things tomorrow
-spektor- said:
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
Click to expand...
Click to collapse
brother did you found anything for repack ext4 img?
Mr Hassan said:
brother did you found anything for repack ext4 img?
Click to expand...
Click to collapse
Have you tried this guide? https://forum.xda-developers.com/showthread.php?t=1588461
-spektor- said:
Have you tried this guide? https://forum.xda-developers.com/showthread.php?t=1588461
Click to expand...
Click to collapse
yes but its for linux , and for window 99% unsuccessfully rates , have you try in window ? this ?
now i,m in next step if you have the time so kindly share your experience
https://forum.xda-developers.com/android/help/repack-img-giving-error-odin-invalid-t3577719
Hmmmmm ? I think you want to change the boot animation (white Verizon logo red background? ) if so your gonna need to either need to flash a pre-made zip with Flashfire (can't seem to get it to apply from twrp) or your gonna need to manually copy into the appropriate directory (mount system directory r/w copy then change permissions of the file you copied to 644 and reboot) presumably with a root explorer though doable from terminal
---------- Post added at 07:47 PM ---------- Previous post was at 07:29 PM ----------
-spektor- said:
Ok so I may have found a solution for you it requires a pc and to download a program. You'll need your rom and any apps you would like to insert into it. The program is as simple as right click and delete for any apps you want to remove. The program is made by a developer on XDA named "_Logie" here's the link to the Web page: http://m.tech.firstpost.com/news-analysis/how-to-add-or-remove-apps-from-a-custom-rom-101986.html and the link to the program is on there or here's the direct link: http://www.solidfiles.com/d/da2dd6335d/
This program compiles the ROM into a .zip if you have TWRP recovery you could do a backup of your previous rom before flashing your current one because you'll have to completely wipe every main partition before flashing new rom to ensure you don't run into problems
Edit: backup system, data, and cache because those are the ones you'll need to wipe also before wiping them just in case I would remove any password that locks your phone because if you try to flash a new rom and fails and your left with the recovery file it'll mess up the password, fingerprints will be forget and backup password will be unchangeable and will require a factory reset to be able to change it.
Click to expand...
Click to collapse
Try flashing with flasfire enabling the option mount system r/w and use common paths (probably not necessary but won't hurt) I have had difficulty getting anything other than ROM and gapps to apply from twrp but flashfire seems to work . I'm thinking its due to the fact that flashfire flashes after boot loader and then resets prior to os load.