Im having an issue with a project i have been playing with. Im not a dev just someone who is experimenting with roms and i have been trying to convert the hyperdroidsense build into a nand rom. I keep getting a kernel error after i flash the system.img and boot.img. Could someone offer me incite into this problem? I think the problem is the boot.img, specifically the init.rc. All i did was convert all the orginal files into the .img. Do i need to edit something in order for it to work on NAND?
nobody knows nothing??????????????
Related
Hi,
I was wondering if there was a way to convert .zip files of ROMs/themes into system.img files so that they can be booted up via the android sdk emulator?
I've seen that it's possible to launch system.img files in the sdk emulator, but after searching for quite some time I wasn't able to pinpoint a method for creating system.img from update-cm-4.2.12.2-signed.zip (for example).
Thanks.
DT
i made a post about those system.img files earlier here: http://forum.xda-developers.com/showthread.php?t=609090
in theory it's possible using the mkfs.yaffs2 tool, but i'm not sure whether the emulator supports danger SPL roms, because the system image file size is limited in the emulator as well...
http://www.dotphone.org/attachment.php?aid=6
it's the mkfs.yaffs2 tool
see usage here:
http://www.dotphone.org/viewthread.php?tid=32
Hi,
Thanks for the link, but I'm quite a newbie in these things, so could someone please walk me through process? I've downloaded the archive in the link.
How many times do I unzip it (I can unzip it up to three times and then I get 5 files numbered 1 through 5)? Where do I paste it? How do I use it? The explanation in the other thread was slightly too complicated for me sorry
Thanks
DT
/push
Anyone willing to help out a newbie?
bump
I am looking to do the same thing
Get someone to Nandroid backup the ROM.
It creates a system.img, recovery.img, data.img, cache.img and boot.img.
Not the easiest method but it works
Ok so on my adventure of overclocking the Eris i have ran into a bit of an issue.
I started with making a nandroid backup of my phone. this gives you system.img, boot.img, and data.img. I have successfully extracted everything from the image files except for one thing...the kernel.
I have taken the boot.img and split it up into the ramdisk and kernel and sorted through the garbage to get working directories and file structures.
I now have the ramdisk in a editable format but the /sys files are created from the kernel on boot and those are the ones i need to edit.
I have the kernel file on my computer, isolated, but i do not know where to begin on decrypting this jumbled mess. As far as i know it isnt compressed as i cant find magic numbers in the headers but this has baffled me.
Any devs out there wanna shed some light as i dont know much about android and i just started this yesterday.
Wait for HTC to give us the kernel source code
That would work if i had some patience. Any idea when we could get the source?
Hi I have a dump from the E-72 rom (Movilnet blocked (I dont know if that is the same of shipped) rom) and i want to convert it back to DIO file to flash it back to my phone, but i dont know what to do. I'm using IMGFS 2.0 rc2 and the last program I used was ImgfsFromDump.exe to make a bin file from the DUMP directory. So i dont know what to do next.
And other question, any of you know what file i need to delete to unlock the rom? be cause I'm trying to get 1 original rom unlocked.
I hope you can help me.
Hi All
Thank you for the great work however in order to enjoy the ROMS I will need to have a smaller boot.img in order to flash the roms.
The image must be 2.35 MB at most, A good example is the Enomther ROM that is flashable.
However the CM6 roms are not (except KANG O RAMA).
Since I dont think that someone is going to do it for me, can you at least explain how can I do that?
There are at least 10 more people that check this forum regulary looking for a solution.
Thank you.
CM6 boot image is just 2.25MB!!!
OHH yea.... checked it out on his site yesterday, then how come rodriguez's image is bigger?
He's most probably using another kernel for CM6, just like MicroMod uses another kernel for TheOfficial.
OK. How can I use those features with a smaller kernel? Is there a way?
1) Ask the kernel / ROM creator to "pack" it to fit in 2.5MB of space.
2) Compile your own kernel and make your own boot.img.
3) Try to mix your desired ROM (for example, Micromod's) with the kernel that fits your limited boot space (for example, Enomther's original). Or you could try to use rodriguez's ROM with CM kernel. To do that mix, replace the boot.img and the WiFi driver - bcm4329.ko - in their locations in the original ROM zip and resign the zip, then flash it.
Why the need for a smaller boot.img?
Sent from my Nexus One using XDA App
HTCinToronto said:
Why the need for a smaller boot.img?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Many N1s do not allow kernels later than 2.4MB (or something like that)... the kernel does not flash because of bad MTD blocks...
Jack_R1 said:
1) Ask the kernel / ROM creator to "pack" it to fit in 2.5MB of space.
2) Compile your own kernel and make your own boot.img.
3) Try to mix your desired ROM (for example, Micromod's) with the kernel that fits your limited boot space (for example, Enomther's original). Or you could try to use rodriguez's ROM with CM kernel. To do that mix, replace the boot.img and the WiFi driver - bcm4329.ko - in their locations in the original ROM zip and resign the zip, then flash it.
Click to expand...
Click to collapse
OK. Thanks.
Can you send me a link with the instructions on how to change and resign roms?
[sorry for being a noob]
Unfortunately, I don't have any instructions available anywhere, but you can use some Google searching.
The boot.img resides in the root of the ZIP, the bcm4329.ko is in /system/lib/modules/.
Changing the files in the ROM is easy - ROM is just a ZIP file, you take a ROM you want to change, open it in WinZip / WinRar / your favorite freeware archiver, find the files you want to replace (the ones I've mentioned above), download the original ROM which is the base (Enomther for MicroMod, CM6 for Rodriguez), extract those files from there, drag&drop them into the ROM you're modifying, that's it.
Then you search Google for "android sign zip apk", and you get a couple of guides that show you how to sign ZIPs.
Then you load the ROM and hope it works.
does not sound complicated
thanks.... I will try that.
Yes, what you need is:
boot.img and everything in /system/lib/modules
It's important that you replace everything in /system/lib/modules with the correct content for the specific boot.img you're using and delete everything else.
My boot.img which is based on Wildmonks BFS 950 kernel supports apps2ext and 720p and should be sufficient for any CM6 rom. It's worth noting that the current one in Kang-o-rama 1.0 Final is not as stable as I would like and I'll be updating it soon.
Since this seems a bit challenging for some rom devs an alternative approach could be:
Create update.zip for small boot image (I can help with this)
Rom dev creates rom update.zip without a kernel (may not boot properly)
Install rom without kernel
Install small kernel update.zip
Or everyone could use Kang-o-rama...
Hey guys
The volume rocker on my HD2 is broken, and I have cLK flashed on my device. My problem is that I can only boot into cLK and fastboot mode as recovery is useless to me because I cant navigate through the options using the volume rocker.
I am looking for a rom (android/winmo) that is a .img file so that I can flash through fastboot, or if any of you know any other possible way I can flash a rom through fastboot so I can get my phone working again. Right now I dont mind which rom I flash, as long as I get my phone in working order again.
All help is GREATLY appreciated....!!!
If anyone also knows how I can compile a rom into a .img file so I can flash through fastboot, that is also welcomed help!
Any ROM you download that is for cLK has a. img file in it. you will have to extract the file from the. zip hou download to find it. Read my post here it will give youthe details on how to flash your ROM.
T-Macgnolia said:
Any ROM you download that is for cLK has a. img file in it. you will have to extract the file from the. zip hou download to find it. Read my post here it will give youthe details on how to flash your ROM.
Click to expand...
Click to collapse
Hey bud, thanks for the reply, but my question still remains... what about the other 2 folders in the rom folder (META-INF and SYSTEM) what happens with those? lol....
atsavlis said:
Hey bud, thanks for the reply, but my question still remains... what about the other 2 folders in the rom folder (META-INF and SYSTEM) what happens with those? lol....
Click to expand...
Click to collapse
Sorry for the late response but those two files do get used, the img file oules the information from them as it is flashing. To put it simply when you initiate the flash the img does the rest of the work. The img file is sort of like a cab file for Windows Mobile only it is not all self contained and has more functions than just to install the software. Note I said sort of not exactly like, that is just a comparison to help you understand. When you flash a Android ROM via CWM it essentialy just activates the img file to flash the ROM.
Daf roms come as a system.img
or
if you have access to another hd2, flash the target rom to it and then use mkyaffs2img command in the terminal to dump the system folder to a system.img file.
Benefit of this would be you can tweak the rom(reduce size for example, by removing unwanted apps) before you dump to system.img
samsamuel said:
Daf roms come as a system.img
or
if you have access to another hd2, flash the target rom to it and then use mkyaffs2img command in the terminal to dump the system folder to a system.img file.
Benefit of this would be you can tweak the rom(reduce size for example, by removing unwanted apps) before you dump to system.img
Click to expand...
Click to collapse
Thanks for getting back to me buddy! Unfortunately I dont have a second HD2, and I dont know anyone willing to help me out in Greece, lol... Would you be willing to dump your system folder for me and upload it so I can use yours?? I would GREATLY appreciate the help... sitting with my HD2 "semi" bricked... lol
Also, if I use the .img file from the DAF roms, can I flash it using fastboot??? You have any suggestions on how I can flash it considering I cant use the volume rocker on my mobile?
Well id like to say yes but it's Easter weekend and my sons 1st birthday tomorrow, so the likelihood of getting near a PC are slim for a few days.
You could always learn how to use the android emulator,, build the image on a virtual hd2
As for flashing,,, no idea, no clue what fastboot does, magldr for me, but in your OP you implied you could use it to write img files to partitions.
You ever got a solution for this? I'm in the exact same situation right now.