Database Info

MIUI for XT720 released!!!!

There is MIUI for XT 720 is released!!! (sorry i'm Korean, so I'm poor at English)
Down load link is here
w1ww.megaupload.com/?d=3QI0U5I0 (Erase 1!!!!!!!)
or
w1ww.mediafire.com/?1ak7sdhs8q667oh
How to installation??
1. copy these files (first unzip!!)
2. Install UK 2.1 ROM (Use RSD)
UK2.1 ROM link (Erase 1!!!!!!!!!!)
w1ww.megaupload.com/?d=WJ4JZUKE
or
w1ww.mediafire.com/?ik579jqkvbtt1tj
3. Root the phone (Use Super One Click)
4. Install System Recovery by using OpenRecovery.apk
5. Run System Recovery
6. Choose Install recovery ( Superuser permission allow)
7. Choose Reboot Recovery
8. In Nandroid - Restore, Choose Miui for XT720, Restore All
*CAUTION*
Some problems was revealed (SD card, Wi-Fi, Usim, Senser, Language ...etc)
This Rom was very very very unstable. so usually fail to boot.
When this situation...solution is.... try,try,try and....try untill success
I'm not Rom developer!!!
This Rom was based on Dexter's Froyo

Why for 2.1 when we already have so much custom 2.2 ROMS?

Vistaus said:
Why for 2.1 when we already have so much custom 2.2 ROMS?
Click to expand...
Click to collapse
This Rom is based on Dexter's Rom! so, install UK 2.1 Rom first..

can i know the source of this MIUI...i mean the developer?

@gera_nium,
I'm just as curious as you are. I googled xt720 miui, and stumbled across this...
"http://www.miui.com/thread-16979-1-1.html"
According to Google translate 2.2 is out...but I'm not fluent in chinese so I can't navigate the website to find the stupid rom...
Anyone fluent in chinese please help. Maybe you'll have better luck.
Thank you,
lilhugo

lilhugo said:
@gera_nium,
I'm just as curious as you are. I googled xt720 miui, and stumbled across this...
"http://www.miui.com/thread-16979-1-1.html"
According to Google translate 2.2 is out...but I'm not fluent in chinese so I can't navigate the website to find the stupid rom...
Anyone fluent in chinese please help. Maybe you'll have better luck.
Thank you,
lilhugo
Click to expand...
Click to collapse
It is not related. Just a post requesting for miui rom based on kr xt720 rom. U can see the date of the post is dec 2010 when motoroi upgraded to 2.2
Sent from my HTC Incredible S using XDA Premium App

lyfkevin said:
It is not related. Just a post requesting for miui rom based on kr xt720 rom. U can see the date of the post is dec 2010 when motoroi upgraded to 2.2
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
miui for xt720 download:http://u.115.com/file/f28c30b22c#
Do not wipe to restore access to the system after.
Can not scan sdcard
Sometimes stay in the first screen. must restart button battery
Media Library can not be used.And can not get online, but can connect wifi

So is this rom usable? Has anyone tried it. Has anyone tried fixing the problems?

Yeah, I'd love to see a usuable MIUI for XT720 if anyone could do it.

Doesnt boot for me no mater what i try

Dang bummer. Ill give it a shot anyway. Hopefully khall or one of the other guys can fix this for us.

easye420 said:
Dang bummer. Ill give it a shot anyway. Hopefully khall or one of the other guys can fix this for us.
Click to expand...
Click to collapse
Meh just looks like IOS what else is there?

Eh its somethin different I'm gettin bored with stock I've got about every laucher made to switch it up and miui has some pretty kool features I really like status bar and widget feature. I wish someone would come out with cm7 for this bad boy. I wish I had a lil more time and knowledge. Isant miui mostly framework changes and launcher changes or is it more than that? What if we took the framework and launcher from this and put it into one of dexters newer builds?

