I haven't been able to find a good answer on miui.us nor have I gotten a reply from any of the devs who have successfully ported to an unsupported device. I have searched for answers as much as possible, and I haven't been able to find out where miui devs get started. Are they compiling from source(I haven't found any source)? I plan on asking the same question there, but I have always gotten the best answers from the XDA community..
I'm waiting for my amaze 4g to come in the mail, the device doesn't have many devs, and while the main dev is working on ICS I figured I'd try to get into development(that is why I finally bought a new device) to see if I can offer the community something while we wait for ICS to get done/stable. If anyone can point me in the direction of where these devs go to get started, I would greatly appreciate it!
Silentbtdeadly said:
I haven't been able to find a good answer on miui.us nor have I gotten a reply from any of the devs who have successfully ported to an unsupported device. I have searched for answers as much as possible, and I haven't been able to find out where miui devs get started. Are they compiling from source(I haven't found any source)? I plan on asking the same question there, but I have always gotten the best answers from the XDA community..
I'm waiting for my amaze 4g to come in the mail, the device doesn't have many devs, and while the main dev is working on ICS I figured I'd try to get into development(that is why I finally bought a new device) to see if I can offer the community something while we wait for ICS to get done/stable. If anyone can point me in the direction of where these devs go to get started, I would greatly appreciate it!
Click to expand...
Click to collapse
They steal the code from CM source. Then they wrap it up in a closed source OS. So you won't find any source for it.
zelendel said:
They steal the code from CM source. Then they wrap it up in a closed source OS. So you won't find any source for it.
Click to expand...
Click to collapse
I figured it might be something like that, would explain why I haven't found anything really helpful.. but then the question becomes how do people port it to other devices? I'm personally a fan of the functionality it has over CM, and it would give the users of my device something to play with(and me something to learn/experiment with) while we wait for ICS to get built. Hell, if I can find some good resources, maybe I could contribute to the ICS build before it is done..
But while the resources I've been finding here are good, I learn best by tinkering, just figuring things out, so the resources between what is offered here and the finished product would do me the most good.
Silentbtdeadly said:
I haven't been able to find a good answer on miui.us nor have I gotten a reply from any of the devs who have successfully ported to an unsupported device. I have searched for answers as much as possible, and I haven't been able to find out where miui devs get started. Are they compiling from source(I haven't found any source)? I plan on asking the same question there, but I have always gotten the best answers from the XDA community..
I'm waiting for my amaze 4g to come in the mail, the device doesn't have many devs, and while the main dev is working on ICS I figured I'd try to get into development(that is why I finally bought a new device) to see if I can offer the community something while we wait for ICS to get done/stable. If anyone can point me in the direction of where these devs go to get started, I would greatly appreciate it!
Click to expand...
Click to collapse
So what we (miui porters) do is take the kernel from cm7 and some lib files from cm7 and add to an existing miui rom until it boots. It helps if you use a similar device as the base (I use the nexus s 4g as a base for my epic 4g ports b/c epic is pretty much a keyboarded version of the nexus s 4g).
Sent from my SPH-D700 using Tapatalk
xboxfanj said:
So what we (miui porters) do is take the kernel from cm7 and some lib files from cm7 and add to an existing miui rom until it boots. It helps if you use a similar device as the base (I use the nexus s 4g as a base for my epic 4g ports b/c epic is pretty much a keyboarded version of the nexus s 4g).
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Where do you guys get the weekly build of miui from, I know it is updated every friday, but I haven't seen where they are getting it from..
The phone I want to develop for is the Amaze 4g, the Sensation is pretty much the same with just a underclocked cpu. The amaze is new enough that everything I've found says they are working on a cm9 build and skipping cm7 all together, so the best I can think of is grabbing some files from the sensation cm7(like you do the nexus) and stock files from the official gingerbread releases for the amaze.
The question is what files can I use from the sensation, will the files from stock ginger work, and which files need to be ported at all. The best I've found is this http://www.madteam.co/forum/support-65/how-to-port-miui/ which I've read the feedback on, and results seem to vary quite a bit.
Silentbtdeadly said:
Where do you guys get the weekly build of miui from, I know it is updated every friday, but I haven't seen where they are getting it from..
The phone I want to develop for is the Amaze 4g, the Sensation is pretty much the same with just a underclocked cpu. The amaze is new enough that everything I've found says they are working on a cm9 build and skipping cm7 all together, so the best I can think of is grabbing some files from the sensation cm7(like you do the nexus) and stock files from the official gingerbread releases for the amaze.
The question is what files can I use from the sensation, will the files from stock ginger work, and which files need to be ported at all. The best I've found is this http://www.madteam.co/forum/support-65/how-to-port-miui/ which I've read the feedback on, and results seem to vary quite a bit.
Click to expand...
Click to collapse
Since your devices are so close, try just copying system/lib/egl and system/lib/hw from stock to Sensation MIUI and also IDK if Amaze and Sensation kernels are compatible, but I'll assume not because that could lead to a brick. So copy boot.img from stock to MIUI. Then Logcat and see what the errors are and replace whatever files error (If it says libcamera failed, replace it with one from stock). It may never boot from a stockbased kernel, it does on some devices and not on others. You may also be able to unpack the boot.img from stock and Sensation MIUI and copy the Sensations intramfs/ramdisk from Sensations folder to Amaze's. Then repack the Amaze folder, which has the Sensation's intramfs in it and then try.
xboxfanj said:
Since your devices are so close, try just copying system/lib/egl and system/lib/hw from stock to Sensation MIUI and also IDK if Amaze and Sensation kernels are compatible, but I'll assume not because that could lead to a brick. So copy boot.img from stock to MIUI. Then Logcat and see what the errors are and replace whatever files error (If it says libcamera failed, replace it with one from stock). It may never boot from a stockbased kernel, it does on some devices and not on others. You may also be able to unpack the boot.img from stock and Sensation MIUI and copy the Sensations intramfs/ramdisk from Sensations folder to Amaze's. Then repack the Amaze folder, which has the Sensation's intramfs in it and then try.
Click to expand...
Click to collapse
Awesome, a place to start. My buy for the Amaze got screwed up, so I'm going to likely get one from tmobile.. but I've already put together a rom to spec that you have described, and I have a few kernels to try too. I hope that checking the logcat and making some tweaks based on the output I get a working rom, the next questions would be what a script looks like(on a pc or mac) I could just apply to pull the files from the different sources to apply to weekly released-- I am pretty sure that is what successful ports do.. and what I could do to be more of a developer rather than just porting or kang'ing. I just figured this would be a good way to get some working experience in the meantime.. but I am guessing that once a good build of an OS is out there, people aren't compiling from source. Seems like many are just learning aspects of the OS and tweaking stock roms with things they have found..
Thanks again for the advice, as soon as I have the phone to test it with, I am gonna give this a try
Silentbtdeadly said:
Awesome, a place to start. My buy for the Amaze got screwed up, so I'm going to likely get one from tmobile.. but I've already put together a rom to spec that you have described, and I have a few kernels to try too. I hope that checking the logcat and making some tweaks based on the output I get a working rom, the next questions would be what a script looks like(on a pc or mac) I could just apply to pull the files from the different sources to apply to weekly released-- I am pretty sure that is what successful ports do.. and what I could do to be more of a developer rather than just porting or kang'ing. I just figured this would be a good way to get some working experience in the meantime.. but I am guessing that once a good build of an OS is out there, people aren't compiling from source. Seems like many are just learning aspects of the OS and tweaking stock roms with things they have found..
Thanks again for the advice, as soon as I have the phone to test it with, I am gonna give this a try
Click to expand...
Click to collapse
Actually, one more suggestion on the kernel. Using dsixdas kitchen, extract the boot.Img from amaze stock and sensation miui and go to boot.img-ramdisk folder and go to init.RC on both devices using notepad++ and find the line that says bootclasspath and copy it from miui to amaze stock. Then recompile using dsixdas kitchen and then test
Sent from my GT-P7510 using Tapatalk
Related
I've looked around and haven't found anything that comes close to the answers I'm searching for so I figured this would be a good place as any to ask, sorry in advance if this isn't the proper place.
I ported 2 ROM's from a device (Desire Z to the EVO Shift) I got the ROM'S nearly fully functional. However, on both ROM's which one is a Sense 3.5 ROM and the others a Sense 4.0 ROM, both ROM's using different kernels come back with the same USB/SD Card mount issues. I'm not sure if its kernel related or what, anybody have any suggestions to fix these issues?
TDJ512 said:
I've looked around and haven't found anything that comes close to the answers I'm searching for so I figured this would be a good place as any to ask, sorry in advance if this isn't the proper place.
I ported 2 ROM's from a device (Desire Z to the EVO Shift) I got the ROM'S nearly fully functional. However, on both ROM's which one is a Sense 3.5 ROM and the others a Sense 4.0 ROM, both ROM's using different kernels come back with the same USB/SD Card mount issues. I'm not sure if its kernel related or what, anybody have any suggestions to fix these issues?
Click to expand...
Click to collapse
I think it might be the kernel because i know certain issues from older versions of the skyhigh kernel for the sgs+ wich occured the errors u are stating in here....
so take into consideration to check the kernel
thats all i know about this topic
Thanks for responding, but what aspect of the kernel. I'm not so kernel savy so lame terms if you will, thanks.
TDJ512 said:
Thanks for responding, but what aspect of the kernel. I'm not so kernel savy so lame terms if you will, thanks.
Click to expand...
Click to collapse
yea...im not a kernel pro too but i think i know a method to find out..
go to this thread and check the kernel sources on github
the kernel has one version wich is called 1.4 and one called 1.4d check the changelog in the thread cus the author stated that he fixed the issues in the 1.4d version so i think if you compare the sources of the 2 kernel u might find out whats wrong with yours
http://forum.xda-developers.com/showthread.php?t=1555431
heres the thread
TDJ512 said:
I've looked around and haven't found anything that comes close to the answers I'm searching for so I figured this would be a good place as any to ask, sorry in advance if this isn't the proper place.
I ported 2 ROM's from a device (Desire Z to the EVO Shift) I got the ROM'S nearly fully functional. However, on both ROM's which one is a Sense 3.5 ROM and the others a Sense 4.0 ROM, both ROM's using different kernels come back with the same USB/SD Card mount issues. I'm not sure if its kernel related or what, anybody have any suggestions to fix these issues?
Click to expand...
Click to collapse
A little more information would be helpful. What does the logs tell you? Either udev does not recognise the sdcard device, or vold does not like it. Do you get the device nodes? Does vold log anything? Is the sdcard properly initialised? Does it mount in a unmodified phone? Can you mount it manually? Does it contain more the four partitions (vold handles no more by default)?
The SD Card mounts fine on builds originally intended for the Shift. Its just with cross ports from Desire Z/G2 these issues are arising. When I attempt to initialize the USB the charge feature activates, but the PCSC.apk (I believe) doesn't pop up with the options to charge/mount, it couldn't mount the SD Card anyhow if that feature would initialize because its not reading that there's anything to mount. I'm thinking this issue is more along the lines of file issues then a kernel issue. Give or take I follow the principles of this guide http://forum.xda-developers.com/showthread.php?t=1222746 with a bit of common sense there after. What could I be missing? See, I also thought maybe it was a kernel issue initially. So I ported a few more ROM's from the Desire Z/G2, builds ranging from Gingerbread 2.3.5 (CM7/Sense 3.5) to 4.0.4 (CM9/Sense 4.0), of course while using proper kernel's intended to boot the builds that are proven to function accurately on the Shift & all of them came back with a usb/sd card mount issue.
Disclaimer: I'm not an android dev but am interested in learning, really my only knowledge of dev'ing is the three hours or so I've spent so far failing at a port this morning. Don't be a douche, I just admitted my ignorance here.
If you don't know about PA (ParanoidAndroid) then go here and marvel > http://forum.xda-developers.com/showthread.php?t=1717079
It's been ported to the Atrix4G so I figured why not try dx2, and I'm using the A4G ROM in porting. I've been following the instructions here and keep getting hung up on rebuilding the modified framework-res.apk with apktool. The error I'm getting is in the attachments.
My process up to this point is:
- decompile framework-res.apk from PA and our CM9 rom.
- combine framework-res/res/values/ and framework-res/res/xml/ from CM9 to PA folder
- this is where rebuilding the apk fails...
Does anyone know anything about porting that can help? I feel like a lack of knowledge is my problem here.
I have nothing to contribute to this other than a simple good luck. It would be cool to have another option for this phone.
Questions should be asked in Q&A forums, not Development forums.
Thread moved.
Sent from my GT-I9100 using Tapatalk 2
wareju said:
Disclaimer: I'm not an android dev but am interested in learning, really my only knowledge of dev'ing is the three hours or so I've spent so far failing at a port this morning. Don't be a douche, I just admitted my ignorance here.
If you don't know about PA (ParanoidAndroid) then go here and marvel > http://forum.xda-developers.com/showthread.php?t=1717079
It's been ported to the Atrix4G so I figured why not try dx2, and I'm using the A4G ROM in porting. I've been following the instructions here and keep getting hung up on rebuilding the modified framework-res.apk with apktool. The error I'm getting is in the attachments.
My process up to this point is:
- decompile framework-res.apk from PA and our CM9 rom.
- combine framework-res/res/values/ and framework-res/res/xml/ from CM9 to PA folder
- this is where rebuilding the apk fails...
Does anyone know anything about porting that can help? I feel like a lack of knowledge is my problem here.
Click to expand...
Click to collapse
Looks pretty straight forward if you are following the instructions here.
http://forum.xda-developers.com/showpost.php?p=27602914&postcount=24
Just be real careful with the merge and edits.
Just as a test, does your build work if you do not modify the original framework-res.apk from PA?
Yeah that's the guide I was using but kept getting hung up on rebuilding the modified framework-res.apk. Haven't tried without making any framework-res changes, I figured that was crucial.
Sent from DX2 CM9
always a good idea to test your build environment on a known good file set.
DigitalMD said:
always a good idea to test your build environment on a known good file set.
Click to expand...
Click to collapse
You're already talking over my head ha, but yeah I do plan to dive back into this soon. If nothing else to learn some of the more technical sides of android. Also going to be running Linux alongside windows soon, may just wait until I get that up and running.
Sent from DX2 CM9
wareju said:
Disclaimer: I'm not an android dev but am interested in learning, really my only knowledge of dev'ing is the three hours or so I've spent so far failing at a port this morning. Don't be a douche, I just admitted my ignorance here.
If you don't know about PA (ParanoidAndroid) then go here and marvel > http://forum.xda-developers.com/showthread.php?t=1717079
It's been ported to the Atrix4G so I figured why not try dx2, and I'm using the A4G ROM in porting. I've been following the instructions here and keep getting hung up on rebuilding the modified framework-res.apk with apktool. The error I'm getting is in the attachments.
My process up to this point is:
- decompile framework-res.apk from PA and our CM9 rom.
- combine framework-res/res/values/ and framework-res/res/xml/ from CM9 to PA folder
- this is where rebuilding the apk fails...
Does anyone know anything about porting that can help? I feel like a lack of knowledge is my problem here.
Click to expand...
Click to collapse
i'd try using the original framework first and then trying to flash it to the dx2 like that. If anything you'd have to update the updater-script and build.prop first before it worked, but it'd be worth a try at least. I haven't messed with the dx2 too much for a while now, but I know for porting ROMs to the samsung fascinate I have to do a bunch of edits & then I have to get data to properly work right (which I'm not sure how to do). So I'd keep trying and keep trying because that'd honestly bring another ROM to the dx2.
I may try and port a rom to the dx2 in the near future, but idk yet.
EDIT: if you need a tester also hit me up on here [pm] or twitter [@ztotherad], my dx2 doesnt have data atm, but i can turn it back on if i need that
also, i may try paranoidandroid port with you, if thats cool
Hey all.
Well first i'm gonna talk a bit about myself.
I have Huawei Ascend G300, and before that i had Huawei Ideos X3 (my first android). I've been playing with ROM's flashing since almost the beginning but now i'm trying to learn a bit more. What i'm trying to do is to port a Sense ROM to my G300. From HTC One V to be exact (http://forum.xda-developers.com/showthread.php?t=1943412). I don't have any kind of experience in developing, this is my first try, but i guess i would learn more porting Sense than any other normal port as it is much deeper than others. Don't give me answers like "you can't do it based on your experience" or "if you want Sense buy HTC". This is Chef Central so i'm expecting tips from experienced Dev's. And this little project is just to learn more about how android works. Finally, i would get a decent HTC if i had money for it.
So, the guid i'm following:
http://forum.xda-developers.com/showthread.php?t=1707177
If you have more detailed guides please send them to me.
What i've done so far. In CM9 (base) i've edited init.rc copying from Sense ROM and compiled the boot.img back. I've tacken the keys from CM9 to Sense ROM. Copied the files that the guide told me to. After this i recompiled the Sense ROM. Tried to flash and got problems with updater script. So i took the updater script and binary from CM9 to Sense ROM and tried again. It flashed this time but doesnt get past Splash Screen.
I've not made changes in framework.res and build.prop yet (it's my next task).
So how am i going? Am i on a good path?
Thanks!
I'm also working on a sense port. And your doing well so far, however, I would recommend editing the updater - script to match your mount points from stock script instead of copying the stock script over. There are some important processes that run that are sense specific. I've only made it to boot animation so far.
Sent from my SPH-L710 using xda app-developers app
Let me also join you
jagannn said:
Let me also join you
Click to expand...
Click to collapse
Have you already started porting? If so how far have you gotten? We haven't made it to the lock screen yet.
Sent from my SPH-L710 using xda app-developers app
I have the ZTE Avail 2 (aka Z992) (and it sucks, considering it's a $70 phone, buying a new one isn't an option because I just built a computer). It hasn't had an update since 4.1.1 and it's very slow, (usually have only ~50mb of ram free when just sitting at launcher) even with all of the tricks to speed it up (greenfiy, cleaner, etc) and on top of that, it's loaded with features that ZTE put in that suck. So after searching and searching for a custom ROM with support for my phone, I can confirm there is zero. I looked at the rom dev tutorial - http://forum.xda-developers.com/showthread.php?t=1272270 and the kitchen program doesn't support my phone either. Does that mean I'm screwed? If there's a way to make a rom compatible other than the android kitchen or straight up learning to program, please tell me. I'm willing to learn anything that isn't hugely time consuming. Thanks for any replies.
FourZer0 said:
Does that mean I'm screwed? If there's a way to make a rom compatible other than the android kitchen or straight up learning to program, please tell me. I'm willing to learn anything that isn't hugely time consuming. Thanks for any replies.
Click to expand...
Click to collapse
No, you are not. You can try many other porting tutorials around the web. I found a list of phones similar to yours, might come in handy.
In fact, since your are trying to "port" ROMs, just think about the fact that "where did those ROMs come from?" Those ROMs were built from source code. The Android project is open source and if you are feeling adventurous, you can just grab the source code and compile it yourself for your device. It might be very easy or very tough, depending on your device. I would advise you to try to build Cyanogenmod 10.1 from source code. Check here and here.
And make sure to check this (must).
Cheers man! Trust me, trying to build Cyanogenmod from source will be a lot of fun!
Thank you! So I found CM for the xperia tipo, which was on the list of similar devices. I should use that one and change whatever needs to be changed, right?
Also, is it possible to do that for 4.4 stock? That may be a better idea if CM consumes too much ram
tuxboy said:
No, you are not. You can try many other porting tutorials around the web. I found a list of phones similar to yours, might come in handy.
In fact, since your are trying to "port" ROMs, just think about the fact that "where did those ROMs come from?" Those ROMs were built from source code. The Android project is open source and if you are feeling adventurous, you can just grab the source code and compile it yourself for your device. It might be very easy or very tough, depending on your device. I would advise you to try to build Cyanogenmod 10.1 from source code. Check here and here.
And make sure to check this (must).
Cheers man! Trust me, trying to build Cyanogenmod from source will be a lot of fun!
Click to expand...
Click to collapse
Okay, ignore my last replies, I've been reading a lot and kind of know what I'm doing now.
Only problem is, I can't find a stock rom of my phone! The closest thing I found was a custom ROM for a phone similar to mine, which is confirmed working to the one I actually have. So would that do okay? androidforums . com/prelude-all-things-root/795640-azazel-rom-z993-aio.html is the one. Thanks again for any help.
FourZer0 said:
Okay, ignore my last replies, I've been reading a lot and kind of know what I'm doing now.
Only problem is, I can't find a stock rom of my phone! The closest thing I found was a custom ROM for a phone similar to mine, which is confirmed working to the one I actually have. So would that do okay? androidforums . com/prelude-all-things-root/795640-azazel-rom-z993-aio.html is the one. Thanks again for any help.
Click to expand...
Click to collapse
You can easily take a backup of your current ROM. Try booting into recovery and making your own custom recovery (ClockWordMod).
tuxboy said:
You can easily take a backup of your current ROM. Try booting into recovery and making your own custom recovery (ClockWordMod).
Click to expand...
Click to collapse
Oh, I didn't know that would work, thanks again! I have my rom modded like crazy though, tons of xposed modules and build.prop edits, also I uninstalled a lot of stock apps - I'm sure I could get the build.prop somewhere, but what about the other things? Do they matter at all?
Edit: after the backup I now have a ton of tars, a recovery.img, and a boot.img. I extracted all of the tars, now do I just put all of the folders from the tars in a folder with the imgs and that's my base rom?
tuxboy said:
You can easily take a backup of your current ROM. Try booting into recovery and making your own custom recovery (ClockWordMod).
Click to expand...
Click to collapse
Okay, I've come pretty far and I've made several flashable zips and fixed many errors, but there's one thing I can't figure out - the updater script doesn't work, and I realized it's because I was using the one from the original port, and I need the one for my phone, which I can't get from the cwm recovery. I really need the whole META-INF folder. Where can I get that?
I tried for 1 week and i didnt find any official and stable rom for my samsung galaxy note 4 Sm 910h. I used resurrection remix unofficial and camara didnt worked there . Please any solution there help me
Correct me if I'm wrong but I read the most important compatibility aspects for porting from one device to another are processor compatibility and screen resolution. The specs for the HTC One Mini are almost perfect. Exact same processor and the screen resolution is almost identitical. There's an officially supported cyanogen release for that device. It would seem to me we could compile that build, using JMZs custom kernel were all using for the 610, and pull the drivers from our device, and that might be enough to do it.
I'm assuming that would basically be the case for any ruu or Rom. Alternately we may just be able to pull the drivers from a 6!0 and JMZs kernel and compile a stock android that way.
I'm a Linux guy but this is my first foray into hacking android so any opinions/advice/criticism would be welcome.
I would've posted this in the developers thread but I don't have a high enough post count.
I'm reading everything I can find regarding porting different roms to new devices so any links you guys can point me to, I would appreciate.
I'm in school for CS and am very interested in porting new roms for the 610. HTC is emailing me the source today.
Lets quit messing around and start using this underrated device to its fullest potential!!
Scurvy
I have been working on porting cm11 and I think Its almost ready to boot but as for getting all the hardware working it may take a while. The desire816 seems to share some of the same hardware so I've started with its cm11 device specific code. I've built cm for my Asus tf101, tf300t and ainol novo fire but this is my first attempt at porting to a new device without someone else's base to work with so we'll see how I go. Best of luck to you and maybe we can share ideas as we move forward.
MiniBlu
Help
MiniBlu said:
I have been working on porting cm11 and I think Its almost ready to boot but as for getting all the hardware working it may take a while. The desire816 seems to share some of the same hardware so I've started with its cm11 device specific code. I've built cm for my Asus tf101, tf300t and ainol novo fire but this is my first attempt at porting to a new device without someone else's base to work with so we'll see how I go. Best of luck to you and maybe we can share ideas as we move forward.
MiniBlu
Click to expand...
Click to collapse
If you're already working on a port, perhaps we can work together? I've never ported code or a ROM to Android but I'm a linux guy and I've got some programming under my belt. I have quite a bit of experience building kernels for linux machines, namely debian.
If there's any way I can help you, I'd love to learn some stuff from you as well, let me know. If you need someone to test it out and do some bug hunting let me know through PM on here or by email at [email protected]
U still trying to port cm11 on the desire 610?
MiniBlu said:
I have been working on porting cm11 and I think Its almost ready to boot but as for getting all the hardware working it may take a while. The desire816 seems to share some of the same hardware so I've started with its cm11 device specific code. I've built cm for my Asus tf101, tf300t and ainol novo fire but this is my first attempt at porting to a new device without someone else's base to work with so we'll see how I go. Best of luck to you and maybe we can share ideas as we move forward.
MiniBlu
Click to expand...
Click to collapse
Hi!, I wanted to ask if your still working on porting cm11 rom on desire 610. I've gotten the htc desire 610 but found out no roms came out for it. I have been checking everyday now :/ but cant find any roms. Thanks.
Superspacex said:
Hi!, I wanted to ask if your still working on porting cm11 rom on desire 610. I've gotten the htc desire 610 but found out no roms came out for it. I have been checking everyday now :/ but cant find any roms. Thanks.
Click to expand...
Click to collapse
Yes I am still working on but have other priorities at the moment. It is currently geting stuck at the boot animation and I havn't had time to investigate why. Hopefully I,ll get it sorted over the christmas break.
MiniBlu
Boot animation
MiniBlu said:
Yes I am still working on but have other priorities at the moment. It is currently geting stuck at the boot animation and I havn't had time to investigate why. Hopefully I,ll get it sorted over the christmas break.
MiniBlu
Click to expand...
Click to collapse
Oh nice great to know you're still working on it and it took me a while to change boot animation on the desire 610 but got it working also it's not located in system/media folder I found the boot animation and stuff located in customization/recourses folder got my bootanimation zip sent it there and changed the name too att_bootup.zip since I got a AT&T version and it started working. Although you probably know that already. And thanks for replying and good luck!
Are you still work on desire 610？my device was desire 610t. I want to port the cm11 for my phone. but isn't bringup！
Sent from my HTC Desire 610 using XDA Free mobile app
---------- Post added at 02:30 AM ---------- Previous post was at 02:24 AM ----------
Are you still work on desire 610？my device was desire 610t. I want to port the cm11 for my phone. but isn't bringup！
Sent from my HTC Desire 610 using XDA Free mobile app
Sent from my HTC Desire 610 using XDA Free mobile app
zihan said:
Are you still work on desire 610？my device was desire 610t. I want to port the cm11 for my phone. but isn't bringup！
Sent from my HTC Desire 610 using XDA Free mobile app
---------- Post added at 02:30 AM ---------- Previous post was at 02:24 AM ----------
Are you still work on desire 610？my device was desire 610t. I want to port the cm11 for my phone. but isn't bringup！
Sent from my HTC Desire 610 using XDA Free mobile app
Sent from my HTC Desire 610 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know what you are trying to say? I am attempting to to create device specific files to be able to compile cm11 for international desire 610 from scratch. When I get it working I will put them on github and you could then download them and merge them with synced cm11 sources yourself.
MiniBlu
Boot Animation
Superspacex said:
Oh nice great to know you're still working on it and it took me a while to change boot animation on the desire 610 but got it working also it's not located in system/media folder I found the boot animation and stuff located in customization/recourses folder got my bootanimation zip sent it there and changed the name too att_bootup.zip since I got a AT&T version and it started working. Although you probably know that already. And thanks for replying and good luck!
Click to expand...
Click to collapse
A cm11 port sounds great but I have a question about the boot animation on the att version. I have replaced the att_bootup.zip file repeatedly and it does not seem to stick because it gets overwritten by the stock one repeatedly. I have made sure the boot animation is the correct size and even went so far as to edit the stock att_bootup.zip. My phone is unlocked, rooted, and has busybox. The animation seems to be overwritten when the phone is restarted.
Any ideas on what I am missing?
Thank you.
kingculex said:
A cm11 port sounds great but I have a question about the boot animation on the att version. I have replaced the att_bootup.zip file repeatedly and it does not seem to stick because it gets overwritten by the stock one repeatedly. I have made sure the boot animation is the correct size and even went so far as to edit the stock att_bootup.zip. My phone is unlocked, rooted, and has busybox. The animation seems to be overwritten when the phone is restarted.
Any ideas on what I am missing?
Thank you.
Click to expand...
Click to collapse
You will also need an insecure kernel. The stock kernel has write protection on the /system partition so any changes made disapear after reboot. You can either try the JMZ-kernel which has write protection removed or If you want to keep stock kernel you can make your changes while in TWRP, just use ADVANCED, FILE MANAGER to copy files to /system or make your changes via ADB while booted into TWRP(twrp boot.img doesn't have write protection on /system). You might have to fix permisions on your files to but TWRP also has a SHELL or FIX PERMITIONS options you can do that with.
MiniBlu
Jmz Kernel
kingculex said:
A cm11 port sounds great but I have a question about the boot animation on the att version. I have replaced the att_bootup.zip file repeatedly and it does not seem to stick because it gets overwritten by the stock one repeatedly. I have made sure the boot animation is the correct size and even went so far as to edit the stock att_bootup.zip. My phone is unlocked, rooted, and has busybox. The animation seems to be overwritten when the phone is restarted.
Any ideas on what I am missing?
Thank you.
Click to expand...
Click to collapse
Most likely you are missing jmz kernel. I had that missing and everytime I restarted nothing sticked so flash that and you should be good. You'll find the download on this forum. Let me know if you don't find it.
Superspacex
Thank you both. I was indeed missing the jmz kernel. I downloaded and flashed it. It changed the att boot animation to the stock text android but now replacing the att_bootup.zip does nothing. Putting a bootanimation.zip into data/local or system/media does nothing. I can not even locate the android boot animation to edit it. I have posted this issue in the jmz kernel thread.
Any thoughts?
THIS HAS BEEN FIXED. Thank you for pointing me in the direction of the jmz kernel. The file permissions were set wrong and not 644.
The boot file is /system/resource/customize caves m under the name (carrier)_bootup.zip
HTC Desire 610 - Root, stock ROM, r/w protection disabled
whats the status of this port? I just purchased this device naively from bestbuy to use as a platform which requires an AT&T LTE radio without checking CM11 availability... My bad... I'll port it... What needs to be done? Mucho Experience hacking HTC Device, Android, and Linux Kernel...
lets do this...
Progress
hey guys I was just wondering how far along the port was , I am also a programmer but I have zero experience in android development so I am eager to test it out though.
Any news about port??
Why don't you guys just compile one.
As you have said the One mini have the almost same specs (same cpu i presume)
Just take the device repo from Cm github and find some local_manifests in their xda forum and compile it
Use the custom kernel you got there too
Should work if the cpu variant is the same
I'm from HD2 forum compiling Android L for it. Booted
Can't wait
Sent from my HTC Desire 610 using XDA Free mobile app
aazzam16661 said:
Why don't you guys just compile one.
As you have said the One mini have the almost same specs (same cpu i presume)
Just take the device repo from Cm github and find some local_manifests in their xda forum and compile it
Use the custom kernel you got there too
Should work if the cpu variant is the same
I'm from HD2 forum compiling Android L for it. Booted
Click to expand...
Click to collapse
Sounds simple enough the way you said also sounds like you have experience doing the compilation maybe you could assist here and we do the testing. To be honest i been trying the virtualbox and ubuntu to start doing that stuff on my own but its just not working out
Shattariff said:
Sounds simple enough the way you said also sounds like you have experience doing the compilation maybe you could assist here and we do the testing. To be honest i been trying the virtualbox and ubuntu to start doing that stuff on my own but its just not working out
Click to expand...
Click to collapse
Sorry bro, can't help with that, but the concept is there now, no need for port
tip, use vmware
But, if One mini 2 is the same thing, just flash it on top
Rename the hw files ex. hwcomposer.msm8960.so to hwcomposer.your devices hw name.so