CANCELLED! GOT A NEW PHONE
Tried so many methods , non worked , I'd keep trying until one works , then I could port hTC Aria's CM10 to hTC HD MINI and redo all this again so that we can have 4.1 on our devices. Till then , I'd love it if munjeni or schlund helped me with the process , because it seems that the kernel extracted from boot.img needs modification , and that every OS needs its own initrd , I hope someone can help.
Update:
I found the required file's details , I have the ramdisk , I have the system.ext2 , what I'm missing is the required kernel , 3.0.1 , I just need a download link to that kernel, can't seem to find any.
Hi,
So I recently got into Android Development and so far , everything is good.
What I'm doing is using munjeni's CM9 ROM as a base for me to get the boot.img and the files in the folder /system/.
I tried to use iPlasm's CM9 ROM but I got some extraction problems , which I'll look into later.
I'm also using the initrd found in Shlund's posts , and the original HD Photon (Froyo 2.2).
I compared the two initrds and found out that the Froyo one was smoother and had lots of unnecessary stuff and that the CM7 one is better , but it may freeze , so I'm going to test both for maximum results.
To-Do:-Ability to Extract zImage from boot.img Done
-Extract system files Done
-Put System Files into system.ext2 Done
-Use shlund's both kernels and see which one works.
-Create a system.ext2
-Extend Data.ext2's size to allow higher storage on higher SD cards.
If you are willing to help on this project...then please help me with these:
I need an empty system.ext2 in ext3 format (so I can put the system files inside).
Or I need someone to be able to empty the system.ext2 that I have which I got from the Froyo 2.2.
Problems :Currently I'm facing these problems that may get fixed later:
Cannot delete bin and xbin from system.ext2 , which leads to files to be read when they are not needed.
No empty system.ext2 file present.
Cannot Modify the initrd to increase the space , looking forward to use this code:
When using the kernel from munjeni (extracted) all what happens is G1 logo appearing and nothing else.
Bases :
zImage from mujeni's CM9 from boot.img
iPlasm's boot.img
initrd from either schlund's CM7.2 or shlund's Froyo 2.2
/system/ from munjeni's CM9
HARET_PHOTON7227.exe from PhotonAndroid Developement
Startup File from schlund's Startup.
All help appreciated
I found a 200mb system.ext2 , however , whenever i put files in it , the next time I mount it I loose everything I put inside , but everything deleted remains deleted. -_-
Glad to see you're trying to do some,
You should not try cm7 kernel with CM9, You're trying to make CM9 SDcard version so forget about cm7 kernel (you may do only for comparing)
please, try the munjeni's boot.img from (update 04.Jun. for rom 24.May.2012) or mine, because the munjeni's rom (24.May.2012) boot.img is older kernel. the new one includes bluetooth fix (NOT Handset Car).
what i see in system.ext2 i don't think you should empty or even use them, it should be writing in command (terminal) that will create those files into EXT2 file.
here is an example: http://forum.xda-developers.com/showthread.php?t=1055923
You can collect more informations in HTC HD2 forums which include SDCard versions,
Have fun,
Will try that , because the kernel from munjeni showed me .T...Mobile and then did nothing. hopefully yours work
I just tried your way iplasm , and guess what , I get the same splash screen G1 TMobile.
any thoughts?
thethiny said:
Will try that , because the kernel from munjeni showed me .T...Mobile and then did nothing. hopefully yours work
I just tried your way iplasm , and guess what , I get the same splash screen G1 TMobile.
any thoughts?
Click to expand...
Click to collapse
Sorry to say that, this htc mini is not my phone, so I'm so limited to work on it. especially going back to windowsmobile for testing sdcard again. :silly:
Let me say, are you still using both these together froyo and merging them with other? don't do that.. this won't work. froyo things with other ROMs won't work!
You should do one ROM for it's settings, don't catch another things, for example froyo or things.
just those files be their,
1- HARET.exe
2- STARTUP.TXT
and begin to do, and choose the only one ROM you want to make it SDCard version,
about splash screen, it means you didn't applied them correctly, because none of these bootscreen include t-mobile,
I remember the cotulla's version was include AT&T splash screen.
iPlasm said:
Sorry to say that, this htc mini is not my phone, so I'm so limited to work on it. especially going back to windowsmobile for testing sdcard again. :silly:
Let me say, are you still using both these together froyo and merging them with other? don't do that.. this won't work. froyo things with other ROMs won't work!
You should do one ROM for it's settings, don't catch another things, for example froyo or things.
just those files be their,
1- HARET.exe
2- STARTUP.TXT
and begin to do, and choose the only one ROM you want to make it SDCard version,
about splash screen, it means you didn't applied them correctly, because none of these bootscreen include t-mobile,
I remember the cotulla's version was include AT&T splash screen.
Click to expand...
Click to collapse
I found the problem , I'm using a new system.ext2 created by me , I put the /system/ files of yours inside , then I took the kernel from your rom , and then I used schlund's initrd (because I compared it to the original initrd and found that the only differences were in :
1-splash screen
2-mounting the sd or mounting the ext/sd
3-order of command execution)
so I found out the Cotulla (the original creator of the init inside the initrd.gz ) has put a G1 .T...Mobile splash screen , and when the kernel is loaded , it is loading it as rom , not as sd boot so it launches the splash screen instead of launching the android bootloader , I'll have a look and see and luckily munjeni will reply to the pm I sent him (he helped me with creating the system.ext2 and the initrd)
thethiny said:
Hi,
may you help me with something?
I have a ramdisk (initrd.gz)
and a kernel (boot.img)
and an zImage (kernel main)
however , I cannot seem to be able to extract the zImage , but I did extract the boot.img and the initrd .
In order for me to make it SD Boot , I should allow SD boot from zImage , but I can't open , do you think you can do that for me?
Click to expand...
Click to collapse
look, zImage is Kernel, you're doing to open Kernel.. zImage isn't an Archive file. so You don't need to edit or open zImage
Boot.img contains RAMDISK & Kernel, RAMDISK=intrd.gz, Kernel=zImage
You will need to extract the Boot.img from CM9, and convert them to initrd.gz and zImage,
iPlasm said:
look, zImage is Kernel, you're doing to open Kernel.. zImage isn't an Archive file. so You don't need to edit or open zImage
Boot.img contains RAMDISK & Kernel, RAMDISK=intrd.gz, Kernel=zImage
You will need to extract the Boot.img from CM9, and convert them to initrd.gz and zImage,
Click to expand...
Click to collapse
ok I already did that , but the zImage extracted from CM7 , doesn't match the zImage from CM7 SD Boot (same ROM , same Dev , diff size).
So I wanna extract the zImage so I can modify the Boot section to SD Boot.
it's not easy to edit kernels, just a Q: have you tried from extracted cm9 two files the kernel & ramdisk and rename them to zimage and initrd.gz to SDCard and see results?
and if you really want to modify zimage (needs unpacking and repack), click here: http://lmgtfy.com/?q=Modify+zImage+Android
iPlasm said:
it's not easy to edit kernels, just a Q: have you tried from extracted cm9 two files the kernel & ramdisk and rename them to zimage and initrd.gz to SDCard and see results?
and if you really want to modify zimage (needs unpacking and repack), click here: http://lmgtfy.com/?q=Modify+zImage+Android
Click to expand...
Click to collapse
Yes I tried , also I'm a Windows User , so I use Cygwin , and none of the commands above worked! I tried using Ubunty 12 and I get error at line 12
Hello All, this is my first post in Xda-forum, I love they way u all interact and help each other out here...well u see I hav a Allwinner A10 based tablet called Ice Xtreme which is very cheap in India do a google search on this tablet. well the company did not provide any software and I had corrupted mine while trying to use a custom recovery which was not from a allwinner a10 based tab. Anyways after alot of fuss I got it fixed but still they did not provide me with the livesuit image. I looked for ways to backing up my current working firmware from my tablet but found none. So after alot of searching I found this Script at a forum which can dump the recovery, the bootloader, boot partitions and system and data folder. But throughout my experience with this Livesuit firmware things I see that the drivers inside the vendor folder are also important as no two tablets have same chips (some thing will be different) so I modified the script and build it into a script that takes most of the directories (excluding mount,as it has only ur SD n extSD data) The dump thus created may help in modifying another image to suit ur needs.
I have only been able to backup directories and boot,recovery,bootloader partition thanks to the original script. I have no Idea how to send/restore these files to the device after flashing another rom to restore most of the things. Any help would be a boon. Thank u all for ur indirect help in bringing out the geek in me.
Try it!! & post feedbacks and suggestions...
This helps to backup the rom files with only adb. Just start the batch file & relax while ur ROM is being dumped.n it will also keep a copy on ur SDcard too.
Just use
#adb backup
for back up and
#adb restore
for restoring
# command...
But will it be possible to extract different files???!!
Hey, suppose I wanna flash a custom ROM which doesnt hav all of my boards drivers in it. So if I backup using adb can I thn restore driver files from the stock ROM backup to the new Custom ROM...
how to write backup ???
extension *.tgz??/
need expalain for restore backup..
thx..
Hi Guys
I need some basic help/understanding about Android ROM modification.
In particular for an Android MX TV Box - but the questions is generic and applies to any ROM I guess.
The Rom im flashing has the following files (and works perfectly):
factory_update_param.aml
hd18d_mx4.zip
recovery.img
I am able to successfully restore my box with this image (so I know that the image is working fine).
Within the hd18d_mx4.zip there is:
Directotories: data, META-INF, recovery, system
files: boot.img, bootloaded.img, logo.img
I tried to do a very basic step of deleting a single system.apk file from the system/app folder (no other changes) and I am unable to flash this firmware.
Any ides - what am i doing wrong?? It seems like i cant make any modifications to the zip file or there are problems.
I tried using dsixda Rom kitchen, and even if put rom in working directory, and then immediately
Please help - this is driving me mad!! Aaarrghghg
I´m tryng to port some roms to THL T11 (mtk6592). I have allready sucess with two but allways the same problem: touch keys (settings, home and back) and physical keys (power and volume) don´t work.
I have allready replace Generic.kl and mtk-kpd.kl from base to port but don´t fix my problem.
Wich more files i have to replace?
Can anyone help me?
Thanks
Hello, that method as followed for porting the mtk6592 rom since I only find for 6589 and previous.
carcaca said:
I´m tryng to port some roms to THL T11 (mtk6592). I have allready sucess with two but allways the same problem: touch keys (settings, home and back) and physical keys (power and volume) don´t work.
I have allready replace Generic.kl and mtk-kpd.kl from base to port but don´t fix my problem.
Wich more files i have to replace?
Can anyone help me?
Thanks
Click to expand...
Click to collapse
I may be very late but still replace lib>hw folder from stock to port delete the port lib>hw folder before copying from stock
carcaca said:
I´m tryng to port some roms to THL T11 (mtk6592). I have allready sucess with two but allways the same problem: touch keys (settings, home and back) and physical keys (power and volume) don´t work.
I have allready replace Generic.kl and mtk-kpd.kl from base to port but don´t fix my problem.
Wich more files i have to replace?
Can anyone help me?
Thanks
Click to expand...
Click to collapse
Hi,was wondering if you could share how you managed to port roms to mtk6592..Tried using some tutorials here but still didn't boot..Thanks
Aeonia said:
Hi,was wondering if you could share how you managed to port roms to mtk6592..Tried using some tutorials here but still didn't boot..Thanks
Click to expand...
Click to collapse
Hi, i´m no longer trying port because i'm theming official rom.
I tried to port some and the method i used is:
You need to port same version of android like 4.2 to 4.2 or 4.4 to 4.4.
Use the boot.image of your phone or decompile the boot.image of your rom and the boot.image of the rom you wanted and combine base’s zImage and port’s ramdisk and recompile to create new boot.img.
I normally replaced System/Etc/firmware from base to port.
Replace all the camera libs from base to rom.
Sometimes i have to replace audio libs if don't have sound.
Of course you need to edit buil.prop and i allways erase line in updater.script that contains install recovery.
If some thing don't work you need to try to replace some libs or else.
With this method i ported some roms and sometimes everything is allright ans sometimes i had some problems like the one i posted before but in 80% of the cases the rom boot.
The only thing that never works is gesture in locker screen.
Try this http://forum.xda-developers.com/showthread.php?t=2701283 and good luck.
carcaca said:
Use the boot.image of your phone or decompile the boot.image of your rom and the boot.image of the rom you wanted and combine base’s zImage and port’s ramdisk and recompile to create new boot.img.
Click to expand...
Click to collapse
Can't seem to find the zImage...all i have is
the rmdisk folder contains may files including the init.rc
Use android kitchen to decompile original boot.image and you get a new folder in kitchen called bootimg_xxxx_xxxx containing a folder named boot.img-ramdisk and a file named zImage.
Save the files in other folder outside android kitchen.
Erase folder bootimg_xxxx_xxxx in kitchen and replace original boot.image with port boot.image in working folder.
Now decompile again boot.image.
Now combine base’s zImage and port’s ramdisk and recompile to create new boot.img.
Try this.
carcaca said:
I´m tryng to port some roms to THL T11 (mtk6592). I have allready sucess with two but allways the same problem: touch keys (settings, home and back) and physical keys (power and volume) don´t work.
I have allready replace Generic.kl and mtk-kpd.kl from base to port but don´t fix my problem.
Wich more files i have to replace?
Can anyone help me?
Thanks
Click to expand...
Click to collapse
Did you solve the problem? How?
I have finally been able to extract the files and modem efs recovery through trwp. hope to provide something .. including but not if boot.img affected by I had to modify the aboot.img found in the dev / block directory for the recovery and ripped ... unfortunately damaged boot my phone but hopefully I could start the recovery and hopefully remove the backup time .. copy the link and enjoy..
reteryreyhttps://drive.google.com/file/d/0BzPfuCLzN40qSmRXOWlzZ0NqMFU/view?usp=sharing.....
HoxFlyLight said:
I have finally been able to extract the files and modem efs recovery through trwp. hope to provide something .. including but not if boot.img affected by I had to modify the aboot.img found in the dev / block directory for the recovery and ripped ... unfortunately damaged boot my phone but hopefully I could start the recovery and hopefully remove the backup time .. copy the link and enjoy..
reteryreyhttps://drive.google.com/file/d/0BzPfuCLzN40qSmRXOWlzZ0NqMFU/view?usp=sharing.....
Click to expand...
Click to collapse
You may want to post this here http://forum.xda-developers.com/att-lg-g3/general/rom-request-waiting-rom-t2902173, as many people are conversing on this subject:good:
removed
pls removed this post
Thread close
HoxFlyLight said:
Thread close
Click to expand...
Click to collapse
Done