Got the phone working but the browsers crash too much it looks like it would be alright if the bugs got fixed I will try working on again later.
Sent from my XT720 using XDA Premium App

Everything works great for me when I installed it, only question I have is there an English version to this rom ?

I tried it. Got it to work for me to. I changed the language to english but only half is in english. It connects to 3g for me but won't download anything from the market and when I rebooted it wouldn't boot again. Ima try dling the english translation pack and see what happpens

hellmonger said:
Meh just looks like IOS what else is there?
Click to expand...
Click to collapse
Has some pretty cool default apps, cool lockscreen, custom transitions through anything, lots of custom themes you can just put on, other tweaks and is supposed to be really fast from what I can understand. It's also a different experience. The launcher and IOS icons is the least attractive thing to me.

The CM7 on MOTO XT720

I heard that this forum is a master transplant CM7 ROM, I would like to ask about the current progress
What is difficult to solve the problem?
Can provide the current ROM, I would like to try
Want to provide,
Thank you

I want to start by saying THANK YOU FOR MIUI!!!! You are awesome. And they have got cm7 booting up on xt720 but only if you flash motoroi 2.2.1. But the touch screen is not working. If I were you I'd get with Mioze7Ae. He's the Guy to talk to about it. There is a thread with the ROM download in it in the general thread.

oyang06 said:
I heard that this forum is a master transplant CM7 ROM, I would like to ask about the current progress
What is difficult to solve the problem?
Can provide the current ROM, I would like to try
Want to provide,
Thank you
Click to expand...
Click to collapse
stlifey made a port of CM7 to XT701. That is here:
http://forum.xda-developers.com/showthread.php?t=1064090
If download links are dead there, let me know and I can mirror/reupload.
I think this is the main development page for the XT701 CM7, but the forum seems to be down for maintenance right now:
http://bbs.gfan.com/android-1297281-1-1.html
It doesn't work on XT720 yet. This is where things stand:
Using Milestone XT720 2.1 sbf
If you use a Milestone XT720 sbf, then it doesn't boot. I've been modifying it and have gotten it to go further with adb logcat working to get some messages out. This is the latest version I've been testing that makes it the furthest before rebooting:
http://www.multiupload.com/ULWN2ERP02
The radio panics and panic_daemon shuts down the phone. If you modify the init scripts, you can disable panic_daemon. Then it will boot to the point that zygote tries to start but has a library link problems so I've changed too many libraries .
From Korean Motoroi XT720 2.2 sbf
sktjdgns1189 figured out that if you flash the Korean Motoroi 2.2 sbf, root, install OpenRecovery, and apply the XT701 update without any modifications it boots up, but the digitizer doesn't work. You can do some things like long press the camera button to get the camera to come up and you can take pictures. See
http://forum.xda-developers.com/showthread.php?t=1118236
Eventually it will crash and reboot. The bad news is that for some reason after you flash the the Motoroi sbf on Milestone XT720, you can't use volume-up to enter OpenRecovery. So you have to use adb ("reboot openrecovery") to get back into OpenRecovery. But I haven't been able to get adb to startup. So that means you're back to sbf for the next try. I can't figure out why the touch screen doesn't work.
sktjdgns1189 has also figured out how to get the battery notification working:
http://forum.xda-developers.com/showthread.php?t=1124927
Edit: Forgot to mention that we're now pretty sure that sktjdgns1189 has a Motoroi XT720 based on his photos. I've reproduced most of his results on a Milestone XT720.

easye420 said:
I want to start by saying THANK YOU FOR MIUI!!!! You are awesome.
Click to expand...
Click to collapse
+1. Very fantastic work on MIUI. Great to see you looking into CM7 as well.

its going to be on android 2.3 right?

eejin2 said:
its going to be on android 2.3 right?
Click to expand...
Click to collapse
If someone gets CM7 working then yes that is Android 2.3

Thank you Oyang06 for Miui rom and I wait CM7
Sent from my XT720 using XDA Premium App

