Related
I decided to make my first custom rom. The main difference over klin1344's klassic is the fact that we can customize what we want with the aroma installer. As of now, there's no customised interface (and there will not be. Consider this like WT Ho's rom for the 5.0).
I stop working on it because I want to try something other than stock. Also thanks for your consideration for this rom. (I will continue the maintenance of it though)
Features:
- Stock 2.3.6 XXKPQ
- Rooted
- Busybox
- Deodexed
- Zipaligned
- Aroma installer: An interactive installer
- Multiple bootanimations.
- Choice between TW 3.0, TW 4.5, Go launcher EX, Xperia S launcher
- Possibility to install DSP manager and voodoo app (for sound enchance)
- Features the CWM 5.0.2.7 (Intl Only. Kernel based from steve's 3.0) (V.1.0)
- US users will recieve the latest klin's R2 custom kernel* (V.1.0).
- Intl and US compatibility in a single zip. (v.2.0)
- SuperSU (v.3.0)
Changelog:
Code:
[B]V.3.0 (Vita) FINAL [/B]
- Deodexed and Zipaligned
- SuperSU is used instead of SuperUser
- Updated Google Play Store, Maps and Youtube app (Can play 720p) (It's real this time)
- Possibility to add Antutu Cpu Master Free (For Overclock)
[B]V.2.0 (Radiance)[/B]
- Name changed only to Renaissance
- Possibility to chose the device type (Thanks to dark_valor's Terra Silent)
- New Honeycomb bootanimation
- Possibility to add terminal to the rom
[B]v.1.0 (Etincelle)[/B]:
- Initial Release.
Download:
1.0
Intl: Intl Renaissance 1.0 Download
US: US Renaissance 1.0 Download
2.0: Renaissance 2.0 Download
3.0: Renaissance 3.0 Download
If you want there's the Xperia S Wallpapers: Xperia S Wallpapers Download
If there's a problem with antutu, install the apk here: Cpu Master Apk Download
If there's a problem with terminal reinstall it.
Instructions:
1. Boot into Cwm
2. Backup
3. Wipe data (BEFORE IT IS MANDATORY)
4. Run renaissance-device.zip
5. Follow the instructions.
6. Reboot
7. Enjoy!
If you do like please hit thanks button. If you have problem with installation, Send me .log file in aroma. If it's problem with the rom please let me know.
Thanks to:
amarullz: for Aroma installer
Klin1344, SteveS and stratosk for the kernel related things.
WT Ho for his base for aroma installer. (and help too )
GO Dev Team , Fr4gg0r and ra3al for their launcher
Dark_balor for his kernel (terra silent)
Jackpal for the terminal emulator
Antutu for the CPU Master
As this is the last version, If you want to use something in the rom (porting) ask me first.(Mostly for Aroma)
These are the possible implementations (suggestions)
- Deodex
- Performance tweaks
- More customisation options
- Better compatibility with apps (Like deviceID hack)
reserved again
screenshots please?
EcHoFiiVe said:
screenshots please?
Click to expand...
Click to collapse
Oh sorry about that. I will put them tomowrrow. (that depends which screenshots you want?)
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Wheatly said:
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Click to expand...
Click to collapse
Well I didin't enable ext4 so data and dbdata will be stuck at rfs. Sorry about that.
Does the CWM 5 in the kernel I gave you work well? Because when I gave it to you there seemed to be a lot of errors... But if it does, I'll probably apply those changes back to my kernel again and update to cwm 5 because it allows easier converting to ext4. Also, did stratosk give you permission because I used his cwm recovery files from his sources. (just making sure, so he doesn't come and flame me for porting cwm5 from his sources without permission)
Sent using Tapatalk
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so everyone will have justice.
Click to expand...
Click to collapse
Ok thanks. But how exactly did you fix it? I didn't flash the kernel you gave me but where are your sources? (the Linux kernel is GPL licensed, so it's mandatory to have a source )
Sent using Tapatalk
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Dark_Balor said:
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Click to expand...
Click to collapse
He based it off stock rom. Tomorrow I'll figure out how he fixed cwm 5.0.2.7 from his initramfs.
Sent using Tapatalk
klin1344 said:
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
Click to expand...
Click to collapse
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
zaclimon said:
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
Click to expand...
Click to collapse
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
klin1344 said:
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
Click to expand...
Click to collapse
I made some changes to the init.rc and lpm.rc I think.
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
EcHoFiiVe said:
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
Click to expand...
Click to collapse
Because it is a stock rom (with multiple apps) I won't put screenshots. Once 2.0 will be released (UI modifications) I will put them. You can backup and try it?
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
Click to expand...
Click to collapse
zaclimon said:
I made some changes to the init.rc and lpm.rc I think.
Click to expand...
Click to collapse
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . I'm really discouraged and very tempted to just take down all my work for the Galaxy Player and just keep all the development to myself. Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
klin1344 said:
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
Click to expand...
Click to collapse
ok don't go blaming me BECAUSE IT GOT ERRORS when YOU sent it to me. I corrected some errors but I can't remember which ones is it. I can't get lucky if EVERY of my backups works(Because I got errors for md5 mismatch as well too). It is sure that your init files are the same because I used some of the text you used when you were building YOUR R1 kernel. (so basically I used some of your sources) but you were always complaining about ext4 not working so you gave up on CWMR5.0. and when I said I've fixed them you didin't tested it. DON'T GO COMPLAINING IF YOU DIDIN'T EVEN TESTED IT. (also check all the init files to be sure and also check the thanks it is `kernel related things`.) -___-
EDIT: If you want all the credits. You can have them. I should have said that you made all the changes but the problem was that you gave up on CWMR5.0 so I was like (The kernel works now but I won't release it because you already have your custom kernel with CWMR3.)
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?
Hey guys,
Do you believe it would be possible to get Team Win Recovery Project on our devices? Because it looks much better than clockworkmod and it has so great functions! But I don't know much about this recovery; if this is only for nexus devices or Samsung or whatever, I just wanted to ask
It looks like they took the AOSP recovery and built it on top, but do you think it would be possible on xperias?
Sent from my Nexus 7 running Android 4.2.1
Okay it looks like we could give it a try and compile it, so would anybody be interested?
Who wants to know what TWRP is could look here!
There is a working recovery for the Xperia S, so maybe we could get one, too? Any developer who would be interested in that?
mihahn said:
Hey guys,
Do you believe it would be possible to get Team Win Recovery Project on our devices? Because it looks much better than clockworkmod and it has so great functions! But I don't know much about this recovery; if this is only for nexus devices or Samsung or whatever, I just wanted to ask
It looks like they took the AOSP recovery and built it on top, but do you think it would be possible on xperias?
Sent from my Nexus 7 running Android 4.2.1
Click to expand...
Click to collapse
I am pretty sure it can be done, because I am pretty sure there is support for mdpi screens (320x480). Thomas1991_12 compiled it for the Ray and I know that it wasn't easy and that ChampionSwimmer helped him out with the dual ramdisk kernel. The instructions from dees_troy are pretty easy to follow but of course it didn't work right out of the box but Thomas1991_12 might be able to help you out. Here is the final product thread: http://forum.xda-developers.com/showthread.php?t=2046977 and here is the dev thread: http://forum.xda-developers.com/showthread.php?t=1948097. It is also working on the X8 at least for ics.
TWRP is really nice. It has some added features which are nice but it is also a lot faster than CWM, at least on my device.
justmpm said:
I am pretty sure it can be done, because I am pretty sure there is support for mdpi screens (320x480). Thomas1991_12 compiled it for the Ray and I know that it wasn't easy and that ChampionSwimmer helped him out with the dual ramdisk kernel. The instructions from dees_troy are pretty easy to follow but of course it didn't work right out of the box but Thomas1991_12 might be able to help you out. Here is the final product thread: http://forum.xda-developers.com/showthread.php?t=2046977 and here is the dev thread: http://forum.xda-developers.com/showthread.php?t=1948097. It is also working on the X8 at least for ics.
TWRP is really nice. It has some added features which are nice but it is also a lot faster than CWM, at least on my device.
Click to expand...
Click to collapse
I would like to see this done, too, but I'm no developer at all, never did anything regarding kernels. I could try to get the recovery image, but I wouldn't know what to do after that. And if there are many errors I couldn't go on, so maybe a "real" dev could do it
Do you think we could even try to do this with cm10.1 cyanogenmod sources or better sync to cm9?
Edit syncing my repos to cm9, let's see how it works!
Okay I'm trying it on cm9, what to do with this error? I thought there was something to delete but not sure
Code:
make: *** Keine Regel vorhanden, um das Target »bootable/recovery/res/images/icon_firmware_error.png«,
benötigt von »out/target/product/mango/root/res/images/icon_firmware_error.png«, zu erstellen. Schluss.
Can you help me?
EDIT: Got it by deleting the whole #PRODUCT_COPY_FILES like explained here, but after flashing with
Code:
fastboot flash boot recovery.img
I get the FreeXperia logo and a black screen. What to do now?
mihahn said:
Okay I'm trying it on cm9, what to do with this error? I thought there was something to delete but not sure
Code:
make: *** Keine Regel vorhanden, um das Target »bootable/recovery/res/images/icon_firmware_error.png«,
benötigt von »out/target/product/mango/root/res/images/icon_firmware_error.png«, zu erstellen. Schluss.
Can you help me?
EDIT: Got it by deleting the whole #PRODUCT_COPY_FILES like explained here, but after flashing with
Code:
fastboot flash boot recovery.img
I get the FreeXperia logo and a black screen. What to do now?
Click to expand...
Click to collapse
obviously, debug. as its been said by justmpm it wont just work out of the box just like that. u probably need to to ask Thomas1991_12 what he changed in the source to get it working for ray. since all xperia 2011 gen share similar hardware, ray config should work for other 2011 phone too with minimal changes.
an0nym0us_ said:
obviously, debug. as its been said by justmpm it wont just work out of the box just like that. u probably need to to ask Thomas1991_12 what he changed in the source to get it working for ray. since all xperia 2011 gen share similar hardware, ray config should work for other 2011 phone too with minimal changes.
Click to expand...
Click to collapse
I wrote him a PM, hope he could help me :good:
Can't thank you for now because the 8 thx limit
mihahn said:
I wrote him a PM, hope he could help me :good:
Can't thank you for now because the 8 thx limit
Click to expand...
Click to collapse
I think Thomas1992_12 might be taking a holiday, as he isn't replying to questions in his kernel threads.
I never tried to compile with cm9 but with cm10 the black screen is where I got stuck. Thomas1992_12 was able to get past this point and if I remember correctly, the problem is with init.rc. If you check the ray dev thread, he has a solution for getting past it. After you fix this, you will
probably face the "ghost touches" on the screen and then you will have to figure out how to boot into recovery. Again, Thomas and/or ChampionSwimmer will probably be able to give you the fixes. But don't give up....you are really close!\
justmpm said:
I think Thomas1992_12 might be taking a holiday, as he isn't replying to questions in his kernel threads.
I never tried to compile with cm9 but with cm10 the black screen is where I got stuck. Thomas1992_12 was able to get past this point and if I remember correctly, the problem is with init.rc. If you check the ray dev thread, he has a solution for getting past it. After you fix this, you will
probably face the "ghost touches" on the screen and then you will have to figure out how to boot into recovery. Again, Thomas and/or ChampionSwimmer will probably be able to give you the fixes. But don't give up....you are really close!\
Click to expand...
Click to collapse
Thanks, I really want this project to be done!
First I downloaded the TWRP bootable/recovery sources as a zip, but the zip was named ..-jb-..zip so now after some research I'm trying it with ...-master-...zip and I hope I will get past this black screen. The init.rc is the one from TWRP, because I replaced the whole bootable/recovery folder with the files/folders from the master zip...
I think I will ask championswimmer, but I guess he is very busy, because he's such a great dev! :good:
GUYS I GOT IT! WORKING!!! TOUCH IS WORKING VERY WELL!!!
BUT!
I just flashed the cm9 FXP kernel and after that I flashed the recovery image. I plugged off and powered on and it's booting straight into TeamWinRecovery 2.2.2.1, hope somebody could help me to get booting in system.
Time is wrong, but touch is working guys
Will upload it for testing purpose if you want :good:
Working:
Touch
File Manager
Settings
Terminal Command
Onscreen Keyboard
Flashing Files
Wiping Cache/Dalvik Cache
Backup
Locking Phone in Recovery
Need to test:
Mount usb (not working in linux, will test with windows tomorrow)
Restore
Changing time zone
Not working:
Booting into system
Click to expand...
Click to collapse
mihahn said:
GUYS I GOT IT! WORKING!!! TOUCH IS WORKING VERY WELL!!!
BUT!
I just flashed the cm9 FXP kernel and after that I flashed the recovery image. I plugged off and powered on and it's booting straight into TeamWinRecovery 2.2.2.1, hope somebody could help me to get booting in system.
Time is wrong, but touch is working guys
Will upload it for testing purpose if you want :good:
Click to expand...
Click to collapse
You the man!!! You the man!!!
ChampionSwimmer has the fix for getting it to boot correctly. The one set up on the ray has dual recovery: hit the power key and you go into twrp, hit vol dwn and you get cwm.
Keep up mihahn, I want TWR so bad, that I can't sleep
Come on mihahn! You can do it!
Sent from Hubble Telescope
Okay guys I will upload it for testing and wait until Championswimmer can help me :good:
Okay guys go here if you want to see the progress or try it yourself
Ramdisk Hijack - what is it?
- We are trying to load a custom ramdisk in order to be able to load a non-Sony based ROM on a locked bootloader using 2nd-init. This is a work in progress.
How can I help?
- My source code is here: https://github.com/keiranFTW/huashan_ramdisk-hijack also, you will find how to install this on there too.
You'll probably wonder why I'm trying to hack the stock ramdisk in - because my phone is my only device, I also need to use it as a phone. Once I can fix things this way I can move to using CyanogenMod Ramdisk.
Progress? CyanogenMod is currently booting on the phone but there are lots of non-working features.
This is not a ROM, do not install this unless you know what you are doing.
On completion I will give you this in form of an update.zip
#keiran
Any developers willing to help me out here?
I am busy with personal work, will check this out later... FYI you can't boot everything on same kernel... Specific kernel patches are required for some ROMs... Without those patches crucial rom features may not work...
Sent from my C6902 using xda app-developers app
DooMLoRD said:
I am busy with personal work, will check this out later... FYI you can't boot everything on same kernel... Specific kernel patches are required for some ROMs... Without those patches crucial rom features may not work...
Sent from my C6902 using xda app-developers app
Click to expand...
Click to collapse
I know this, and some of these kernel patches can be loaded as a module or even the ROM source code edited to suit the needs of the stock kernel.
Edit: I have had many people asking me if kexec could work, and the answer is no, probably not. Why? Because it requires a in-kernel patch as well as a module and so it is not possible to get it to work as we cannot flash a new kernel.
I have an idea and I'll start to merge changes soon
Sent from my C5303 using Tapatalk
I am not experienced in kernel dev but maybe i can contribute in limited extent.
Unluckily, i also got "NO" in bootloader unlockable and very dissappointed to see that.
I hope someone will be able to find an alternative.
Have you looked at this?
http://www.xda-developers.com/android/locked-bootloader-xperia-s-and-want-cm10-no-problem/
Work in peace...
OP
can you link me to some good references about chroot? I got the basic understanding, want to try it on linux on my laptop.
Closest analogy i can draw is the linux live cd, which runs the OS live without installation. If thats the case, and if we succeed in this process, we could use some partition to dump cm and run it from there.
But lets not get too far, im still in infancy stage.
Regards
Yasir
finally Got the basics of what you are doing... You are essentially doing the same thing letama atis112 and company did to run cm10 usng stock kernel, but hijacked stock ramdisk to run cm ramdisk.... Seems a good idea but will only work for CM10 (4.1 based) and later when locked bootloader gets 4.3, we could get cm10.2 as well. If you are doing the same thing they did, then hopefully it will work soon. If its something different, then wish u luck, ill keep tracking ur progress.
Yes, he is trying to have it done the same way as letama, atis and others with one minor difference - we don't have pre_hwconfig.sh, so he's trying with chargemon. Older ramdisk Keiran's github worked fine, but after some commits he made it doesn't boot. When I try with older ramdisk and newest step2.sh, everything except sdcard works fine. I have an idea - what if we kill every process with every possible way(killall5, pkill,etc) and then start it manually, by calling them from /system/bin? Maybe it's the way.
Some offtop here:
Maybe the kernel from leak works on locked BL's? If DooM haven't changed anything in it - it's very possible. Maybe someone with 4.3 leak on their phone would try locking the bootloader?(Of course only if that person knows how to unbrick, if something goes wrong).
MrSteve555 said:
Yes, he is trying to have it done the same way as letama, atis and others with one minor difference - we don't have pre_hwconfig.sh, so he's trying with chargemon. Older ramdisk Keiran's github worked fine, but after some commits he made it doesn't boot. When I try with older ramdisk and newest step2.sh, everything except sdcard works fine. I have an idea - what if we kill every process with every possible way(killall5, pkill,etc) and then start it manually, by calling them from /system/bin? Maybe it's the way.
Some offtop here:
Maybe the kernel from leak works on locked BL's? If DooM haven't changed anything in it - it's very possible. Maybe someone with 4.3 leak on their phone would try locking the bootloader?(Of course only if that person knows how to unbrick, if something goes wrong).
Click to expand...
Click to collapse
I assume you have the same issue of unlockable BL? anyways, i am waiting for 4.3 so that after playing with, we can try and run cm10.2 at least... + miui
I've redone your work, and i can succesfully hijack ramdisk...
I've CM booted up, but:
1. graphical glithes (i know the solution)
2. no baseband
3. no sdcard (inner, external)
But it's improvement
Source: https://github.com/dh-harald/hijack-ramdisk-huashan
dh.harald said:
I've redone your work, and i can succesfully hijack ramdisk...
I've CM booted up, but:
1. graphical glithes (i know the solution)
2. no baseband
3. no sdcard (inner, external)
But it's improvement
Source: https://github.com/dh-harald/hijack-ramdisk-huashan
Click to expand...
Click to collapse
If my girlfriend would let me and I was near you I would kiss you right now :*
Jokes aside, I think I might be able to fix SD card and the rest
Sent from my C5303 using Tapatalk
I dont think any processes with late_start class are working... This would explain SD and also network.
Try:
/system/bin/sdcard /data/media /mnt/shell/emulated 1023 1023
/system/bin/qseecomd
/system/bin/secchand
Anything really..
When I was hijacking ramdisk before but loading the stock ramdisk just for testing I also lost network as well as sdcard, and I'm sure that I lost WiFi too. A possible solution would be *not* to stop these services maybe?
Sent from my C5303 using Tapatalk
New source code is at: https://github.com/keiranFTW/huashan_ramdisk-hijack
- Updated to work with Android 4.3
- Using 2nd-init instead of chroot
- Recovery included (not sure if working)
#keiran
hijack
Hy
I modified the hijack source and recompiled the cm10.2 was.
hijack
dev tree
vendor blobs
I made a new thread on xda.
bagyusz said:
Hy
I modified the hijack source and recompiled the cm10.2 was.
hijack
dev tree
vendor blobs
I made a new thread on xda.
Click to expand...
Click to collapse
Hey,
Thanks, your changes have helped a lot, so I have expanded on them to make it possible to integrate into AOSP more easily. I also use /system/bin/chargemon instead of system/bin/wipedata, it is earlier in boot process.
I also might want to note that you are not killing all processes, you need awk {'print $2'} instead of awk {'print $2'}
But yeah, great work.. you did what many others couldnt.
My repositories:
dev tree
vendor blobs
hijack
Feel free to add pull requests, and i can add you to the repository if you like.
Keiran
If only this could be done in other devices, as I also have a locked Xperia, but it's a Live Walkman. Unfortunately it also has the Unlock Bootloader: "NO", so if could also be ported to other devices it would be great. Not forcing or pushing you, but trying something more updated than 4.0.4 would be great
is this...?
@KeiranFTW & @bagyusz
sick work guys way to not never give up and accomplish what was thought to not be possible goes without saying one of the best development breakthroughs this year!
hey, in either of your opinions would this in some way be portable to our locked as **** bls on S4 Verizon and AT&T? We havent had ASOP capabilities or 4.4 for that matter yet and everyone is stuck on safestrap 4.3 stock kernels. Any help on this would be much appreciated. Its either trying to port this method or trying that new AnyKernel2.0 today not trying to hard brick heh
msm7x27
KeiranFTW said:
.
Click to expand...
Click to collapse
would this method work on any msm7x27 after pointing partitions ?? @KeiranFTW
deleted.
I still don't know what you're talking about. eace
Sent from my C5303 using Tapatalk
concerning hijack
KeiranFTW,
i am sorry to bother you with what may or may not be a 4 square dev question(s).
can i attempt something similar without building custom kernel? ( i read evrything i can but, lack funds for proper hardware so am limited.)
can i alter the insmod-ing of kernel modules to come as close to the beginning of the boot process as possible and have hardware functional in spite of slaying zygote/android userspace ?
this thread http://forum.xda-developers.com/showthread.php?t=1937328 outlines a means to
mount?load? a loop device from init.rc
my thought is as i have a gt-p5210 x86 device it might be possible to fire up (no matter how ugly)
a livecd or straight forward ext4 linux.img.
I would be interested in any insight/ideas you may have toward that end.
thank you for your time.
m
Hi,
Just wondering if/when MadCatz will release the kernel?
I know linux being GPL, it has to be shared, but not sure about Nvidia's sources?
I'm new to android but not java(my day job) and linux.
I've compiled and installed my own kernels on desktop and on my mobile phone (Nokia N900).
I want to try and add a few things.. ie filesystem/DVB/webcam support etc.
Following this how to.
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
Sweet! many thanks :victory:
:highfive:
:good:
omg.... does this mean we can finally have a cifs module!? AWESOME!
So now that the kernel source is avialable, I'm looking forward to the first custom kernels. Would be great to have some kernel optimizations and other tweaks built in :good:
RollingRoman said:
So now that the kernel source is avialable, I'm looking forward to the first custom kernels. Would be great to have some kernel optimizations and other tweaks built in :good:
Click to expand...
Click to collapse
Yes i hope someone can make a kernel to re-apply resolution settings on the m.o.j.o, as mad catz said to me via a phone call some tv's can't adjust to 1080p natively because the os is preventing it,and stupidly they removed the resolution changing slider in settings don't ask me why they did that?
If there is a way to set resolution without endangering the console booting up afterwards would be awesome,i am thinking it is there but hidden away and accessable some way but don't know how,developer options can be opened but not resolution settings as far as i have found any way.
PHYSC-1 said:
Yes i hope someone can make a kernel to re-apply resolution settings on the m.o.j.o, as mad catz said to me via a phone call some tv's can't adjust to 1080p natively because the os is preventing it,and stupidly they removed the resolution changing slider in settings don't ask me why they did that?
If there is a way to set resolution without endangering the console booting up afterwards would be awesome,i am thinking it is there but hidden away and accessable some way but don't know how,developer options can be opened but not resolution settings as far as i have found any way.
Click to expand...
Click to collapse
I think it automatically sets the resolution based on the TV/monitor, try a different one?
TMK, the slider has nothing to do with the kernel.
gwaldo said:
I think it automatically sets the resolution based on the TV/monitor, try a different one?
TMK, the slider has nothing to do with the kernel.
Click to expand...
Click to collapse
I would do that but i only have a panasonic 50" plasma it's a 600hz 1080p it p50x50b model,there are 2 variants of it a hd ready and a 1080p model,i know it's the 1080p model as i used blu ray and xbox 360 and a wiiu etc in 1080p modes so it's definately not 720p only on my model.
I still think it is possible to reinstate that hdmi resolution slider though? I would love for someone to find a fix for that to bring back the slider though.
It also has nothing to do with the overscan as that's off,and the guy said it's an argument between the console's os and the tv,but maybe if i had an option to change resolution within the console when in operation it would ammend this,resolution changer pro works then looses usability eventually and it's awkward and time consuming to get that to work,only for it to stop after a time?
There is no forced hdmi resolution setting in the tv menu unless of course there is in engineer mode but all that seems to do when entered is show test and it's results coming up as ok,after testing it factory resets the tv as well so sick of trying that now.
Someone needs to get a custom rom made up with kitkat and 1080p natively set.
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
Unable to untar the tar.gz file. It says "tar: kernel/drivers/net/wireless/bcm43341/src/include/proto/p2p.h: Cannot open: Not a directory" and there are many lines like this. Tried everything from sudo, sudo -s, chmod, chown....
Also it says cannot mkdir: is not a directory
Its a .h and .c files ofcourse they aren't directories! Its not letting me execute make without errors since my source is like crap crawling with this "NOT A DIRECTORY"
Nothing is working. Command used was tar xvfz mojo-jb-kernel.tar.gz with many combinations and OS is Ubuntu 12.04 LTS 64 bit...
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
Can you help me. Is there any other place from where I can get source?
Thanks in advance..
Kingshoo said:
Can you help me. Is there any other place from where I can get source?
Thanks in advance..
Click to expand...
Click to collapse
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
gwaldo said:
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
Click to expand...
Click to collapse
It doesn't time out but it says some .c and .h cannot open: Not a directory when I use tar to extract it. Then I thought that I should install something else to extract and tried ARC. It extracted and then the same message box as appeared in windows 7 OS "file already exists cancel or overwrite"
I then said overwrite and then I get the extracted package. I just want to ask you that when you extracted it did you got any errors? What procedure you used to extract it? I downloaded twice with same results...
gwaldo said:
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
Click to expand...
Click to collapse
OK as per your suggestion I used wget c and the address. That gave me again the same file and upon extracting it I am getting same errors.
May be that the file isn't corrupted as you can extract it and its possible that I am doing something wrong in extraction..
I tried to create the kernel from sources and got a make error, to remove that I must delete a line in the make file (Line no 603) and after that I can successfully compile the zimage. But the issue is that after completing the procedure for boot.img file the original and compiled one has a difference of 0.1 MB and device don't boot with the newly compiled boot.img
Please if you can provide me with the steps on how you exctracted it and which OS you are using?then it will be really helpful. Also can you please upload the makefile of kernel and config.gz file you are using to make the kernel...
One useful information that can prove that there is an issue in extraction:
Extracted content on windows OS with Administrator priviledges: 42889 items , 487.8 MB
Extracted content on Ubuntu with Tar and other utilities: 42692 items, 482.5 MB
gwaldo said:
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
Click to expand...
Click to collapse
Seems like you are the only person who can help me as no one else seems to be active on MOJO development department. Sorry to disturb you again friend but you know I tried extracting on Android too and it failed there too!
I am completely exhaused with two days 24hrs of searching only extraction process. Please let me know if you successfully compiled and booted the kernel on your MOJO. If yes then I need more information from you as I had compiled the kernel but as I told you earlier it didn't worked... Please reply ASAP
Kingshoo said:
Seems like you are the only person who can help me as no one else seems to be active on MOJO development department. Sorry to disturb you again friend but you know I tried extracting on Android too and it failed there too!
I am completely exhaused with two days 24hrs of searching only extraction process. Please let me know if you successfully compiled and booted the kernel on your MOJO. If yes then I need more information from you as I had compiled the kernel but as I told you earlier it didn't worked... Please reply ASAP
Click to expand...
Click to collapse
Hi,
I'm in Aust. so there's a time difference.
I'm also about to leave on a 4week holiday and don't have my mojo dev stuff on my laptop.
I just used tar -vxzf filename
I think the only errors were a bad lsymbolic links which arent required.. from memory I could be wrong.
If you read the other threads here, I and someone else explain how we got the kernel compiled and yes it works fine.
http://forum.xda-developers.com/showthread.php?t=2691985&page=2
You dont use their makefile you recreate it .
If this is your first linux kernel or even android kernel, it's a tricky process and it takes time research all the steps.
Good luck
gwaldo said:
Hi,
I'm in Aust. so there's a time difference.
I'm also about to leave on a 4week holiday and don't have my mojo dev stuff on my laptop.
I just used tar -vxzf filename
I think the only errors were a bad lsymbolic links which arent required.. from memory I could be wrong.
If you read the other threads here, I and someone else explain how we got the kernel compiled and yes it works fine.
http://forum.xda-developers.com/showthread.php?t=2691985&page=2
You dont use their makefile you recreate it .
If this is your first linux kernel or even android kernel, it's a tricky process and it takes time research all the steps.
Good luck
Click to expand...
Click to collapse
I have gone through with the links you provided already and I understand every bit of conversation. Yes I am new to kernel compiling but its reasonably understandable.
I respect your valuable answer no matter when you reply since you have a minute for me and don't worry about TimeZone differences as I am not in a great hurry, I just don't wish to waste time on errors for which I ain't responsible
OK I tried compiling modules for which I had to compile the kernel to get the module.symvar file and "THE MODULES WORK!" that too with the Default kernel Makefile and ofcourse my own module Makefile.
"You dont use their makefile you recreate it" this line you wrote.. What do you mean by that??
I mean were you talking about the kernel Makefile or our own module Makefile, Please clear me here? As far as I know the Kernel Makefile should be the same when only compiling the stock kernel as that is my purpose "JUST TO COMPILE THE STOCK KERNEL"...
My compiled kernel boots but just shows a black screen! I don't want to spoil your holidays sincerely but if some help I can get from you then I will be able to relieve me from this burden
Hmm got it compiled finally even after that make issue with -k flag to make
Also all I needed was ramdisk from latest OTA and not the one from the kernel. That was the issue with kernel booting but it freezing at blank screen...
RESOLVED :highfive:
Kingshoo said:
Hmm got it compiled finally even after that make issue with -k flag to make
Also all I needed was ramdisk from latest OTA and not the one from the kernel. That was the issue with kernel booting but it freezing at blank screen...
RESOLVED :highfive:
Click to expand...
Click to collapse
Glad you got it working.
Re the makefile, I think you have to run config first to check your systems compilers/linkers/etc which then creates the makefile.
:highfive:
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
is there any reason this is done via some random ftp server and not some place like github/bitbucket with better management? or heck even sourceforge would be an improvement.
is that account for developer outreach? are there any datasheets on the components used in the device? sony does a beta program for updates on their flagship devices have you considered doing something similar where people can grab images and help test updates? ever think about tossing the device trees up for aosp to help encourage a porting of 3rd party roms and spread the community?
the nook color and touchpad being hack and having Cyanogenmod and the like being ported to it drove sales up, i would imagine having a hackable android console that isnt some no name chinese brand would probably do decent. unfortunately now with android tv you guys have some serious competition on the horizon, its a matter of how you go from here and try to make the most of it so everyone already has your product and doesnt need another.
edit: i also see there is several updates yet only one kernel source... any chance of updated source?
@Mad Catz Rich
The new update (205-TS) has a new kernel build of May 2nd.
Any chance that can be put on the server?
from http://madcatz.com/mojo/en-ca/
Ready to Root
As any Android power-user knows, the best way to get the most out of your device is to root it. Root access opens up all sorts of options including adding custom keymapping capabilities and installing custom ROMs. Mad Catz provides a short step-by-step guide to rooting, and our tech support team is ready to help.
The best part – rooting won’t void your warranty.
Click to expand...
Click to collapse
Please help, tech support team!
We need custom ROMs!
make kernelversion
3.4.35