Database Develop

[Discontinued]Miui port

Hello!
Ok so this is an attempt to port MIUI to LGP500. We are trying this because porting on the Galaxy 3 (LDPI armv6) was a success and i'm sure it will work on our device too.
This is what we're using so far: MIUI for Desire & Overflow ROM
So far this has been done:
ADB now working
Merged framework.jar from base rom with MIUI one
Replaced all apks with miui except LatinIME.apk which seems to give an error on boot
Use libs, bin and xbin from base rom
Merged permissions
[Update 9.07.2011 - 17:48 GMT+3 DST]
Now using framework from CM7
Libs, and bins from CM7
Boot.img still from Overflow (CM7 Boot.img stops adb on boot after a while - so using Overflow for developing for now)
Replaced many smali files in framework but errors keep popping up - I think framework is pretty screwed up now and must be redone (again)
No more nasty error on boot (with stack dump and stuff...)
No need for logcat now because errors come from framework
[Update 11.07.2011 - 15:32 GMT+3 DST]
MIUI boots up and we have graphics BUT
It only boots up to some error dialogs that say some processes force closed with "Close" and "Report to MIUI"
Gapps, Provision, and StatusBar force close so they need work
Removed ContactsProvider.apk and CalendarProvider.apk
[Update 14.07.2011 - 10:58 GMT+3 DST]
Fixed framework.jar - no more errors seem to come from it
New zip not made on mac so no low memory errors
New problem that might fix the apps: All apps look for their classes.dex in /cache/dalvik-cache but only system classes are there. The app classes are created in /data/cache/dalvik-cache
All apps are back because the errors don't come from them
[Update 28.07.2011 - 18:53 GMT+3 DST]
Added dalvik-cache to /cache script
New zip with init.d script and updated framework
Need to fix dead code in framework
Need new kernel
Need MDPI apks
Need libs that don't make the apks crash
Latest flashable zip:
http://www.multiupload.com/VNM8QTDBZ3 [Updated 28.07.2011] Thank you 4silvertooth
(DOES NOT BOOT! DON'T FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!) Sorry... i had to put this in big red letters because apparently people didn't see it well...
If you would like to help go ahead. Download the rom or make your own one if you don't like our development and give input. But most of all don't try to bring us down with "this can't be done" stuff. It can be done and it was done for another armv6 device. We need to get apps and framework to work and rom to boot. Libs and bins will come after...
This being said i would like to thank these people for their work so far and for making me get off my ass and do something useful:
4silvertooth
jazux
DJoptimus-One
Also i would like to thank overflow for his rom. It's the base for our miui so far.

Fantastic news! I can't wait too see how this works out. Good luck, you're gonna need it!

look forward to.

Thanks popdog
Will get into works as soon as i get my laptop back

Great news!
Waiting for testing release!

wow ! MIUI for o1 ?
oh sh*t this is what i've been waiting for so long !

looks good ill be happy to help, just ask for now im looking the motorola dump... maybe theres something that will help my team on galaxy 3 but anyway i subscribed tol this thread
EDIT: damn that motorola dump is useful, already found many, many tweaks thanks a million times for 4silvertooth

Hey can we use pastebin.com for all the logs.. it will be convenient and easy.
Sent from my LG-P500 using XDA Premium App

good point... also do you know a way to upload the files like in a git source (only the ones that changed) because multiuplad is painfully slow for me...

popdog123 said:
good point... also do you know a way to upload the files like in a git source (only the ones that changed) because multiuplad is painfully slow for me...
Click to expand...
Click to collapse
No but make a base rom and update.zip which will have all changes and will be small in size.
Sent from my LG-P500 using XDA Premium App

About the log.
The error so.lcddensity(something) is in build.prop you have to add it, it's using 160 by default.
All the missing class will have to be taken from the decompiled framework.
Sent from my LG-P500 using XDA Premium App

I'm redoing framework.jar... See what i missed... Then i'll get to build.prop
Also using boot.img from mik's cm port now

Breaking news of the day! I'll one of the first tester Keep going, heroes!

popdog123 said:
I'm redoing framework.jar... See what i missed... Then i'll get to build.prop
Also using boot.img from mik's cm port now
Click to expand...
Click to collapse
Will have to replace some smali. Merge the missing wont do.
@jazuk which one mainly.
Sent from my LG-P500 using XDA Premium App

Great news!

4silvertooth said:
No but make a base rom and update.zip which will have all changes and will be small in size.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
+1 for this, it would be easier to download for people with a slow connection like me.

ok ok... will do that... but for now we have to make a good base to start off of...

4silvertooth said:
Will have to replace some smali. Merge the missing wont do.
@jazuk which one mainly.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Whaaat???

Nice to see another dev porting some other firmwares to our phone if you want help then I'm in
Sent from my LG Optimus One P500 using XDA Premium App

jazux said:
Whaaat???
Click to expand...
Click to collapse
Never mind back to that later.
Sent from my LG-P500 using XDA Premium App

[DEV][ICS+SENSE][Mar.20.2012]HTC One V development[Source+RUU]

Original APP folder from most current leak::
App Folder
Original Framework folder from most current leak::
Framework Folder
Tiny's One_V Port so far:
(Boots to the Bootanimation.)
tiny4579 said:
Here is my logcat, maybe someone can figure it out. I'm taking a break for now:
logcat.txt
My current ROM is below.
sense-ics-inc.zip
Click to expand...
Click to collapse
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTCCN_CHS_1.68.1400.2_Radio_20 .67.30.0831U_3831.15.00.28_M_release_254948_signed .exe
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
HTC_One_V_Ramdisk:
V_Ramdisk Download

Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.

I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595

PureMotive said:
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
Click to expand...
Click to collapse
I thought of that too. But since the DInc is a 'QSD' (1000Mhz Qualcomm Snapdragon) and the Desire HD and the Desire S are 'MSM' (Mobile Station) We can't use their ports to help us :/
Being that the DInc is a qsd8k (8650 to be exact) we'll need to keep an eye out for ports with the same processor.. Oh man I wish the old Desire could get a port of this, lol. We'd have no problem at all..

Tribulattifather said:
Saw nobody was getting this started.
I am currently working on it a bit but I defenitley need help compiling a kernel.
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTC_Europe_1.56.401.1_Radio_20.66.30.0831U_3831
(For the newbies)
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
Kernel Source:
HTC Sensation XE (HTC Europe) - ICS CRC - 3.0.16 kernel source code
Look at the 9th one in the list
I hope that we can get this working for our DInc's.
Click to expand...
Click to collapse
kernel source wont help you at all for the 3.xx kernel from other htc phones, so dont bother
i ported sense 4 to the inc 2 (admittedly a lot easier cuz its msm7x30 which most of the ports are) and will give it a shot on my og inc time permitting
see inc2 port here: http://forum.xda-developers.com/showthread.php?t=1553357
the hacked .35 kernels from your ics aosp roms *should* be good (only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot

When you say
nitsuj17 said:
(only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
Click to expand...
Click to collapse
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.

Tribulattifather said:
When you say
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Click to expand...
Click to collapse
no, you need the zimage from one of the ics aosp inc roms and the extracted ramdisk from the htc one v

Okay. Thank you for clarifying for me.
I'm getting down to business now ^>^

PonsAsinorem said:
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
Click to expand...
Click to collapse
can u tell the link to wildstang83 porting guide thread?

orochi9999 said:
can u tell the link to wildstang83 porting guide thread?
Click to expand...
Click to collapse
★wildstang83's Guide For Basic Porting★

PonsAsinorem said:
★wildstang83's Guide For Basic Porting★
Click to expand...
Click to collapse
thank u!

I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium

2012oasis said:
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
Click to expand...
Click to collapse
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.

Tribulattifather said:
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Click to expand...
Click to collapse
can you get a logcat or pm me a ROM link? I'd like to look. No guarantees of success. Sadly the sense devs that could figure it out I think have left the incredible.
Also a working ramdisk still doesn't mean the kernel is good. The kernel may need some changes.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5

I'll upload the ROM port I just made a few days back. It has most of what I thought might work..

Tribulattifather said:
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Click to expand...
Click to collapse
I'd like to try tonight if I can. I'm hoping that an HWA enabled AOSP ICS kernel works with it.

I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..

Ahh! Excited..
Sent from my HTC Droid Incredible using Tapatalk 2 Beta-5

Tribulattifather said:
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Click to expand...
Click to collapse
I'm actually stabbing in the dark as much as you. Never messed much with roms. I'm more of a troubleshooter rather than a rom/kernel chef. I find tweaks and adapt for my kernels. But I noticed there's no init.inc.rc in that ramdisk. Other than that my mind's dead so I'll have to look tomorrow/this weekend.

I apologize for the delay in posting the port link. You'll have to forgive my internet. But, I assure you that the download is as fast as I can get it with my own server that I use.
EDIT: Port is on the next page --->
Just to make sure that everyone is on the same page - This port is NOT a working port.
It will flash to the DInc and it will install properly but it does not boot. And it is obvious why, lol, because we are still missing the piece to the puzzle to make a working kernel.
I hope that this will give you what you need to get this project I started the thrust in the right direction.
As for my method thus far, I am using the zImage from and AOSP ICS port with Ramdisk parts from the One_V.
Post Script - Today is my third year anniversary being apart of XDA. And I can only hope many more years to come.
CHEERS ALL!

port jelly bean Unsuccesfull HELP NEEDED

I have not succesfully ported Android 4.1 Jelly Bean to our devices HELP NEEDED
Now i have one problem it's not booting
i see the Galaxy Tab 8.9 Logo after that a nexus s booting logo and the boot logo fades away really fast after that black screen on boot and not booting into Android 4.1
Any help is welcom

safariking said:
I have succesfully ported Android 4.1 Jelly Bean to our devices
Click to expand...
Click to collapse
it's not booting
Click to expand...
Click to collapse
Rrrright

If it's not booting you didn't successfully port it, so i'm wondering how someone could help you.

There is no point in trying to port it. We will have Jelly Bean source in about two weeks. If ICS drivers work with JB, like everyone seems to think, then it should be easy to make it work.
But if you just want to play with it... What kernel and which Rom are you using as base? Did you extract the boot image and use our ICS kernel and rc files in ramdisk? Did you use libs from our ICS rom?

poisike said:
There is no point in trying to port it. We will have Jelly Bean source in about two weeks. If ICS drivers work with JB, like everyone seems to think, then it should be easy to make it work.
But if you just want to play with it... What kernel and which Rom are you using as base? Did you extract the boot image and use our ICS kernel and rc files in ramdisk? Did you use libs from our ICS rom?
Click to expand...
Click to collapse
Used CM9 Nightly's and copied apps,framework,fonts and media from JB to CM9/ICS after that i have changed the updater-script and the build.prop file after that i have copied some other thing from JB to CM9/ICS!

safariking said:
Used CM9 Nightly's and copied apps,framework,fonts and media from JB to CM9/ICS after that i have changed the updater-script and the build.prop file after that i have copied some other thing from JB to CM9/ICS!
Click to expand...
Click to collapse
I would try it the other way, copy our libs to JB rom. You probably need to copy our graphics libs, egl folder and hw folder. You probably need to use JB ramdisk and copy our rc files (with our device name) to it. You should also enable adb at boot, so you can see where it hangs. Then repack the boot.img with our kernel.

poisike said:
I would try it the other way, copy our libs to JB rom. You probably need to copy our graphics libs, egl folder and hw folder. You probably need to use JB ramdisk and copy our rc files (with our device name) to it. You should also enable adb at boot, so you can see where it hangs. Then repack the boot.img with our kernel.
Click to expand...
Click to collapse
Im in the infuse forums and accidentally stumbled across this, but i have to point this out... You cannot simple take the ramdisk from another JB device and repackage it with yours. The ramdisk contains device specific information/files that differ from phone to phone.. So i dont think i need to explain what happens if you do what you suggested without making the necessary changes..

scott.hart.bti said:
Im in the infuse forums and accidentally stumbled across this, but i have to point this out... You cannot simple take the ramdisk from another JB device and repackage it with yours. The ramdisk contains device specific information/files that differ from phone to phone.. So i dont think i need to explain what happens if you do what you suggested without making the necessary changes..
Click to expand...
Click to collapse
You are correct. I was in hurry when i wrote this and i didn't think about the possibility that the person who asked possibly doesn't know that.

[DEV][7/17][FIXES + FASTER] Jellybean - Collab (less broken stuff)

It's important for everyone to know that since this is a development thread, most, if not all conversation should be dedicated to helping us boot the ROM. All questions related to and including "will our device be able to handle Jellybean?" should be moved to the following thread: http://forum.xda-developers.com/showthread.php?t=1736089
Our biggest problem so far: There are incompatibilities with Jellybean and the Adreno drivers, which our phone needs to function. We can't just remove the Adreno drivers and boot the ROM (I tested this, by removing them from our latest CM9 nightly, which wouldn't boot as a result. I also removed the Adreno drivers and used the Jellybean ramdisk, framework, libs, and bin files but still no boot.).
PureMotive's port
I booted my source-built Jellybean.
Status: ALPHA
Working
Root
ADB
3G
WiFi
Calls (outgoing and incoming)
Signal
UI
Soft keys + lights
RIL
GPS
Brightness settings
Sync
SMS
MMS
Gmail
Gtalk
Twitter
Facebook
Audio
Downloads
Native screenshot (should work now)
Google Now
Untested
Video
Bluetooth
Camera
Broken
Butter
Browser (default)
HWA
Click to expand...
Click to collapse
Albinoman's port
Check his thread located here
Click to expand...
Click to collapse
PORTING FILES:
Code:
Jellybean SDK: [URL]http://d-h.st/EUH[/URL]
Jellybean Ramdisk: [URL]http://d-h.st/XhF[/URL]
Boot.img used in Tiny's port: [URL]http://d-h.st/a0C[/URL]
Vicious Jellybean (VZW GNex port): [URL="http://rootzwiki.com/topic/28486-rom-vicious-toro-jellybean-v3-100-functional-franco-kernel-beats-audio-mods-optimized-link-in-op-for-stock-kernel-added-112am-06302012/"]Vicious Jellybean[/URL]

On vacation. When I get back next week I'll check it out
Sent from my unrootable DROID2

where the hell is the ramdisk

Just wanted to mention my scan of the ramdisk the other night didn't lead to anything conclusive. I checked real quick yesterday I think but didn't really have time to look in depth. I didn't see a problem with the way the system mounted so something else is causing it. I'm trying to port it right now. We'll see what happens.

Maybe I should give it a try.

How about paste bin a logcat?

Here is my current logcat
http://paste.ubuntu.com/1074131/
Sent from my Droid Incredible using xda premium

Shano56 said:
where the hell is the ramdisk
Click to expand...
Click to collapse
Posted in the OP.
PonsAsinorem said:
How about paste bin a logcat?
Click to expand...
Click to collapse
We cannot get a logcat with the Jellybean ramdisk, even with these edits to default.prop:
Code:
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
persist.service.adb.root=1
ro.secure=0
ro.allow.mock_location=1
ro.debuggable=1
service.adb.root=1
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
The only way a logcat will work is if we use the ramdisk from a CM9 ROM in addition to the CM9 libs.

PureMotive said:
Posted in the OP.
Click to expand...
Click to collapse
hehe now u post it. ty
edit: i thought you needed it extracted

PureMotive said:
Posted in the OP.
We cannot get a logcat with the Jellybean ramdisk, even with these edits to default.prop:
Code:
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
persist.service.adb.root=1
ro.secure=0
ro.allow.mock_location=1
ro.debuggable=1
service.adb.root=1
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
The only way a logcat will work is if we use the ramdisk from a CM9 ROM in addition to the CM9 libs.
Click to expand...
Click to collapse
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
Initial Port Below:
http://d-h.st/shx

Upload!!!! Lol
Sent from my Droid Incredible using xda premium

tiny4579 said:
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
zip file coming next.
Click to expand...
Click to collapse
Did you use the ramdisk from the OP or the boot.img I sent you? I got it to the point where it would load the framework .jar files, but haven't encountered what you did in your logcat so I'd consider it progress lol. Seems to be an issue with EGL...
EDIT: Nevermind lol

The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
Sounds to me like you are missing /bin/mksh either in ROM or in symlink in updater
Sent from my PG06100 using xda premium

Just wanted to first of all say thanks for this - it's awesome that this is even being worked on. We have such an awesome dev community. Secondly, just wanted to offer my support in any way possible. I don't have a lot of experience with porting Android, but I do have pretty good Linux system knowledge and a willingness to experiment. Downloading tiny's build now, going to mess around with some system files and see what happens. Thanks again guys!

Cm is going to working on cm10.
http://briefmobile.com/cyanogenmod-cm10-coming-with-jelly-bean-source-code-release
Sent from my ADR6300 using xda app-developers app

tiny4579 said:
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
Initial Port Below:
http://d-h.st/shx
Click to expand...
Click to collapse
Hey tiny4579 could you post what you changed/added in your build?

Albinoman said:
Hey tiny4579 could you post what you changed/added in your build?
Click to expand...
Click to collapse
I don't remember quite what I did and I'm not in a position to test but what if you take evervolv as a base and replace the app and framework folders with the ones from my port and the boot.img with the one from the port. It probably won't work by a long shot but at least it's worth a try.
Sent from my Galaxy Nexus using Tapatalk 2

I see progress! I will download your port right now and see what I can help you with.

tiny4579 said:
I don't remember quite what I did and I'm not in a position to test but what if you take evervolv as a base and replace the app and framework folders with the ones from my port and the boot.img with the one from the port. It probably won't work by a long shot but at least it's worth a try.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try that later today. What version of evervolv are you using?
Sent from my Droid Incredible using xda premium

Albinoman said:
I'll try that later today. What version of evervolv are you using?
Sent from my Droid Incredible using xda premium
Click to expand...
Click to collapse
I was testing with 2.2.0a1.
Sent from my Galaxy Nexus using Tapatalk 2

[GUIDE]How to Port ROMS from same resolutions phones- Easy way

Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev

Thanks..
Very Interesting and useful..
Infact i find some guide simple to try...
Good Job!

Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app

SnXo said:
Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app
Click to expand...
Click to collapse
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app

tobixdev said:
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
I tried a while ago with this rom: http://forum.xda-developers.com/showthread.php?t=1562603.
The end result was a bootloop. I will maybe try to do it again when I have more time.

this doesn't work with sense without additional work.
Sent from my LG-P880 using xda app-developers app

tobixdev said:
Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev
Click to expand...
Click to collapse
ths very much