Looks like stlifey plans to release CM 7.1 for XT701 this weekend.
Off topic: Does anyone know what all the "ah"s that Google Translate adds means? I think wiktionary suggests "啊" == surprised+"!"? Also, does anyone know a good place to look up those four-character idioms? There's one about hunters that comes up a lot. Just curious.

lols. ah is like "oh". for idioms maybe you can copy to google then add "english meaning"

khankuan said:
lols. ah is like "oh". for idioms maybe you can copy to google then add "english meaning"
Click to expand...
Click to collapse
I see! The google translated posts just seem a little strange because I guess "ah" and "oh" would come at the front of the expression in English. It can seem like reading threads where everyone is talking about Candlejack and then sudde

Haha, just post here if you need any translations awaiting patiently for CM7 Gingerbread XDXD

i can help a little with the translations too, haha. SOOOOO EXCITED FOR GINGERBREAD. i like the stock look of cm7 and of course the turning off crt animation of 2.3. CANT WAIT!
do you think we can get 2.3 miui running on our phone?

eejin2 said:
i can help a little with the translations too, haha. SOOOOO EXCITED FOR GINGERBREAD. i like the stock look of cm7 and of course the turning off crt animation of 2.3. CANT WAIT!
Click to expand...
Click to collapse
Yeah, gingerbread is much more attractive than 2.2 and below all around. Plus it's supposed to be faster (and CM is supposed to be even faster) and have other goodies... would be so fantastic to see this for the XT720.

if you want to use adb
just use 2nd-init (default.prop : ro.secure=0, ro.debuggable=1, persist.service.adb.enable=1, persist.factory.allow_adb=1)
(and some code in init.mapphone_umts.rc (it for adb on bootup))
then you can use logcat/dmesg and etc even on bootup

wait and sad

CM7 would be a dream come true.
Best of luck guys, I will be watching

Wish I would know how to contribute to this happening... would make me feel better knowing I was making some progress. Well, hope this goal is attainable.

Dexter_nlb said:
Cyanogen from Milestone could easily be ported, like i did htc sense like on milstone... the issue is requirements and added extra button and fm radio.
but the rest would work from a milestone release.. fairly easy to do.
Click to expand...
Click to collapse
I don't wanna sound arrogant and I really appreciate what you guys are doing, but am I missing something?

My take on that is their talking about milestone not milestone xt720.
Sent from my XT720 using XDA Premium App

mchlbenner said:
My take on that is their talking about milestone not milestone xt720.
Sent from my XT720 using XDA Premium App
Click to expand...
Click to collapse
No, Dexter posted that in his XT720 thread. I saw that the other day and was considering mentioning it, but I'm sure Mio and others are doing everything already.
Here's the post Dexter is responding to:
"From my understanding of the situation, Cyanogen is out of the question, for now. Dexter's roms are modifications of the official MOTOROI XT720 2.2 (KR) for our handsets. Due to the bootloader lock placed on the phone by Motorola, we can't compile our own systems based on the android sources.
Anybody correct me if I'm wrong with my situation assessment. "
Click to expand...
Click to collapse
Though if Dexter feels it's so simple I wish he would elaborate for the benefit of our devs, just in case he knows something they don't.

|ROM||AOSP||JB||4.2.1||Perfect Android 2.1

