Develop Bugs

Porting IHO to other carriers? Check in here.

This is meant to be a dev thread, not an end-user thread. Please keep this on-topic. End-user support and VM670 development are off-topic.
For the more user and Optimus V (VM670) oriented thread please check in here:
http://forum.xda-developers.com/showthread.php?t=1176888
If you are working on porting the phone to the VS660, LW690, US670, or MS690 with the eventual goal of inclusion in the IHO repository please check in here.

I'm trying port this for the ms690. I'll admit it's a bit over my head but I have a rooted and flashed M and a rooted but stock M at my disposal and a working android development environment.
My rom is compiling now after fixing the typo in the mms_config.xml. I would like to help get the proper changes in the IHO repo if I get this working, but I have absolutely no idea how all that works.
I'll update here if I get my rom compiled and let ya know how it runs. Anyone know how long it should take to completely compile a rom error free? I'm running 2 dual core xeons at 2ghz... This is a long compile for a >100MB file, heh.

Has anyone successfully ported using Ubuntu 11.xx on a 32 bit, vmware setup? I got it to work with wubi, but that messed up my windows. Can you run Ubuntu off of a thumb drive but use your hard drive for storage?
Sent from my LG-VM670 using XDA App

1. I thought you couldn't successfully compile on 32 bit since 2.2
2. Setting up a development environment in vm? or on a flash drive? Do you really deserve that kind of punishment?
I guess you could build on a persistent usb but but it sounds scary to me. I don't know if you could properly mount a drive in live usb, seems like you would need your build folder on a hdd or a 32gig flash.
Backup your stuff and throw on an ext partition. Your building will be easier in a native environment and a clean windows install never hurts.

My compile is stopped. I've been poking around and I don't think I'm gonna figure this out like all the other BS I've figured out.
GRRR this is ****ing stupid, tried to post my error but the forum thinks that xxx.xml is a web address and wont let me post cuz I don't have enough posts. If anyone can help me shoot me a PM I'm not gonna spam the forums to get my posts to post a ****ing error log. If I ever met a spammer I would kick him in the nuts for all the bull**** I have to deal with because of the crap...

pbailey212 said:
Has anyone successfully ported using Ubuntu 11.xx on a 32 bit, vmware setup? I got it to work with wubi, but that messed up my windows. Can you run Ubuntu off of a thumb drive but use your hard drive for storage?
Sent from my LG-VM670 using XDA App
Click to expand...
Click to collapse
I use a 32-bit version of whatever the LTS version is with VirtualBox. 10.04?
Sent from my LG-VM670 using XDA App

blarfiejandro said:
I use a 32-bit version of whatever the LTS version is with VirtualBox. 10.04?
Sent from my LG-VM670 using XDA App
Click to expand...
Click to collapse
I was thinking about downgrading Ubuntu and trying it, I'm on Ubuntu 11.xx now. I would like to keep the vmware setup, I like just minimizing vmware to go back and forth to windows. Plus everything's transferable between the 2 os'
Sent from my LG-VM670 using XDA App
Update: Its creating the zip file now, I just needed to up the ram available to vmware, I wish I would have tried that a week ago, thanks for hearing me ***** and moan about this

pbailey212 said:
I was thinking about downgrading Ubuntu and trying it, I'm on Ubuntu 11.xx now. I would like to keep the vmware setup, I like just minimizing vmware to go back and forth to windows. Plus everything's transferable between the 2 os'
Sent from my LG-VM670 using XDA App
Update: Its creating the zip file now, I just needed to up the ram available to vmware, I wish I would have tried that a week ago, thanks for hearing me ***** and moan about this
Click to expand...
Click to collapse
I had problems setting up a good build environment with 11.04, but 10.10 64 bit with VMware works great for me on Windows 7 64 bit.
EDIT: I forgot to mention that if anyone want to try my Optiums Cricket version they can grab it here: http://www.mediafire.com/?vcfc5jtwncsxkzg
I don't own a OC, I built it for a friend. He tells me that GPS, BT, and MMS are not working.

