• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Building CM 10.1 (JB 4.22) from source for Motion

Lol.
When I factory wiped..
I lost my backups...
So I'm flashing everything all over again.
:rofl: :shot:
 
i still had bobz rom on my sd so i just flashed that then rebooted into bobz recovery and restored
but i keep my backups on my pc so i had to copy it via usb first
 
Y'all should check out orange backup on the market. Scheduled nandroids, made even while your phone is on, and can be backed up to dropbox. the backups can be restored with our 2nd init recovery.

I have a post about it on here
 
hi Bob

I mainly worked off of your jellybean branch, took some stuff from your cm10.1 branch, and then added a bunch of stuff

the media/video from Dm47021 was a big help, but introduced a camera issue, i think we need a camera hal

i may have went backwards on some of the stuff, one thing i can think of is the wrong apn file is in there now

i made some chages to the cm10.tar to get it to boot, but I do not think it has your fix that gets the phone starting again after first boot / reboot issue

I am gonna try and rework the 4.2 camerahal to work with my display-legacy
 
make clobber
source ./build/envsetup.sh && brunch l0


it should now build the ROM, when it is done it will be in cm10.1/out/target/product/l0 folder



when you put it like that it doesn't sound that difficult. just because i've never done it before doesn't mean i can't. i'm gonna try a build. after some more research and setting up my linux partition as an android build computer. thanks for the tutorial:)
 
when you put it like that it doesn't sound that difficult. just because i've never done it before doesn't mean i can't. i'm gonna try a build. after some more research and setting up my linux partition as an android build computer. thanks for the tutorial:)


that is what i like to hear
 
Haha yeah.
That's what I was gonna do :]
Do research again.
I just got done being able to dual boot my computer for it to run Linux and Windows 8
So now I can also help build.
I'm gonna learn and help any way I can.
And learn as I go ;)
 
Haha yeah.
That's what I was gonna do :]
Do research again.
I just got done being able to dual boot my computer for it to run Linux and Windows 8
So now I can also help build.
I'm gonna learn and help any way I can.
And learn as I go ;)

right now my pc quad boots win 7,kubuntu,fuduntu, and android x86 using burg to select. i did have 5 but win 8 sux. oh and i have persistent ubuntu secure remix on bootable sd
https://www.facebook.com/photo.php?v=4679918719091&l=1401767610995172280
 
Of course I'm in, although I will mostly likely not be around much the next few days as my wife is in the hospital (she has crohens). Will know more tomorrow after her GI and the surgern check in on her. But I'm sure I will be here in the wee hours tinkering instead of sleeping. lol

Good Job bro!!!

oh and you forget to link the frameworks edit for 2ndint reboot recovery. ;)

and a fyi
Code:
. build/envsetup.sh && brunch l0

will work too. . = source. ;)
 
I feel stupid for asking, but I'm kind of out of options, is there any other way to get into recovery on the motion? I flashed this rom, played around a little bit and everything was fine, I was surprised at how much worked, then I went to flash back and that's where things got ugly. I used adb reboot recovery, and instead of it booting to the custom recovery it booted the stock factory reset, no big deal, I let it finish then battery pulled, booted normally and hit the volume keys at the Lg logo, got into recovery but there was nothng there because it factory reset, no big deal, just adb push the zip,that didn't show up in the list as being on the sdcard either, so I gave up and used the debrick method to restore a kdz of version c that I had on my computer. It now boots to a looping metropcs animation, adb is not active in that mode or just charging (battery animation),or download mode, and I tried using volume down and power which flashes the LG logo a few times then sits at a black screen till I let go, then boots normally(looping), I tried volume down and power till it vibrates then tapping back and home a bunch like a YouTube video said to do, that just booted normally, and I tried restoring the kdz 3 times, no matter what I do its bootlooping because I didn't factory reset after i restored from a rom but I can't figure out how to get into recovery to do that.any other time this has never been an issue, the phone booted fine after kdz.
 
Of course I'm in, although I will mostly likely not be around much the next few days as my wife is in the hospital (she has crohens). Will know more tomorrow after her GI and the surgern check in on her. But I'm sure I will be here in the wee hours tinkering instead of sleeping. lol

Good Job bro!!!

oh and you forget to link the frameworks edit for 2ndint reboot recovery. ;)

and a fyi
Code:
. build/envsetup.sh && brunch l0
will work too. . = source. ;)

PG I am sorry to hear about you wifi, I hope you get good new about her tommorow

the framework edit for reboot recovery will need to be different on this rom, it can be done, but the power file is laid out a little different, and we will need to figure it oit

I will update the OP about the source, so I do not look like the Linux noob that I am
 