Perfect Android is a redistribution of the Android Open Source Project and Google software code that I have lightly modified to make as a daily driver for myself that I'm sharing with the community. This project doesn't have and won't focus on adding a ton of features and mods but instead focus on stability, and reliability so yes basically this is a stock like rom but not just stock my only efforts will be to make it run better, and be more polished, and complete.
GOOGLE APPS ARE INCLUDED
DOWNLOAD:
https://hotfile.com/dl/181925379/d84644d/perfect_grouper_ota_2012-12-01.zip.html
Mirrors:
If you have an error or something pops up I ask that before you post about it please make sure that you are running the ROM as provided. I cannot troubleshoot anything that is related to using other kernels, mods, or themes.
This ROM is basically like a stock rom of jelly bean so there is not a need for screen shots ........
Always remember that XDA started out as a great place and will remain a great place as long as we are great to each other anything used in this ROM is available upon request and feel free to use this as a base rom for any other project my ROM is un-branded just give me some mention .......
WANT TO CUSTOMIZE THIS ROM READ THIS:
Like the ROM and want to add or remove anything or customize for yourself use this http://forum.xda-developers.com/showthread.php?t=633246 DSIXDA's Kitchen. Its a great kitchen for customizing prebuilt ROMs
CREDITS:
CyanogenMod Team
Google - I used their apps
AOSP - of course

Probably gonna add a changelog here

AOSP 4.2 ROM so quickly? That will be interesting

Can you have some screenshots?

yep its uploaded

it looks just like stock I built it to be at least as good as what you get from google if everything is working correctly that is when I will begin modifying but for now it looks like the stock ROM so I didn't think screenshots would be needed

first of all you have to give us changelog, then i'll flash it, because now i don't know exactly what are the differences between Your rom and stock, so is it worth flash it?

Patroy said:
first of all you have to give us changelog, then i'll flash it, because now i don't know exactly what are the differences between Your rom and stock, so is it worth flash it?
Click to expand...
Click to collapse
Its solely up to you guys if you want to flash it as this is an expensive hobby for me I'm just sharing what I do with the community so is it worth it, for me yeah, for you I really don't care, I hope I'm not coming off as an ass but I have to draw a line somewhere. I not making any claims with this ROM I just sharing it if you use it fine if not fine, I don't get into the whole screenshots large claims huge changelog thing I just post and share I also maintain this ROM for the Sprint Galaxy Nexus which it has done just fine so if you want you can do a search here and see what and where I come from .......

I'm very happy when see any new rom in N7 development, because nexus need fresh look from developers, so i was thinking that You could push some new tweaks into ours devices. Almost all roms here are just "cleaned" or "minimalistic" or "performanced" in real these rom are almost stock with the same user experience. So do not get angry when I want to know if there will be something more here...

Does it work with twrp?
After flash with twrp, I see the information is Android 4.2 JOP40C. I dont know whether it is flashed or not?

I will happily try your rom to see how it compares to CleanRom, give my feedback tomorrow

Patroy said:
I'm very happy when see any new rom in N7 development, because nexus need fresh look from developers, so i was thinking that You could push some new tweaks into ours devices. Almost all roms here are just "cleaned" or "minimalistic" or "performanced" in real these rom are almost stock with the same user experience. So do not get angry when I want to know if there will be something more here...
Click to expand...
Click to collapse
I'm not getting angry with you in fact I agree however, regardless of how you feel about those roms someone still put that effort into them. Honestly for me the N7 is a new device and before I go making claims that my ROM can start your car and end world hunger I want to make sure that it at least meets stock standards. AOSP has done a lot of work to somewhat remove google entries in their code so it has taken me a few days to re-build AOSP code to work correctly with G-APPS and other Google code I do NOT claim to be an over the top developer I just do this as a pastime I have certain things that I do not like and thats why I have started making my own ROMs so that I always get what I want. Now I can tell you this and I know this as a fact THIS IS NOT A WINZIP KITCHEN ROM IT IS BUILT FROM SOURCE it took hella work to get it up to a win zip ROM and thats where we're at so far lol. When I learn all the changes to the 4.2 coding I will start to add small feature to my ROM.

SuperBoUDS said:
Does it work with twrp?
After flash with twrp, I see the information is Android 4.2 JOP40C. I dont know whether it is flashed or not?
Click to expand...
Click to collapse
yes it works with TWRP and the information in the About screen is correct

There isn't developer section in setting menu. Is this normal?