So I got my very own zip file, backed, wiped flashed, my phone told me It was "bad" so I went and restored my backup it said bad md5, I thaught no big deal, I keep a couple backups handy, all 3 of them said bad md5. I restored them before just fine, I don't know what's going on, I should just give up, but I'm stupid and enjoy a challenge. I guess I will start completely fresh again. "Goin back to compile"
Sent from my LG-VM670 using XDA App

somedood81 said:
I'm trying port this for the ms690. I'll admit it's a bit over my head but I have a rooted and flashed M and a rooted but stock M at my disposal and a working android development environment.
My rom is compiling now after fixing the typo in the mms_config.xml. I would like to help get the proper changes in the IHO repo if I get this working, but I have absolutely no idea how all that works.
I'll update here if I get my rom compiled and let ya know how it runs. Anyone know how long it should take to completely compile a rom error free? I'm running 2 dual core xeons at 2ghz... This is a long compile for a >100MB file, heh.
Click to expand...
Click to collapse
It'll probably take a couple of hours to compile. The easiest way to get everything included is to file a pull request on Github. Keep in mind I'm not going to accept any applications (so that rules out the real popular MMS patches floating around for the C and M). Most of the stuff for the M is already in the tree, I believe...
Some of the other stuff like cnd probably won't get fixed /just/ yet, but I'll rename the keymap file. What else did you have to change?
pbailey212 said:
So I got my very own zip file, backed, wiped flashed, my phone told me It was "bad" so I went and restored my backup it said bad md5, I thaught no big deal, I keep a couple backups handy, all 3 of them said bad md5. I restored them before just fine, I don't know what's going on, I should just give up, but I'm stupid and enjoy a challenge. I guess I will start completely fresh again. "Goin back to compile"
Sent from my LG-VM670 using XDA App
Click to expand...
Click to collapse
Someone mentioned that IHO wasn't computing checksums properly in the general dev thread. Try using another recovery and/or making sure your build box isn't on its way out?
Anyhow I'm using a 32-bit Ubuntu 10.04.3 VM to build everything and it works just fine for me (definitely need to throw some more RAM at the machine tho).

blarfiejandro said:
It'll probably take a couple of hours to compile. The easiest way to get everything included is to file a pull request on Github. Keep in mind I'm not going to accept any applications (so that rules out the real popular MMS patches floating around for the C and M). Most of the stuff for the M is already in the tree, I believe...
Some of the other stuff like cnd probably won't get fixed /just/ yet, but I'll rename the keymap file. What else did you have to change?
Click to expand...
Click to collapse
I had to fix a typo on a tag in the mms_config.xml, I think using the cnd from the V was a no no, so i commented out the cnd in the build. There was an extra space in a string in an xml file I can't remember that needed removed. Other than that I just put in the ko files and the gps libs and it was building fine.
I fixed the last error I had which was about 2.5 hours into the build and started the compile over... Then my workstation shut down. It refuses to even post. Tried a new video card to no avail. Dual xeon running rambus ram, LOL. Don't have any parts laying around for it other than drives and video cards.
My port is kind of stalled at the moment, heh.

Just thinking out loud:
Has anyone done a build for the MS690(Metro version)?
Is the "LG Optimus One, P500, > Optimus V Android Development" thread for all Optimus phones? Or just the V?

I was working on the ms690 b4 my linux box died. There are a couple of us working on it.

somedood81 said:
I was working on the ms690 b4 my linux box died. There are a couple of us working on it.
Click to expand...
Click to collapse
Do you have a CWM recovery?
What wasn't working on your ROM?
My first attempt gave me this: make: *** [out/target/common/obj/APPS/Mms_intermediates/src/R.stamp] Error 1

