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
Related
so....... yeah. I've been working on this since MoDaCo dropped the Galaxy Nexus rom dump a few days ago. so far...... the phone vibrates when I hit the power button. It showed a boot screen once, and nothing more..... I do not plan on releasing this rom, well, ever. Unless I can get it to boot fully. If/when that happens, I'll post it up if it does, it'll be full of bugs that I probably won't know how to fix, so, sorry
If anyone else wants to try porting and gets it done before me, more power to ya if not, please pray that I at least get to the lockscreen xP
More info when stuff happens
UPDATE: December 11th, 2011, thus far, it boots, but touchscreen still does not work... Will keep trying.
always wanted to do this,
RESERVED
and,
RESERVED AGAIN
thanks you are also there..
tj_style has successfully booted ics sdk on our fih-fbo & ported the touchscreen drivers..
nothing else is working other than that
here's a video-
www.youtube.com/watch?v=_13ikGCviJg
may you should ask him for help..
i think it would more easy porting sdk than the dump porting as system dump is already coded for a device with completly different hardware..
nitindeck said:
thanks you are also there..
tj_style has successfully booted ics sdk on our fih-fbo & ported the touchscreen drivers..
nothing else is working other than that
here's a video-
www.youtube.com/watch?v=_13ikGCviJg
may you should ask him for help..
i think it would more easy porting sdk than the dump porting as system dump is already coded for a device with completly different hardware..
Click to expand...
Click to collapse
true, although the sdk is missing tons of stuff... so i just thought porting this would be easier haha guess not... i mean ive gotten further than most devs, my device at least powers on i think im gonna try a different kernel. maybe tomorrow.... ill report back
great work man keep going on you will get it
Source Code OUT NOW!!
groups.google.com/group/android-building/browse_thread/thread/4f85d9242667a85f?pli=1
nitindeck said:
Source Code OUT NOW!!
groups.google.com/group/android-building/browse_thread/thread/4f85d9242667a85f?pli=1
Click to expand...
Click to collapse
i know ive been working on it since yesterday
ICS ported to HTC G1
ICS has been ported to HTC G1 the first android phone... so it is just matter of time that we could also get it in our device..
http://forum.xda-developers.com/showthread.php?p=19648827
welp, i got it to boot, and it goes to the lockscreen, but then goes into bootloop... and the touchscreen doesnt work...... ah.. lots of work ahead, but i think the hard parts over ill keep updating!!!
keep going man you will get it
ICS Update by Huawei
Huawei U8860 Honor Official ICS Beta Update Released.....I am not a programmer so this might be a DUH! post...but still came across so shared...maybe the great Devs can shed some light..
Specs:
Chipset Qualcomm MSM8255T Snapdragon
CPU 1.4 GHz Scorpion
GPU Adreno 205
News Update: http://bbs.huaweidevice.com/cn/forum/index.php?app=forum&mod=Detail&act=index&id=32441
ICS Update: http://www.huaweidevice.com/cn/technicaIndex.do?method=gotoProductSupport&productId=3826&tb=0
hope it would be fast port coz' m' totally failed
this would be MUCH easier to port, considering propriotary drivers, and the chipset is nearly exactly the same. im gonna work on this when i get home.
I WILL LET YOU KNOW MY PROGRESS TONIGHT STAY TUNED!!!
^ I am tuned to hear updates from you on ICS ............
c_anuraag said:
Huawei U8860 Honor Official ICS Beta Update Released.....I am not a programmer so this might be a DUH! post...but still came across so shared...maybe the great Devs can shed some light..
Specs:
Chipset Qualcomm MSM8255T Snapdragon
CPU 1.4 GHz Scorpion
GPU Adreno 205
News Update: http://bbs.huaweidevice.com/cn/forum/index.php?app=forum&mod=Detail&act=index&id=32441
ICS Update: http://www.huaweidevice.com/cn/technicaIndex.do?method=gotoProductSupport&productId=3826&tb=0
Click to expand...
Click to collapse
More Data Here.....
https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=shortlog;h=refs/heads/msm-3.0
egarly waiting
c_anuraag said:
More Data Here.....
https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=shortlog;h=refs/heads/msm-3.0
Click to expand...
Click to collapse
kernels... i dont know a thing about em.. xD
this is odd....
you download the .zip, inside it goes like this
.zip
u8860IceCream_B863_Kernel2.6.35
dload
UPDATE.APP
if I'm not mistaken, .app is a Mac OSX file extension.... Anyone know how to decompile or extract it on windows? cuz i'm stuck.
alx294 said:
this is odd....
you download the .zip, inside it goes like this
.zip
u8860IceCream_B863_Kernel2.6.35
dload
UPDATE.APP
if I'm not mistaken, .app is a Mac OSX file extension.... Anyone know how to decompile or extract it on windows? cuz i'm stuck.
Click to expand...
Click to collapse
Bro...i was able to use below to extract Update.App using a Perl Script that I found here:
http://android.modaco.com/topic/311344-repacking-updataapp-was-new-version-of-split-updatapl/
I installed Perl from here : http://www.perl.org/get.html#win32
the command : perl split_updata.pl update.app extracts the files recovery.img and system.img along with other files that I have no clue about. However this does throw lots of CRC errors....
I am not a Perl script expert maybe you can look further into that
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!
Before everyone starts flaming me and trying to kill me for being such a noob, i would like to say that i'm a teen and a noob.
ANYWAYS, i got bored and decided to have a go at porting Firefox OS to the Optimus 2X. After figuring out how to make a flashable zip out of .img's, I tested a bit. Unfortunately ADB doesnt work and I don't know how to do live kernel debugging.
What works: Kernel
What doesn't work: everything else
Source code: http://github.com/JordanRulz
Download:
First Semi-working attempt: http://d-h.st/juX (not a flashable zip)
2nd attempt: link on http://jordanrulz.tk/ (flashable)
3rd attempt (current): http://d-h.st/0We(flashable)
Turn signature verification off before flashing
BUILD INSTRUCTIONS (still doesn't work, but for anyone who thinks they might have the answer, go right ahead)
1.
Code:
git clone http://github.com/JordanRulz/B2G.git
2.extract a cm9 rom to B2G/my_device_backup
3.cd to the B2G directory and
Code:
ANDROIDFS_DIR=my_device_backup ./config.sh p990
and wait for the code to download. This has a good chance of failing because repo and git are stupid.
4.
Code:
./build.sh
5.edit core/sysroot/init.rc so that it imports init.p990.rc
6.go to line 98 of build/core/Makefile and change the build fingerprint to something acceptable by the build system
7.go online and find a wpa_ctrl.h and put it in hardware/libhardware_legacy/wifi/libwpa_client/wpa_ctrl.h
8.copy libcamera.so and libwpa_client.so from a cm9-based rom to out/target/product/p990/obj/lib/
9.it should turn out boot,img, system.img, a system folder, userdata.img, a userdata folder, etc. with adaptations, you should be able to craft a flashable zip out of the folders.
Please hit donate if you feel my work is worth donating to.
Good effort bro!
Way to go buddy.... Expecting this Rom for our beloved Optimus 2x. (me too a noob cant help much)..
Thanks and wish u best of luck..
ahahaha, great work! bring to the old O2X a new system!
Interesting tread, I'll look at the files. Let's hope this will be a cooperative tread to make this
Ok. What i did similarly to my phone to get this up. First, use PowerISO and extract userdata.img and system.img. Once done, its just like system folder of android while userdata is just data folder for user's data. Obviously. And then, the boot.img goes to the same as a flashable rom zip root folder. So basically, they are the same as flashing cm. Just need to add another few commands for recovery.img so that the whole thing is flashed like cm10
nicholaschw said:
Ok. What i did similarly to my phone to get this up. First, use PowerISO and extract userdata.img and system.img. Once done, its just like system folder of android while userdata is just data folder for user's data. Obviously. And then, the boot.img goes to the same as a flashable rom zip root folder. So basically, they are the same as flashing cm. Just need to add another few commands for recovery.img so that the whole thing is flashed like cm10
Click to expand...
Click to collapse
doesn't work. "invalid image file"
i think probably you can pm any recognised dev's for help....if you post a thread here i dont think anybody will try to help....you can pm the dev's like tonyp, harsh, carburano or anyone and you can ask for help in packaging and later on continue with your development....just an idea....:good:
good stuff man., were not the flaming community of yester year
This is getting really frustrating, after restarting multiple times and over 10 failed attempts. I have forked all the repos to my github so that all that want to help are able to do so. http://github.com/JordanRulz
Hello everyone. It's for new bl or old bl? Thanks
Sent from my LG-P990 using xda app-developers app
I say it´s for the old BL, if i don´t read the updater-script inside completly wrong.
It's for old bl
Sent from my LG-P990 using xda app-developers app
build instructions (for a non-working build, but still useful for f*cking around) were added.
JordanRulz said:
build instructions (for a non-working build, but still useful for f*cking around) were added.
Click to expand...
Click to collapse
:good::good:
Don't know if you're going at it the right way but good luck, and you should contact another dev just to make sure at least that you're on the right path.
I'm trying to get help from several devs.
Sent from my LG Optimus 2x using xda app-developers app
JordanRulz said:
I'm trying to get help from several devs.
Sent from my LG Optimus 2x using xda app-developers app
Click to expand...
Click to collapse
I hope if you develop successful, it will have 1 for SU660 :victory:
http://jordanrulz.tk/ not open the sites, is a virus java drive, jordan you really noob report on f.b.i
alexcyb said:
http://jordanrulz.tk/ not open the sites, is a virus java drive, jordan you really noob
Click to expand...
Click to collapse
Its not a "virus java drive", its a hidden bitcoin miner. If u use a secure browser like Firefox, it will prompt you before running it.
Sent from my LG Optimus 2x using xda app-developers app
Hello guys:laugh:
I searched every forum thoroughly but didn't found a proper and working solution for Xperia devices
I am trying to make a custom ROM from stock using dsixda kitchen
I used stock 12.1.A.201 as the base ROM
I believe that it's either the updater script error or kernel probelm as I am using stock kernel and my zip is like this
Data
META-INF
system
boot.img
check_data_app
Click to expand...
Click to collapse
This happens when rom is created
De-odexed it rooted it and added X-Reality engine and created the rom
First on installing I got error of status 0 so I changed my update binary file from same de-odexed version from this link http://forum.xda-developers.com/showthread.php?t=2704312 by @dipesh1502 (thanks to him for that awesome rom)
Next I am getting error status 7
ROM Starts flashing then it comes to this part
formatting system bla bla
expected 5 args got 3
Click to expand...
Click to collapse
something like that and then it stops on error status 7
here is the updater-script please have a look. I really want to create this ROM. Please help
Updater-Script Download
here is my build prop build.prop download
Help guys please I'll be highly grateful
My device is C5302 rooted and unlocked bootloader with 12.1.A.205 stock kernel
EDIT : Got past the error status 7 now ROM gets installed
But unfortunately now it ends in a bootloop :/ Got stuck on Sony splash logo and then reboots constantly :/
Had a nandroid backup ready x)
Had to flash the ftf file over and over again. :/
Phone is allright just want to catch this error of bootloop.
I changed kernel with the dipesh1502's ROM but still no luck. Modified Updater script but still no luck. help me I am soo confused and screwed!! :'( :'(
My new Updater-Script
There's a HUGE difference in creating boot animations and creating a ROM.
Don't expect to teach yourself how to make a ROM in just a few days.
It takes, weeks, months, years...
If you're mainly planning to make some exterior changes, which I think you're currently doing, I would focus on making complete themes and not ROMs.
People are not waiting for a ROM which is already available but that looks somewhat different and maybe has some extra or removed apps.
Regarding your problem, I will not be able to help you since I don't have that kind of knowledge.
Anyway, good luck!
Gamm86 said:
There's a HUGE difference in creating boot animations and creating a ROM.
Don't expect to teach yourself how to make a ROM in just a few days.
It takes, weeks, months, years...
If you're mainly planning to make some exterior changes, which I think you're currently doing, I would focus on making complete themes and not ROMs.
People are not waiting for a ROM which is already available but that looks somewhat different and maybe has some extra or removed apps.
Regarding your problem, I will not be able to help you since I don't have that kind of knowledge.
Anyway, good luck!
Click to expand...
Click to collapse
Thanks for the reply.
Yeah I know that it's not easy to create ROM and also it takes a lot of time. I am ready to give it a shot
I am just making some small changes just for my sake I'll be using this ROM personally for my own use I know that there are a thousand times better ROM's than mine
Anyway glad you considered my probelm.
Bootloop can be cause by:
- Wrong permissions
- Corrupt installation
It is nice if you collect either the last_ksmg or logcat when bootlooping. (if possible)
~~Regard
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
But first:
Share me the .zip you have created perhaps I can take a small look
~~ Regards
mrjraider said:
Bootloop can be cause by:
- Wrong permissions
- Corrupt installation
It is nice if you collect either the last_ksmg or logcat when bootlooping. (if possible)
~~Regard
Click to expand...
Click to collapse
Thanks for the reply
Can you please have a look at my new updater-script and tell me what is wrong?
I will surely try to get logcat but before that if you can just analyze this updater-script and pinpoint the mistakes it'll make my work a lot easier.
Thanks in advance :good:
Sent me the entire .zip file instead (but start with updater-script)
~~Regards
mrjraider said:
Sent me the entire .zip file instead (but start with updater-script)
~~Regards
Click to expand...
Click to collapse
Sure thing I'll
I am compressing it to maxium extent using KGB archiver and it'll become around 10~20 mb only
It's still compressing so it'll take some time before it reaches it's max compression.
I'll surely send you asap
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