SuperBoUDS said:
There isn't developer section in setting menu. Is this normal?
Click to expand...
Click to collapse
Tap on the build in settings>about phone 7 times and it appears.
Paul
Sent from my Nexus 7 using xda app-developers app

PAULO76 said:
Tap on the build in settings>about phone 7 times and it appears.
Paul
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you! I dont know this.
This ROM doesn't include busybox. I think jakdillard should install busybox by default .
Testing this ROM with LeanKernel.

SuperBoUDS said:
Thank you! I dont know this.
This ROM doesn't include busybox. I think jakdillard should install busybox by default .
Testing this ROM with LeanKernel.
Click to expand...
Click to collapse
lol who knows I might depends on how things go with this

Installed thid yesterday and so far no problems, nice deep sleep of 96%. Nice work

With leanKernel, I just have 86% batterry overnight :crying:. I charged it fully the night before.

SuperBoUDS said:
With leanKernel, I just have 86% batterry overnight :crying:. I charged it fully the night before.
Click to expand...
Click to collapse
haven't checked for myself but is leankernel updated for 4.2

Why an official CM 10 is not possible for Atrix 2?

This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.

androiddecoded said:
This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
Click to expand...
Click to collapse
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.

Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..

alteredlikeness said:
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
Click to expand...
Click to collapse
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL

jimbridgman said:
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
Click to expand...
Click to collapse
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..

alteredlikeness said:
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
Click to expand...
Click to collapse
so do I.... Don't forget who is on the cm coding team....
I did some looking internally at CM and found that these are semi-official, right now, with a big but, the kexec I am told is what is keeping it with the semi status...
They are looking into changing that for kexec based compiles, so.... Hopefully, that happens.

jimbridgman said:
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Click to expand...
Click to collapse
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?

androiddecoded said:
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
Click to expand...
Click to collapse
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.

jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
I don't want to be the antagonist here , but I did everything in Windows until I started my attempts at building from source.
Dsixda's kitchen works fine in Windows with Cygwin. I started off building pseudo-ROMs (or rebuilding the stock ROMs) with the kitchen, and then I eventually just used 7-zip and other tools and did it manually.
I currently use Ubuntu 12.04 64-bit in Virtual Box in Windows on my laptop to compile from source. But I did just install 12.10 fully on my old PC... 32-bit unfortunately.. I need to upgrade that comp, or find a work-around to build in 32-bit.. Anyhow, it runs much nicer than windows xp did.
Sent from my paranoid phone's mind

jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:

androiddecoded said:
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
Click to expand...
Click to collapse
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.

jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
Thanks sir. Got that
Will try to contribute something if I can. Kudos to our dev team. You guys are doing a great job. Happy to be a part of a great community

jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?

androiddecoded said:
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
Click to expand...
Click to collapse
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.

jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
I will do it tomorrow. Really thank you for assisting me.

jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference

androiddecoded said:
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
Click to expand...
Click to collapse
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.

jimbridgman said:
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
Click to expand...
Click to collapse
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?

4.1 leak is not a flashable zip.
The meta-inf folder items are for zips that are flashed in recovery.
And, not to dissuade you from jumping in to modding/dev'ing, but you may want to take things a bit slower... Start small.. And read/research a lot.
Sent from my paranoid phone's mind

androiddecoded said:
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
Click to expand...
Click to collapse
No, there is not a flashable "zip" for the Moto 4.1 leak, you will have to build that on your own with the Rom kitchen, since it is an FXZ, it will not have those flashable parts. The kitchen is very easy to use, it is menu driven and only takes about 30 min to an hour to do what it seems you want to do.
You can replace the launcher from within a flashable zip, but you might have issues, because the MOTO blur junk that is in their ROMS DEPENDS on it, if you do NOT leave it (moto blur launcher) in /system, then a number of things will not work that depend on the moto launcher (they are embedded in the xml files in the apks, and need to be edited to NOT look for the moto laucher), I think it is more trouble than it is worth, personally.
I would throw Apex in there if that is what you want, and then on first boot select it as your default launcher and be done with it, less issues and mess, other than the old moto launcher taking space in /system. BY the way ANYTHING that you put in /system is not really 100% upgrade-able by the market app, so like lets say you put apex in /system, then the market can not update the version in /system, since it is read only, and it will either fail the update, or try to put the newer updated files /data, so you will have things in two places for your 3rd party launcher. It is MUCH better to put any APKS that would come from the market into /data so they can get updates with out any odd issues, just a heads up...
--EDIT--
As alteredlikeness said about the same time I was posting, start a little smaller, and do a bunch of learning, because from what I see you asking about and posting in here, you have a good bit of learning to do, about how the directory structure and things are and work in android, as well as some ROM building basics.

