Related
Got bored again, this time I merged my device tree and fixes into CM7 Gingerbread ROM is built from the newest CM7 source code, and has been merged with the majority of my device specific fixes from previous ROMs. I love open source, so of course source code is available for everything, here (ROM), here (kernel), and here (initramfs). If you would like to follow the changes I make, check my github rss feed here.
*** WORKING ***
RIL (calls/sms/3g data)
WiFi
GPS
sdcard and USB mass storage
rotation and proximity sensors
screen on/off animation
haptic feedback
*** NOT WORKING ***
Camera/Camcorder
MMS
BT
most video codecs - Youtube playback (LQ & HQ) is broken for example - youtube does work from a browser if you use a desktop user-agent
Voodoo lagfix conversions
There are still plenty of bugs! and there likely will be until we have a true GB leak or official release to work off of.
PLEASE READ
It is considerably difficult for me to stumble upon every issue out there, and even more difficult to narrow these issues down, let alone fix them. That said, PLEASE do not clutter this thread with "thank you" or "X/Y/Z doesn't work" or "I'd love to flash this if..." type posts. I APPRECIATE THE THANKS AND THE FEEDBACK!!! Don't get me wrong. But these posts are not at all helpful in moving this ROM forward, and simply add more clutter to the forum. If you make such a post, don't expect a response.
If you experience a bug, PLEASE GET LOGS! I can't fix something simply by knowing that it does not work. A bug report without significant details is a useless post, it just is what it is. Logs help identify the code affected, and thereby help facilitate the fixes that we all love. PLEASE share your issues if you can provide helpful data in fixing them
THANKS FOR READING
The ROM package currently includes the base CM7 ROM, and a compatible kernel. Flash gapps from the package linked below. DO NOT FLASH ANY OTHER GAPPS OR KERNEL PACKAGES! The ROM package uses edify scripting, so it is flashable with any iteration of ClockworkMod recovery.
ALSO: devs and noobs alike please take notice : this ROM uses ClockworkMod recovery 3.x. I will no longer be supporting older recoveries!
Much thanks to the EpicCM and teamhacksung folks for code and ideas, and of course props to the CM team for all they do, it's their ROM after all.
If you appreciate the time and effort I have put into this ROM please click the "Thanks" or "Donate" buttons. Either one is fine by me
***** Update 4/26 - ALPHA2 *****
fixed USB mass storage
fixed haptic feedback
fixed TiBu 'whoami' bug
update to 3.x ClockworkMod recovery
sync'd with latest CM code
updated to latest Market
stubbed the camera (yes, I know it takes pictures of nothing but a green android )
** package still includes gapps and kernel **
** changed to new kernel that can be used with BOTH rfs AND ext4 - but it does not include the Voodoo lagfix code, so no conversions! **
** Make sure to wipe data even if coming from the previous alpha! **
***** Update 5/11 - ALPHA3 *****
updated to latest CM7 code (7.0.3)
enabled recent CM code to prevent "ring only once" bug (lightly tested)
made one of my sms hacks "optional" for easy editing by the mesmerize/showcase users (simply remove "ro.sms.padding=1" from build.prop to fix sms on these devices)
fixed some memory settings in kernel - should fix the lag experienced when using previous versions
added other tweaks to kernel for speed improvement (increased sdcard readahead cache/lowmemkiller/etc)
included punk-kaos' recent camera changes into kernel (cam not working, but getting there)
unstubbed camera (no more pics of a green android )
cleaned up my build tree a bit for a smaller download for people building themselves
removed gapps from ROM package, download from link below (kernel still included in ROM package)
ROM package will no longer flash a recovery
switched to bmlwrite for flashing kernel (screen will no longer wig out during kernel flashes)
Instructions:
flash with Clockwordmod recovery
flash ROM first then flash gapps package
WIPE DATA! if coming from ANY other ROM
Don't worry about disabling lagfix or any of that nonsense, ROM will work whether you are using ext4 or rfs
ALPHA3
http://www.mediafire.com/?ziawa7ot8dhdq4k
GAPPS
http://www.mediafire.com/?ogylu5w024148lt
Enjoy and remember: If your phone breaks after flashing, YOU broke it! Not ME!
You work pretty quickly for someone who gets bored.
This may peg my level of knowledge but here goes. . .What logs would be most beneficial? Assuming alogcat is the standard method, there are a lot of different options of logs in there. Any specific ones that would be the most helpful in tracking down a bug?
Not trying to clutter, hopefully avoiding more in the future
dw77x said:
This may peg my level of knowledge but here goes. . .What logs would be most beneficial? Assuming alogcat is the standard method, there are a lot of different options of logs in there. Any specific ones that would be the most helpful in tracking down a bug?
Not trying to clutter, hopefully avoiding more in the future
Click to expand...
Click to collapse
any random bugs can usually be picked up from the main log. anything having to do with the radio (call issues/sms issues/etc) need the radio specific log
I'm not familiar with alogcat (market app right?), but the logs can be dumped using adb from a pc. ex:
adb logcat > logcat.txt
will dump the main log
adb logcat -b radio > radio.txt
will dump the radio log
thank you for your concern
Hey JT, I was talking to you on twitter today (@ScottColeBCS). I sent my email addy, I don't know if you got it. Let me know if you figure out a way for me to do that for you. Thanks Bro.
EDIT: Nevermind bro. I'm stupid. I just checked my email and saw that you sent the info I needed. Be expecting it.
I need to clean my keyboard...great job jt!!
Sent from my SCH-I500 using XDA Premium App
Thank you JT. You are a boon to this community. Have a beer on me.
Thanks Jt....good stuff
Sent from my SCH-I500 using Tapatalk
Sweet. So what are the chances this will bebe compatible with the Mesmerize eventually? I assume it is not currently.
Sent from my MIUI SCH-i500
What's the difference between this and the one you released on Twitter last night?
Hey JT, I know there are many thread junkies (like myself) who are constantly checking for bug fixes and updates. I also read in the OP that you said there will plenty of bugs still until we get an official leak. Does this mean that with what you have available to you at the moment the functionality will remain as is, or are you still plugging away at some of these issues? I ask this simply to see if we should be checking for updates. Not complaining one bit! I love this rom so far. Thanks a ton!!
running great
Sent from my SCH-I500 using XDA App
kidserious said:
Hey JT, I know there are many thread junkies (like myself) who are constantly checking for bug fixes and updates. I also read in the OP that you said there will plenty of bugs still until we get an official leak. Does this mean that with what you have available to you at the moment the functionality will remain as is, or are you still plugging away at some of these issues? I ask this simply to see if we should be checking for updates. Not complaining one bit! I love this rom so far. Thanks a ton!!
Click to expand...
Click to collapse
I will still make do with what we have. As far as what that entails, who knows. One thing I'm relatively sure of is the fate of the camera. It's likely to remain non-functional until we have a GB base to work with.
You are the man, man! Thank you so much that you do for us. You guys are awesome! Thank you again!
Sent from my SCH-I500 using XDA Premium App
jt1134 said:
I will still make do with what we have. As far as what that entails, who knows. One thing I'm relatively sure of is the fate of the camera. It's likely to remain non-functional until we have a GB base to work with.
Click to expand...
Click to collapse
Ok, Well I will take that as there is a definite possibility you will be able to fix some of the non-camera bugs. It lets me know that fixes for these issues are not out of the realm of possibility with current sources. JT, your new name is Mr. Fascinate (with a thunderbolt) Lol. Keep doing what you do brother, you're making a lot of people happy.
Did Punk.kaos stop working on CM7 too? If not, why don't you guy help each other?
What will be different between This rom and the Kaoscinate?
Sent from my SCH-I500 using XDA App
deaffob said:
Did Punk.kaos stop working on CM7 too? If not, why don't you guy help each other?
Click to expand...
Click to collapse
Apparently kaos has been MIA for quite a while now.
kallell said:
Apparently kaos has been MIA for quite a while now.
Click to expand...
Click to collapse
maybe he just likes the thunderbolt people better
Works damn good for an alpha.
This thread is now for bug reports/development only. Do not post in this thread any more until you have fully read the first four posts of this thread, and the first two posts of the Q&A Thread. If you post in this thread and it is clear that you have not read the posts indicated above, your post will be reported. For other discussion and "Is this a bug?" type questions, go to the Q&A Thread
Heeeeere we go! As LinuxBozo, one of the most talented developers in the Infuse community said, "Welcome to a new and sick, twisted world!"
Over in the Infuse community, we had an oddball device that had little in common with anything else. As a result, it was not easy to port ROMs from the I9000/Captivate. However, after LOTS of work, LinuxBozo pulled it off and came up with an automatic porting package that could get most I9000/Captivate ROMs running on the Infuse. As a result, it opened the Infuse community up to a massive variety of ROMs.
For the month since the I777 came out, people keep asking about I9100 ROMs. In general, the answer has been, "It should be possible, but no one other than designgears has done it yet." - I didn't have the time as I had too much kernel work to do. However, as the kernel is at a fairly mature and stable state, when someone asked for SensatioN to be ported, I figured it was time for a challenge.
I was successful, but encountered a few glitches. Tethering was broken, fortunately the Infuse community had the same issue and the same fix worked. Mic in calls was broken, just like CM7 - I finally got atinm's list of the blobs to swap out. As a result, nearly all of the challenges in porting an I9100 ROM to the I777 have been identified.
This is a package that should automatically port most I9100 ROMs to the I777. It has been tested by myself as follows:
SensatioN 1.8 by Crysis21 has been manually "Hellraised", and was the basis on which this package was developed. Do note that the author of this ROM tends to be unresponsive to porters. I asked for permission to release a ported ROM but never heard back.
VillainROM 3.0 was the first ROM to be tested with the attached package - it seems to work, if there are any problems, it is likely because I missed something in the permissions settings of the updater script. - Also, I have tested JKay's Deluxe Themes on VillainROM successfully - his thread is at http://forum.xda-developers.com/showthread.php?t=1154278 - You need to use the XXKI3 theme packages.
In general, XXKI3-based ROMs work. XXKI4-based ROMs may have issues with WiFi (see Known Issues below). I am working on compiling a more complete list in the Q&A Thread.
Please don't report bugs with ROMs to the upstream author of the ROM in the event that the bug was caused by Hellraising - unfortunately, it is going to be very difficult to identify when Hellraising caused a bug and when the ROM itself has a bug.
Instructions for the package:
Download an I9100 ROM to be Hellraised - must be CWM-flashable Gingerbread (ICS will NOT happen until after kernel source code becomes available, and if you spam me with 10000 "did you see this" links when it does I'll just go watch some TV. You have been warned.), and must be Samsung-derived (not CM7/MIUI/AOSP-based), ROMs distributed as Odin .tar files like Litening won't work. (I've tried...)
Download the package above
Unzip the ROM, check to make sure it does not have bootloaders. If it has Sbl.bin or param.lfs in it, RUN AWAY. No ROM developer should EVER include a bootloader without explicit warnings of this, if a ROM includes a bootloader it's a sign that it'll be **** in almost all cases. Similarly, param.lfs corruption can lead to a device that won't boot and I believe it can even break download mode. ROMs shouldn't be messing with this either without warning users.
Once you've done your safety check, put the ROM zip and the Hellraiser zip onto your SD card
Enter CWM
You should probably do a Nandroid backup here...
Wipe Data/Factory Reset - Some ROMs write apps to /data and you'll lose these if you wipe afterwards
Flash the ROM, DO NOT REBOOT, STAY IN CWM
Flash the Hellraiser package
Reboot and enjoy!
Known issues:
NFC files are included, but enabling NFC requires smali modifications to Settings.apk on some ROMs. (Starting to look like this is only for I777 stock-derived ROMs - VillainROM doesn't actually need any smali.)
Touching an NFC tag containing NDEF data will cause the NFC service to crash due to being unable to obtain STOP_APP_SWITCH permissions
Wifi tethering settings are not persistent and keep resetting themselves (At least on SensatioN and VillainROM) - Workaround for now: Enable tethering, THEN set the SSID and password, OR see http://forum.xda-developers.com/showthread.php?t=1335377&page=24
When initially setting up the ROM, it claims that network time is not available, and takes you to Settings - where you can check it to enable it and it works fine... Infuse Hellraiser had the same issue. Happens only once per flash so it's a very low priority.
When flashing other ROMs that do device compatibility checks (such as CM7), they will think you have an I9100 instead of I777. You need to flash an I777 ROM first.
Download links have been moved to the ChangeLog post (Post #2 below)!
Alpha 0.3.1 Release, 12/3/2011:
Download: http://www.multiupload.com/NUV8KDF9OZ or http://dev-host.org/4up if MultiUpload never comes back
Changes:
Only one - actually include Daily Driver 12/1/2011. People who flashed 0.3.0 only need to reflash Daily Driver from my kernel thread, no need for a full flash of Hellraiser.
Alpha 0.3.0 Release, 12/1/2011:
Download: PULLED, BAD RELEASE: Use 0.3.1 instead. If you already flashed 0.3.0, flash the 12/1 release of Daily Driver
Changes:
Update to some random kernel pulled from the wrong location on my hard drive
Overwrite /system/etc/apns-conf.xml with a "known good" one
Overwrite the CSC with a "known good" one
Home button haptic fix, courtesy of LinuxBozo of Infuse Hellraiser. Thanks to amtrakcn for pointing out that LinuxBozo's fix works on our device
Alpha 0.2.2 Release, 11/10/2011:
Download: http://www.multiupload.com/C1W5S6XW0R
Changes: Update to Daily Driver 11/10/2011 kernel (disables autoroot which broke root for a bunch of people), tiny installer script cleanups.
If root is working well for you, it is not worth flashing this
If root is broken for you, I recommend installing Daily Driver 11/10 and flashing ChainsDD's latest su package (linked from the DD thread's first post now). If you flash this it will remain broken, this only fixes new installs
Alpha 0.2.1 Release, 11/08/2011:
Download http://www.multiupload.com/ORQESFHVBT
Changes: Only one, replace Nfc.apk with the correct one. Fixes NFC service force closes.
Alpha 0.2 Release, 11/07/2011:
Download - PULLED due to excessive fail. Use 0.2.1 instead!
Changes:
Should now flash without the mount workaround trick after ROMs that unmount /system
Added NFC files from the I777 and one permissions XML - These combined with a small mod to Settings.apk will allow NFC to work. Will post details for ROM devs on making these mods soon. NOTE: Right now this only supports reading tags! Google Wallet support requires a LOT more work, if even possible! (Edit: I'm fairly certain it'll only be possible in CM7 - but I think I also know what's needed for the CM7 guys to get the rest of the way there.
Initial release, 11/06/2011:
Version - Alpha 0.1
Download - http://www.multiupload.com/9RJKKSBFZ0
How it works
Here's the details of how this package works.
1) This package replaces the modem with a known good I777 modem
2) It also replaces the kernel with an I777 kernel (Right now, Daily Driver 11/03 release) - This is half of the keymap fix. Also, DD 11/3 contains a fix that allows wifi tethering to work on both I777-derived ROMs and I9100-derived ROMs
3) It replaces two of the keymap files in /system/usr/keylayout/ - see http://forum.xda-developers.com/showthread.php?t=1313050&page=56 for details - thanks to MikeyMike01 and Dungeon47 for this one
4) It replaces most of the audio library files to fix the issue with outgoing mic audio in calls - this is the same fix used by Cyanogenmod 7 - see https://github.com/koush/proprietar...12f711197665edeb28522386a77a62da24bab#diff-28 for details, thank atinm for this one
Attached:
Hacked settings APK for VillainROM 3.0 - This, along with Alpha 0.2.1, should allow you to turn on NFC. May work on other XXKI3-based ROMs
For ROM Authors:
To get NFC to show in Settings, baksmali the Settings APK and open WirelessSettings.smali
Look for the line below:
Code:
invoke-static {p0}, Landroid/nfc/NfcAdapter;->getDefaultAdapter(Landroid/content/Context;)Landroid/nfc/NfcAdapter;
Delete the next two instances of lines that contain the word removePreference
NFC should then show in Wireless settings
Great work! I can't wait to try this out when I have some free time.
well aren't you awesome bro. Thanks a lot. This opens the door to a lot of good things.
this looks awesome i have to find a rom i want to try from their forums though since lite'ening doesnt work
Dude you freaking rock! Thanks so much for this! What is your donate link?
Sent from my SAMSUNG-SGH-I777 using xda premium
jgrimberg1979 said:
What is your donate link?
Click to expand...
Click to collapse
Under his Thanks Meter.
THANKS!!!
about to test it out with the sensation rom! Really appreciate the effort you have been putting in lately!
Entropy
What about Roms that have a different version of cwm recovery, for ex some of them have 4.x cmwr. Does your kernal that you including relash cwr 5.x?
Sent from my SAMSUNG-SGH-I777 using xda premium
Awesome, just awesome entropy
Let the flashing and testing begin! You are a genius sir.
Sent from my SAMSUNG-SGH-I777 using XDA App
jgrimberg1979 said:
Entropy
What about Roms that have a different version of cwm recovery, for ex some of them have 4.x cmwr. Does your kernal that you including relash cwr 5.x?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
CWM is in the kernel, and this replaces the kernel.
Entropy512 said:
CWM is in the kernel, and this replaces the kernel.
Click to expand...
Click to collapse
Awesome, what would be some of the reason why this would not work with some roms, since the package addresses most of the differences between the two phones? Is there something we should look for besides bootloader, that may stick out as a possible incompatibility?
Sent from my SAMSUNG-SGH-I777 using xda premium
jgrimberg1979 said:
Awesome, what would be some of the reason why this would not work with some roms, since the package addresses most of the differences between the two phones? Is there something we should look for besides bootloader, that may stick out as a possible incompatibility?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Thank you Entropy, can I use this with i9100 MIUI rom as well?
Sent from my SGH-I777 using xda premium
Entropy512 said:
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Click to expand...
Click to collapse
Home button is not working. I've went and flashed sensation twice, following your steps of course. Did you have the same issue?
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
Home button is not working. I've went and flashed sensation twice, following your steps of course. Did you have the same issue?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
You need to map the keys correctly...
Sent from my GT-I9100 using xda premium
Entropy512 said:
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Click to expand...
Click to collapse
Still not workin
Edit; to clarify audio issue on the sensation rom is still there
Sent from my GT-I9100 using xda premium
WANTED: Users to port SGS roms to the 4.0. You will need to know how to complete a full restore if something goes wrong, but that's it. I cannot go through the forums searching for good SGS roms, as I have several threads to manage, and a rom to work on. The steps are easy for you though, and if you port a rom I will add it in the OP.
First of all, I want to say that I take NO credit on any of these roms. All I did was port them over and add speed tweaks, or added ones that users have ported. If the rom creators or mods have any issue whatsoever with this thread, I will happily take it down, even though I think it would be a large contribution to the 4.0 community. I will continue to update this forum with info as I go along.
I, after a fortunate afternoon of boredom, have managed to successfully begin porting I9000 roms to our devices! Fortunately, they are similar enough that it boots without any modifications. I will put up here any ports that I make, and any that the users create. Note that these WILL NOT BE UPDATED! These are one-time ports, to be used and improved upon by the community. Anything that is broken now will stay broken, unless a user decides to fix/update it, then I will include it in the OP.
What *should* work in all ported roms:
wifi
GPS
home buttons
everything else
What will probably *not* work on ported roms:
Bluetooth
Camera
backlight on buttons
Ported roms:
~GamerzRom odexed V11-~
Link to original thread: http://forum.xda-developers.com/showthread.php?t=1656081
Added:
V6 supercharger, and build.prop tweaks from it.
init.d tweaks from my rom
ext4 filesystem
Advanced mount options
Auto zipalign and Database optimize
Removed apps that do not work on our Player (such as the Dialer)
Download:http://www.mediafire.com/download.php?ctuu2w295w2xlk6
~Saurom~
Original thread:http://forum.xda-developers.com/showthread.php?t=1388342
Ported download link:http://www.mediafire.com/download.php?csua40hkg1r3m86
~JellyBeanRom~
Original thread: http://forum.xda-developers.com/showthread.php?t=1260709&highlight=gb
Ported download link:http://www.mediafire.com/download.php?mgec81f3ifck221
~Ario Rom (ported by ChaosChris)~
Ported thread link : http://forum.xda-developers.com/showthread.php?p=29950015#post29950015
Original thread: http://forum.xda-developers.com/showthread.php?t=1536558
To use these Roms:
You MUST use a Gplayer kernel! GT-I9000 kernels will not boot!
A full wipe may be necessary with some roms if you encounter issues.
Converting (for porters)
Steps:
1. Download wanted rom (must be GB)
2.Move the zip to the internal sdcard
3.Reboot into recovery
4.Flash zip, then boot into download mode
5.Flash a SGP kernel
6. apply my mod pack to the rom, by either copying/pasting the system directory over the SGS rom's system directory, or by pushing it via adb, (eg. adb push /path/to/modpack /system).
7. Profit!
NOTE: after applying this, porters may want to remove non-working packages such as the dialer and mms, as they may cause issues with the end result if they are kept in. Do not delete phone.apk though!! This is required for the camera and some other things, and breaks stuff on certain roms. You have been warned.
NOTE: If you use this modpack, please give me credit, and link back to this thread so that more people can use it. Also, you should probably link back to the ported rom's thread as well, to avoid "ripping off" those devs.
Modpack:
Changelog
V1-
Preliminary release
Fixes wifi and GPS
Includes v6 supercharger and init.d tweaks
V2-
fixed vold.fstab so sdcard is mounted properly.
Download:
ModpackV1:
http://www.mediafire.com/download.php?diaq6im4i18ktf7
NOTE:Note that this is preliminary. It fixes everything listed, and attempts to fix some broken things. Your mileage may vary. This is not a cwm flashable zip! you much extract and adb push this over the existing system directory. This is mainly intended for porters, so users apply at your own risk. This will work, but is a very early release.
Modpack V2 (thanks to ChaosChris):
https://docs.google.com/open?id=0B9OVlH2Pl76DZk5Pa3lJVXlrYzA
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
iJimaniac said:
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
Click to expand...
Click to collapse
Yeah, it says that because it includes semaphore's kernel, which raises the max rom to 380, which we could do on our kernel's, but apparently that breaks a lot of stuff if you go much further then 350 (according to klin).
is the wifi fixed in your port or do we have to do your fix after flashing?
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
check over in the operation: ics for the 4.0 thread I believe they are already attemping to use the cm7 kernel to boot a cm9.
daniel644 said:
is the wifi fixed in your port or do we have to do your fix after flashing?
Click to expand...
Click to collapse
Yeah, it is fixed before you flash. Once I manage to iron out a few more bugs, I will probably release a "conversion pack" that fixes all the issues. I already have one that fixes wifi and gps, but bluetooth and camera have me stumped, and I do not want to replace the entire hw/lib folder, because some of these roms have lib optimizations, but I may have to.
Sent from my GT-I9000 using xda app-developers app
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that zaclimon has tried it, and he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable. I also believe that he said the issues may have been rom based, so here it goes, and wish me luck.
Sent from my GT-I9000 using xda app-developers app
hanthesolo said:
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that daniel has tried it, abd he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
zaclimon said:
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
Click to expand...
Click to collapse
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course . A lot farther out there, but maybe I can use a SGP5.0 kernel to get it booting. A LOT less likely, but hey, i'm experimenting .
EDIT: I cannot try ICS, since I need to reboot into recovery a second time, and I cannot do that, as I have the intl bootloader on my US device, and it would require it to be booting first.
hanthesolo said:
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course .
Click to expand...
Click to collapse
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
zaclimon said:
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
Click to expand...
Click to collapse
Well, thet camera shows a preview, but fails when a pic is taken, for some reason. Bluetooth does turn on, but is not seen by any other devices, and cannot scan for others either. I did do a little tweaking with Gamerz, so it will be even faster than it was already, which is pretty blazing! I have 2 more that I can put up (I have a preliminary package that I just adb push over the system files that works for now). I have also gotten the camera apk onto my rom, and it works really well! It doesn't take 5 MP pics, or record 720p video (which may be because I am using Terrasilent, which reduces the amount of Vram the system can have), but tap to autofocus and everything else works pretty well. I have a sneaking suspicion that the camera is soft limited, not hard-limited.
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
zaclimon said:
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
Click to expand...
Click to collapse
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
hanthesolo said:
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
Click to expand...
Click to collapse
Here's the vold.fstab if you need it
Okay, it seems that the zip hosed my partitions (converted them to yaffs2 and mtd), so I am going to perform a full restore, and just keep porting GB roms. As soon as you can get the usb gadget driver working, zaclimon, I guess I can keep working on it, but for now I will just keep to GB.
Two more roms up! I will probably not port any other unless I see an especially good one, but I will put up my mod pack tomorrow.
has anyone found out if the ported roms enable tv out or has someone found out if tv out support is in the i9000 kernal?
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
iJimaniac said:
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
Click to expand...
Click to collapse
what hardware does the galaxy s i9000 have that allows for tv out? I thought the galaxy s i9000 and the galaxy player 4.0 had the same gpu?
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