BobZhome said:
Do you have a CWM recovery?
What wasn't working on your ROM?
My first attempt gave me this: make: *** [out/target/common/obj/APPS/Mms_intermediates/src/R.stamp] Error 1
Click to expand...
Click to collapse
That was the last error I was working with actually. Don't know if I had it fixed.
The op m can't use CWM recovery. We have 2 custom ones, joneidys recovery and getitnowmarketing recovery.

somedood81 said:
That was the last error I was working with actually. Don't know if I had it fixed.
The op m can't use CWM recovery. We have 2 custom ones, joneidys recovery and getitnowmarketing recovery.
Click to expand...
Click to collapse
Can't use CWM? All other Optimus phone do!
Sent from my VM670 using Tapatalk

I don't know the details of why, here is a thread on it:
http://androidforums.com/optimus-m-all-things-root/352401-do-not-use-clockwork-mod-rom-manager.html
It would be cool if someone could figure out the problem and fix it...

BobZhome said:
Do you have a CWM recovery?
What wasn't working on your ROM?
My first attempt gave me this: make: *** [out/target/common/obj/APPS/Mms_intermediates/src/R.stamp] Error 1
Click to expand...
Click to collapse
Sounds like you need to have the proper MMS overlays in the device folder. Maybe.

blarfiejandro said:
Sounds like you need to have the proper MMS overlays in the device folder. Maybe.
Click to expand...
Click to collapse
The overlay/MS690/packages/apps/Mms/res/xml/mms_config.xml has a bad string.
Profile<string/> needs to be changed to Profile</string>
I posted a comment on your git.
I compile my 0.1 kernel and trying an other MS690 build.

Blarf, can you look at these two pastebin to see if you see anything wrong.
There are problems with my LW690 builds, wifi produces an error and camera is broken.
wifi - http://pastebin.com/hMmhH9Bk
camera - http://pastebin.com/ukSGQaWz
Bluetooth wasn't working and when I used the MS BT file it worked, do you think by using the MS BT in the LW is giving me the wifi problem?
Thanks for the help,
Bob

[Q]Heimdall Support?

Basically, does Heimdall support this phone? I have a Mac/Ubuntu, and dislike having to use someone else's computer to flash stuff that isn't flashable with cwm.
Sent from my Herculean Juggernaut.

Not yet, but I asked in another thread (an OS X thread asking the same thing) for someone to post a USB log of ODIN attaching to the device. Actually, a full log of it attaching and also updating would be useful but probably large. Since log data like that is plain-text and very repetitive, it would probably compress well.
Also, I've opened an issue at the Heimdall github (issue #29). I can't post a URL because my XDA account is too new, but I've poked around in the code and it should be straighforward to implement (Benjamin did a pretty good job making it readable).
I'm going to try to do that implementation once I have the data.

Thanks for replying.
Sent from my HëЯ¢ú1ëλN júGGëЯNλú＋!

Here is something that would be really awesome
http://forum.xda-developers.com/showthread.php?t=1347899
Sent from my SGH-T989 using Tapatalk

GBGamer said:
Thanks for replying.
Click to expand...
Click to collapse
No worries! Actually, I completely feel your pain; I run Ubuntu on my desktop and laptop at home, on my workstation at work, and my work laptop is a Mac. The biggest reason I'm asking for USB logs is that I just can't stand going through the motions to set up Windows & ODIN myself
Perhaps a bit lazy and loser-y, I suppose, but I'll redeem myself if I get Heimdall working, for sure.

billydroid said:
Here is something that would be really awesome
http://forum.xda-developers.com/showthread.php?t=1347899
Click to expand...
Click to collapse
Definitely!! But we still need ODIN/Heimdall for CWM recovery in a softbrick situation, right? If we just want to root, I think there are a couple one-clicks reported to work... but for ROM development you definitely want an easy recovery mode, just in case.

droidjaggers said:
Definitely!! But we still need ODIN/Heimdall for CWM recovery in a softbrick situation, right? If we just want to root, I think there are a couple one-clicks reported to work... but for ROM development you definitely want an easy recovery mode, just in case.
Click to expand...
Click to collapse
Right we do. But that mobile Odin is simply awesome.
Sent from my SGH-T989 using Tapatalk