[DEV]- Pantech Vega N6 A860 - CM10 Porting

This thread is going to be WIP thread for the porting of CM10 to the Pantech Vega N6 A860 codename e51.
Currently kernels are extracted and device tree wip while I collect the files to be input
https://github.com/VincentEmmanuel/android_kernel_pantech_e51k.git
I welcome anyone who is interested to help out in any way because I am really new in this porting stuff.
WIll update as and when more work is done.
Things working on now
1. Trying to find a suitable msm8960 common files repo (Not sure whether needed this at all but conducting R&D now)
2. Compiling a list of proprietary files needed for the build
God bless.
Vincent

ClockworkMod
ClockworkMod for A860 K/L/S
Flash using fastboot. Instructions are all over XDA so please search.
Thanks

thanks so much for your work...
another than CM10.1 , I also want to see customized kernel which can further enhance A860 , like power tweaks, disable logging, init.d or even add FauxAudio mod

Finally something about te Vega No6
I have the A860K. I installed a customized ROM from here http://mizal.net:82/pantech/NO.6/
Works fine, but it is not very customized. Still would like to get rid of Korean characters.Another kernel. deodexed. Less bloatware, etc.
Any other customizations?
Cheers!
---------- Post added at 11:58 AM ---------- Previous post was at 11:20 AM ----------
Leechoonhwee said:
This thread is going to be WIP thread for the porting of CM10 to the Pantech Vega N6 A860 codename e51.
Currently kernels are extracted and device tree wip while I collect the files to be input
https://github.com/VincentEmmanuel/android_kernel_pantech_e51k.git
I welcome anyone who is interested to help out in any way because I am really new in this porting stuff.
WIll update as and when more work is done.
Things working on now
1. Trying to find a suitable msm8960 common files repo (Not sure whether needed this at all but conducting R&D now)
2. Compiling a list of proprietary files needed for the build
God bless.
Vincent
Click to expand...
Click to collapse
I would not mind helping, but I am even newer than yourself
I am not a programmer, but I know very good shell scripting, PHP, and not so good C and some other useless languages.
I have pro skills in Linux as well (I work with it)
Let me know if I could be of any help.
Cheers and good luck!

magare said:
I have the A860K. I installed a customized ROM from here http://mizal.net:82/pantech/NO.6/
Works fine, but it is not very customized. Still would like to get rid of Korean characters.Another kernel. deodexed. Less bloatware, etc.
Any other customizations?
Cheers!
---------- Post added at 11:58 AM ---------- Previous post was at 11:20 AM ----------
I would not mind helping, but I am even newer than yourself
I am not a programmer, but I know very good shell scripting, PHP, and not so good C and some other useless languages.
I have pro skills in Linux as well (I work with it)
Let me know if I could be of any help.
Cheers and good luck!
Click to expand...
Click to collapse
Anyone can help in anyway they can! Please take a look at the following page about CM porting.
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
Currently, I am trying to find a similiar device in terms of hardware and use their kernel github and try to build a test build
Device Tree
https://github.com/CyanogenMod/android_device_sony_yuga
Kernel
https://github.com/CyanogenMod/android_kernel_sony_apq8064
Let me know. Thanks!!!!