I feel stupid for asking, but I'm kind of out of options, is there any other way to get into recovery on the motion? I flashed this rom, played around a little bit and everything was fine, I was surprised at how much worked, then I went to flash back and that's where things got ugly. I used adb reboot recovery, and instead of it booting to the custom recovery it booted the stock factory reset, no big deal, I let it finish then battery pulled, booted normally and hit the volume keys at the Lg logo, got into recovery but there was nothng there because it factory reset, no big deal, just adb push the zip,that didn't show up in the list as being on the sdcard either, so I gave up and used the debrick method to restore a kdz of version c that I had on my computer. It now boots to a looping metropcs animation, adb is not active in that mode or just charging (battery animation),or download mode, and I tried using volume down and power which flashes the LG logo a few times then sits at a black screen till I let go, then boots normally(looping), I tried volume down and power till it vibrates then tapping back and home a bunch like a YouTube video said to do, that just booted normally, and I tried restoring the kdz 3 times, no matter what I do its bootlooping because I didn't factory reset after i restored from a rom but I can't figure out how to get into recovery to do that.any other time this has never been an issue, the phone booted fine after kdz.


at this point you would need to flash version D firmware or higher

you will then be be able to do the vol down + power button to get the factory reset option
 
Just wanted to give my thoughts on some of the stuff that needs to fixed.

When I was trying to get this thing to build and boot, I started to get frustrated and copied large amount of files to the prebuilt directory to try and make some progress, it was kind of lazy and sloppy of me to do it this way, but I am a lazy and sloppy person, and I got it to work eventually.

To get sound working properly, we may need to mod the audio-caf folder in CM and change some the source files or it may just be a config file in the etc folder

To get senors working, I think we need to put back the correct prebuilt files in the bin or lib folder, probably both, may need to look at the rc files in the cm10.tar too

I used the cm10.tar and the recovery tar from that cm10.1 ported alpha that I put out a while ago, I had to make changes to the init.target.rc to get it to boot because of a storage error with dalvic, the changes I made got it to boot, but there is an sdcard / storage issue with the changes I made, so that may be why things are not installing. We may also need to put back the old recovery tar file since some one was saying that there restore did not work

To get camera to work we either need to get a working camera hal or mod Dm47021's media / video drivers to work with the camera folder that Cyanogen provides

Since the actual RIL files from stock ROM seem to work somewhat with 4.22 we may need to revisit that to see if they work better that the P930 files

The framework edits from CM10.0 may not work, and we will need to find equivalents for the CM10.1 framework

We are still using a quite a bit of prebuilt files, the more that we can shift over to source the better, as long as they work as good or better than the prebuilts

The device tree is a little sloppy, especially the device.l0.mk, we should probably organize it a little better, it may make things easier to trouble shoot.

The cm10.tar is basically our ramdisk, I think there are some files in there that are not needed, and the files that are needed may have stuff in them that we do not need, and may be missing some stuff that we do need, or that would improve performance and such

I had to use the su binary and the liblog.so file from a prebuilt ROM, I am not sure why, but the ones that CM were building for me were not working

Anyway, that is all I can think for now, I got to go back to bed





hK
 
candoopa, this evening I will do my thing you know I do so well.... that sounded dirty lol.

also checkout my l0 repo, I have extract-files etc setup, not that those are actually needed atm, but yanno how ocd I am lol.

Have you investigated the audio to see if its the same as the higher end msm8960 LG's??

I built this last night and booted right up, so again good job bro, I just have to get the both booting on the spirit now. lol

I'll prolly be at the hospital most of the day, but will have my phone with me and my N7 is up there all ready.


But check the N4 and OG repo's out as well as patricks others, as I am sure you already have. lol

PG
 
When I was trying to get this thing to build and boot, I started to get frustrated and copied large amount of files to the prebuilt directory to try and make some progress, it was kind of lazy and sloppy of me to do it this way, but I am a lazy and sloppy person, and I got it to work eventually.
so if i'm correct, basically what your saying here is, we should make changes one or two at time so we don't have to guess what worked and what didn't and can debug one thing at a time, being more efficient in the long run. you guys are gonna teach me how to do this, you just don't know it yet :p
 
i like the way you think. your post are very informative and i can come here and learn little by little how to go about this. like the the old saying two heads are better than one. well 5 or 6 is even better. everybody has a different view on things or has seen or done different things so the more minds on this the better chance of perfecting it sooner. keep em coming.
 
i like the way you think. your post are very informative and i can come here and learn littile by little how to go about this. like the the old saying two heads are better than one. well 5 or 6 is even better. everybody has a different view on things or has seen or done different things so the more minds on this the better chance of perfecting it sooner. keep em coming.

Yea trust me when i say having mire pll on this is alot better than just one lol.

Now there always will be
 
as soon as i get woke up enough and get all the sleep crud out of my eyes i'm gonna start setting up my build environment. i'm on kubuntu 13.04 at the moment. any suggestion as to the best base for a build environment.

edit: i decided to switch to ubuntu because i was already running into unmet dependencies errors and all the tutorials i found were for ubuntu so i figure it would make things easier if i use the os that the tutorial was written for.

edit:downloading cm source. guess i better go find something else to do for awhile :)
god i hope my internet connection doesn't drop or something till this is done! :turtle:
 
@ Candoopa, If you want, you can use a prebuilt libsurfaceflinger.so from the cm10 rom. that will likely make camera easier to get working, as we are currently using a surfaceflinger_client stub
 
Back
Top Bottom