Major thread necro here, but... I actually have news!
Heimdall works on SGH-T989 now. One caveat... it's not the 1.4RC1 that Benjamin is releasing soon, rather, it is a fork. Unfortunately, the first of two contributors who built the required functionality chose to rename almost all the variables and functions, making it a serious pain in the ass to merge the changes back to the mainline Heimdall source tree.
This is the currently working tree: git://github.com/jamiejackson/Heimdall.git
Check it: http://mulad6.blogspot.com/2012/09/getting-heimdall-to-work-with-sgh-t989.html
I just built it and used it to install CWM Recovery on two T989's, and it worked like a champ on the first try, both devices (no "keep trying it because ODIN sometimes screws up"). \m/

Clockworkmod for Ion

Anyone tried building a clockworkmod image from builder.clockworkmod.com? If we can get a good image maybe we can mod the rootingkit to flash that image instead of the Xperia S one. I am going to try in a day or two, but this will be my first time trying.

Just a follow up on this: I think I finally found the right way to build this, but I am afraid it will take more than a few attempts to get it right. I did find the dev/block locations to pull. I just have to get everything finalized on my new Ubuntu partition so I can do this properly. (Man, a lot more work then what I thought it would be)

popfan said:
Just a follow up on this: I think I finally found the right way to build this, but I am afraid it will take more than a few attempts to get it right. I did find the dev/block locations to pull. I just have to get everything finalized on my new Ubuntu partition so I can do this properly. (Man, a lot more work then what I thought it would be)
Click to expand...
Click to collapse
I'm willing to test for you. when you are ready, just message me.
That goes for ALL devs for this phone... I am NOT afraid to test, so hit me up. Email and personal number via PM if you prefer faster more reliable communication.

Pl. Look into this.
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Sent from my LT28h using xda premium

ganeshbiyer said:
Pl. Look into this.
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Sent from my LT28h using xda premium
Click to expand...
Click to collapse
I was using that, but the problem is that is not updated for the newer stuff. I am using http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-os-x-part2/ as a guide which has more compressive information about how to build it.

Ok, I was able to find what I think was the kernal but the recovery sector is messed up a little I think, due to having a bad recovery sector. Looks like I am going to have to root without the Clockworkmod recovery built into it, so I can extract the recovery sector correctly.

Well, I think I might be able to fix the Xperia S one as I could not figure out how to extract the right folders and stuff. I was looking at the recovery.fstab and it has the wrong mounts for us. So I think that if I fix them then we can have a usable recovery.

popfan said:
Well, I think I might be able to fix the Xperia S one as I could not figure out how to extract the right folders and stuff. I was looking at the recovery.fstab and it has the wrong mounts for us. So I think that if I fix them then we can have a usable recovery.
Click to expand...
Click to collapse
Doesn't look like it worked.

Help, Flashing Image from Ubuntu to Stock!

Noob here... I just installed Ubuntu to see what all the hype is all about. I had no problems flashing, however I found it toooo laggy and unstable and I decided to go back to stock. There is one problem, i forgot to back up google factory images. I need to put the images in the root to flash, but i have no way putting them on because my Mac computer doesn't recognize my Ubuntu Nexus. Any Ideas guy, need some big help

Well yet another one of these. There's this thing called Google. I don't know if you ever heard of it. Ask there and you might get an answer. Google also has a friend called YouTube if reading seems to hard for you.
Sent from my Galaxy Nexus using xda premium

I can't find anything in my situation.. Why comment, if your not going to help in the first place.

you dont put images in root to flash...
use fastboot
calling yourself a noob doesnt absolve you from doing some basic research and reading.

Pirateghost said:
you dont put images in root to flash...
use fastboot
calling yourself a noob doesnt absolve you from doing some basic research and reading.
Click to expand...
Click to collapse
I guess I'm not explaining it right. I no longer have the Factory Image on my phone, I'm currently running on Ubuntu. My PC nor Mac could recognize the device, so fastboot wont work. I am looking for way to flash the image, that doesn't involve me downloading Ubuntu OS on my PC.

