Database Users

[ROM][PORTING] Galaxy S3 ROM for the S2

Hi all,
Sadly, I have irrecoverably bricked my S2 and I am no longer as active in the S2 forums. This does not mean you guys should stop trying to port this ROM to the S2 - It is a great device that should still be considered as one of the high-end phones in the market. Even though I've moved on to the S3 I will gladly try to help this project that I started and I am following this thread post by post.
I think it would be a good idea if everyone that has done something for the porting post exactly what they did and what were the results.
Hi guys,
I know that I've been fairly quiet over the past week, and that is because this project is going nowhere. I know we have some general direction of what we have to do, but a lot of fine details are unclear to me and everybody else. These details are ones such as: how to decompile & recompile the apks, which images to resize & how, what folders should be renamed, what files are needed in the new Rom, and more.
I have asked for assistance from the people porting the Sense 4 One X Rom to the S2, and I am waiting for a reply.
Sit tight, and hope for the best!
Hi guys!
This thread is meant to organize the porting of the Galaxy S3 firmware to our Galaxy S2.
The first thing we have to do is make the /system folder of the Rom smaller than 500MB, because that is how our phone is partitioned. To achieve that the first thing we have to do is convert all the XHDPI images in the apks to HDPI images because it will make the apks smaller and anyways - our phone is a HDPI device. After we do this, we will see if we have to trim down on more space in our /system folder.
To test if the Rom will boot after we do the above steps, I deleted a bunch of non-essential apps such as voice talk to make the /system folder smaller than 500MB. I then replaced the /system/app & /system/framework with the modified S3 ones, but unfortunately the Rom did not boot fully and got stuck at boot animation. To figure out why it didn't boot, Pulser suggested that we use a kernel that has adb force enabled and then we can get a logcat and see what the problem is.
For people who want to help meanwhile:
The task that is needed to be done is convert all the XHDPI images in the apks to HDPI images.
How to do this:
1. Download the S3 Rom (below).
2. Download Resizer 1.0 (below).
3. Resize all XHDPI images in all the apks in /system/app & /system/framework.
Download Links:
I9100 Rom - http://www.mediafire.com/?4v6i6isqa3pa4lw
I9300 Rom - http://www.mediafire.com/?9xk39miljh3l9vw
Resizer 1.0 - http://www.mediafire.com/?d6h6lpwm8jxdjxr​

Resized Apps: (0/190)
/system/app (0/188)
/system/framework (0/2)

Would love to see this happen, not sure how viable it is though.

please post in gereral ore q&a thead
request move

it would be more then WOW to get it ported to the sgs2.
But is it posible to run quad-core kernel/modem/radio software on a dual-core carrier

I thing good intentions are not enough. There must be several developers interested in thic project

mad-monk said:
Have to agree repost it to Q/A.......but it would be more then wow to get it ported to the sgs2.
But is it posible to run quad-core kernel/modem/radio software on a dual-core carrier
Click to expand...
Click to collapse
And that is where porting comes in!

Patroy said:
I thing good intentions are not enough. There must be several developers interested in thic project
Click to expand...
Click to collapse
That is why this thread was opened, to get developers interested...

Please do that awesome devs !

this is very interesting.

A great idea, I'll be watching to see com evolves.

They have ported the ICS based ROM to the SGS. Why can the SGS3's ROM not be ported to ours as well? :/

Now that we have a few dozen users interested within a few hours of this thread existing, we have to try to raise the awareness of developers in the hope that some of them join the project.
Whoever has names of developers that might be interested, please try and contact them and see if they are interested in joining the project.

Well if any devs are going to do this...There is not much use in porting the UI and the SGSIII theme. Rather shouldn't the emphasis be on the handy features and new apps that Samsung have made?
Sent from my GT-I9100 using xda premium

very problematic idea
have you seen how much space take an I9300 rom ?
to do a proper port the developer will need to creat a new pit file (wich will re format the space on the phone to give larger drive for the system)
and a new bootloader wich he will have to make to work with the new pit
without cusing hard brick to the user