Sorry. Got busy at work and don't have time now.

Interesting
Sent from my IM-A860S using xda app-developers app

I found a gitub source for this device github.com/mifl/android_kernel_pantech_im-860s, but i have no time to verify yet
i would like to help since i just got mine today, but i only do android programming and driver compiling, and i never successfully make a kernel that can boot my galaxy s2 and some chinese tabs

Hi Vincent,
I just bought a A860S and want to back up boot/system/recovery partitions, probably all partitions, except the data one.
Do you know anyway to open those official update .binx file?
Thanks.

aget1 said:
I found a gitub source for this device github.com/mifl/android_kernel_pantech_im-860s, but i have no time to verify yet
i would like to help since i just got mine today, but i only do android programming and driver compiling, and i never successfully make a kernel that can boot my galaxy s2 and some chinese tabs
Click to expand...
Click to collapse
I think this is the stock kernel. I think we need to grab a working kernel from Xperia Z or Oppo Find 5 since we are on the same architecture.

totalz said:
Hi Vincent,
I just bought a A860S and want to back up boot/system/recovery partitions, probably all partitions, except the data one.
Do you know anyway to open those official update .binx file?
Thanks.
Click to expand...
Click to collapse
I remembered coming across a CWM mod that can allow you to choose which to backup. You can try ROM Toolbox.

Leechoonhwee said:
I think this is the stock kernel. I think we need to grab a working kernel from Xperia Z or Oppo Find 5 since we are on the same architecture.
Click to expand...
Click to collapse
As long as it boots, and it is a 3.4.0 kernel, i think it will work with cm10
anyway i am checking out cyanogenmod, but i dont find the a860 cwm recovery_ui.cpp source, only binary... i guess i need time to find the button mapping?

You could get answers from SDA.
Sent from my KM-S220 using xda app-developers app

There is a working CWM around in the 91dongji forum - works fine on my A860S with 1.30 software; now updating to 1.36 and see if the recovery sticks.
I'll post detailed instructions here once it is confirmed to work

i hope we can get some update on your efforts. though the crowd for this specific device is fewer than a handful for now, a lot of users are just waiting anxiously for any development....

Is there hope for this device to receive custom ROM?

there's a very active community in vegaviet coming up with mods and roms based on stock.you may want to check them out.

tommyrumbler said:
there's a very active community in vegaviet coming up with mods and roms based on stock.you may want to check them out.
Click to expand...
Click to collapse
I tried flashing the roms from the Vegaviet but i had a problem getting my network to connect. after the restore was complete there was no apn settings for the network. I tried reading but the translations from the website but it dont make sense and no one noticed issue because they are not located in korea.

clockedtouch said:
I tried flashing the roms from the Vegaviet but i had a problem getting my network to connect. after the restore was complete there was no apn settings for the network. I tried reading but the translations from the website but it dont make sense and no one noticed issue because they are not located in korea.
Click to expand...
Click to collapse
so why not set up your APN? that should be easy.
Also, using the ROM from vegaviet, i noticed the following observation :
-there was a considerable build-up of lag after three to four days of use, especially when doing a lot of web browsing
-the browser is unable to open some websites/webpages due to Ad-Block restriction
-the forced DNS settings most times slow-down my internet connection
-the keyboard still retains Korean functionality, with Korean characters sometimes getting in the way when typing
-kernel logging was enabled
much of the above were solved using the uninstall zip of crossbreeder - i just noticed our Vietnamese friends are fond of using cross-breeder on all their ROM mods.
the keyboard i uninstalled and deleted the IME file in system and just replaced it using Optimus G Pro's keyboard IME installer.
everything should be all good. don't ask me where i got those zips - a simple search should do wonders for you.

The rom doesn't allow for setting up your own APN. Those features are not available in JB. Thanks for the tips but I just went back to stock since I wasn't able to get the network going.
Sent from the brightest star in the sky using xda app-developers app