you dont understand.
YOU DO NOT PUT .IMG FILES DIRECTLY ON THE DEVICE
you flash them in FASTBOOT mode, which has NOTHING to do with UBUNTU
pretend you flashed a broken rom. GO BACK TO STOCK, none of this actually has anything to do with ubuntu

Man so hard the longest minute of my life. But finally found it. https://www.youtube.com/watch?v=QZcSC_MHkl0&feature=youtube_gdata_player
Sent from my Galaxy Nexus using xda premium

Esteway.619 said:
Man so hard the longest minute of my life. But finally found it. https://www.youtube.com/watch?v=QZcSC_MHkl0&feature=youtube_gdata_player
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
watch out, that spoon might come back tarnished....

Pirateghost said:
watch out, that spoon might come back tarnished....
Click to expand...
Click to collapse
Haha I know right.
Sent from my Galaxy Nexus using xda premium

Esteway.619 said:
Haha I know right.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
he should still be able to get into the bootloader manually...

Not only do Ubuntu have a guide on how to get back to Android but there is a nice thread in General which is called (funnily enough) 'How to get back to stock' - read that
What this clearly highlights is the fact you didn't read the official flashing guidelines as provided by Ubuntu

Question "Rooted" now what?

Oneplus finally came through with my bootloader unlocking token.Not to mention all the hoops T-Mobile had me jump through.With that being said im in possession of my very first fully rooted phone that just happens to be a 9 Pro.Any suggestions on which modules I can command Majisk to install first?How bout any general pointers thus being this is my first experience free and in full control of my 9pro.?

Here's some ideas:
What Magisk modules are you using?
Hey all moving up from my OP 7 pro to the OP 9 pro. What are all the magisk modules everyone is using on the OP 9 pro.? 1.Anything to force full screen mode on all apps? The settings for full screen apps dont include all the apps im using as...
forum.xda-developers.com

Shanemichealrowland said:
Oneplus finally came through with my bootloader unlocking token.Not to mention all the hoops T-Mobile had me jump through.With that being said im in possession of my very first fully rooted phone that just happens to be a 9 Pro.Any suggestions on which modules I can command Majisk to install first?How bout any general pointers thus being this is my first experience free and in full control of my 9pro.?
Click to expand...
Click to collapse
To be honest, I would hold off until we have a working TWRP build, especially if this is your first experience of root, etc

djsubterrain said:
To be honest, I would hold off until we have a working TWRP build, especially if this is your first experience of root, etc
Click to expand...
Click to collapse
I was thinking the same thing .I just thought maybe there are some safer mods I should do in the meantime.

@Shanemichealrowland
I've been rooting Android for many years now. I always read read and read some more before I begin to install anything and I always wait until there is a working custom recovery and make a FULL backup of every partition and transfer it to a USB drive and or my computer first thing. Make sure to backup your efs as well so that if you lose your IMEI at some point it too can them be reflashed using fastboot. These are things I've always done and will continue to always do. Many users get excited and rush out to install things and don't read enough about their device and end up with an expensive piece of plastic and glass. If you always wait and read everything and make sure you fully understand how your device works before you install things then you will always have a great experience and never have to go through the bad feeling of ruining your expensive device. I read everything in a forum about my device first. You can't go wrong doing things that way. I hope this helps. OnePlus makes great devices! I'm using my OnePlus 6t now to type this and I still love it!! Welcome to XDA my friend.
Edit added: I see you're from Houston. Me too.

