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

Root Development progress on Cyanogenmod7/9/10 Updated: 5/10

Ill be lending a helping hand soon enough :-P ... granting that I receive the donation phone

Manage to get it to boot pass the LG logo but the phone starting acting wonky and started becoming super hot. Updated build seems unstable as hell. When finally getting it boot pass LG animation the screen decided to go black on me on hearing a little sound in the background or must be me hearing things. Nice to hear another person will be helping out.

Note: Also kept rebooting itself after sitting on the black screen of death. This only happen when I started messing with the Boot.img that gave the device the ability to boot pass the LG logo. Maybe the boot.img that needs to be look at little bit more.
 
Cool, looks like things are starting to pull together. Seems like now everyone just needs to work together to get the phone to the people who can use it and the source codes, device trees and all.
Where's Giantpune when you need him...lol. Maybe Julian, Rukin, Jet, Downthemachine, and GP can all band together on this.
 
Cool, looks like things are starting to pull together. Seems like now everyone just needs to work together to get the phone to the people who can use it and the source codes, device trees and all.
Where's Giantpune when you need him...lol. Maybe Julian, Rukin, Jet, Downthemachine, and GP can all band together on this.

Almost had a heart attack once I saw the phone acting wonky due to this not being my phone.I pray for the little device everytime I install these experimental CM7-9 builds. lol "Back on topic". I need Giantpune to send me one of his boot.img from one of his working CM9 builds.
 
Cool, looks like things are starting to pull together. Seems like now everyone just needs to work together to get the phone to the people who can use it and the source codes, device trees and all.
Where's Giantpune when you need him...lol. Maybe Julian, Rukin, Jet, Downthemachine, and GP can all band together on this.

Don't forget Dm47021... he's WAAAYYY more experienced than me :-P
 
Well I can see why you have to replace the boot.img, you need a /root directory with the contents of your ramdisk, then define them as product files in the device.mk
 
The reason for building the boot.img separately is due to the build system being broken. If you do "make bootimage" it will build it correctly, and use all the addresses that you specify in your boardconfig.mk. If you do "make otapackage" the resulting boot.img contains the incorrect ramdisk address. It comes from one of the python tools in the build process simply not checking that parameter.

I worked around this locally by creating a copy of that python tool into my device tree and hardcoding the "force-ramdisk-address" or whatever name the argument had.
 
The reason for building the boot.img separately is due to the build system being broken. If you do "make bootimage" it will build it correctly, and use all the addresses that you specify in your boardconfig.mk. If you do "make otapackage" the resulting boot.img contains the incorrect ramdisk address. It comes from one of the python tools in the build process simply not checking that parameter.

I worked around this locally by creating a copy of that python tool into my device tree and hardcoding the "force-ramdisk-address" or whatever name the argument had.

Totally didn't understand any of that crap....Rock on! Keep up the good work:thumbup::thumbup:
 
The reason for building the boot.img separately is due to the build system being broken. If you do "make bootimage" it will build it correctly, and use all the addresses that you specify in your boardconfig.mk. If you do "make otapackage" the resulting boot.img contains the incorrect ramdisk address. It comes from one of the python tools in the build process simply not checking that parameter.

I worked around this locally by creating a copy of that python tool into my device tree and hardcoding the "force-ramdisk-address" or whatever name the argument had.

Thanks for the information about the boot.img situation.
 
Like?
20130119201909_zpse400fd2b.jpg
 
i stand corrected about the ramdisk, i was on the phone and missed some stuff. just cloned the repo :)
 
Hell yeah, I love seeing this much development progress on here for our phone. :] Keep it up guys. If you need any testing just pm me. I won't be wanting to do anything like that black screen hot battery build tho.. But if you get it to work and need someone to spot any problems with what works in CM7 or CM9 then I can do that.
 
same here, don't know how much I would be able to do by way of pulling logs, but I can probably give y'all enough information to know what's wrong.
 
Currently working on a new app for the Galaxy Note 10.1, so I may have to put the development on hold for a couple of days.I will still keep you all up-to-date on the thread about my progress on the build. The good thing we have at least is more devs slowly pitching in to get development moving again for this device.Also forgot to mention If any developers want to help create the app with me I'm happy to have you aboard or even test it for me. Still learning all the ropes of app developing. :D
 
Currently working on a new app for the Galaxy Note 10.1, so I may have to put the development on hold for a couple of days.I will still keep you all up-to-date on the thread about my progress on the build. The good thing we have at least is more devs slowly pitching in to get development moving again for this device.Also forgot to mention If any developers want to help create the app with me I'm happy to have you aboard or even test it for me. Still learning all the ropes of app developing. :D

Actually... app development is my strongpoint... I began just a few months ago and have created a few of my own apps... I think ill be able to pitch in a little
 
Back
Top Bottom