Related
Help.... with the Boot.img
I m Trying to port sense Htc desire in nexus s i m confused about the boot.img file kernel
1. Does it needs to be changed / modified
2. If yes then is there any software i can use to Extract the kernel and repack it too Windows / linux
3 i Zimage of the boot.img any clue how to edit it
Plzz... reply.
this thread is going places... >.>
but in the off chance.. of, well i dont even know, ill try to be helpful
1) yes, lots. in fact your better off not trying to port that kernel to this phone and just start a fresh one and reverse engineer it
2) windows idk, linux makebootimg scripts will unpack it
3) nope, you better have source to compile that zimage
Hmm okk i guess i try that out on the next weekend thankz,, man...
After a few headaches and some claps on the forehead i finished a very alpha build of CM9 for the IDEOS X5. It was ported from the Galaxy W port of arco68 with the files of Aurora ICS and this guide.
I don't know the bugs, so please PM me if you find a bug.
NOTE: I think i am only too stupid to sign a zip, so you have to sign it by yourselves or toggle verification in the recovery.
Download
Mediafire
Thanks to fjsferreira for re-packung the boot.umg
Thanks to dzo for Aurora ICS
Thanks to arco68 for the Galaxy W ICS port
Thanks ti freeeyourandroid.com for the porting guide
alex1301 said:
After a few headaches and some claps on the forehead i finished a very alpha build of CM9 for the IDEOS X5. It was ported from the Galaxy W port of arco68 with the files of Aurora ICS and this guide.
I don't know the bugs, so please PM me if you find a bug.
NOTE: I think i am only too stupid to sign a zip, so you have to sign it by yourselves or toggle verification in the recovery.
Download
Mediafire
Thanks to fjsferreira for re-packung the boot.umg
Thanks to dzo for Aurora ICS
Thanks to arco68 for the Galaxy W ICS port
Thanks ti freeeyourandroid.com for the porting guide
Click to expand...
Click to collapse
Can't flash it, starts but then getting error and no message as the phone reboots. First time ever it has done something like this and my heart skipped...
cirnocirno said:
Can't flash it, starts but then getting error and no message as the phone reboots. First time ever it has done something like this and my heart skipped...
Click to expand...
Click to collapse
Did you toggle signature verification first?
Is there any chance for u8800pro?
Sent from my u8800pro using XDA
... finished a very alpha build of CM9 .....
Click to expand...
Click to collapse
Please go to advance edition and put a big ALPHA warning in the title thread.
why? is it that bad?
have you tyed? whats working and not?
thanks for ypu effort alex1301
r1c4rd0 said:
why? is it that bad?
have you tyed? whats working and not?
thanks for ypu effort alex1301
Click to expand...
Click to collapse
Alpha is not bad nor good, just a phase of software development. Please confirm the rom is working, otherwise I will move it to general section.
poyensa said:
Alpha is not bad nor good, just a phase of software development. Please confirm the rom is working, otherwise I will move it to general section.
Click to expand...
Click to collapse
i´m downloading it right now, and will test it in one hour and i will say someting here...
It doesn't install, always Error status 6 in CWM. I replaced the METAINF folder in the zip with aurora, and changed the name of the zip itself, then it installs, but doesn't boot...
Next, I replaced the boot.img inside with the 3.0.8_v2 from DZO, then it boots but never goes further than boot animation
It is not rom development if you just switch some of the files, compress the file into a .zip and post it here.
Can anyone have a look at it and help me? I think the problen is the updater script, because i've only copied the one from aurora.
Sent from my SGH-T989 using xda premium
I will do a port from desire z
Sent from my SGH-T989 using xda premium
will test it soon btw yeah port from desire z would be better.
i have only one problem. the guide says the Easiest way to replace the kernel is to take a kernel update zip for your device, un-zip it and rename the zImage file to "boot.img-kernel" and copy and replace the file of the same name in your directory.
but when i take the boot.img-kernel from the unpacked aurora boot.img, it has 2,6 mb, but when i rename the packed boot.img from aurora to boot.img-kernel it has 3.0 mb. which one should i take?
alex1301 said:
i have only one problem. the guide says the Easiest way to replace the kernel is to take a kernel update zip for your device, un-zip it and rename the zImage file to "boot.img-kernel" and copy and replace the file of the same name in your directory.
but when i take the boot.img-kernel from the unpacked aurora boot.img, it has 2,6 mb, but when i rename the packed boot.img from aurora to boot.img-kernel it has 3.0 mb. which one should i take?
Click to expand...
Click to collapse
Boot.img is ramdisk and kernel, compiled into one. You need kernel.
Unpack both boot images, replace kernel with auroras and change init.rc scripts to mount the correct partitions.
On mobile now so can't give a tutorial.
Sent from my U8800 using Tapatalk 2 Beta-5
the guide i follow says, that i only have to rename the init.devicename.rc to init.huawei.rc. should i also change the init.rc to the one of aurora?
does anyone have the mkbootimg for the X5?
alex1301 said:
does anyone have the mkbootimg for the X5?
Click to expand...
Click to collapse
We don't need to have any device specific mkbootimg, any mkbootimg will do it just fine
Sent from my U8800 using Tapatalk 2 Beta-5
i've uploaded a new version. it's ported from the desire z, but i think it's too big for the x5. i can't upload it to mediafire, because it doesn't load my files correct. so i only can upload it to dropbox, but there is also a limitation of downloads. http://db.tt/u8PrGM5m
alex1301 said:
i've uploaded a new version. it's ported from the desire z, but i think it's too big for the x5. i can't upload it to mediafire, because it doesn't load my files correct. so i only can upload it to dropbox, but there is also a limitation of downloads. http://db.tt/u8PrGM5m
Click to expand...
Click to collapse
Can you confirm this one boots?
Sent from my U8800
Hello!
This is a thread where potential developers can get kernel and platform source code for Samsung Galaxy S I9070 Advance, and other info. I will try to update this until we will have first custom rom ready. I encourage everybody with some experience with android development, to share their knowledge with other users here. Please if any of you will make any progress in rooting, making recovery or developing custom rom, to write here in this thread or even start a new one if some major break trough will be made.
Ok so here are the links to sources (I don't know the diference between those to, but I guess it is region related):
GTI9070_GB_OpenSoruce
GTI9070_LA_GB_OpenSoruce
All sources, can be found HERE.
In the attachment you can also find some other info I've pulled from my phone, which used to be rooted, cause I had some test version. I hope all this stuff will help us get root access, custom recovery and last but not least a whole bunch of custom roms.
NOW LETS HACKING AND DEVELOPING BEGIN!!!
One more thing, PLEASE take a minute to VOTE for this phone to get its own forum section here on XDA. Just make a post in THIS THREAD. The device is not in the poll yet, so you must write a post in thread. THANK YOU!
We've made a step into a right direction with a lot of help from forum I've made a working root method!
I've hard bricked my phone, so I am off the developemnt from this phone, only if by some chance I get a replacement. Sorry guys, in spirit of developing I've killed my phone .
I wish I was better at kernel development... I would love some development for this phone!
Sent from my GT-I9070 via Tapatalk 2
I've somehow managed to configure linux and pulled andorid sources from the repo, now I have to figured out how to compile a kernel. I have much to learn but if nobody else will give it a try, maybe I will succeed.
yeah...we as new wannabe devs are learning back the basics...i'm still trying to figure out what to do about the kernel source...afraid of bricking my phone in the process... hehe.. but all the kernel sources for all regions has been released...
kilsmap said:
yeah...we as new wannabe devs are learning back the basics...i'm still trying to figure out what to do about the kernel source...afraid of bricking my phone in the process... hehe.. but all the kernel sources for all regions has been released...
Click to expand...
Click to collapse
Dear friend. I come from China, now I already have a good i9070, I can help you with your test, you can send to my mailbox [email protected]
hmmm...qzem, im getting stuck at initramfs...how do we get these for our phones? because the kernel can only be flashed safely when it is compiled with initramfs files from our phone... and for the phone to get custom recovery, i think they will also need initramfs files...
kilsmap said:
hmmm...qzem, im getting stuck at initramfs...how do we get these for our phones? because the kernel can only be flashed safely when it is compiled with initramfs files from our phone... and for the phone to get custom recovery, i think they will also need initramfs files...
Click to expand...
Click to collapse
Same thing here. I have no idea how to get those, been asking around the forum an searching, but for now all the directions indicates that you need to have root access to get iniramfs. That really sucks...
hahaha...from this point of view, all Samsung phones after Galaxy S Advance will be quite hard to root... I'm waiting for the Galaxy SIII to launch, and for someone to root it... Maybe then we will be able to use the same way to root our phone... If only we can see what's inside our kernel.bin.md5... I'm sure the files we needed are in there...
the initrams? u mean ramdisk?
grab stock boot.img and extract from it.
the stock boot.img can be grabbed from odin flashable stock rom.
an0nym0us_ said:
the initrams? u mean ramdisk?
grab stock boot.img and extract from it.
the stock boot.img can be grabbed from odin flashable stock rom.
Click to expand...
Click to collapse
Yeah.. We have the stock rom, but can't figure out which one should we extract the boot.img from.. There was system.img.md5, cache.img.md5, hidden.img.md5, modem.bin.md5, and kernel.bin.md5... So which one? My suspicion lies to the kernel.bin, but I have no idea how to extract it..
Sent from my GT-I9070 using XDA
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
qzem said:
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
Click to expand...
Click to collapse
Good luck!
Hope you get to a solution soon
I can't work on it as I currently don't have a phone to test on, sent it in for repairs.
qzem said:
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
Click to expand...
Click to collapse
Have u tried flashing it directly to the phone? You don't have to make it into a boot.img to flash it.. Because I'm afraid that the zImage will be useless if not paired with working initramfs.. Compiling the kernel is quite straightforward, the thing is to get the initramfs to turn the kernel insecure.. There are also scripts to extract initramfs from zImage, but I haven't had time to test it..
Sent from my GT-I9070 using XDA
Ok what exactly is in initramfs, that is what I am trying to figured out? I've recompiled some other samsung boot.img with dsixda kitchen, and I got zImage and a folder caled boot.img-ramdisk, which included different files like init, init.goldfish.rc init.rc, default.prop, etc. In a file default prop is the setting ro.secure=0, and this is the settign I belive, that makes kernel insecure. I've also tried to unpack the zImage that I got from thsi boot.img, with the kitchen to see if includes those so called initramfs, but it doesn't. So I think that if I figured out which files should be in ramdisk, and if those files can be pulled of the phone, that than maybe I can repack a working boot.img. What do you think?
qzem said:
Ok what exactly is in initramfs, that is what I am trying to figured out? I've recompiled some other samsung boot.img with dsixda kitchen, and I got zImage and a folder caled boot.img-ramdisk, which included different files like init, init.goldfish.rc init.rc, default.prop, etc. In a file default prop is the setting ro.secure=0, and this is the settign I belive, that makes kernel insecure. I've also tried to unpack the zImage that I got from thsi boot.img, with the kitchen to see if includes those so called initramfs, but it doesn't. So I think that if I figured out which files should be in ramdisk, and if those files can be pulled of the phone, that than maybe I can repack a working boot.img. What do you think?
Click to expand...
Click to collapse
Yep, you got everything right there, I think.. Initramfs, ramdisk are the same thing.. They should include the cpio.gz, init.rc, default.prop etc... Have you extracted these files from the source kernel? Cos I don't think we can copy directly from phone, cos we need to preserve the permissions set on the files... Can you do that with kitchen?
Sent from my GT-I9070 using XDA
I am following the topic and hoping it works out the development of kernels and roms to the device.
Come on it has to be a way to compile an insecure kernel without having the access to rooted phone. Cause all the options I found till now, required some files, that can only bee pull from rooted phone. But the whole point of an insecure kernel is the possibility to root the phone. Anybody can help us? Maybe I should start another thread, damn it!
Haha... Yeah, somehow I feel that Samsung is screwing with us, what with the new firmware format (never had kernel.bin before) and secured kernel, this is becoming impossible.. If we just have some devs good-hearted enough to port CWM recovery for us.. But without initramfs, I don't know if it's possible..
Sent from my GT-I9070 using XDA
The initramfs is inside kernel.bin.md5 (as for the Galaxy S firmware).
kernel.bin.md5 is a normal zImage Linux kernel (+md5).
the initramfs is included in the kernel image (see http://forum.xda-developers.com/wiki/Extract_initramfs_from_zImage)
the initramfs is in our case a uncompressed cpio archive, therefore the script in the wiki does not work, but https://github.com/mistadman/Extract-Kernel-Initramfs/blob/master/unpack-initramfs can extract it without problem.
So, there should be no difficulty to root the i9070...
The easiest way would be to change the initramfs and repack everything.
hi
after alot of search i found a way to extract the kernel
some details for how i extract it
i use http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to get boot.img
and i use moto depacker to extract sbf to get system.smg
after that i use unyaffs-x86-win to extarct system,smg
i use dsixda-Android-Kitchen to make work folder
and i use the system and boot
and i use the method that unpack the kernel and i upload the kernel below
..... is there a way to make a rom using the same kernal (stock but extracted) ????
..
..
Looks interesting...
I don´t think that we will get any Rom for the Flipout, i have one, too!
The Community is way toooo small for that Phone, and everything is locked by Motorola.
But i changed to Sony Xperia Arc S.
System.img
you could flash the new system.img only directly, or you could repack the new system.img into a new cg39.smg and then repack the sbf and flash.
But repacking cg39.smg has failed for me, that is after flashing the new sbf the bootloader wouldn't accept the new system partition, either because the cg39.smg I repacked is corrupted or signature verification failed.
hsr0 said:
you could flash the new system.img only directly, or you could repack the new system.img into a new cg39.smg and then repack the sbf and flash.
But repacking cg39.smg has failed for me, that is after flashing the new sbf the bootloader wouldn't accept the new system partition, either because the cg39.smg I repacked is corrupted or signature verification failed.
Click to expand...
Click to collapse
Cause you need the to sign it with Motorola key that we didn't know it so I will wait until found way to flash rom or to unlock bootloader
Sent from my U8160 using xda app-developers app
ososmam said:
Cause you need the to sign it with Motorola key that we didn't know it so I will wait until found way to flash rom or to unlock bootloader
Sent from my U8160 using xda app-developers app
Click to expand...
Click to collapse
try the bootstrappped CWM recovery from the flipout and charm android development forum, you should be able to flash a custom ROM without signing it
hsr0 said:
try the bootstrappped CWM recovery from the flipout and charm android development forum, you should be able to flash a custom ROM without signing it
Click to expand...
Click to collapse
it stop at installing packeage not moving and not work good must be able to mount to install rom from it
ososmam said:
it stop at installing packeage not moving and not work good must be able to mount to install rom from it
Click to expand...
Click to collapse
package shouldn't have any problem Installing, try downloading from reference link provided in the thread in posted in development forum.
hsr0 said:
package shouldn't have any problem Installing, try downloading from reference link provided in the thread in posted in development forum.
Click to expand...
Click to collapse
We can only try to port rom with stock kernel but we can only use android 2.1 custom rom
Sent from my flipout with stock rom
we can use froyo or gingerbread, provided we can change the features of the ROM such that the kernel supports it.
makefile mods
Im editing some makefiles but is there any apk i can install to show advance board details and hardware chipsets and manufacturers?
plageran said:
Im editing some makefiles but is there any apk i can install to show advance board details and hardware chipsets and manufacturers?
Click to expand...
Click to collapse
you can copy build.prop from system to your computer and open it with nootpad++ and you will found some information
I found yaffs explorer, it give most of the hardware info
Sent from my MT27i using xda app-developers app
Easiest and best way to port CM7,CM9,CM10 Based ROMs to HTC Aria/Intruder/Gratia
Code:
I do not guarantee any successful porting.
I am not responsible for [B]bricked devices, dead SD cards, or a broken device[/B].
[B]YOU[/B] are choosing to make these modifications,
and if you point the finger at me for messing up your device,
I will laugh at you.
->Copied from some xda thread.
*****
But a rom, no matter how bad should *not* do any physical non recoverable harm to your device,flashing a rom or restoring a nandroid backup via cwm *should* immediately fix any problems what so ever.
And I will try to help in any ways I can.
I am NOT a developer, I can not code,compile,etc, I am only an android enthusiast with half a brain able to follow specific instructions.
This guide is actually somewhat a good combination of various "how to port roms"
guides found here on xda suited and very slightly modified for our beloved Aria.
Thanks to all of those threads and their writers.
Click to expand...
Click to collapse
Actual Tutorial starts here:
I will try to make this guide as straight forward as possible.
PORT ROM:
First you need to figure out what rom you are going to be porting.
For our Aria, The rom you want to port should belong to a device that has:
HTC brand (optional but recommended)
A ArmV6 CPU (VVVV important)
A HVGA Resolution (optional, any mdpi should do,if not just open the system apk files using 7zip and resize all the BIG images.)
The Rom needs to be:
CM7 BASED OR CM10 BASED OR CM9 BASED.
The full zip size less than 150MB(Recommended).
What Does Port Mean:
This simply refers to the rom you will be trying to port.
Recommended device to port from is the HTC Wildfire S a.k.a Marvel.
But any other device
BASE ROM:
What Does Based Mean:
It means that the rom should have similar sources and stuff,
Meaning you can only attempt to port a android 2.3 rom if you already have a 2.3 rom on the device.(In our case cm7).
So,
For porting 2.3 roms, chose cyanogenmod 7.2 as BASE.
For porting 4.0 roms, chose cyanogenmod 9 as BASE.
For porting 4.1 roms, chose cyanogenmod 10 as BASE.
ETC... I hope you get the point.
:fingers-crossed:
Thing you will need:
A good Zip extractor and compressor. (I use 7zip, its free. If you have winrar or something else,it will also do.)
Notepad++ (This thingy is awesome! And you need it for some stuff)
Android SDK(Not the whole thing, just adb zip from our sticky thread will do.)
Some Basic Android Knowledge, Root knowledge.
Mostly Common Sense.
Click to expand...
Click to collapse
Step 1:
Extract our device rom zip and name the folder AriaRom,
Extract our Port rom zip and name the folder PortRom.
Step 2:
Delete the following folders on the AriaRom/system folder:
App(You can keep some non conflicting indepent apps if you want)
Framework
Fonts
Media
Step 3:
Go to
Code:
PortRom folder/system
and copy:
App(You can keep some non conflicting indepent apps if you want)
Framework
Fonts
Media
and then paste them to AriaRom/system.
Step 4:
You need to open these two folders side by side(on windows, open both folders then right click on the task bar and click "Tile windows vertically").
The two Folders are:
Code:
[LIST]
[*]AriaRom/system/etc
[*]PortRom/system/etc
[/LIST]
In
Code:
etc/permission
folder copy all the permissions files in PortRom to your AriaROM folder except
Code:
platform
handheld_hardware
Then open init.d Folder in AriaRom and Delete Everything except
Code:
banner
and then copy all the files inside init.d folder of PortRom to init.d folder of AriaRom.
Step 5:
Now
Code:
AriaRom/system/buid.prop
and
PortRom/system/buid.prop
files using Notepad++
On AriaRom Build.prop make changes as you wish.
Code:
[LIST]
[*]ro.build.id=
[*]ro.build.display.id=
[*]ro.build.date=
[*]ro.modversion=
[/LIST]
Copy and replace these values from PortRom buildprop to Aria rom buildprop.
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
Also Copy anything you Find Extra and important-ish in ADDITIONAL BUILD PROPERTIES using common sense.(Not much major stuff, but if bootlooped, copy whole thingy.)
IMPORTANT Step of commons sense:
Open up both
Code:
META-INF/com/google/android/updater-script
using Notepad++.
Compare AriaRom AND PortRom line by line(on two tabs in notepad++ easily done).
Copy extra/additional lines from PortRom which are not present in AriaRom to aria roms updater script.
Step 6:
If You find any extra file or folder in system folder of PORTrom than copy them to your Ariarom system folder.
Finally, zip the
Code:
META-INF
system
boot.img
data(if exists).
folders/files togather and use "normal" compression if asked.
Name the zip to whatever you want, and walla you have successfully ported the rom!
:fingers-crossed:
Doing the above steps should land you a pretty solid rom, as solid as the base rom.
Still,Incase of problems:
If the ported rom does not boot:
Stuck at boot screen
Bootlooping
Then copy system/lib/
Code:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
files from PortRom to AriaRom system/lib.
It should boot, if it still doesnt, check the above steps and find out what you did wrong.
Common reasons could be:
Build.prop mess up
Updater Script mess up
Forgot to delete or copy file
After it boots,
Everything that worked on Base rom, should work on Ported.
Every problem on Base Rom will exist on Ported.
In case of root related problems(settings not being saved,system app FCs,etc), install a root app like titanium backup or something and check if it works,if it doesnt its surely root issue,just download and flash latest superuser zip.
If some FC,Port rom funciton not working,etc issues appear, you need to decompile framework-res.apk using apktool and change device specific xml files to ours.This is a part where I have the most trouble and suck at.
Just search xda for
How to Logcat,
Click to expand...
Click to collapse
this will help you to find the problems and search xda to solve them. Ask me if you want on this thread, & I will try to help, but I dont think I will be able to help much as I have very limited knowledge on compile De-compile stuff.
If someone is good at framework-res and framework decompile & recompile stuff, please help us.
Click to expand...
Click to collapse
Thanks for reading this,I hope you port over some awesome roms to our device.
:highfive:
I just tried to port the PACman ROM from Samsung Galaxy Ace to the Aria, but I am stuck at boot screen after following your tut, which is awesome by the way. Could you post a working build.prop and updater-script for this ROM? Maybe this will help me get it booting...
dansou901 said:
I just tried to port the PACman ROM from Samsung Galaxy Ace to the Aria, but I am stuck at boot screen after following your tut, which is awesome by the way. Could you post a working build.prop and updater-script for this ROM? Maybe this will help me get it booting...
Click to expand...
Click to collapse
That's an Armv7 device.
Still I'm gonna download it & try.
In the meantime take a look at bootclass path.
Why are SMARTphones soo... Freaking Dumb?
sifat3d said:
That's an Armv7 device.
Still I'm gonna download it & try.
In the meantime take a look at bootclass path.
Click to expand...
Click to collapse
I don't think so... the Samsung Galaxy Ace with device number S5830 should be Armv6, but in the Galaxy Ace Forums there is also a place for the Galaxy Ace II, which is Armv7. Maybe that's a bit confusing. But nims11 PAC-Man Rom is definitely for the Armv6 device.
hey man thnx for the tut but i tried porting the paranoid rom like you but i keep getting this error while flashing ( set_perm: some changes failed) i think it have something to do with the updater-script, could u upload the build.prop and the updater-script for me ? and btw why do we need the sdk ??
---------- Post added at 02:43 AM ---------- Previous post was at 02:03 AM ----------
actually now i tried not to change the updater-script and the rom flashed but stock at boot pleaaase help me i really want to try the paranoid rom (ive been trying to port the "pa_marvel-2.54-beta1-08NOV2012-164651" )
rami.ejle said:
hey man thnx for the tut but i tried porting the paranoid rom like you but i keep getting this error while flashing ( set_perm: some changes failed) i think it have something to do with the updater-script, could u upload the build.prop and the updater-script for me ? and btw why do we need the sdk ??
---------- Post added at 02:43 AM ---------- Previous post was at 02:03 AM ----------
actually now i tried not to change the updater-script and the rom flashed but stock at boot pleaaase help me i really want to try the paranoid rom (ive been trying to port the "pa_marvel-2.54-beta1-08NOV2012-164651" )
Click to expand...
Click to collapse
Here you go,
http://pastebin.com/62hbaQwL
on THAT ROM,
IF you follow the guide & use my posted script,
100% assurance rom will boot and work. except cm
The sdk is for getting the logcat when a problem occurs.
Why are SMARTphones soo... Freaking Dumb?
Nice tut very well done
XDA Moderator
dansou901 said:
I don't think so... the Samsung Galaxy Ace with device number S5830 should be Armv6, but in the Galaxy Ace Forums there is also a place for the Galaxy Ace II, which is Armv7. Maybe that's a bit confusing. But nims11 PAC-Man Rom is definitely for the Armv6 device.
Click to expand...
Click to collapse
In that case you'll need to unpack both boot.img aka the kernel , fix bootclass path in init.RC by replacing it with the value from port roms init.rc.
Ill try to port that rom soon and upload a fixed boot.img (if I can get it to boot),if you don't beat me to it. it looks cool.
Why are SMARTphones soo... Freaking Dumb?
Bootclasspath is the same on both roms. So there must be a mistake in updater-script and / or build.prop. I've just messed up my updater-script, I guess, so I'll make a new one and post it later together with the build.prop.
I got this pac rom booting & everything operational except per app dpi(exists in port rom).
This rom works with the guide.
http://forum.xda-developers.com/showthread.php?t=2118567
Why are SMARTphones soo... Freaking Dumb?
I'll try this and let you know if it worked.
Hi guys,
If you only want per app dpi,persistent apps,etc
Try this on winsuk bros cm10
http://forum.xda-developers.com/showthread.php?t=1574401
Its quite good.
...Devided by zero
dansou901 said:
I'll try this and let you know if it worked.
Click to expand...
Click to collapse
btw,
did it work?
...Devided by zero
Sadly, I didn't get any time to try so far. But on Sunday I lost my Gratia, so I won't continue this project; I've upgraded to the HTC Desire X.
dansou901 said:
Sadly, I didn't get any time to try so far. But on Sunday I lost my Gratia, so I won't continue this project; I've upgraded to the HTC Desire X.
Click to expand...
Click to collapse
That's a shame. Similar thing happened to me. I lost my Aria right before i had a chance to try this, and upgraded to the Nexus 4.
will this method work on cm10.1 and this http://forum.xda-developers.com/showthread.php?t=2297580 ??
Could work, just try... I would do it if I still had the phone...
dansou901 said:
Could work, just try... I would do it if I still had the phone...
Click to expand...
Click to collapse
rami.ejle said:
will this method work on cm10.1 and this http://forum.xda-developers.com/showthread.php?t=2297580 ??
Click to expand...
Click to collapse
It should pretty much work,
If it doesnt, just send me the
Updater script
Build.prop
files of BOTH roms, And I'll have a look.
I wouldve tried myself but my aria has no network and has random reboot issues due to falling hard.