flash713 said:
@Shanemichealrowland
I've been rooting Android for many years now. I always read read and read some more before I begin to install anything and I always wait until there is a working custom recovery and make a FULL backup of every partition and transfer it to a USB drive and or my computer first thing. Make sure to backup your efs as well so that if you lose your IMEI at some point it too can them be reflashed using fastboot. These are things I've always done and will continue to always do. Many users get excited and rush out to install things and don't read enough about their device and end up with an expensive piece of plastic and glass. If you always wait and read everything and make sure you fully understand how your device works before you install things then you will always have a great experience and never have to go through the bad feeling of ruining your expensive device. I read everything in a forum about my device first. You can't go wrong doing things that way. I hope this helps. OnePlus makes great devices! I'm using my OnePlus 6t now to type this and I still love it!! Welcome to XDA my friend.
Edit added: I see you're from Houston. Me too.
Click to expand...
Click to collapse
Wow,your so right. Ive already caught and stopped myself from installing a couple things I wasnt sure about.I think im gonna slow down a bit and keep learning.Thanks for bringing me back to whats should be going on.

Shanemichealrowland said:
I was thinking the same thing .I just thought maybe there are some safer mods I should do in the meantime.
Click to expand...
Click to collapse
There are Magisk modules but if you get into trouble you need to be able to access recovery, OnePlus's default recovery isn't quite as all encompassing as TWRP

djsubterrain said:
There are Magisk modules but if you get into trouble you need to be able to access recovery, OnePlus's default recovery isn't quite as all encompassing as TWRP
Click to expand...
Click to collapse
Afaik you can delete problematic magisk modules in safemode. Plus I havent used TWRP pretty much for anything with OnePlus 8 pro and after. That just helps me understand better how things work. Plus because I use Linux msm is useless to me but thats another topic
Edit: Dont get me wrong, not trying to convince people to mod/flash anything. Just pointing out that TWRP is not necessity.

pyry666 said:
Plus because I use Linux msm is useless to me but thats another topic
Click to expand...
Click to collapse
Could you clarify this? What procedure do you follow in the event of a brick? I use Linux exclusively and would prefer to be able to recover from a brick using Linux instead of relying on MSM, but I'm not clear on all the steps MSM does or where/how I would find the specifics needed to do the same thing myself.

terlynn4 said:
Could you clarify this? What procedure do you follow in the event of a brick? I use Linux exclusively and would prefer to be able to recover from a brick using Linux instead of relying on MSM, but I'm not clear on all the steps MSM does or where/how I would find the specifics needed to do the same thing myself.
Click to expand...
Click to collapse
Ive only done that once myself and that was with 6T. But basicly you need to flash every partition etc via terminal

pyry666 said:
Ive only done that once myself and that was with 6T. But basicly you need to flash every partition etc via terminal
Click to expand...
Click to collapse
Ok, I've flashed all partitions before, but I thought there was more to MSM's steps than that. E.g. fixing the partitions themselves, or some sort of voodoo required to recover from any sort of soft brick.

terlynn4 said:
Ok, I've flashed all partitions before, but I thought there was more to MSM's steps than that. E.g. fixing the partitions themselves, or some sort of voodoo required to recover from any sort of soft brick.
Click to expand...
Click to collapse
AfaIk there is not that much. It locks bootloader though and IF something goes wrong that could cause issues. One of the reasons ive never used it.
Edit: Ill correct myself. MSM uses EDL mode. And if device is borked that badly then only it works. And imo should be used only then
Edit2: One could try using virtual machine to use MSM with Linux but I have zero knowledge how that would play out

pyry666 said:
AfaIk there is not that much. It locks bootloader though and IF something goes wrong that could cause issues. One of the reasons ive never used it.
Edit: Ill correct myself. MSM uses EDL mode. And if device is borked that badly then only it works. And imo should be used only then
Edit2: One could try using virtual machine to use MSM with Linux but I have zero knowledge how that would play out
Click to expand...
Click to collapse
Right, I've been in situations with my last phone where EDL was my only option and I had to use MSM. I have dual boot on a laptop for those occasional Windows-only things like MSM. In the past I've found the USB passthrough to be unreliable for this purpose using a VM in virtualbox, though I haven't tried in a few years so it may have improved.