Original APP folder from most current leak::
App Folder
Original Framework folder from most current leak::
Framework Folder
Tiny's One_V Port so far:
(Boots to the Bootanimation.)
tiny4579 said:
Here is my logcat, maybe someone can figure it out. I'm taking a break for now:
logcat.txt
My current ROM is below.
sense-ics-inc.zip
Click to expand...
Click to collapse
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTCCN_CHS_1.68.1400.2_Radio_20 .67.30.0831U_3831.15.00.28_M_release_254948_signed .exe
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
HTC_One_V_Ramdisk:
V_Ramdisk Download
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
PureMotive said:
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
Click to expand...
Click to collapse
I thought of that too. But since the DInc is a 'QSD' (1000Mhz Qualcomm Snapdragon) and the Desire HD and the Desire S are 'MSM' (Mobile Station) We can't use their ports to help us :/
Being that the DInc is a qsd8k (8650 to be exact) we'll need to keep an eye out for ports with the same processor.. Oh man I wish the old Desire could get a port of this, lol. We'd have no problem at all..
Tribulattifather said:
Saw nobody was getting this started.
I am currently working on it a bit but I defenitley need help compiling a kernel.
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTC_Europe_1.56.401.1_Radio_20.66.30.0831U_3831
(For the newbies)
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
Kernel Source:
HTC Sensation XE (HTC Europe) - ICS CRC - 3.0.16 kernel source code
Look at the 9th one in the list
I hope that we can get this working for our DInc's.
Click to expand...
Click to collapse
kernel source wont help you at all for the 3.xx kernel from other htc phones, so dont bother
i ported sense 4 to the inc 2 (admittedly a lot easier cuz its msm7x30 which most of the ports are) and will give it a shot on my og inc time permitting
see inc2 port here: http://forum.xda-developers.com/showthread.php?t=1553357
the hacked .35 kernels from your ics aosp roms *should* be good (only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
When you say
nitsuj17 said:
(only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
Click to expand...
Click to collapse
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Tribulattifather said:
When you say
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Click to expand...
Click to collapse
no, you need the zimage from one of the ics aosp inc roms and the extracted ramdisk from the htc one v
Okay. Thank you for clarifying for me.
I'm getting down to business now ^>^
PonsAsinorem said:
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
Click to expand...
Click to collapse
can u tell the link to wildstang83 porting guide thread?
orochi9999 said:
can u tell the link to wildstang83 porting guide thread?
Click to expand...
Click to collapse
★wildstang83's Guide For Basic Porting★
PonsAsinorem said:
★wildstang83's Guide For Basic Porting★
Click to expand...
Click to collapse
thank u!
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
2012oasis said:
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
Click to expand...
Click to collapse
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Tribulattifather said:
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Click to expand...
Click to collapse
can you get a logcat or pm me a ROM link? I'd like to look. No guarantees of success. Sadly the sense devs that could figure it out I think have left the incredible.
Also a working ramdisk still doesn't mean the kernel is good. The kernel may need some changes.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Tribulattifather said:
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Click to expand...
Click to collapse
I'd like to try tonight if I can. I'm hoping that an HWA enabled AOSP ICS kernel works with it.
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Ahh! Excited..
Sent from my HTC Droid Incredible using Tapatalk 2 Beta-5
Tribulattifather said:
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Click to expand...
Click to collapse
I'm actually stabbing in the dark as much as you. Never messed much with roms. I'm more of a troubleshooter rather than a rom/kernel chef. I find tweaks and adapt for my kernels. But I noticed there's no init.inc.rc in that ramdisk. Other than that my mind's dead so I'll have to look tomorrow/this weekend.
I apologize for the delay in posting the port link. You'll have to forgive my internet. But, I assure you that the download is as fast as I can get it with my own server that I use.
EDIT: Port is on the next page --->
Just to make sure that everyone is on the same page - This port is NOT a working port.
It will flash to the DInc and it will install properly but it does not boot. And it is obvious why, lol, because we are still missing the piece to the puzzle to make a working kernel.
I hope that this will give you what you need to get this project I started the thrust in the right direction.
As for my method thus far, I am using the zImage from and AOSP ICS port with Ramdisk parts from the One_V.
Post Script - Today is my third year anniversary being apart of XDA. And I can only hope many more years to come.
CHEERS ALL!
Related
Hey the update.zip for nexus's one update is out
here is the link android.clients.google.com/packages/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
and here the prerooted from modaco romraid.com/paul/nexusone/update-nexusone-FRF50-signed.zip
i've started porting. help devs .
Does anyone know how to not flash the new radio cause when i remove the radio.img it always says line 70 installation abonded cause it couldn't find radio.img. any help ? don't worry figured it out
Yeah. I want froyo.
Ohh.. is that real to made 2.2 on Tattoo??
-------------------------------------
Sent via the XDA Tapatalk App
I'm waiting for 2.2 on tattoo.
Developers pls help the Tattoo user.
Thanks in advance.
I'm sorry to say it, but you'll have the same problems as with the 2.1 porting...: the drivers for the camera, sensors, FM radio, etc....
don't tell me xD and what do you believe about the new kernel ? anyway i can always try . and if i don't do it i'm loser .
rwmanos said:
don't tell me xD and what do you believe about the new kernel ? anyway i can always try . and if i don't do it i'm loser .
Click to expand...
Click to collapse
you are brave!
i hope you will be a winner
Guys, I'm confident that we can at least look at the source of 1.6 Tattoo regarding the camera and port it to the new Kernel...I won't stop researching until a decent ROM is created by all of us!
First I will download the source code of the tattoo ROM, then I will build a VM featuring Ubuntu and get all necessary dev-tools to decently start programming that son of a b****!
TheSSJ said:
Guys, I'm confident that we can at least look at the source of 1.6 Tattoo regarding the camera and port it to the new Kernel...I won't stop researching until a decent ROM is created by all of us!
First I will download the source code of the tattoo ROM, then I will build a VM featuring Ubuntu and get all necessary dev-tools to decently start programming that son of a b****!
Click to expand...
Click to collapse
yeahhhh
TheSSJ said:
Guys, I'm confident that we can at least look at the source of 1.6 Tattoo regarding the camera and port it to the new Kernel...I won't stop researching until a decent ROM is created by all of us!
First I will download the source code of the tattoo ROM, then I will build a VM featuring Ubuntu and get all necessary dev-tools to decently start programming that son of a b****!
Click to expand...
Click to collapse
I belive in you!...You can do it!
If there is source code for HTC's 1.6 camera drivers, then it should be easy to port those drivers for 2.1 or 2.2, even if the Android has changed. It's more easy than reverse engineering binary drivers, no?
We just don't have a man who can (or want) to do it.
I have a problem...I wanted to unpack the boot.img file, but unfortunately the structure of this update.zip seems to differ a lot from the normal update packages...this one seems to patch most files, which unfortunately means that there's no way to start this thing up on our Tattoo's, or am I wrong?
TheSSJ said:
I have a problem...I wanted to unpack the boot.img file, but unfortunately the structure of this update.zip seems to differ a lot from the normal update packages...this one seems to patch most files, which unfortunately means that there's no way to start this thing up on our Tattoo's, or am I wrong?
Click to expand...
Click to collapse
If you flash the original Nexus One 2.1 rom, and the nexus one recovery image, then you should be able to flash this...
Yeah, but I don't think the Nexus One recovery image will work on my phone...this smells like bricking the phone hard
use the modaco one. but i can't find a way to not flash the radio.img . i remove it from update-script but the i can't get rid off the syntax error can't figure out why.
I hope you ALL will be winner
rwmanos said:
use the modaco one. but i can't find a way to not flash the radio.img . i remove it from update-script but the i can't get rid off the syntax error can't figure out why.
Click to expand...
Click to collapse
I know this sounds stupid, but did u resign the zip file after deleting radio.img or did u just deleted the img file from the zip and update-script? I'll resign it and then check - anything else I have to pay attention to? I saw again a patchfile for the recovery image, I hope it does not brick my good Amon_RA one...
/Edit: doesn't the update-script normally need an update-binary?
TheSSJ said:
/Edit: doesn't the update-script normally need an update-binary?
Click to expand...
Click to collapse
Not if uses the recovery images built-in syntax...
kiljacken said:
Not if uses the recovery images built-in syntax...
Click to expand...
Click to collapse
thanks for the info...will try to flash the update package when my tattoo is charged..
yeah i did resign . i don't think it's a radio idea to flash it with the radio.img but you know if you just delete resign and flash it won't work cause it is going to look for the file and poof installation aborted . i think i figured out the syntax error .I'll flash when is my tattoo is charged too always out of battery
The blog where i found everything
This server was not really that private ... http://cafe.naver.com/develoid.cafe?iframe_url=/ArticleRead.nhn?articleid=24692&
http://dogsolefoot.iptime.org/D.Kim Kor/frame.htm?action=SkinFile#/Atrix/
On this site there is roms that have not been posted on xda.
After going to the website, click the rom folder, and there they are.
If you go to the fifth folder from the bottom, then go to the secret folder, there are files that seem to be ICS ports.
Tell me what you think!
The Site seems to be down...
http://dogsolefoot.iptime.org/D.Kim Kor/frame.htm?action=SkinFile#/
Mirror of Roms:
*If you have any please post ill give credit
http://www.multiupload.com/IE98U6DSI9 - TurTleRom beta5
Very cool! Folks, if you're thinking of flashing this, you may want to consider reviewing the contents of the .zip before flashing, removing anything like recovery.img that could lock you out of the Rom Manager or RomRacer CWM you're familiar with.
If you have no idea what I'm talking about, wait for someone else to come around and take a look first.
Happy Hacking and don't brick yourself!
----
While I was writing this, I see the trolls have descended upon the thread. If you're not technical enough to rip it apart and flash it, don't post.
It's a developer forum folks, nobody cares if you're anxiously awaiting everyone else to take the first try, we only care if you did and your results...
Damn, im so tempted..
I will review the contents of the zip, and report back.. Although I don't technically know what Im looking for besides a recovery image.
currently downloading some of those and taking a look inside them, everyone please go about this careful!
You're so freaking awesome man, here you come to the rescue again
checked out the one tittled ics_port_olympus_singed_test.zip, currently in the process of flashing it, will let you guys know whats up! the size seems legit
I would have to reluctantly check out mentally from my family for the night if this is true
ROM > TurtleRom > TurTleRom beta5.zip is ro.modversion=CyanogenMod-7-12112011-NIGHTLY-Olympus Didn't bother looking further as this looks boring
MIUI > alpha2-miui-Snya.zip is CM7 based too, but looks like it's default locale is in korean. Definitely has MIUI apks, rooted with Dolphin Browser HD too and Titanium Backup.
samcripp said:
checked out the one tittled ics_port_olympus_singed_test.zip, currently in the process of flashing it, will let you guys know whats up! the size seems legit
Click to expand...
Click to collapse
What directory did you find that in Sam?
_Alex_ said:
What directory did you find that in Sam?
Click to expand...
Click to collapse
It's in the op
Sent from my MB860 using XDA App
Yeah, that one's in 디프/secret.
_Alex_ http://dogsolefoot.iptime.org/Atrix/ROM/디프/secret/ics_port_olympus_test_signed.zip
but the file has installations issues, it aborts, let me fix that shiot and give it a second try!
Just found a kernel in there too called the jaryo 1.45 kernel it booted up fine but when i checked my about phone settings it clearly shows its actually fauxs kernel so nothing new there either.
my Koreans a bit rusty but this hopefully will turn out good.
Lots of it is just mirrors to other roms and something about a trackball
sent from my Atrix via XDA premium
the are several ics ports in there!
just waiting to see if it is safe!
marko! said:
my Koreans a bit rusty but this hopefully will turn out good.
Lots of it is just mirrors to other roms and something about a trackball
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
Yeah im bettin this is all the same ole **** with just different names. that ics port is probably just evogp's rom!
No, it's clearly not; the build.prop file, for example, is totally inconsistent with a CM7 build.prop, and quite consistent with the build.prop files of other ICS beta ROMs that have been appearing.
begadkepat said:
No, it's clearly not; the build.prop file, for example, is totally inconsistent with a CM7 build.prop, and quite consistent with the build.prop files of other ICS beta ROMs that have been appearing.
Click to expand...
Click to collapse
Looks asop to me. Launcher2 is included some other stuff. The updater script is messy
Only one apn included and odexed
sent from my Atrix via XDA premium
I found this site the other day it supposedly has an miui ics rom and is also in korean. http://m.cafe.naver.com/ArticleList...arch.menuid=78&search.boardtype=L&usenotice=N only thing is i believe youve got to register to dl
so has anyone tried ics yet?
There is a mod for the EVO 4G called Slide 2 Wake, it seems pretty awesome. I was wondering can we have kernel with Slide 2 Wake support on SXL?
http://forum.xda-developers.com/showthread.php?t=1346760
I found another one sweep2wake http://forum.xda-developers.com/showthread.php?t=1256668
Its on one x as well in bricked kernel. Its a battery hog but nice feature
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Sweep to wake works on my ordinary Sensation. It's controlled from the Tweaks app but not sure if the kernels are similar in the two phones. Probably not lol.
it will be cool if somebody implement this
shingers5 said:
Its on one x as well in bricked kernel
Click to expand...
Click to collapse
i sow it on different devices, not only One X
cool feature...anyone can write and ask in the original thread what function must be activated...maybe there is a github kernel patch (would be the easiest way)
with kind regards
Nice.. Hoping to see it on my SXL ...
Any Dev Can have a breif look in this...
as i understand it is in sweep2wake.sh script inside of kernel
-=AsteriX=- said:
as i understand it is in sweep2wake.sh script inside of kernel
Click to expand...
Click to collapse
it should be no problem to edit this file and post a kernel... but we must know what to edit....
delete this and paste that...etc....
also is it all...or must be also a edit of framework...or so..
with kind regards
I think that's all
this is a patch i found on github...
https://github.com/showp1984/bricke...mmit/284f0a5cdb45eef6539c3c1a3641256794804035
and the rest all with sweep2wake
https://github.com/showp1984/bricked-shooteru-ics-sense/commits/master
these are kernel commits/patches...can be a bit different from some points because they are made for a different phone...but with some time it can be patched i think
thx to showp1984
with kind regards...Alex
so who can cook kernel with this patch?
Surely its not that easy to enable slide2wake.... I will have a go later and see if it compiles...
[vertigo] said:
I will have a go later and see if it compiles...
Click to expand...
Click to collapse
i`ll be waiting for it
Well it compiled ok but the slide2wake hasn't worked so I'm going to have a closer look...
I am very grateful to you for you are doing this
[vertigo] said:
Well it compiled ok but the slide2wake hasn't worked so I'm going to have a closer look...
Click to expand...
Click to collapse
you only use the main patch..or all other..? i´m unsure if the patches are all..or if framework must be patched also or a build.prob thing...etc...but nice you working on this...
with kind regards
I patched all to start off with, but I did notice that the touchscreen driver in the kernel is different to the SXL, so I tried patching the driver for the SXL and it wouldn't compile....
[vertigo] said:
I patched all to start off with, but I did notice that the touchscreen driver in the kernel is different to the SXL, so I tried patching the driver for the SXL and it wouldn't compile....
Click to expand...
Click to collapse
thank for dont giving up
Here is my port thus far:
X Disclaimor - Rom does not boot meaning this is not working yet X
I think since sense 4 was obtainable I'd like to think Sense 3.6 is too.
Now, i'd like to ask for a little help if anyone is available.
Plus, I know developers because I am one; we have an insatiable palette for a good project.
I've discovered two things that have made me feel like i'm stuck:
4/12/2013
1) I am not sure what else I can remove from the system dir to decrease the size to what is needed ~ 272524902.4 bytes (259.9Mb)
The Roms system dir is ~274083573.9bytes (261.4Mb); I basically need to know what else I can get rid of that equal up to 1558671.5 bytes (1.5Mb)
Here's the catch- I already took out the weather from media and apps and have symlinked them from the data partition.
2) I am not sure if I have correctly made the kernel.
I have a boot.img from the sense 3.6 rom i used to port. And I added the bootclasspath from the base kernel.
I also have renamed the proper files that needed to be renamed with inc.
Update: 4/13/2013
I've shrunk the system/usr dir down and now the port is under the size limit.
I have also tinkered with the boot.img more. Can someone check it to make sure that I have done is okay..
`Link in my sig:
First thing check how we did it before using symlinks to make some of the files physically on data but linked to system.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
First thing check how we did it before using symlinks to make some of the files physically on data but linked to system.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So far I've symlinked system/media/weather to data/system.weather and the system/app dir to data/system.app.
This is what i'm using:
symlink("/data/system.app", "/system/app");
set_perm_recursive(0, 0, 0755, 0644, "/data/system.app");
symlink("/data/system.weather", "/system/media/weather");
set_perm_recursive(0, 0, 0755, 0644, "/data/system.weather");
Do you think i could do the same with the system/vendor dir?
Edit: Don't need to worry now that the current port's system partition,which is now uploading, will be under the size limit.
*Bumpdated*
v1_1 Upload
Glad to see a Sense ROM getting some love.
Sent from my Infected HTC Incredible
We need to see how PureMotive got it booting on Sense 4. My brain's rusty on that project as it died a while ago and I am not sure how he got it to boot. I also need dedication to work on Sense after the superiority of AOSP on an aging device let alone ICS Sense. I don't know if I will have time to dedicate now that I'm working more on the Galaxy Nexus and a CM 10.1 ROM.
ChemicalSymphony said:
Glad to see a Sense ROM getting some love.
Sent from my Infected HTC Incredible
Click to expand...
Click to collapse
Yeah. I really wanna see this work lol. It's funny, I even dreamed I saw the Sense 3.6 taskbar on my Inc lol.
tiny4579 said:
We need to see how PureMotive got it booting on Sense 4. My brain's rusty on that project as it died a while ago and I am not sure how he got it to boot. I also need dedication to work on Sense after the superiority of AOSP on an aging device let alone ICS Sense. I don't know if I will have time to dedicate now that I'm working more on the Galaxy Nexus and a CM 10.1 ROM.
Click to expand...
Click to collapse
Yeah. Exactly. My brain is rusty too. I probably should try to find that Rom we worked on and see what the kernel looks like.
But don't worry about that, I think ppl like seeing devs even conversing together lol.
Tribulattifather said:
Yeah. I really wanna see this work lol. It's funny, I even dreamed I saw the Sense 3.6 taskbar on my Inc lol.
Yeah. Exactly. My brain is rusty too. I probably should try to find that Rom we worked on and see what the kernel looks like.
But don't worry about that, I think ppl like seeing devs even conversing together lol.
Click to expand...
Click to collapse
This is just a thought but couldent you for now pull the puremotive boot.img until you can build a patched kernel that you can push to the zip
zachf714 said:
This is just a thought but couldent you for now pull the puremotive boot.img until you can build a patched kernel that you can push to the zip
Click to expand...
Click to collapse
That's not enough on its own. Need to swap some files with those from an aosp ics build for the Inc.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
That's not enough on its own. Need to swap some files with those from an aosp ics build for the Inc.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll find a good stable ICS build then
Sent from my Nexus 7 using Tapatalk HD
zachf714 said:
I'll find a good stable ICS build then
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
How about the latest evervolv ICS release. That's what pure pulled from I believe.
@zachf714:
I will look also. If I find any, i'll upload them to the working folder i created for the project.
And if you guys find any, link me here and i'll download and do the same thing.
@tiny4579:
On the Luxe Rom we worked.. I don't have any of the files anymore. Do you happen to have a rom.zip of the project?
@project Community:
I've uploaded the Rom I used to port with to the dev host - droid in working folder.
I'm about to upload the other Rom I used.
Both the base and port rom I used to make the WIP are uploaded now.
Cm9 http://goo.im/devs/invisiblek/dinc/.../dinc-CM9-invisiblek-KANG-09-03-2012-1608.zip
This was actually the most stable ICS ROM I ran
Sent from my Nexus 7 using Tapatalk HD
I at least got a splash screen loop by flashing the boot.img from the cm9 rom
And man do I LOVE GITHUB https://github.com/PureMotive/sense36-ics-inc Those are the files Pure had put on Github
zachf714 said:
I at least got a splash screen loop by flashing the boot.img from the cm9 rom
And man do I LOVE GITHUB https://github.com/PureMotive/sense36-ics-inc Those are the files Pure had put on Github
Click to expand...
Click to collapse
That was an initial failed attempt. I think I worked on this with pure. Was it a fork?
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
That was an initial failed attempt. I think I worked on this with pure. Was it a fork?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Not until I just forked it and yeah you did
Damn. Wish I wasn't in bed already.
I'd compile pures git and see if his kernel does anything with the WIP.
My kid gets on the bus at 7:50a (est) and will Dev a bit before I get going for the day.
But if someone tries before then let us know the outcome.
I'm transferring over two versions of the WIP now.
One with the boot.img from pure's git injected into it.
And another that is redesigned to look like how pure had it. Also, I merged my bin, lib and xbin.
Also using the boot.img from pure.
Testing in a minute or so and i'll report back with the outcome.
(Off topic ~ Today's my 4 year anniversary being at xda )
Edit: Yeah, they both didn't work. I'm uploading v0_3 now so you guys can take a look at what I did.
Tribulattifather said:
I'm transferring over two versions of the WIP now.
One with the boot.img from pure's git injected into it.
And another that is redesigned to look like how pure had it. Also, I merged my bin, lib and xbin.
Also using the boot.img from pure.
Testing in a minute or so and i'll report back with the outcome.
(Off topic ~ Today's my 4 year anniversary being at xda )
Edit: Yeah, they both didn't work. I'm uploading v0_3 now so you guys can take a look at what I did.
Click to expand...
Click to collapse
I just thought about this but maybe the updater script is bad
Sent from my ADR6300 using Tapatalk 2
zachf714 said:
I just thought about this but maybe the updater script is bad
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
That is exactly what I thought so took care of that hahaha.
Right now, imo, I'm thinking it's a lib problem from my recent logcat.
I'll hop on in a few minutes and take another logcat and upload it.
(I deleted the one I had because I hadn't realized that you all might want to take a look too)
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
dongdong6968 said:
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
Click to expand...
Click to collapse
Okay, so now I need to run extract-files.sh, only problem is it doesn't exist. and from my understanding, I have to already be running cm12 to do this, which obviously is not possible. Can anyone help me get the proprietary blobs?
You're better off looking at the g2 proprietary blobs as when I was trying I had the most success with them on CM11, its a good starting point
So should I take those, then make changes to suit the flex?
Yeah, its a good place to start, but it won't suddenly make it compile, it helped sort a couple of issues once we'd got it compiling in the first place....
Try msg playfulgod and see if he will point you in the right direction
Alright, I've got something that looks pretty good going, but I can't do anything without a working kernel. And as I don't know much about kernels, could Someone possibly try to make one for cm12? Also, I have the blobs from my boyfriend's g2, and I've made a lot of changes, but I might need a little more guidance. Any help is appreciated.
Do you have coding experience though thats the question.
Either Build a dummy kernel or modify the original kernel from cm11 roms that your device has and built it alongside the system images.
CyanogenMod doesnt allow Building of only the system.
Youll need to modify the following:
Kernel Source
Device Trees
Vendor Files
A good way to look at what is required for a cm12 bringup is to check other similar devices with the same architecture and compare the changes and the sources you have on your pc.
Regards
Sent from my Xperia SP using xda Forum
I took programming classes, and there were a few units on android.
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
mattwheat said:
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
Click to expand...
Click to collapse
I would really appreciate that! What means should I take of sending you the output?
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Furrydaus said:
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
If anyone wants to take a look I zipped the out folder.
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
dongdong6968 said:
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
Click to expand...
Click to collapse
The device tree repos found in lg-devs github are the correct ones just change kernel source to our stock kernel and edit z.mk and verndor files can be extracted with the ./extract-fikes.sh script . But our kernel needs to be updated a little which i am working on mostly caf header need to be added to include/Linux for media and display. I trued using msm8974 kernel but our kernel has specific blobs we use which is easier to use stock kernel.
---------- Post added at 06:26 PM ---------- Previous post was at 06:16 PM ----------
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
What you mean you got something lol. We just need to update our stock kernel which you can have a better understanding. Of what i mean visit lg-devs for z repos . we should stick to stock kernel doe.
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
Upload it to drive then message me with a link
mattwheat said:
Upload it to drive then message me with a link
Click to expand...
Click to collapse
https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
Furrydaus said:
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
Sorry, completely forgot. https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0