[DEV] Samsung Galaxy Express GT-I8730 - Samsung Galaxy Express GT-I8730 ROMs, Kernels, Rec

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:

Related

[ROM][5.0] CyanogenMod 9 - possibly nightlies, post your thoughts

Okay almost got camera. Anybody have any ideas on camera please let me know. And I haven't been working on it to much because I've been spending most of my time getting jellybean on the galaxy player.
Don't get mad at me if they brick your device. Infact treat them with a high chance of brickage, unless otherwise noted.
Source: https://github.com/gmillz
cm9:
Stable: Testing
Nightlies:here Not sure if I'm gonna do nightlies
Debloated:here Not sure about this either
gapps:gapps-ics-20120429-signed.zip
International patch: INTL_patch.zip untested so please don't try this unless you know what you are doing. And if you try this please start with your home button not working.
Navbar addon: Almost done. Testing
Okay I think I covered everything
Thanks:
cyanogen
ambrice
zaclimon
Samsung
JackpotClavin
Supermaster34
Okay first reboot to recovery...
Make a backup......
Factory reset........
Mounts and storage > format system.......
Advanced > Wipe Dalvik Cache.......
Install Rom......
Reboot......
If you find something that doesn't work, get a logcat......
Anything I'm missing? let me know
Build Instructions.
For those people that want to help but aren't sure where to start.
Okay first you need ubuntu or linux mint installed and setup.
I might make a guide on how to do this eventually.
But here's the guide.
1. Make a working directory and cd to it.
Code:
mkdir ~/cm9
cd ~/cm9
2. Initialize the repo.
Code:
repo init -u git://github.com/CyanogenMod/android.git
3. Sync the repo. (this will take a while)
Code:
repo sync
4. Get the device tree and vendor files.
Type: gedit .repo/local_manifest.xml
Paste this in the text editor:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="gmillz/device_samsung_venturi_usa" path="device/samsung/venturi_usa" remote="github" revision="ics" />
<project name="gmillz/vendor_samsung_venturi_usa" path="vendor/samsung/venturi_usa" remote="github" revision="ics" />
</manifest>
5. Choose the device.
Code:
. build/envsetup.sh
lunch cm_venturi_usa-eng
(notice the period in front of build)
6. Build
Code:
make -j4 bacon
7. If its successful the rom will be in out/target/product/venturi_usa/
This is a great idea! I will test your CM9 build.
THE EDIT: SystemUI FC'S. After wiping everything. Also, is theme Chooser working for cm9? And did you happen to fix anything/upgrade anything in cm7? Will also post feedback on cm7. And yes changelog please. Sorry if I annoy you haha
ANOTHER EDIT: DO. NOT. FLASH. CM7! Gets your player bricked, stuck on Sammy logo, can't boot into recovery! Do not flash!!
Sent from my YP-G70 using xda app-developers app
Thanks for your hard work, looks great...
Great work! Much needed!
Will help testing ASAP if needed/possible. And on the other hand, I saw your CM10 build section empty. Are you posting anything soon?
Sent from my YP-G70 using xda app-developers app
YoBob said:
Great work! Much needed!
Will help testing ASAP if needed/possible. And on the other hand, I saw your CM10 build section empty. Are you posting anything soon?
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
I have a few cm10 builds, but for some reason they won't install properly it hangs on flashing the kernel
gmillz said:
I have a few cm10 builds, but for some reason they won't install properly it hangs on flashing the kernel
Click to expand...
Click to collapse
Check your updater script. Might have some issues there. Also does anyone know why the system UI crashes? I'll see if I can fix it tomorrow
Sent by my Robot Butler
Supermaster34 said:
Check your updater script. Might have some issues there. Also does anyone know why the system UI crashes? I'll see if I can fix it tomorrow
Sent by my Robot Butler
Click to expand...
Click to collapse
with this one
Nope, you just boot up and it tells you that it's crashed and that's it. I was going to replace the .apk of Jackpots CM9 with this one and see if it would work, but I'm recovering my Galaxy Player from a brick
EcHoFiiVe said:
with this one
Nope, you just boot up and it tells you that it's crashed and that's it. I was going to replace the .apk of Jackpots CM9 with this one and see if it would work, but I'm recovering my Galaxy Player from a brick
Click to expand...
Click to collapse
How did you brick?
gmillz said:
How did you brick?
Click to expand...
Click to collapse
Haha you didn't read my other edit did you? Your CM7 Nightly bricked my playaa! It's cool though as I am recovering right now! Couldn't boot into CWM so back to Odin3
EcHoFiiVe said:
Haha you didn't read my other edit did you? Your CM7 Nightly bricked my playaa! It's cool though as I am recovering right now! Couldn't boot into CWM so back to Odin3
Click to expand...
Click to collapse
Sorry. Guess I gotta do a lil more with the kernel source. I'm rebuilding it with the prebuilt kernel for now
New build posted
@gmillz so you are saying that it may be possible for you to port CM 9 and CM10 to the Galaxy 4.0?
Wow, ambitious goals considering that we don't have a booting ICS kernel yet on the 4.0. Do you plan on forming a team? I tried too early on, but it fell apart after awhile. Good luck to you!
EcHoFiiVe said:
with this one
Nope, you just boot up and it tells you that it's crashed and that's it. I was going to replace the .apk of Jackpots CM9 with this one and see if it would work, but I'm recovering my Galaxy Player from a brick
Click to expand...
Click to collapse
Yeah try replacing the apk file. Also Jellybean is soo smooth
Sent from my Nexus 7 using xda app-developers app
Supermaster34 said:
Yeah try replacing the apk file. Also Jellybean is soo smooth
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Damn you!!!!!!!!!!!!!! I wish I had a nexus 7 right now
I'm having some toruble compiling cm7 for the 4.0 player. it hangs when looking for flash_kernel
gmillz said:
New build posted
Click to expand...
Click to collapse
CM7 build? Also, if you are forming a team, I would be more than happy to be the beta tester!
EcHoFiiVe said:
CM7 build? Also, if you are forming a team, I would be more than happy to be the beta tester!
Click to expand...
Click to collapse
Yeah. A new cm7 build. It has the same name but its been updated.
And I may form a team.
You can definitely be the beta tester

