I also posted a thread in the dream forums, and as stated above, I need the original .img's or an update.zip containing the original ION build.
The specific thing I need is the boot.img and the recovery.img
I couldn't find the original files due to all the updated builds that have been surfacing.
Thanks for the assistance!
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
anybody can tell me how to convert official ROM to update.zip
I want to know how to make an official from the ROM can customize the ROM, instead of only at others do the update.zip in thickening delete...
First, you need to run the RUU.
Check in your system TEMP folder, and you should have an update.zip there.
Unzip that, and you'll have amongst others, system.img
Extract the files via unyaffs or other means, customize your build, zip and sign.
Voila.
My guess is that a simple search via the search tool would've resolved that, then again, I guess you were too lazy to do that.
adwinp said:
First, you need to run the RUU.
Check in your system TEMP folder, and you should have an update.zip there.
Unzip that, and you'll have amongst others, system.img
Extract the files via unyaffs or other means, customize your build, zip and sign.
Voila.
My guess is that a simple search via the search tool would've resolved that, then again, I guess you were too lazy to do that.
Click to expand...
Click to collapse
I have get the system.img, but I don't know what tools and methods reduction system.img to update.zip file format,can replace programs self.
Can you explain it step by step?
He actually told you in the post above to use unyaffs, all you need to know is already in this forum if you search for it. Here's a thread to get you started:
http://forum.xda-developers.com/showthread.php?t=566235
thanks , i went to see
https://xiaomifirmware.com/roms/download-official-roms-for-xiaomi-mi-a2-lite/
or this one seems to be even more up to date (credits to a1291762 for finding it)
https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
Apparently nobody in this forum has ever posted a link to this blog.
This blog seems to be made by a xda member using automated scripts to scrap download links for ROMs.
It seems to be quite up to date and also includes the fastboot zip for the most current security patch v10.0.15.0.PDLMIXM , which I haven't seen in this forum yet.
Not sure how trustworthy these sites are but they actually just link to the official Xiaomi OTA download site(https://bigota.d.miui.com), thus the downloaded zips are the official one.
p-walker said:
https://xiaomifirmware.com/roms/download-official-roms-for-xiaomi-mi-a2-lite/
Apparently nobody in this forum has ever posted a link to this blog.
Apparently this blog is made by a xda member using automated scripts to scrap download links for ROMs.
It seems to be quite up to date and also includes the fastboot zip for the most current security patch v10.0.15.0.PDLMIXM , which I haven't seen in this forum yet.
Not sure how trustworthy the site is though. Seems to exist for quite a while though and it's been mentioned in other threads on xda.
Click to expand...
Click to collapse
It could be useful for some OTA files specially for the latest v10.0.14.0 and v10.0.15.0 (wrongly placed in fastboot section) but about the fastboot roms the thread opened here is more updated and complete https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871 it contains the latest fastboot rom for our device, v10.0.13.0.
I recently found this site.
https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
That looks like every fastboot and full OTA (site calls them "recovery") to me.
a1291762 said:
I recently found this site.
https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
That looks like every fastboot and full OTA (site calls them "recovery") to me.
Click to expand...
Click to collapse
Thx that site seems to be even more up to date, I will include it in the top post if you don't mind. However it is very "minimalistic" I mean there is no information at all about this site available and at least on xiaomifirware you get some extra information blog posts on top and they actually have a disclaimer that they are not affiliated with Xiaomi.
However it seems both sites are actually linking to the official https://bigota.d.miui.com site when downloading the files, thus they should be kinda trustworthy as long as they actually linkt to the official xiami site.
The files from these sites aren't made to be used on Mi Flasher. How I can use these files? TWRP?
romulocarlos said:
The files from these sites aren't made to be used on Mi Flasher. How I can use these files? TWRP?
Click to expand...
Click to collapse
The .tgz files are designed to be used with fastboot/MiFlash. Not every version has one of these.
The .zip (Recovery) files are OTAs that get flashed by the system. I don't know how people usually unpack and flash those but it is possible.
a1291762 said:
The .tgz files are designed to be used with fastboot/MiFlash. Not every version has one of these.
The .zip (Recovery) files are OTAs that get flashed by the system. I don't know how people usually unpack and flash those but it is possible.
Click to expand...
Click to collapse
I know about .tgz files. Just unpack and use with Mi Flasher. But these big zip files aren't. Inside have a big "payload.bin" file. Maybe is for use with stock recovery or TWRP, but I'm unsure.
romulocarlos said:
I know about .tgz files. Just unpack and use with Mi Flasher. But these big zip files aren't. Inside have a big "payload.bin" file. Maybe is for use with stock recovery or TWRP, but I'm unsure.
Click to expand...
Click to collapse
Files with extension tgz are full global rom to be used with MiFlash tool, fastboot or EDL and first you have to unpack it.
Files with extension zip are OTA updates to be flashed through system when it does use the scripts of the stock recovery (when you receive that you have an update) or totally through a custom recovery like TWRP and you don´t need to unpack it (inside within other files you will see payload.bin file)
All the rest that can be founded out there is unnoficial, adapted roms at the like of the user.
Hi guys. Do you know which firmware version is the last android 9 version?
Hello all.
I haven't posted here for years. My account is still active, but I am no longer allowed to post in specific forums regarding ROMs, so I am asking here.
[moderators: sorry if this is the wrong topic. It is the closest I could find, since my question is not device specific]
I have an Android 9 box which is signed with AOSP test certificates.
I also have an update.zip file for this box.
This box has A/B OTA support, it is working and verified through fastboot.
I want to edit and repackage the update.zip
I know how to do it on old ROMs, but I could not find any tool that can repackage payload.bin
There are several tools to unpack it, and I used one to extract boot.img and system.img
But I can't find any way to package these files back in to payload.bin format.
I tried various google searches and even analyzing the open source unpacking tools, but building a packaging tool from scratch is too complex for me at this point.
Any advice?
Have you found anything for this? I am trying to repack the payload.bin as well from modified IMG files, but I cant find anything on the web.
I extracted this script from linux-86 tools, pretty sure this is the one that repacks all the images into payload.bin, but donno what's the exact code inside it that makes it possible... Understand the last 100 lines & you might succeed.
MPK99 said:
I extracted this script from linux-86 tools, pretty sure this is the one that repacks all the images into payload.bin, but donno what's the exact code inside it that makes it possible... Understand the last 100 lines & you might succeed.
Click to expand...
Click to collapse
MPK99 said:
I extracted this script from linux-86 tools, pretty sure this is the one that repacks all the images into payload.bin, but donno what's the exact code inside it that makes it possible... Understand the last 100 lines & you might succees
Click to expand...
Click to collapse
Please Teach me, how to repack .img files into payload.bin
Did u Already Know How To Repack .img Files Into Payload.bin?
MPK99 said:
I extracted this script from linux-86 tools, pretty sure this is the one that repacks all the images into payload.bin, but donno what's the exact code inside it that makes it possible... Understand the last 100 lines & you might succeed.
Click to expand...
Click to collapse
Hello do you still have this script trying to repack a QCM6125 with magisk and twrp
Edit: Its advised to use superR's kitchen
SuperR Kitchen
forum.xda-developers.com
Hey
I've also tried everything, how do you pack it back into a payload.bin, I only wanted usb rights in the Platform.xml, I didn't want that anymore, that's enough for me, but how do I pack it again, thanks
I'm asking here as I never got an answer, sorry
don't want root
Thanks
Hello,
First post here though in the past I have read discussions on many occasions in search for information and it was always to my benefit, thank you.
My question revolves around the TWRP installation files for Fairphone 3.
On the TWRP website (https://twrp.me/fairphone/fairphone3.html#) are given 2 files, a twrp-installer-.......zip and a matching version of a twrp- ........img, and from the instruction given it is not clear to me what is the purpose of the .img file - are both used concomitantly during the installation, or not.
At one early and critical stage the TWRP instduction reads:
"...Download the correct image file and copy the file into the same folder as your platform-tools as well as device's storage. Rename the image to twrp.img."
Since the file needs to be renamed to .img apparently it is the original installer.zip.
The entire instruction afterwards refers to this downloaded and renamed file.
What then is the the purpose of the matching .img file? Is it used at all? The TWRP installation instruction doesn't even mention it.
Sorry for asking if this is common knowledge, but I did several searches all to no avail.
Thank you