I've read, I've tried using other ROMs scripts, I've googled. I still don't understand. I set up the kitchen, tried that way. Fail. All I want is the D80020y system folder I have made into a flashable zip. Don't need kernel, just want to update the system. I don't get when, or even how, or why to symlink. When to Loki? Can someone competent enough help me out? Thank you.
Related
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
I am looking for some guidance as to what I may be doing wrong here. I've followed the instructions here:
http://www.londatiga.net/it/how-to-create-android-update-zip-package/
and I've created an update.zip with all of the basic stuff that I do after a flash of DG's Cognition releases. It should put stuff in /system/etc, /system/media, and /data/gps. Every step has been followed to the T, however when I try to apply it, I get "Installation Aborted". It seems I can apply it through ROM Manager, but I'm hard-headed and want to figure out how to get it to work natively.
I've attached my update.zip for perusal, so someone might be able to see where I've gone astray.
Thanks for any help.
Hello Daoist, not sure if u got my messages, so here goes. Im on a rooted stock US transformer os version 8.6.5.9 i tried using your method to update to 8.6.5.13 and i used the check if all apks are there .zip you included in that tutorial. The test zip showed me that for some reason im missing kindle-oem.odex kindle-oem.apk maps.odex and maps.apk. So now im at a loss on what can be done, i would love to get my transformer up to speed, 8.6.5.19 I believe is your latest tutorial update. Any help will be greatly appreciated.
Vitto
If you want to update, you have a few choices:
1) find the source and restore the missing/modded files. You can download the manaul updates from the ASUS website (but you need to know how to unblob the files), or there might be a full rom floating around somewhere on xda or the internet.
2) modify the ota so that it skips the kindle and maps files. This would involve editing the updater-script and removing 8 lines- 2 lines for each file. Then rezip everything, (sign it), and flash it.
You could also roll your own custom rom...
Thank you gee one I would have to go with option 1 as i have no idea about either coding or editing a script. So far no luck with the source I might end up d/ling the update from asus website, just need to learn how to unblob it.
Vitto
Ok so i dug through couple of .zips even found the files and got them back in system/app but update is still not recognizing them. Any way anyone could post kindle-OEM.odex maps.apk and maps.odex from v8.6.5.9 US? If sharing apks and files like that is not allowed then i am truly sorry i even mentioned it.
Vitto
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?
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 !