Related
Can a kernel dev contact QuBe2 on xda he wants to port sense 4 to the mes,showcase,and fascinate he just needs a kernel dev to make a small change to the kernel for him so contact him please
Jurellz said:
Can a kernel dev contact QuBe2 on xda he wants to port sense 4 to the mes,showcase,and fascinate he just needs a kernel dev to make a small change to the kernel for him so contact him please
Click to expand...
Click to collapse
hope someone contacted him
ztotherad said:
hope someone contacted him
Click to expand...
Click to collapse
This was what I always used!
Please nobody don't do anything stupid!
Take the prebuilt's and the tools from any cm10/aosp source and place in ramdisk folder!
Linux
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.img | cpio -i
cd ..
mv ramdisk.img ramdisk.bak
./mkbootfs ramdisk | gzip > ramdisk.img
./mkshbootimg.py boot.img kernel ramdisk.img ramdisk-recovery.img
notta said:
This was what I always used!
Please nobody don't do anything stupid!
Take the prebuilt's and the tools from any cm10/aosp source and place in ramdisk folder!
Linux
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.img | cpio -i
cd ..
mv ramdisk.img ramdisk.bak
./mkbootfs ramdisk | gzip > ramdisk.img
./mkshbootimg.py boot.img kernel ramdisk.img ramdisk-recovery.img
Click to expand...
Click to collapse
Did you tell QuBe2 that?
he told me " I cant build kernels i need a kernel dev to do a edit to a cm9 kernel" before i posted this thread
but i just told him about this edit. hopefully this is it
Jurellz said:
he told me " I cant build kernels i need a kernel dev to do a edit to a cm9 kernel" before i posted this thread
but i just told him about this edit. hopefully this is it
Click to expand...
Click to collapse
I have used that exact code to boot sense myself!
notta said:
I have used that exact code to boot sense myself!
Click to expand...
Click to collapse
On the Fascinate??
istealhome said:
On the Fascinate??
Click to expand...
Click to collapse
Yes it was but now the fassy has a 1gb sys partition!
notta said:
Yes it was but now the fassy has a 1gb sys partition!
Click to expand...
Click to collapse
Sorry, I'm a little confused haha. I stopped flashing after JT redid the partitioning in jb (I'm to lazy to restore all my apps unless its for a brand operation system version, or skin lol) is that what you are talking about?
istealhome said:
Sorry, I'm a little confused haha. I stopped flashing after JT redid the partitioning in jb (I'm to lazy to restore all my apps unless its for a brand operation system version, or skin lol) is that what you are talking about?
Click to expand...
Click to collapse
Yes I am speaking of Jt's new partition layout for the 1gb!
notta said:
Yes I am speaking of Jt's new partition layout for the 1gb!
Click to expand...
Click to collapse
So does that break Sense or something? Why not use the old layout? I'm sure people would forfeit the new layout for Sense
istealhome said:
So does that break Sense or something? Why not use the old layout? I'm sure people would forfeit the new layout for Sense
Click to expand...
Click to collapse
NO! Was implying it would run much better and be much easier on the new partition layout!
I myself was planning on attempting it again on the new layout but I sorta picked up extra work I wasn't planning on! Plus, somebody bricked my HTC dev phone.... :laugh:
notta said:
NO! Was implying it would run much better and be much easier on the new partition layout!
I myself was planning on attempting it again on the new layout but I sorta picked up extra work I wasn't planning on! Plus, somebody bricked my HTC dev phone.... :laugh:
Click to expand...
Click to collapse
Ahhhh I see! Hey! You should talk to xboxfanj; he's been trying to get Sense 2.1 to boot on the fassy for a while now but hasn't been successful, tell him about the new partition layout and it should help him get 4.0 working for our phones! I'd be glad to test out for a dev duo like that
notta said:
This was what I always used!
Please nobody don't do anything stupid!
Take the prebuilt's and the tools from any cm10/aosp source and place in ramdisk folder!
Linux
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.img | cpio -i
cd ..
mv ramdisk.img ramdisk.bak
./mkbootfs ramdisk | gzip > ramdisk.img
./mkshbootimg.py boot.img kernel ramdisk.img ramdisk-recovery.img
Click to expand...
Click to collapse
My preferred method is to just do everything within the cm build directory. The only thing that needs modification is init.rc, so copy the sense init.rc to system/core/rootdir of the cm directory. Then build and get the boot.img from the zip. It takes awhile, but it's the most reliable method for Galaxy S devices (on others, you can easily just use kitchens). In other news, if someone could please test and logcat this Sense 2.1 ROM, I would appreciate it http://darkierawr.com/Android/Users/xboxfanj/FascinateSensemediafix.zip
istealhome, its a newer build than the one before at rootzwiki.
this wouldnt work on the showcase right?
Jurellz said:
this wouldnt work on the showcase right?
Click to expand...
Click to collapse
It would still boot most likely on the showcase if it does on the fascinate. I think kernels should be interchangable.
i flashed it and it rebooted and looped in recovery
Jurellz said:
i flashed it and it rebooted and looped in recovery
Click to expand...
Click to collapse
What do you mean by that
Sent from my SPH-D700 using Tapatalk 2
xboxfanj said:
My preferred method is to just do everything within the cm build directory. The only thing that needs modification is init.rc, so copy the sense init.rc to system/core/rootdir of the cm directory. Then build and get the boot.img from the zip. It takes awhile, but it's the most reliable method for Galaxy S devices (on others, you can easily just use kitchens). In other news, if someone could please test and logcat this Sense 2.1 ROM, I would appreciate it http://darkierawr.com/Android/Users/xboxfanj/FascinateSensemediafix.zip
istealhome, its a newer build than the one before at rootzwiki.
Click to expand...
Click to collapse
xboxfanj said:
What do you mean by that
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
nevermind i flashed it and this is what i get .
http://pastebin.com/YMQVULvZ
xboxfanj said:
My preferred method is to just do everything within the cm build directory. The only thing that needs modification is init.rc, so copy the sense init.rc to system/core/rootdir of the cm directory. Then build and get the boot.img from the zip. It takes awhile, but it's the most reliable method for Galaxy S devices (on others, you can easily just use kitchens). In other news, if someone could please test and logcat this Sense 2.1 ROM, I would appreciate it http://darkierawr.com/Android/Users/xboxfanj/FascinateSensemediafix.zip
istealhome, its a newer build than the one before at rootzwiki.
Click to expand...
Click to collapse
Well you could do that if you have the repo as well...
You could also save yourself some time by running "make bootimage"!
Hey guys, we have here a kernel built from the kernel source HTC released on 8/29/12 for Vigor. This kernel is a modified version of what came in the Official 3.14.605.12 ICS OTA except it is built from HTC's kernel source release. What else can I say?
Bugs:
-?
Current features:
Perflock Disabled
Fast charge enabled using any power source - Thanks to Chad, I used his commits as a reference
Download:
Link Removed
Download Global OTA Compatible Version (Thanks to MicroMod for making it happen
Link Removed
Install:
Place zip on sd
Reboot to recovery (I use amon)
Install from zip
Select the zip file
The file will flash and then the phone will reboot to hboot
Once there, simple press power to select bootloader
Accept the update
It will install
Reboot your phone
????
Enjoy
Don't forget to go delete the PH98IMG.zip from your SD Card after boot.
Disclaimers:
I won't be responsible for what you flash on your phone or any damge that could be caused. Always use caution when modifying any part of your device.
Credits:
Thank con247 for the auto kernel flasher.
Thanks Chad for all your awesome kernel knowledge.
My Github for this kernel:
Link Removed
/// Info for new devs \\\
How to disable perflock in an HTC kernel through source
Simple, open you source. Open the arch/arm/configs. Find the file vigor_defcofig. Find the following lines:
Code:
CONFIG_PERFLOCK=y
CONFIG_PERFLOCK_BOOT_LOCK=y
Change them to:
Code:
# CONFIG_PERFLOCK is not set
# CONFIG_PERFLOCK_BOOT_LOCK is not set
Perflock is now disabled. Build your source
Changing the kernel name
Open the scripts folder in the root of your source. Find and open the file makecompile_h. Find the lines:
Code:
echo \#define LINUX_COMPILE_BY \"`echo $LINUX_COMPILE_BY | $UTS_TRUNCATE`\"
echo \#define LINUX_COMPILE_HOST \"`echo $LINUX_COMPILE_HOST | $UTS_TRUNCATE`\"
Edit how you want:
Code:
echo \#define LINUX_COMPILE_BY \"`echo wildstang83`\"
echo \#define LINUX_COMPILE_HOST \"`echo vigor-ics`\"
Enjoy
Is this a sense kernel? I know...but noobs should have heads up.
Sent from my HTC Rezound using xda premium
I'm going to keep count of the flood of kernels that are sure to come.
This is #1
Anyway will download tomorrow, way too tired right now
Sent from my Nexus 7 using Tapatalk 2
What makes this different from the stock ones?
apophis9283 said:
What makes this different from the stock ones?
Click to expand...
Click to collapse
As far as I know, absolutely nothing. I could be wrong though. Some of you that remember the Incredible or Thunderbolt will remember how the kernel that was in the ota for those devices and the kernel source released after the ota were different. HTC had added in minor fixes to the kernel source release that was not in the ota. I don't know if that is the case here, just a thought though.
It's not different. Lmao read the title. Looking forward to see what come from this, stang
Sent from my ADR6425LVW using Tapatalk 2
antp121 said:
It's not different. Lmao read the title. Looking forward to see what come from this, stang
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Exactly, we can assume this kernel is no different from the one in the OTA. Unless of course someone else can prove otherwise.
wildstang83 said:
As far as I know, absolutely nothing. I could be wrong though. Some of you that remember the Incredible or Thunderbolt will remember how the kernel that was in the ota for those devices and the kernel source released after the ota were different. HTC had added in minor fixes to the kernel source release that was not in the ota. I don't know if that is the case here, just a thought though.
Click to expand...
Click to collapse
Is that Kernel still perflocked?
Not totally familiar with what could be different between stock and custom built stock from source.
Quantumrabbit said:
Is that Kernel still perflocked?
Not totally familiar with what could be different between stock and custom built stock from source.
Click to expand...
Click to collapse
If built as is from source, I'd say yes. Give the devs some times, you'll see them come out with perflock removed.
mjones73 said:
If built as is from source, I'd say yes. Give the devs some times, you'll see them come out with perflock removed.
Click to expand...
Click to collapse
Right, this kernel was not intended to be custom in anyway whatsoever. It is simply a kernel built from source. I know I like stock things, I'm sure others do as well.
i honestly love you wild stang. and neo and mbobino.
Nice work stang
Sent from my ADR6425LVW
I got a stock build with PERFLOCK disabled building right now. I'll upload that to the OP in just a minute.
I love you
Sent from my Nexus 7 using Tapatalk 2
Perflock disabled version added to OP.
Will this work with sense 4 roms?
i guess with perflock disabled, we could underclock? or at least change the governors and stuff using cpu controller apps?
apophis9283 said:
Will this work with sense 4 roms?
Click to expand...
Click to collapse
in theory, yes. would i attempt it? not quite yet.
antp121 said:
in theory, yes. would i attempt it? not quite yet.
Click to expand...
Click to collapse
Should be fairly simple to insure a Sense 4 version. Just grab a sense 4 boot.img like newtoroots or whatever, open it up in android kitchen and drop in the zimage from my kernel's zip. Repackage the boot.img and fastboot flash it. ant, you should try it
wildstang83 said:
Should be fairly simple to insure a Sense 4 version. Just grab a sense 4 boot.img like newtoroots or whatever, open it up in android kitchen and drop in the zimage from my kernel's zip. Repackage the boot.img and fastboot flash it. ant, you should try it
Click to expand...
Click to collapse
sounds a little bit difficult for an end user just like me with no idea about dev things
Sent from my ADR6425LVW using xda premium
Hey all, since a lot of folks are wondering about custom roms for the DX, I decided to start this thread to document my exploits in trying to compile CM9.
Basically, I'm new to Android (had an iPhone 3GS for about 2 years) so I'm going to need a lot of help and this is really going to start of very basic. But since I had my Desire X and been on this forum, I have met more and more cool people that are actively trying to help development for our phone, like stereo8,maartenxda and yasir, so I'm sure we'll be alright. None of this would be even possible if not for LLior that made the CWM recovery for us. :good:
OK, so to build CM9 you need a build environment set up specifically for the job, there's many guides out there on how to do this, but I found this one (props to mbroeders, OP of the tut) pretty good :
http://forum.xda-developers.com/showthread.php?t=1566224
Basically, building CM9 is done in linux, Ubuntu being the most popular version, and I'll be using the latest Ubuntu 12. If you don't use Ubuntu as main OS, you can still try this, but you'll need to set up a good (!) portion of your harddrive to install it in a virtual environment, like VMWare Player (free). Mind you, we'll be downloading the CM9 source, which ended up being around 10 gig on my pc, and we'll be needing at least another 16 gig to actually build CM9. To be on the safe, I set aside 50 gig on my drive for the virtual Ubuntu-pc in VMWare.
The guide I'm using will show you how to set up a general build environment, but since we are talking about the Desire X, which is brand new and without official CM support (yet?), we are going to have to adapt it to make CM9 for our phone. Several people have already worked on this, mainly Lloir, so I got his permission to use the stuff he's already done. A big thanks btw, from one and all
And this is basically the first time I'm going to need help. To adapt the build system specifically for the DX, we'll need to make a local_manifest file that points it to device and vendor trees LLoir has made. The local_manifest is supposed to go in the .repo folder of your CM9 source.
How do I do this ?
Goto cm9 wiki and install all prerequisites. Then do a repo init of the main build tree(cm9) and then add the device trees to manifest.xml found in .repo. after that , you sync via repo sync and then you setup environment through envsetup.sh and then you build for protou by brunch protou. Debug the errors you encounter. That's about it. If it doesn't boot after successful build, then the device/hardware/vendor/kernel trees need some sorting out .
Regards.
Sent from my HTC Desire X using xda app-developers app
help for local_manifest - Llior ?
Morning, googled some more, and found a template for a local_manifest.xml file I'm adapting for the DX.`I prefer to go as much by the book as possible for now, apparently putting these in manifest.xml can mess up your source.
So far, I have :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Lloir/protou" path="device/htc/protou" remote="github" revision="ics"/>
<project name="LLior/XXXXXXXXXXXXX" path="device/htc/msmXXXX-common" remote="github" revision="ics"/>
<project name="Lloir/android_vendor_htc_protou" path="vendor/htc/protou" remote="github" revision="ics"/>
<project name="Llior/XXXXXXXXXXXXX" path="kernel/htc/msmXXXX" remote="github" revision="XXXXXXXXXXXX"/>
</manifest>
The XXXX need editing, not sure which repositories though
manifest
Here you go, you can see it for your reference...
Attachment
CM9 - first build - result
Yasir Javed Ansari said:
Here you go, you can see it for your reference...
Attachment
Click to expand...
Click to collapse
OK, using your manifest, I managed to set up the system to build with Lloir's device and vendor trees.
I had to edit the msm7x30.mk file in /device/htc/msm7x30-common though so the first section of it would point to /frameworks/base rather than /frameworks/native as in the original for it to build.
It then compiled to the end, I ended up with a boot.img, recovery.img, system.img and userdata.img, which I turned into a .zip file to flash in CWM.
It installs, but gets stuck on the HTC-logo screen, but I can't take a logcat -same as with stereo's paranoidandroid : logcat.txt says logcat cant be found in /sbin/sh- even when I create a sbin/sh folder with logcat.
Anyone know what I'm doing wrong ? I would really like to see what's going on during boot.
infernal77 said:
OK, using your manifest, I managed to set up the system to build with Lloir's device and vendor trees.
I had to edit the msm7x30.mk file in /device/htc/msm7x30-common though so the first section of it would point to /frameworks/base rather than /frameworks/native as in the original for it to build.
It then compiled to the end, I ended up with a boot.img, recovery.img, system.img and userdata.img, which I turned into a .zip file to flash in CWM.
It installs, but gets stuck on the HTC-logo screen, but I can't take a logcat -same as with stereo's paranoidandroid : logcat.txt says logcat cant be found in /sbin/sh- even when I create a sbin/sh folder with logcat.
Anyone know what I'm doing wrong ? I would really like to see what's going on during boot.
Click to expand...
Click to collapse
Stock Rom showed our device shares common config from msm7k and not msm7x30. I'll try another build with some modified things to see if it boots . One thing you can do is to compare lloir device tree with other trees of similar devices to verify whether we are missing something critical. Also did you use pre.built kernel ?
AND framework native is used in jelly bean , not ics. You're syncing jelly bean cm source and device tree is currently for ics. Recheck please.
Sent from my HTC Desire X using xda app-developers app
Yasir Javed Ansari said:
Stock Rom showed our device shares common config from msm7k and not msm7x30. I'll try another build with some modified things to see if it boots . One thing you can do is to compare lloir device tree with other trees of similar devices to verify whether we are missing something critical. Also did you use pre.built kernel ?
AND framework native is used in jelly bean , not ics. You're syncing jelly bean cm source and device tree is currently for ics. Recheck please.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Hm, thanks for the input, Yasir. I was wondering about it, I just synced using the default.xml in the last post. I guess that means I was using the prebuilt kernel as well. Don't worry about the source code I synced, it's definitely cm-ics. As far as I can see, there aren't files relating to msm7k in Lloir's github. I'll see if I can find out about a device that uses the msm7k.
cheers :good:
EDIT : Yasir and me are working together on trying to get a CM9 to the Desire X, anyone that wants to help (preferably with experience) is welcome Use this thread to keep things organised. Thanks
update on CM9 - wip - all help welcome !
OK, update on what's happening :
Because our phone has a new Qualcomm processor there's no CyanogenMods out yet for any device that uses it, let alone by HTC, that we can compare it to. This could help us out a lot to get the device specific information and sources the build system needs to make us a CM9. This info and these files are contained in and referred to by the so-called device and vendor trees. Lloir has done the most work for the Desire X up to now in making these device and vendor trees, but since first test builds aren't booting, Yasir and me are going over them again.
By the way, if anyone knows more about why logcat doesn't work, that would be extremely helpful. All response I get is that logcat isn't in /sbin/sh. I tried adding it to a separate /sbin/sh folder in my test build, but no dice
Good news is I found out the MSM8225 chipset was designed to be fully backward compatible, both hardware and software, with the MSM7225A and MSM7227A phones, of which Qualcomm sold about a 100 million. So, I've begun studying the device and vendor trees for the HTC Explorer (Pico), which is a MSM7225A model. Important because it has the compatible 7225A chipset and uses the ARMv7 cpu instruction set - which is the same as the Desire X.
We'll keep you guys posted, also when we need testers. :good:
Ours is cortex a5, that's why it is compatible with msm7227. But the not booting issue is probably due to some thing missing or wrong in device.mk. the board config is ok. And kernel source is also available on htcdev and git simonsimons23. The device tree and vendor mk files need correction. At least that's my thinking.
Sent from my HTC Desire X using xda app-developers app
Yasir Javed Ansari said:
Ours is cortex a5, that's why it is compatible with msm7227. But the not booting issue is probably due to some thing missing or wrong in device.mk. the board config is ok. And kernel source is also available on htcdev and git simonsimons23. The device tree and vendor mk files need correction. At least that's my thinking.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
OK, I'll leave the boardconfig for now (am checking the files alphabetically) and move on to device.mk If I see anything I don't get or differs from the pico source (has official CM9), I'll let you know here or through pm. I was thinking the same about the device and vendor trees, it's our starting point and we're stuck here already lol. I know about the githubs, I'll check the changes (if any) simonsimons made.
I was thinking though : don't we need the 1.18 kernel to do this ? I already flashed the updated kernel with the 1.18 ruu. I checked on htcdev and it only lists the 1.14 kernel source. Or is there a way to get it from a running phone ?
missing logcat....
Hi Guys,
I don't know why logcat is missing, but to obtain kernel messages you could run the "dmesg" command instead.
I would like to participate in DX porting. I got intermediate knowlegde in android, but I'm really good in linux and kernel stuff.
Are you guys hanging around in IRC somewhere so we cant talk directly?
currently I am compiling lloirs tree. It is running for some time already...
hang loose
maze
atmel-touchscreen.kl is not in any git
Hi Guys,
I still try building the stuff, but atmel-touchscreen seems to be missing so I decided to remove it from
htc/protou/device_protou.mk. Now it continues compiling ....
( device/htc/protou/prebuilt/usr/keylayout/atmel-touchscreen.kl:system/usr/keylayout/atmel-touchscreen.kl)
Any progress OP??? I did a recent build with some mods on weekend but it failed to boot. I'm highly suspicious that its a kernel issue although i cant say for sure. If any one manages to boot it, even if its till the boot animation, DO POST AND SHARE, coz then its easier going forward.
Regards
neXus PRIME said:
Any progress OP??? I did a recent build with some mods on weekend but it failed to boot. I'm highly suspicious that its a kernel issue although i cant say for sure. If any one manages to boot it, even if its till the boot animation, DO POST AND SHARE, coz then its easier going forward.
Regards
Click to expand...
Click to collapse
got a logcat? or even a kmsg? you can get the kmsg by rebooting into TWRP mount system and open the file manager in advanced and going into /proc grab last_kmsg from in there, you can also find me on IRC Most days, (except tonight i'm working )
-Lloir
I'm sorry guys, haven't been able to do much for this project anymore...no time (holidays and starting training to become system administrator), not to mention I spilled coke all over my Macbook Pro
Lloir said:
got a logcat? or even a kmsg? you can get the kmsg by rebooting into TWRP mount system and open the file manager in advanced and going into /proc grab last_kmsg from in there, you can also find me on IRC Most days, (except tonight i'm working )
-Lloir
Click to expand...
Click to collapse
Doesnt even get past the splash screen (the one with HTC red letter sentence about private build). I used the prebuilt kernel which i have used in recovery. I'll try getting kmsg though.
Regards
neXus PRIME said:
Doesnt even get past the splash screen (the one with HTC red letter sentence about private build). I used the prebuilt kernel which i have used in recovery. I'll try getting kmsg though.
Regards
Click to expand...
Click to collapse
You can still logcat on that screen if adb sees it
Sent from my HTC One X+ using Tapatalk 2
nopes. I have QtADB running in background with logcat ON all the time. Thats how i can never miss if it gets to boot. But i didnt check kmsg though.
My laptop is in a mess right now and i have jellybean source synced by mistake over night. Now i gotta go back to ICS and it will again take a day to sync as the net is crappy here.
I got a ramdisk hack for you when I get home to enable very early adb. If I had the DX I would do it for you guys, but I'll help where I can. Don't be afraid to pm me if you need to.
Sent from my HTC One X+ using Tapatalk 2
Lloir said:
I got a ramdisk hack for you when I get home to enable very early adb. If I had the DX I would do it for you guys, but I'll help where I can. Don't be afraid to pm me if you need to.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Tell me, should I use pre built kernel or use HTC provided sources?
Im trying using latest cm10.1 source to compile the latest cm10.1 for my old phone...i use this tutorial http://forum.xda-developers.com/showthread.php?t=1971645 and an old dev device tree that haves some bugs but at least it compiled for him properly...
First of all when i type
Code:
$ gedit ~/paranoid/.repo/local_manifest.xml
im getting after a while an error with term.apk and it stops..i can't do anything so i keep up... and i type
Code:
$ brunch u8800pro(my device)
after 10-15 minutes im getting this
Code:
make: * [/home/pikachukaki/cm10.1/out/target/product/u8800pro/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/src/omx_vdec.o] Error 1
always this error!!
and it stops completly...i sync the repo again...nothing....i delete the out folder and try again...nothing...im not very experianced with developing..this is my 1st test complety rom compile...anyone can help thanks!!
fatal: remove-project element specifies non-existent project: CyanogenMod/hardware/qcom/display
at least to this??anyone?
u might have a bigger error then that
mostly it says it above
post 8/15 lines of above the error her also
Sent from my S500 using xda app-developers app
SpaceCaker said:
u might have a bigger error then that
mostly it says it above
post 8/15 lines of above the error her also
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
At least an answer...i manage to pass the 2nd post error by fixing local_manifest.xml
but im still getting the error 1 now...in another cpp..i repo sync again...i will post entire log after getting the error again!!!
Whats the difference between git://github.com/CyanogenMod/android.git -b cm-10.1 and git://github.com/CyanogenMod/android.git -b jellybean???
pikachukaki said:
Whats the difference between git://github.com/CyanogenMod/android.git -b cm-10.1 and git://github.com/CyanogenMod/android.git -b jellybean???
Click to expand...
Click to collapse
jellybean is JB 4.1.2 and cm10.1 is cm10.1 4.2.2
Sent from my S500 using xda app-developers app
SpaceCaker said:
jellybean is JB 4.1.2 and cm10.1 is cm10.1 4.2.2
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
Thanks i found another tutorial that uses first this command
lunch cm_devicename-userdebug
and then
make otapackage
That seems to make it through my errors...i dont know the difference between this and brunch...but it seems it work....
As you can think i dont have enought knowlage over coding and programming...i study only about the hardware...i wanna ask something if you don't mind...where the compile procedure find the kernel (boot.img) i dont see the kernel source inside my device tree...only a raw file called kernel!!!
pikachukaki said:
Thanks i found another tutorial that uses first this command
lunch cm_devicename-userdebug
and then
make otapackage
That seems to make it through my errors...i dont know the difference between this and brunch...but it seems it work....
As you can think i dont have enought knowlage over coding and programming...i study only about the hardware...i wanna ask something if you don't mind...where the compile procedure find the kernel (boot.img) i dont see the kernel source inside my device tree...only a raw file called kernel!!!
Click to expand...
Click to collapse
if u do this
. build/envsetup.sh
then it loads all devices
and then do
lunch
then u can see a list of wich devices are available
type the numbe of ur device and it selects it
thwn do make -j6 bacon
thata how i do build
as for kernel
it can be a prebuilt kernel
wich will be using some parts of system/core
Sent from my S500 using xda app-developers app
SpaceCaker said:
if u do this
. build/envsetup.sh
then it loads all devices
and then do
lunch
then u can see a list of wich devices are available
type the numbe of ur device and it selects it
thwn do make -j6 bacon
thata how i do build
as for kernel
it can be a prebuilt kernel
wich will be using some parts of system/core
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
The point is that it compiling all this time...its slow as hell too many cpp's but what can you do...
About the kernel so maybe the rom isn't bootable after this...maybe i have to replace it with a working 4.2.2 boot.img after this!!!
pikachukaki said:
The point is that it compiling all this time...its slow as hell too many cpp's but what can you do...
About the kernel so maybe the rom isn't bootable after this...maybe i have to replace it with a working 4.2.2 boot.img after this!!!
Click to expand...
Click to collapse
jup
also it can take sometimes up to 24 hour to a complete build
i so happen to use VMware soi can pause stop mine always
Sent from my S500 using xda app-developers app
SpaceCaker said:
jup
also it can take sometimes up to 24 hour to a complete build
i so happen to use VMware soi can pause stop mine always
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
No vmware was extremly slow to do other things too so i install ubuntu on a 2nd hard drive...24hours...omg!!
for nightlies i have to do the same again??
Code:
. build/envsetup.sh
lunch cm_devicename-userdebug
make otapackage
pikachukaki said:
No vmware was extremly slow to do other things too so i install ubuntu on a 2nd hard drive...24hours...omg!!
for nightlies i have to do the same again??
Code:
. build/envsetup.sh
lunch cm_devicename-userdebug
make otapackage
Click to expand...
Click to collapse
yeah sure
my total compile time is 8 hours
i use linux mint + gnome classic no effects
also the time depends on how much ram and cpu u have + if u have installed ccache
Sent from my S500 using xda app-developers app
SpaceCaker said:
yeah sure
my total compile time is 8 hours
i use linux mint + gnome classic no effects
also the time depends on how much ram and cpu u have + if u have installed ccache
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
Nop i don't run the ccache command...phenom x4 with 4GB ram...its ok..my point was to learn now i found a proper device tree...its ok if it takes time..and also to help the community of my olderst phone that have no dev support at all!!!
This project involves the GT-I8730, not the SGH-I437 or the SGH-I437P.
Disclaimer
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
General Info
CyanogenMod is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community.
CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced.
Click to expand...
Click to collapse
Developers/Contributors
• @kotzir (TWRP, cm-11.0, cm-12.x, cm-13.0)
• @aureljared (General Help)
• @szezso (cm-10.1, cm-11.0)
• @KINGbabasula (cm-10.1, 10.2) (General help)
• @jjchico (CWM/CM) (General help)
• @arco68 (Kernel Porting)
GitHub repos
- @kotzir's GitHub
- @aureljared's GitHub
- @KINGbabasula's GitHub.
- @jjchico's GitHub
- @szezso's GitHub
The CyanogenMod team would like to thank everyone involved with this project!
The Express does not follow standard kernel and ramdisk addresses.
To decompile the boot image:
Code:
unmkbootimg boot.img > info.txt
mkdir ramdisk
mv initramfs.cpio.gz ramdisk/initramfs.cpio.gz
cd ramdisk
gunzip -c initramfs.cpio.gz | cpio -i
To recompile, make sure you're still in the ramdisk folder, and do these to make the ramdisk:
Code:
find . | cpio -o -H newc | gzip > initramfs.cpio.gz
mv initramfs.cpio.gz ../initramfs.cpio.gz
cd ../
Now look at the info.txt you created earlier. At the bottom of 'To recompile this image...', there will be a mkbootimg command. Copy and paste that to your terminal, but before you hit Enter, add this just before '--base 0x80200000':
Code:
--ramdisk_offset 0x02000000
You may want to take a backup of the original boot image.
Reserved 2
Reserved 3
Sent from my GT-I8730 using Tapatalk
So is this rom stable and everything? cause I'm pretty noob at all of this and dont want to mess things up
EDIT: Link is dead :/
*Bump
Is it possible for someone to upload it to another site? I must try this out lol :d
Noisecake said:
*Bump
Is it possible for someone to upload it to another site? I must try this out lol :d
Click to expand...
Click to collapse
I've tried a couple on my phone but they won't upload, we'll have to wait for goo. im to fix there site.
Sent from my GT-I8730 using XDA Premium 4 mobile app
You are to fix the site?
You have an idea of when it will be fixed?
Or maybe somebody else can provide a temp upload? The site shows that the file has been downloaded over 200 times so someone must have it right? Xd
Sent from my GT-I8730 using xda premium
Yes i seen that to, it's either the download quantity is wrong or it maybe down in certain country's, I'm in Australia and i can't get it to download.
Sent from my GT-I8730 using XDA Premium 4 mobile app
Noisecake said:
You are to fix the site?
You have an idea of when it will be fixed?
Or maybe somebody else can provide a temp upload? The site shows that the file has been downloaded over 200 times so someone must have it right? Xd
Sent from my GT-I8730 using xda premium
Click to expand...
Click to collapse
Noisecake said:
So is this rom stable and everything? cause I'm pretty noob at all of this and dont want to mess things up
EDIT: Link is dead :/
Click to expand...
Click to collapse
Noisecake said:
*Bump
Is it possible for someone to upload it to another site? I must try this out lol :d
Click to expand...
Click to collapse
barclac said:
I've tried a couple on my phone but they won't upload, we'll have to wait for goo. im to fix there site.
Sent from my GT-I8730 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Please read top of original post.
Got Goo to download. When I install CM 10.2 it sits on splash screen for about 20 seconds and then goes dark, double buzz and splash screen again. Not managed to change the boot image as yet. Not sure I can find time for that until Thursday.
Got my PC to boot to a 64 bit Ubuntu 13.10. Thanks to your tutorial @aureljared am having a go at building. What are you using to pack and unpack in Linux when you replace the boot image? Windows usually messes up.
Bazzan
bazzan said:
Got Goo to download. When I install CM 10.2 it sits on splash screen for about 20 seconds and then goes dark, double buzz and splash screen again. Not managed to change the boot image as yet. Not sure I can find time for that until Thursday.
Got my PC to boot to a 64 bit Ubuntu 13.10. Thanks to your tutorial @aureljared am having a go at building. What are you using to pack and unpack in Linux when you replace the boot image? Windows usually messes up.
Bazzan
Click to expand...
Click to collapse
I modified mkbootimg and unmkbootimg.
Download the tools by doing these in a terminal (I'm going to refer to my folder as tools):
Code:
[email protected]:~$ mkdir tools
[email protected]:~$ cd tools
[email protected]:~/tools$ git clone https://github.com/aureljared/mkboot_and_mkrecovery.git
[email protected]:~/tools$ cd mkboot_and_mkrecovery
[email protected]:~/tools/mkboot_and_mkrecovery$ ./copy.sh
The script copies the tools into your /usr/bin folder, but will ask for root permissions nonetheless.
Take note that you will be typing mkboot into the terminal, not mkbootimg.
Any progress, guys? =>
You know even though i wouldn't have a clue what I'm doing, i gave it another go, and even stuffed things up more than i did before, so I'm leaving it up to you guys, but at 64 I'm not afraid to give it a go.
Sent from my GT-I8730 using xda app-developers app
So guys is CM 10.2 working on the Galaxy Express ?
Hiro Nakamura said:
So guys is CM 10.2 working on the Galaxy Express ?
Click to expand...
Click to collapse
No. Problem with kernel.
Sent from my GT-I8730 using Tapatalk
aureljared said:
No. Problem with kernel.
Sent from my GT-I8730 using Tapatalk
Click to expand...
Click to collapse
Explain the problem, maybe we can make other developers understand and help, that we know from other phones and kernels.
Been doing a bit of experimenting. Flashed @KINGbabasula's rom and as reported stuck on the samsung splash screen, buzzes twice and reboots. Tried flashing a s4 mini kernel over it . Long shot but no joy.logic was as cwm came from the s4 mini and they are close cousins so might work.
Built my own cm10.2 using the tutorial provided by @aureljared using the KINGbabasula Git repository. First. Installed using the older cwm. Same result as KINGbabasula's rom. When i updated the cwm and had another go it gave me the same errors we saw on page 26 with assert failed. At least helps me spot errors in my build. Don't get the error with KINGbababasula's build.
Bazzan
Svennen said:
Explain the problem, maybe we can make other developers understand and help, that we know from other phones and kernels.
Click to expand...
Click to collapse
Okay.
CyanogenMod automatically packages boot.img with its own kernel, right? Well, that kernel doesn't boot on this phone (I don't know why).
So far we have tried numerous builds, even got to the point of using the stock kernel, all to no avail. The events below simply occur when we try booting CM:
1) phone stays at phone logo, goes black, vibrates twice, and reboots only to repeat the process; OR
2) phone stays at phone logo, then screen slowly maxes out brightness making screen extremely hot (has to press and hold power to reboot)
Also, since our CWM is from the S4 Mini (which has extremely close specs to ours) repackaged with stock kernel and correct addresses, @bazzan here tried repackaging the boot.img with a kernel from a cm-10.2 build for serranoltexx (this is what you did, right?), also to no avail.
So right now we are stuck on rooted stock 4.1.2 with CWM 6.0.3.7.
Take note: mkbootimg does not use the same addresses as the stock boot.img.
* load addresses:
kernel: 0x80208000
ramdisk: 0x82200000
tags: 0x80200100
* cmdline = console=null androidboot.hardware=qcom user_debug=31
Click to expand...
Click to collapse
Any developer aid would be greatly appreciated.
Sent from my GT-I8730 using Tapatalk
bazzan said:
Been doing a bit of experimenting. Flashed @KINGbabasula's rom and as reported stuck on the samsung splash screen, buzzes twice and reboots. Tried flashing a s4 mini kernel over it . Long shot but no joy.logic was as cwm came from the s4 mini and they are close cousins so might work.
Built my own cm10.2 using the tutorial provided by @aureljared using the KINGbabasula Git repository. First. Installed using the older cwm. Same result as KINGbabasula's rom. When i updated the cwm and had another go it gave me the same errors we saw on page 26 with assert failed. At least helps me spot errors in my build. Don't get the error with KINGbababasula's build.
Bazzan
Click to expand...
Click to collapse
Hi, i get this error too...
Can you update your rom backup?
thanks:cyclops: