I am trying to figure out how to create a dummy test file for testing out the OTA process. I have been told there is a way to make such a test OTA file, but have not been able to find any info on how to do so online.
Essentially, I want it to be in the format of an OTA package, but not to actually perform an OS update.
Hi !
This is something related to development
If you have already built your own rom then there is something related to updater script file which needs a certain editing and signing
Here is a tutorial about updater script , I don`t know how much it helps
https://forum.xda-developers.com/showthread.php?t=1931585
You must also learn about Edify script language information which can be found on google wiki
Good luck !
Related
Hi guys, I was wondering how you would go about personalizing ROMs for your own use. Nothing code-wise, but installed programs and such. Opening up the zip files of downloaded ROMs I see the apk files and the system apk files - is it really as easy as just removing those you don't want and plotting in the ones that you do?
If this rom is from the same board as you, can say so.
But, .. you still need to run a linux terminal the code to sign the package that you previously made with same special files..
Just the search tools and you'll find it!
...You can easily too start porting rom's too...
I would love to help the community by using your kernel for the newer radios to port any roms for the older radio... is there any help you can give me? should i use your boot.img from the test-donut.img/test-eclair.img?
Click to expand...
Click to collapse
first, a thing we must know for porting job is what boot.img included.
here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
the ramdisk do some initializing jobs, so if we port a ROM, we should ensure that the content in ramdisk and files which are included in ramdisk (like init.rc), have necessary things the ROM needed.
for the first step, we can just extract the boot.img from the ROM, and extract the ramdisk from the boot.img which extracted just now, then repack it with my kernel (you can extract the kernel from my boot.img with same tools).
(to execute the perl script in link above, you need linux or just cygwin. )
but if we are sure that the ROM we want to port have nothing special with ramdisk, just like common ROMs, we can use my boot.img files directly. for eclair ROM, I suggest you extract the boot.img from my ROM, and don't use the first boot.img (test-NOCDB.img) I had posted.
after this, make our update.zip (use other's ROM as an example, especially the update-script in META-INF directory). sign our zip with testkey and apply it, then we can make our phone booting into desktop.
(you can find information about sign and download tools here: http://forum.xda-developers.com/showthread.php?t=471586, though the thread is not talk about how to sign things)
the main troubles we may meet probably are symlinks and setperm* in the update-script. if there is already a file/link has a name we want to symlink to, or if there isn't a file we want to symlink from or setperm, we will fail. so check the files carefully.
the next step is make everything work properly. we can use file from a ROM which made for new radio (and work well of course) to replace the one in the ROM we are porting. we can find these files in my 2.x ROM for eclair, or other's 1.6 ROM for donut (and for new radio, since the maker of them tested them already).
the most important files are (to my knowledge):
system/lib/libhtc_acoustic.so
system/lib/libhtc_ril.so (if something wrong with mobile network)
system/lib/libcamera.so
system/lib/libcameraservice.so
system/lib/liboemcamera.so (for 2.x) or system/lib/libqcamera.so (for 1.6)
system/lib/libgps.so
system/bin/akmd
(are there something I missed?)
(if we want to use NCommander's work on CameraHardwareInterface with a 2.x ROM, we should use my kernel for DONUT instead. I didn't try it, and I don't recommend it.)
these files are some thing work with hardware partially, so different radio may need different files. but if something just work fine, don't hurry to replace the file for it.
and now...., I don't have more thing to talk about, since we have most things work well. but for further tweaks, there are lots of things to do.
everyone can post your question here. if I know the answer I will post it. if I don't or I am not online, I think others will response you. and if there are things I missed or made some mistake, plz point it out
I will update this post when we collection more info or correct something. I find that I don't organized everything in order . I will update it later.
Thanks for the post... what's the difference between your eclair/donut kernel? (This is based on your original post about your kernel... is there an updated kernel somewhere i should know about?)
Edit
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions
Thank you very much for this sanpei. This is the type of posts that really should be on this forum
Appreciated so much. waiting for your next updates.
Phil_McRevis said:
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions
Click to expand...
Click to collapse
sorry for my poor ability of expression
asero said:
This is the type of posts that really should be on this forum
Click to expand...
Click to collapse
I expect more people can share their knowledge, and we can make a wiki for all
Hello!
I have to edit some lines of init.rc of your kernel. I've thus extracted the ramdisk, edited the file, repacked and tried booting with fastboot boot kernel-img ramdisk-img, but the phone hangs on the operator logo. I've tried even just extracting kernel+ramdisk and boot them - same result (the boot.img works well).
how can I fix it? Thanks
Wrong post
Hey everyone!
On the rom I currently use there are about 20 apk's I have no need for. What I do is download the rom, and individually delete the apk's before flashing the rom. The thing is I flash quite often (cheeky, I know ) and this is getting quite frustrating.
Ideally I want a script that does this all for me. I found one but it seems be for running on the phone, after the apk's have been installed. Does anyone know how I can create a script for the PC that does this before I even install the rom?
Thank you for any suggestions.
Oh and here's the thread I found that looked relevant...
http://forum.xda-developers.com/showthread.php?t=674357
edcoppen said:
Hey everyone!
On the rom I currently use there are about 20 apk's I have no need for. What I do is download the rom, and individually delete the apk's before flashing the rom. The thing is I flash quite often (cheeky, I know ) and this is getting quite frustrating.
Ideally I want a script that does this all for me. I found one but it seems be for running on the phone, after the apk's have been installed. Does anyone know how I can create a script for the PC that does this before I even install the rom?
Thank you for any suggestions.
Oh and here's the thread I found that looked relevant...
http://forum.xda-developers.com/showthread.php?t=674357
Click to expand...
Click to collapse
Over what OS?
If in Windows (or any M$ OS, incl. DOS) you can make a batch file.
My file is adjunted as example (modify as you like, put in the root dir -obviously to the unzipped ROM- and run. Rezip and maybe re-sign)
salu2
Thank you. This is exactly the kind of thing I am after. If I had of been born just a few years earlier I would probably know all about batch scripts. Fortunately, I just missed the DOS days!
Anyway, I puzzled out / looked up the commands in the script you posted. Based on that I extracted the rom, then placed the batch file within it, so that the cd (current directory) command runs correctly.
Unfortunately this mucks up the signing on the rom. Do you re-sign your CM7 roms every time you do this or is there an easier way?
Edit: My PC is Win 7, 64bit, soon to be Win 8 Consumer Preview.
Edit: The roms do not need resigning.
I don't re-sign the ROM, simply flash again over Clockworkmod Recovery.. and work.
But, you can:
1) sign using Auto-Sign....
2) Click [Thanks]...
Salu2
__________________________________________________________________
I know, I know.... my english is ****ty... but my spanish is much better... ;-)
Big thank you. That's solved that one nicely for me!
You're welcome.
Updated zip in my first Post.
Salu2
Hey again. I was hoping to build on the script you kindly provided. At the moment I am using various alpha roms where the exact apk's present changes fairly often. It would be great if I could see the outcome of each action. This way I would know if the apk has had it's name changed or been removed. How would I enable this?
Here I present,
An easy to use and effective, Flashable-zip(or update.zip) Signer!
There are many update-zip(flashable zip) Signers available, but this is special.
This Signer WHOLE-FILE signs your update.zips/flashable-zips, so it can pass even recovery's Signature Verification(Tested on CWM 5.0.2.8 on HTC Wildfire S)!
Unfortunately, as I am not very veryGood at C/C++ Programming, this tool does not have a Graphic User Interface(GUI).
I apologize, but as I am new to XDA, I don't know how to insert pictures, "Code:" etc, so this thread may look very ugly to you.
Oh yes! And DON'T EVER delete any file included in the zip, as it will cause the zip signer to malfunction.
I may have made this flashable-zip Signer, but I couldn't have done it without this people:
zeppelinrox ( for teaching me a little C/C++ Programming with his scripts )
The creator of signapk.jar ( an important part of this tool )
Google ( For Creating Android so that these tools can be developed )
YOU! ( for testing out my flashable-zip Signer )
And many more, who I apologize for leaving you out
Guide to using this zip signer
To Use this Signer:
1) Unzip the file(Obviously!)
2) Copy & paste the update-zip(a.k.a flashable zip) that you want to sign into that folder.
3) Run ROM Signer.bat
4) Follow the instructions in the application.
5) When it says "File successfully signed......", You are DONE!
After File signing operation succeeds, check the "signed" folder for your signed zip file.
Thank you for Using my Flashable-zip Signer!
I would appreaciate if you would hit the "Thanks" button.
Portable Java(jPortable by PortableApps.com) DIRECT link
Here are the direct links for the 32-bit & 64-bit Windows Portable version of the Java(R) Runtime Environment:
32-bit : http://jaist.dl.sourceforge.net/pro...Versions/jPortable_7_Update_25_online.paf.exe
64-bit: http://jaist.dl.sourceforge.net/pro...rsions/jPortable64_7_Update_25_online.paf.exe
Just click on the link and the Portable Java RE should start downloading!
Nice work
Marília de Oliveira said:
Nice work
Click to expand...
Click to collapse
Lol didn't expect to see you here. Hi @haoyangw long time no see mate
Hi thanks for this signer! good work!
Please if someone can help me,
i have all firmware files for the Nokia 8110 4G and im not sure how to make the META-INF file what do i need to put in there and how to do it, as im trying to sign the package and it dose not go
yowejowe said:
Hi thanks for this signer! good work!
Please if someone can help me,
i have all firmware files for the Nokia 8110 4G and im not sure how to make the META-INF file what do i need to put in there and how to do it, as im trying to sign the package and it dose not go
Click to expand...
Click to collapse
Sorry let me better understand your issue first, you want to create a flashable update.zip for installing your firmware files right? So you want to create the correct META-INF files from scratch? Do you have TWRP recovery installed on your phone already? Cos it supports a newer kind of META-INF structure that makes a lot easier. Also your firmware files are for installing into the /system partition, or to be flashed? Sorry for having so many questions haha, I can better help you if I understand the technical details
haoyangw said:
Sorry let me better understand your issue first, you want to create a flashable update.zip for installing your firmware files right? So you want to create the correct META-INF files from scratch? Do you have TWRP recovery installed on your phone already? Cos it supports a newer kind of META-INF structure that makes a lot easier. Also your firmware files are for installing into the /system partition, or to be flashed? Sorry for having so many questions haha, I can better help you if I understand the technical details
Click to expand...
Click to collapse
HI thanks for the reply,
i have all .img files for this model i want to flash, its a kaios phone, and i have the original recovery still on it, (will the TWRP recovery work on kaios?) and yes i need to create a META-INF file from scratch.
THANKS FOR MAKING THIS TOOL!!!
You just saved me from a chao of broken bootanimation issue!
I REALLY REALLY APPRECIATE YOU AND I ALMOST CRIED( •̥́ ー •̀ू )!!!
THAAANK YOU!!!!Ｏ(≧▽≦)Ｏ
Is there a Linux version
Hello
I own a Chinese phone with a lot of unneeded applications.
Fortunately, the maker has given the .zip software to flash it.
I'm able to open and mount on my Ubuntu computer the .img files and I can see the .apk I would remove. So far so good.
But I bet it is not that easy....
I've tried searching but all I can find is for flashing back the ROM and not about making it.
I would also like to add an su binary at the correct place ...
So I would like to find some documentation for packing back the software and flash it to the device. An How TO would be great and/or some documentation about the process.
Many thanks in advance for your help !