Yandvoiris said:
very problematic idea
have you seen how much space take an I9300 rom ?
to do a proper port the developer will need to creat a new pit file (wich will re format the space on the phone to give larger drive for the system)
and a new bootloader wich he will have to make to work with the new pit
without cusing hard brick to the user
Click to expand...
Click to collapse
Then I guess we'll need one hell of a developer!

Yandvoiris said:
very problematic idea
have you seen how much space take an I9300 rom ?
to do a proper port the developer will need to creat a new pit file (wich will re format the space on the phone to give larger drive for the system)
and a new bootloader wich he will have to make to work with the new pit
without cusing hard brick to the user
Click to expand...
Click to collapse
app folder and framework folder of sgs3 is 470 MB and our system partition is 500 MB so not enough space for other files such as libs,bins,media,etc
Maybe if its ported then devs can remove some bloatware and move some apps to data partition

ata1918 said:
Well if any devs are going to do this...There is not much use in porting the UI and the SGSIII theme. Rather shouldn't the emphasis be on the handy features and new apps that Samsung have made?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I tend to agree with this
Sent from my GT-I9100 using XDA

Won't the apps be portable anyway its all 4.0.4 - not sure why you would want the whole ROM for a different phone?

Have been thinking about this all morning... glad people are already on the case!! After using an S3 yesterday, I'd personally be keen for a straight/similar ported ROM where possible rather than pulling out all the best bits. I've had enough of AOSP ROMs for now....

[MOD][MIUI4] Volume+ Mod for MIUI4 v2.7.20 (Hold volume to skip tracks)