Kernel Devs<<

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"!

Compiling CM9 for the Desire X - for noobs

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?

[DEV][WIP] Ubuntu Touch port for Dell Streak

I am working on getting Ubuntu Touch up on Dell Streak 5.
I got it up to the point when it boots, but crashes surfaceflinger, drmserver, mediaserver, servicemanager right after start and I could use some help. So I decided to share what I have so far. :fingers-crossed:
You will need:
CWM recovery (StreakMod recovery won't do; I use ClockWork-6.0.1.2)
saucy-preinstalled-touch-armhf.zip from http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/
cm-10.1-20130818-UNOFFICIAL-streak.zip from https://docs.google.com/uc?id=0BwLXYTrPyZc0YzFNQnlENjZQM1E&export=download
Flashing:
Reboot to recovery
Install cm-10.1-...-streak zip
Wipe user data / factory reset
Install saucy-preinstalled-touch zip (be patient - it takes A LOT of time)
You're done - reboot. Take a look at logcat.
THANKS:
This would not be possible without invaluable help of the following people
- giveen (CM10 android device files)
- nom051205 (CM9 android device files)
Sources:
https://github.com/smokku/android_device_dell_streak
https://github.com/smokku/android_kernel_dell_streak
To get started building on your own see https://wiki.ubuntu.com/Touch/Porting
DISCLAIMER
Please keep this thread technical.
Please restrain from praises - instead you can get me a beer (preferably of your own brew).
Please restrain from "this sucks and yo momma" comments - you will be quietly ignored.
Part of the problem is the need for a proper CM10.1 port. You've probably seen that in the porting guide. Also the ICS binaries/proprietary files will probably help you. Try it from our ICS port or grab from a similiar device.
Also try going back to quantal, as saucy requires a flipped image (loads ubuntu first, then android parts)
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/monthly-04.1/
Also this really helped get my device to display
Step 5. Download http://d-h.st/eFQ
Step 5a. adb push libc-2.15.so /data/ubuntu/lib/arm-linux-gnueabihf/libc-2.15.so
Step 6. adb reboot
Don't forget to set up your DPI conf file.
giveen said:
Also try going back to quantal, as saucy requires a flipped image (loads ubuntu first, then android parts)
Click to expand...
Click to collapse
Is it really worth trying?
Assuming that it would work, it does not help me in getting saucy up, and running outdated release isn't really a goal.
Could you please describe what is changed in your libc-2.15.so? (Or point me to a post explaining the change)
smokku said:
Is it really worth trying?
Assuming that it would work, it does not help me in getting saucy up, and running outdated release isn't really a goal.
Could you please describe what is changed in your libc-2.15.so? (Or point me to a post explaining the change)
Click to expand...
Click to collapse
A guy has patched it,
Also I used this guys gits as they were easier to do deal with than ubuntu's weird system of updating their junk. Just add these to your manifests
https://github.com/f69m/ubuntu-phablet_libhybris
https://github.com/f69m/ubuntu-phablet_platform-api
giveen said:
A guy has patched it,
Click to expand...
Click to collapse
What is the nature of this patch?
giveen said:
Also I used this guys gits as they were easier to do deal with than ubuntu's weird system of updating their junk.
Click to expand...
Click to collapse
Yeah. They really suck at sticking with Bazaar.
Thanks for the tip.
smokku said:
What is the nature of this patch?
.
Click to expand...
Click to collapse
No idea, I didn't make the patch. If you look in those gits commit history, its in there somewhere.
Any progress @smokku ?
Sent from my Dell Streak using xda app-developers app
I'm still at the point where the system boots, but Ubuntu services are crashing right after. :crying:
So I moved to getting Android up, to have a working base to work on. See: http://forum.xda-developers.com/showpost.php?p=45668042&postcount=43
Most of the time you need a cm 10.1 port first.
Sent from my LG-P999 using Tapatalk 2
Maybe kernel 3.x can help you?
There is a thread of hunderteins and nop in the forum about the kernel 3.x.
Any progress yet..????
Sent from my Dell Streak using xda app-developers app
It won't happen until I find out why enabling devtmpfs makes Streak's kernel unbootable.
So far I found out that it fails on memory initialization then, but without serial console and kprint, I'm unable to debug this issue.
I found a process online in which ubuntu is flashed over streakdroid
Is it same or different.?
If used, is it smoother.?
Sent from my Dell Streak using xda app-developers app

[DEV ONLY]Xperia ZU kernel building instructions

I think the time has come to share the info about kernel development we've been keeping for ourselves until now. just be sure to ready the complete thread and not just execute everything without thinking. I won't be responsible for any bricks etc.
Warnings!!
- Only start with a kernel if you are a developer with knowledge about kernel developping.
- Always use the specific dt.img build for your kernel!!!!! Very important!
- Don't complain if it doesn't work when you do something wrong!
== Information ==
Let's start with some info first.
MSM8974 needs something new to build a kernel, this is called a dt.img. This basically is an img file which holds information about the board pagesize, kernel version and some other kernel related things. You can only use a specific dt.img with a kernel, this file needs to be generated by a binary called dtbTool. This bin4ry can be found in the Cyanogen repo's or you can download a prebuild one in this thread.
== Compiling a kernel ==
I'll skip this part for now, every kernel dev should know this part maybe I'll add it later.
== Generating a dt.img ==
Basically you will only need your kernel sources and the dtbTool binary, then you need to generate it using a command like this:
Code:
./dtbTool -o ~/dt_files/dt.img -s 2048 -p ./scripts/dtc/ ./arch/arm/boot/
This seems very simple but it's quite important when building a kernel for MSM8974, or other S800 boards.
After this step has been completed you will find your dt.img in a folder callled dt_files, this folder should be in your home of linux now.
== Making the actual boot.img ==
After making the zImage and dt.img you need to have your ramdisk and an mkbootimg adapted for the dt.img to make a booting/working kernel for our rhine board.
be sure the naming of your files is correct:
- zImage
- dt.img
- intrd.img for your ramdisk
You can generate it by using the following command:
Code:
./mkbootimg --base 0x00000000 --kernel zImage --ramdisk_offset 0x02000000 --tags_offset 0x01E00000 --pagesize 2048 --cmdline "androidboot.hardware=qcom user_debug=31 maxcpus=2 msm_rtb.filter=0x3F ehci-hcd.park=3 msm_rtb.enable=0 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y" --ramdisk initrd.img --dt dt.img -o boot.img
Let's get kernel development started for everyone!
== Extra ==
If you like my work consider donating me a beer
I was only thinking yesterday it was about time we had some custom kernels :victory:
binary files attached
Don't add the compile guide. The way it is now, we'll weed out the noobs, and if there's one thing we don't want, it's a half baked kernel roaming around the forum
Sent from my Z Ultra, using XDA Premium 4
LordManhattan said:
Don't add the compile guide. The way it is now, we'll weed out the noobs, and if there's one thing we don't want, it's a half baked kernel roaming around the forum
Sent from my Z Ultra, using XDA Premium 4
Click to expand...
Click to collapse
I didn't added it for that reason
Sent from my Xperia Z1 using xda app-developers app
LordManhattan said:
Don't add the compile guide. The way it is now, we'll weed out the noobs, and if there's one thing we don't want, it's a half baked kernel roaming around the forum
Sent from my Z Ultra, using XDA Premium 4
Click to expand...
Click to collapse
No waaaaaay I wanted to build a kernel on my stuuuupid LG and then upload it as a Z Ultra kernel and then tell:
"What???? Isn't that working? That's impossible, you MUST have done a mistake. My work is perfect. Wait what? Isn't this the stoooopid 2X forum?? Sry guyz I did it for the lulz. "
Ok I lost it. I need my ZU back. I need it baaaad.
Jokes aside, great work krabappel, keep it up, as soon as I get my phone back I'm going to unlock the bootloader right away and try whatever kernel comes up.
Sent from my Nexus 7 using xda app-developers app
fastest83 said:
No waaaaaay I wanted to build a kernel on my stuuuupid LG and then upload it as a Z Ultra kernel and then tell:
"What???? Isn't that working? That's impossible, you MUST have done a mistake. My work is perfect. Wait what? Isn't this the stoooopid 2X forum?? Sry guyz I did it for the lulz. "
Ok I lost it. I need my ZU back. I need it baaaad.
Jokes aside, great work krabappel, keep it up, as soon as I get my phone back I'm going to unlock the bootloader right away and try whatever kernel comes up.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Ooh, you're using the 2X now? Poor soul! Let's hope you'll get you ZU back ASAP. I finally rooted mine yesterday (my two week rule was over) and I'm loving it. Installed Xposed and change some DPIs around. Still using the stock launcher, so I guess that's kind of weird.
I remember a dude over at the Note section modified a kernel and posted it. Things didn't go well, and several people bricked their device.
BUT let's keep things ON TOPIC guys (me). Btw, we should create a "general ZU chat" thread in the general section so people like me can speak without going off topic all the time.
Edit: I made the thread in the general section.
Sent from my Z Ultra, using XDA Premium 4

Categories

Resources