The prebuilt android.policy.jar ZIP attached is only for MIUI v2.7.20 for the Arc S (and unofficial ports based on that build, as long as the porter didn't already mess with that jar file). If you want it for other devices, get the 'Source Info' file and port it yourself.
You all know it. Roots in Cyanogenmod, ported to MIUI Gingerbread and many other ROM's over time... but new MIUI4 ROM's have missed out for too long. So here it is. Hold Volume-Up to skip forward a track, Down for back. Only works while music is playing and while screen is off and locked. Apparently it will also change FM channel if playing Radio, don't know and don't care.
It is based on MIUI UK's MIUI v2.7.20 for the Arc S, with the source info it should be easy to port to any other device. Might work on older/newer versions of MIUI too, don't know. This took me half an hour to do, it wouldn't have been possible without 7OH's original mod for Xperia's on Stock ICS. I just ported it to MIUI.
This is not a flashable ZIP, sort it out yourself. Extract, push android.policy.jar to /system/framework/ (overwrite old one) and optionally chmod it to 644.
Integrate it in your ROM if you wish, credit would be appreciated. Don't be an ass and claim it as your own. Just say "Volume+ Mod by CosmicDan and 7OH" in the credits.
Also attached is some info on the smali changes (a unified diff and two new files).
Bye!

i tried this on my galaxy siii but i just get bootloops

daniel9522 said:
i tried this on my galaxy siii but i just get bootloops
Click to expand...
Click to collapse
Galaxy S III is an unofficial MIUI device, contact your ROM developer to make the changes or try a different port. Also tell us which MIUI version it is and where you downloaded it from so others know. Thank you.

daniel9522 said:
i tried this on my galaxy siii but i just get bootloops
Click to expand...
Click to collapse
Just fyi, now that miui is based on stock firmwares, this will only work on devices it comes from (I.e the arc s). Miui gb was compiled from source, which is why stuff like this worked on all roms. Now they just patch some miui stuff into the original jar file, so the chances of a one-jar-fits-all are non-existant. The same patch will work, just that it needs to be done specifically for each rom. Too many framework changes between e.g. sense, touchwiz, Xperia etc.

lenny_kano said:
Just fyi, now that miui is based on stock firmwares, this will only work on devices it comes from (I.e the arc s). Miui gb was compiled from source, which is why stuff like this worked on all roms. Now they just patch some miui stuff into the original jar file, so the chances of a one-jar-fits-all are non-existant. The same patch will work, just that it needs to be done specifically for each rom. Too many framework changes between e.g. sense, touchwiz, Xperia etc.
Click to expand...
Click to collapse
Ahhhh OK fair enough, thanks for the info! I guess I will post in the Arc S section then. I will leave this here though because the other ZIP has a diff of the smali changes. and the MIUI port maintainers can take care of it. Still relevant for this section, also this is a first (at time of writing, no other site/ROM has it in MIUIv4 except for mine).
First post updated.

and this probably works for Neo V also thanks I try that later

Dan can you please provide me any information about how to use the diff file?

_polimorph_ said:
Dan can you please provide me any information about how to use the diff file?
Click to expand...
Click to collapse
Pretty sure you can't. It's for devs and users who want to integrate this feature into other roms. (Unless diff is associated with miui or somthing else then ignore me)

_polimorph_ said:
Dan can you please provide me any information about how to use the diff file?
Click to expand...
Click to collapse
With a program like WinMerge or patch binary compiled for win32. But you will need to edit variables, labels and line numbers where necessary. If you don't know how, don't bother. Basically if it's v0 on mine it might be v1 on yours, you can compare similar code around my changes to get an idea of what it should be.

[TUT] How to easily port CM7,CM9,CM10 Based ROMs to HTC Aria

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.

[Q] Help with Safestrap/Cyanogenmod on Razr m

Hello,
I'm a little late to the Razr M game, but I just got a device off ebay since it's only about a year old and in great shape and quite cheap :good:
In any case, I've so far managed to unlock the radio for Tmobile in the US (GSM), and root it the device. Unfortunately, I didn't know when i bought it about the inability to unlock the bootloader with OTA from May and beyond, which mine is according to fastboot. I believe I came across the actual number being 98.18.78 somewhere.
So I've been doing a lot of reading, got SafeStrap running, made a stock backup, and am testing on slot1. However, I can't seem to get any CM ROM's running! Most of them 'boot' but then all I get is a blank screen, though I can connect with adb and therefore confirm that it does actually run some CM build.
I'm first of all somewhat confused on what ROM i should be using. I've found several links that should seem like they work, but none have succeeded (all have that halfway functionality that only works in ADB):
http://d-h.st/FgU
http://skrilax.droid-developers.org/cm10.1nightly/razrqcom/index.php?device=xt907
http://goo.im/devs/Hashcode/scorpion_mini/cm10.1
http://skrilax.droid-developers.org/cm10.2nightly/razrqcom/index.php?device=xt907
I found these in various threads on XDA and droidrazr.com. I basically read the entire 55 pages of http://forum.xda-developers.com/showthread.php?t=2012093 and since the link in the first page is dead I tried all the links that came up on the thread, which got a couple of the links in my list above.
Also, I did run across the tip that I had to mount system in SafeStrap to get these working, no success. And what's this thing about having to wipe dalvik and system and cache two or three times??
Basically I'd like the proper, up to date link that should be working, along answer to above question and and other tips!
Thanks!!! I love the phone otherwise it's great
UPDATE:
I did manage to get an CyanogenMod spinning forever startup screen with an ancient rom described here http://www.droidviews.com/install-first-aosp-based-unofficial-cm10-rom-on-motorola-droid-razr-m-xt907/ which appears to have come again from the thread mentioned above. The link is now gone but I have the .zip that I must have snagged right before it disappeared!

flyingsilverfin said:
Hello,
I'm a little late to the Razr M game, but I just got a device off ebay since it's only about a year old and in great shape and quite cheap :good:
In any case, I've so far managed to unlock the radio for Tmobile in the US (GSM), and root it the device. Unfortunately, I didn't know when i bought it about the inability to unlock the bootloader with OTA from May and beyond, which mine is according to fastboot. I believe I came across the actual number being 98.18.78 somewhere.
So I've been doing a lot of reading, got SafeStrap running, made a stock backup, and am testing on slot1. However, I can't seem to get any CM ROM's running! Most of them 'boot' but then all I get is a blank screen, though I can connect with adb and therefore confirm that it does actually run some CM build.
I'm first of all somewhat confused on what ROM i should be using. I've found several links that should seem like they work, but none have succeeded (all have that halfway functionality that only works in ADB):
http://d-h.st/FgU
http://skrilax.droid-developers.org/cm10.1nightly/razrqcom/index.php?device=xt907
http://goo.im/devs/Hashcode/scorpion_mini/cm10.1
http://skrilax.droid-developers.org/cm10.2nightly/razrqcom/index.php?device=xt907
I found these in various threads on XDA and droidrazr.com. I basically read the entire 55 pages of http://forum.xda-developers.com/showthread.php?t=2012093 and since the link in the first page is dead I tried all the links that came up on the thread, which got a couple of the links in my list above.
Also, I did run across the tip that I had to mount system in SafeStrap to get these working, no success. And what's this thing about having to wipe dalvik and system and cache two or three times??
Basically I'd like the proper, up to date link that should be working, along answer to above question and and other tips!
Thanks!!! I love the phone otherwise it's great
UPDATE:
I did manage to get an CyanogenMod spinning forever startup screen with an ancient rom described here http://www.droidviews.com/install-first-aosp-based-unofficial-cm10-rom-on-motorola-droid-razr-m-xt907/ which appears to have come again from the thread mentioned above. The link is now gone but I have the .zip that I must have snagged right before it disappeared!
Click to expand...
Click to collapse
There is not much.
You will not find much better than Mhous33's dst & my sd swap here : http://forum.xda-developers.com/showthread.php?t=2442384
There is also one at RZR http://www.droidrzr.com/index.php/topic/33740-rom-jb-98163-xt907-rage-m-v10-1232013/
---------- Post added at 07:47 PM ---------- Previous post was at 07:43 PM ----------
Your boot ,which includes the kernel & recovery are locked. All the roms you list use a non stock kernel.
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
There are others but they are not current.

Well, none of the custom ROMs out now will work with SS. Their are some stock based ROMs, one of which was posted by Avi, that will work with SS. There are some older ROMs that were designed for SS and they were built prior to April (when our bootloader was unlocked). You'll have to dig back a couple of page to find them. I know there was SS compatible CM10 in that link you posted, but I don't think the link is active for it anymore. If you decide to run an older SS compatible ROM on your newer system version, you're going to run into kernel issues. Things like the gallery not working and WiFi signal being weak. Your best bet right now is to load a stock ROM on slot 1 and start tweaking that with XPosed and enabling Init.d so you can get some performance tweaks going.

Thanks for the response, I'll check those out. Glad to find some up to date roms haha
aviwdoowks said:
Your boot ,which includes the kernel & recovery are locked. All the roms you list use a non stock kernel.
Click to expand...
Click to collapse
This is something I didn't realize/know before, good to know! That would explain some of the problems. May I ask how you know they don't use stock kernels? Just experience in the development process or is there a way to check?

RikRong said:
Your best bet right now is to load a stock ROM on slot 1 and start tweaking that with XPosed and enabling Init.d so you can get some performance tweaks going.
Click to expand...
Click to collapse
Thanks for the info, I'll have to do some research if aviwdoowks's pointers dont work out! Second day fiddling with this stuff on android so I don't know what XPosed is/what Init.d does (although I think Ubuntu has that file too...)
Also, I tried the DeadCalm SS rom and i get an
E:signature verification failed
error

flyingsilverfin said:
Thanks for the response, I'll check those out. Glad to find some up to date roms haha
This is something I didn't realize/know before, good to know! That would explain some of the problems. May I ask how you know they don't use stock kernels? Just experience in the development process or is there a way to check?
Click to expand...
Click to collapse
Word would get round if they did, but What vzw wants moto to do to a phone is not what cwm wants to do. 4 cyl hi mpg VS racing v8

Same problem with the xt907-98.30.1-deodexed rom:
E: signature verification failed
Not sure what's wrong with BOTH of these?
Sorry, didn't do enough testing. Disabled zip verification and it wrote, just have to see its working!

flyingsilverfin said:
Thanks for the info, I'll have to do some research if aviwdoowks's pointers dont work out! Second day fiddling with this stuff on android so I don't know what XPosed is/what Init.d does (although I think Ubuntu has that file too...)
Also, I tried the DeadCalm SS rom and i get an
E:signature verification failed
error
Click to expand...
Click to collapse
Did you mount system before installed it?
All SS roms need mounting.
My link has steps.
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I think DC is not SS ready.
---------- Post added at 09:18 PM ---------- Previous post was at 09:08 PM ----------
DC flashes the damn skull bootlogo, easy to delete the bootlogo & # out instructions in the updater-script, other things too for a DIY SS rom
---------- Post added at 09:21 PM ---------- Previous post was at 09:18 PM ----------
DL my SS deodexed & use it as a templet as to what items need to be taken out.
Root Explorer is all you need.

Thanks for the help and links, I have the deodexed SS version from your link working. I see that it is not a debloated version; is the odexed version debloated?
Also I was originally hoping for a ROM with functionality like Cyanogenmod, but I guess the situation is too specific for that too happen. I might be interested in getting to ROM making/customizing at some point, I did some preliminary reading, I should be able to edit the deoxed SS ROM and then 'stitch it up again' in simplest terms, and it will still work on my device, correct? I feel like editing a ROM would be a great way to learn more about Android/Linux/bootloaders etc before I go to college.

flyingsilverfin said:
Thanks for the help and links, I have the deodexed SS version from your link working. I see that it is not a debloated version; is the odexed version debloated?
Also I was originally hoping for a ROM with functionality like Cyanogenmod, but I guess the situation is too specific for that too happen. I might be interested in getting to ROM making/customizing at some point, I did some preliminary reading, I should be able to edit the deoxed SS ROM and then 'stitch it up again' in simplest terms, and it will still work on my device, correct? I feel like editing a ROM would be a great way to learn more about Android/Linux/bootloaders etc before I go to college.
Click to expand...
Click to collapse
The odexed is DST which means a debloated to the same specs at the Telstra build. The SD swap works on both.

aviwdoowks said:
The odexed is DST which means a debloated to the same specs at the Telstra build. The SD swap works on both.
Click to expand...
Click to collapse
What is the telstra build? Is that the name of the stock motorola ROM that came with the device? Also I'm guessing SD swap is just a way have the phone treat the SD as internal memory?
Also, any idea if it would be possible or how difficult it would be to modify the ROM you linked me to to turn it into a Cyanogenmod port?
Thanks for all the help

flyingsilverfin said:
What is the telstra build? Is that the name of the stock motorola ROM that came with the device? Also I'm guessing SD swap is just a way have the phone treat the SD as internal memory?
Also, any idea if it would be possible or how difficult it would be to modify the ROM you linked me to to turn it into a Cyanogenmod port?
Thanks for all the help
Click to expand...
Click to collapse
Telstra is the Australian firmware, I believe. If you want to port CM, you need to pull from their source. The DST ROM is a stock Moto ROM that's built by the Moto software team. You can't really take that and change it into a CM port, but you can make your own build environment and start building CM.

flyingsilverfin said:
What is the telstra build? Is that the name of the stock motorola ROM that came with the device? Also I'm guessing SD swap is just a way have the phone treat the SD as internal memory?
Also, any idea if it would be possible or how difficult it would be to modify the ROM you linked me to to turn it into a Cyanogenmod port?
Thanks for all the help
Click to expand...
Click to collapse
Telstra is a carrier for the xt905. There are builds posted in our dev section. Any telstra rom is encrypted & if flashed w/ Rsd or Fastboot will brick an xt907.
Very difficult. Edit impossible.

RikRong said:
Telstra is the Australian firmware, I believe. If you want to port CM, you need to pull from their source. The DST ROM is a stock Moto ROM that's built by the Moto software team. You can't really take that and change it into a CM port, but you can make your own build environment and start building CM.
Click to expand...
Click to collapse
Alright thanks for the info. I was just doing some reading on the Linux Kernel. Since I am stuck with the stock motorola kernel, but this implements all the things I need to make the upper level, platform independent sys calls and other api's, there shouldn't be a need to build a special kernel for a cyanogenmod port, correct? If i port the higher level things everything that is implemented in cyanogenmod should work... am I getting this right? I'm trying to figure out what the OS kernel requirements are.

Porting CyanogenMod to Desire 820s MT6752

I came across CM12.1 rom for Lenovo K3 Note on needrom. Considering that K3 have the same chipset as ours, I've been thinking that it can be ported to our device.
I've tried to port it past few days but failed. Any developer would come up and try to port it?

What have you done? Device tree something else?

Nope. Just changing libs here and there, according to this guide. I'm still noob in porting roms so I can't do much.

amirarsyad97 said:
I came across CM12.1 rom for Lenovo K3 Note on needrom. Considering that K3 have the same chipset as ours, I've been thinking that it can be ported to our device.
I've tried to port it past few days but failed. Any developer would come up and try to port it?
Click to expand...
Click to collapse
Did you edit the updater script?

Gibz97 said:
Did you edit the updater script?
Click to expand...
Click to collapse
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.

amirarsyad97 said:
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
Click to expand...
Click to collapse
If you have an idea for kernel, I'll help you

amirarsyad97 said:
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
Click to expand...
Click to collapse
Let's wait for the response then

Would be graet to see CM to release this device's potential. Especially since HTC is taking it's sweet time with 6.0 update and 5.1 was officially skipped.
Anyway if you would need some testers I would gladly help.

Good news! The permission has been granted. I will try my best to port this rom.

And what with 820n?
Sent from my HTC Desire 820 using XDA Free mobile app

Dragonfail said:
And what with 820n?
Sent from my HTC Desire 820 using XDA Free mobile app
Click to expand...
Click to collapse
We don't have 64-bit kernel sources for 820n MSM chipset

Hi @amirarsyad97, so did you manage to extract system files?

Gibz97 said:
Hi @amirarsyad97, so did you manage to extract system files?
Click to expand...
Click to collapse
I already did, but I can't repack it. So instead I tried looking for other roms while staying away from dat files - cm12.1 ulefone be touch 2 and blisspop k3 note.
Now I'm having problems with the kernel. The rom won't boot at all, the worse I can't get the dmesg.
I don't have much free time to explore kernels in detail. If anybody can help me with porting the kernel, it would be a pleasure.

amirarsyad97 said:
I already did, but I can't repack it. So instead I tried looking for other roms while staying away from dat files - cm12.1 ulefone be touch 2 and blisspop k3 note.
Now I'm having problems with the kernel. The rom won't boot at all, the worse I can't get the dmesg.
I don't have much free time to explore kernels in detail. If anybody can help me with porting the kernel, it would be a pleasure.
Click to expand...
Click to collapse
I will try porting the kernel using the kitkat kernel as base when I find time

Unfortunately, I did not succeed, I could not even get into the bootanimation. Hope someone can help us.
I am now trying to squeeze the Lollipop system partition so that we can liberate some more free space for the internal storage, hope it works

That would be the coolest thing???

Hello guys hope you have been doing great, Was too busy with school, exams and stuff.
Good news!! I have finally managed to boot into CM 12.1 after I successfully ported it today.
It's lightning fast but has some bugs: USB, bluetooth and Sim don't work currently and it needs some resizing of the framework images.
I will try to work on it until Sunday and hopefully someone else can take over with modifying it

Gibz97 said:
Hello guys hope you have been doing great, Was too busy with school, exams and stuff.
Good news!! I have finally managed to boot into CM 12.1 after I successfully ported it today.
It's lightning fast but has some bugs: USB, bluetooth and Sim don't work currently and it needs some resizing of the framework images.
I will try to work on it until Sunday and hopefully someone else can take over with modifying it
Click to expand...
Click to collapse
I was wondering how you can make the kernel work. Anyway good work!

amirarsyad97 said:
I was wondering how you can make the kernel work. Anyway good work!
Click to expand...
Click to collapse
Use this kernel and build.prop and use the original system (don't replace with stock files) https://mega.nz/#!c4USzSTL!rXmsjMYaxR9ECwNeiMjissLPuFRLBWBUSLIuwiBFwQk
Almost everything works right now except Bluetooth, camera and Sim

Great work keep it up
Sent from my HTC Desire 820 dual sim using XDA-Developers mobile app