Basically, due to a few of my friends having this phone and the lack of development here, I'm going to attempt to whip out a rom or two.
I plan to start with a stock rom, deodexed, zip aligned, optimized, bloatware removed, blur removed, ADW or GO launcher added..custom kernel..we'll see. I'd like to eventually port a few roms, but we really need a stable and legit Froyo rom to get anything stably ported.
At the moment, the only stock rom I have is a .SBF. Unfortunately I have no idea how to decompile this and the kitchen I plan to use won't do it either. I've tried ezxcodec, sbfcodec, and sbftool to open the file and none of which will work!
Currently I'm not around one of my friends with the phone, so I can't do this myself. We have some pretty bad weather conditions around here right now and I might not see him for a day or so.
So, what I need is a CLEAN nandroid. Preferably, fresh flash, root, nandroid..it would be great if you could run the optimizer script before nandroid also. As my testing time is somewhat limited since I don't have the device.
BUT please be sure this is a fresh flash with no sim card in or Google info ever entered...I don't want to accidentally get someone's private info.
Please send me a message if you can help me out and let's get the long over due development started.
Are you going to attempt to work with the Korean 2.2 ROM or the 2.1?
I think the 2.2 would be the one that would most benefit this community at this point. I know that the biggest piece to the Korean 2.2 ROM is that it does not work in the 1700/2100 Mhz range to allow US 3G service. Maybe this is something that you could help us to fix?
No matter what you end up doing, it is much appreciated.
I think I could knock out a nice 2.1 rather quickly, enough to hold people over while I work on a 2.2 rom. A cleaned up 2.1 would be much faster, better on battery, and still maintain stock functionality and stability..and would only take a little work to be released.
Has the radio issue been explored at all yet or is it still unknown to the cause? I could certainly work on Froyo, as a stable-ish 2.2 rom would lead to the ability to port other roms to the XT but I want to get a stable 2.1 out first.
The other problem is that I don't actually own the device, so testing is somewhat limited..
Either way, I need a nandroid before I can get started with anything because nothing seems to decompile these SBF files.. :-/
custom kernel? just curious how are you going to flash it in? are you aware that the bootloader is locked?
i've got a spare xt720 at home, i'll try to do a flash install and upload the nandroid when i have time.
Thank you.
Crap I forgot about the locked bootloader..I come from all HTC devices and forget about how locked down Moto is.
There is a thread already working on a custom kernel, which once completed could be baked into a rom and flashed with open recovery. However, since there's no source released, it's still in development..
Back to the locked bootloader tho, what additional limitations does this place on custom roms? I'm assuming it means no custom roms? Which would mean that unless someone manages to unlock the bootloader we're limited to only official Moto roms/leaks? I hadn't even fully considered that issue...
Sent from my HTC Glacier using XDA App
Ok so from my understanding, due to the locked bootloader, any rom built around a custom kernel can't be fully ported and retain all functionality unless its somehow piggy backed on the stock kernel.
So a modded stock rom would work fine then, right?
Once a working open source kernel is out, either for 2.1 or 2.2, at that point we can begin to modify it to work with different rom ports.
I'm going to continue research and hopefully will have a clean 2.1 out soon, so there will be something to play around with.
Sent from my HTC Glacier using XDA App
I will upload my nandroid later tonight for u. U can get the system.img from a link on navalynts abandoned thread if u wanna start now. The boot.img i uploaded was from 2.1 (im an idiot) so ill upload the right one later.
I looked thru that thread and couldn't find anything useful..I'd greatly appreciate it if you can upload the nandroid, I would like a full nandroid of 2.1 and the 2.2 leak if possible (the original 2.2 nandroid was pulled), as I'm currently unable to find a way to recompile the official SBF files from Moto. I won't be able to work on this till tonight tho, so no rush on anything.
Sent from my HTC Glacier using XDA App
On one of the last pages of the thread someone posted the link. Navalynt took down. It only contains system tho. Yea i work all day so it wont be till tonight grill i can post it.
Thanks man. Please do 2.1 first so we can get a stable/clean/fast rom out, then work on the Froyo issues, since it seems to be very buggy at the moment!
Hopefully will have a stable rom and a WIP rom ready by the weekend. Since testing is limited, it may take a little while longer than desired, but this forum knows how to wait lol..
Related
2708 kernel only!
I give to you my leaving present....it seems to be fully working,no lag and everything working..All i did was add some files,delete some,change some bits in the build.prop and in the updater script.
My phone will be gone from tomorrow so i provide no support,no updates and am not responsible for any broken phones etc etc...
The name....
Called EZ FRankenCYAN because its a bit of all their work therefore i take NO CREDIT! All i did was use bits and pieces from each of their efforts.
By the way i did it all on my Magic so big thanks to Astro File Explorer!!
I have been using this for the last couple of days and get a respectable 4.4+ linpack scores,Please enjoy as i have and as the new phones owner will.
Thanks to EzTerry, FireRat and CYANogen team.Hopefully i wont annoy anyone by putting this up!
Im now off to the Hero Section again to goodbye for now!
Usual stuff,wipe before you flash backup etc
DOWNLOAD HERE!
Do you have any pictures of the ROM?
May I ask where you pulled the kernel from exactly? I have a 32A Magic and a G1 to test this on. I want to know if this is the same as the ordinary custom Froyo kernels with a modified init, or just a plain customized Froyo kernel.
Is this a fork from ezterry's 2.3 aosp?
or the same? thx..
anyone tried this?
downloading now
bonesy said:
2708 kernel only!
I give to you my leaving present....it seems to be fully working,no lag and everything working..All i did was add some files,delete some,change some bits in the build.prop and in the updater script.
My phone will be gone from tomorrow so i provide no support,no updates and am not responsible for any broken phones etc etc...
The name....
Called EZ FRankenCYAN because its a bit of all their work therefore i take NO CREDIT! All i did was use bits and pieces from each of their efforts.
By the way i did it all on my Magic so big thanks to Astro File Explorer!!
I have been using this for the last couple of days and get a respectable 4.4+ linpack scores,Please enjoy as i have and as the new phones owner will.
Thanks to EzTerry, FireRat and CYANogen team.Hopefully i wont annoy anyone by putting this up!
Im now off to the Hero Section again to goodbye for now!
Usual stuff,wipe before you flash backup etc
DOWNLOAD HERE!
Click to expand...
Click to collapse
Listen up, breh... You can't just dump this on the forum and then run off.
Yeah, kinda akward... How can you expect someone to use this without any support.
do you know if it's 2.3.3 ?
Its 2.3 and yes i can dump it and leave!
Unless you want to buy my a bloody Magic!
Anyway Yoshua has taken over this development
HERE
So after seeing many things that is said with the D2 I thought I should write a post like this. This is just to clear up confusion so users can have the knowledge to use in the future.
Every ROM for the D2 is AOSP
I have seen this said many times and it bugs me that people think that all ROMs are AOSP. As of now, there are actually only a few AOSP ROMs for the D2, cvpcs' Tanzanite/Obsidian, Cobalt, and blackdroid's Ultimate Droid. Other ROMs like rubiX, Liberty, ApeX, and Fission are basically Motorola ROMs with the blur applications replaced with AOSP applications. Now this does not actually make it AOSP. It has features from AOSP, but there is much more to it than the applications. These blur-based ROMs actually have other AOSP-like features, such as lock screen music controls and a few others. Now that also doesn't make it AOSP, those are just a few features that were originally modifications to AOSP to add more functionality to a ROM. That doesn't mean these ROMs are bad in any way. They are actually very good. The only downfall of them is the fact that they are limited to what can be done.
There can't be AOSP ROMs without a custom kernel.
Another statement I have been told or have seen several times. It is considered AOSP if it comes from Google's source. A kernel won't affect the fact that it was built from source. Although it would be ideal for a custom kernel with AOSP, it isn't needed.
A custom kernel is needed.
This is another incorrect statement. It would be nice to replace the kernel, but it isn't needed. The kernel that is provided to us from Motorola includes basically everything the end user would need. Also there is overclocking(although it isn't the easiest implementation) by adding a temporary module to the kernel that is erased after the phone is powered off.
Gingerbread won't come to the D2 until Motorola releases a new kernel with their Gingerbread update.
Incorrect. What the original concern was that Gingerbread would not boot with a .32 kernel(the kernel the D2 has.) and that it needs a .35 kernel. This was later proven wrong with D1. The D1 has been running Gingerbread for a bit now with a .32 kernel. Now I know people will say it is is a different kernel or something along those lines, but that doesn't matter. Gingerbread will boot on it without needing to replace the current kernel.
Fantastic post. Very clear, informative and I learnt more in the 2 minutes reading your post than the hours I've spent reading other threads.
Top stuff.
"Most truths were once deemed blasphemy"
Whats taking so long for Gingerbread then?!
Nice write up, very informative.
Matt, can you check out the MIUI thread in D2 development? Another developer and I are working on the port but we need someone with really good D2 experience to look over the rom and tell us why it gets stuck on the moto logo each time, we would really appreciate it if you could check it out for us.
Thanks,
ljbaumer
P.S. nice post it's really clear and will help out noobs.
ljbaumer said:
Matt, can you check out the MIUI thread in D2 development? Another developer and I are working on the port but we need someone with really good D2 experience to look over the rom and tell us why it gets stuck on the moto logo each time, we would really appreciate it if you could check it out for us.
Thanks,
ljbaumer
P.S. nice post it's really clear and will help out noobs.
Click to expand...
Click to collapse
Matt I would have to ask nicely along with ljbaumer, if you wouldnt mind taking a look at the rom dev section for the MIUI D2 rom!
I know you lost your D2 and no longer have it but anything could help them w/ progress
Would be greatly appreciated! Thanks!
Someone should sticky this thread cause it is really useful information
Gingerbread won't come to the D2 until Motorola releases a new kernel with their Gingerbread update.
Incorrect. What the original concern was that Gingerbread would not boot with a .32 kernel(the kernel the D2 has.) and that it needs a .35 kernel. This was later proven wrong with D1. The D1 has been running Gingerbread for a bit now with a .32 kernel. Now I know people will say it is is a different kernel or something along those lines, but that doesn't matter. Gingerbread will boot on it without needing to replace the current kernel.
Click to expand...
Click to collapse
This is now irrelevant, take a quick jaunt over to MDW where P3Droid has released full stock moto gingerbread builds for both D2 and DX in update.zip formats (new blur builds). Only catch with them at this time is that no one has figured out how to root them yet, but you can restore back with a previous SBF.
What differences could be expected if GB were to be paired with a .35 kernel rather than the .32 kernel of the current Moto GB leak?
bladearronwey said:
This is now irrelevant, take a quick jaunt over to MDW where P3Droid has released full stock moto gingerbread builds for both D2 and DX in update.zip formats (new blur builds). Only catch with them at this time is that no one has figured out how to root them yet, but you can restore back with a previous SBF.
Click to expand...
Click to collapse
I'm pretty sure they've rooted the GB builds... I had superuser access and could boot to recovery and everything. You do have to SBF back to them though, I learned that the hard way.
I am running the rooted Gb and loving it. I would love to see a cm7 version for the Droid 2
Sent from my DROID2 using XDA App
DX is supposedly getting the GB OTA, so the D2 should be next and soon!
FRESH OUT THE KITCHEN
STACKZzHOUSE PRESENTS TO YOU
SENSE 2.1 FULLY OPTIMIZED
ULTRA STABLE NOT A SINGLE PROBLEM(hopefully lol)
A LIL CELLSOUTH A LIL CDMA
BUT FIRST OFF
NOT RESPONABLE FOR ANY DAMAGE YOU DO TO YOUR PHONE
FIRST RELEASE PRETTY GOOD FOR FIRST
Code:
ROOTED
SUPERUSER:rolleyes:
DEODEXED
ZIPALIGN
APPS2SD BOILED IN(BAKED):cool:
WIRELESS TETHERING
CUSTOM BOOT ALLOWED
BASH SHELL:p
GOOD OLD PACMAN GAME HEHE
SOME BLOAT WAS REMOVED
MUCH MORE:D
WORKING ON GETTING MORE FREE SPACE 110MB AFTER INSTALL
LINK TO DOWNLOAD
http://www.mediafire.com/file/zvrmvvq6d5wle4l/STACKZzHOUSE_V1.0.zip
ONE MAN TEAM
[email protected]
Quick question. Is this Ginger bread 2.3, Froyo 2.2, or Eclair 2.1?
I know its sense 2.1, but what android version is it?
alex_camacho said:
Quick question. Is this Ginger bread 2.3, Froyo 2.2, or Eclair 2.1?
I know its sense 2.1, but what android version is it?
Click to expand...
Click to collapse
Given the market icon that represents android 2.1, I'd wager it's just a modified stock rom...could be me, but wasn't this done more than enough times already? Like almost 2 years ago? Android 2.1 is completely obsolete and nobody really wants it anymore...plus, liquidsense and nfx are already the best 2.1 roms out there...nothing can really be done to improve on them...OP, why not just use Android 2.3? I could just ruu and root if I wanted this
Holy Miracle Batman! It's alive! (Been trying to flash ROMs all week trying to revive this HERO from the dustbin...all other ROMs have been stuck at the HTC screen and bootlooping.)
Thanks for making a ROM that works for my HERO...now I got music at the gym! Just in time too...3 minutes to spare!
alex_camacho said:
Quick question. Is this Ginger bread 2.3, Froyo 2.2, or Eclair 2.1?
I know its sense 2.1, but what android version is it?
Click to expand...
Click to collapse
this is straight from stock sprint and a lil stuff from overseas versions
SiNJiN76 said:
Holy Miracle Batman! It's alive! (Been trying to flash ROMs all week trying to revive this HERO from the dustbin...all other ROMs have been stuck at the HTC screen and bootlooping.)
Thanks for making a ROM that works for my HERO...now I got music at the gym! Just in time too...3 minutes to spare!
Click to expand...
Click to collapse
glad to hear
goliath714 said:
Given the market icon that represents android 2.1, I'd wager it's just a modified stock rom...could be me, but wasn't this done more than enough times already? Like almost 2 years ago? Android 2.1 is completely obsolete and nobody really wants it anymore...plus, liquidsense and nfx are already the best 2.1 roms out there...nothing can really be done to improve on them...OP, why not just use Android 2.3? I could just ruu and root if I wanted this
Click to expand...
Click to collapse
its probably was done alot but this my first time modding a rom so i decided to start with an old phone with it on stock if you knew its stock then maybe the post didnt apply to you ,,just saying i know for a fact theres people who is looking for this just like the guy who wants it for music in the gym
money2392 said:
its probably was done alot but this my first time modding a rom so i decided to start with an old phone with it on stock if you knew its stock then maybe the post didnt apply to you ,,just saying i know for a fact theres people who is looking for this just like the guy who wants it for music in the gym
Click to expand...
Click to collapse
That's good job man. Ive been wanting to learn how to do this stuff but i just never get around to it.
You took a step in the right direction. Keep up the good work.
good to have another stock rom easily accessible, thanks for this
Multilingual ?
Does this rom support Multilingual?
Thanks
hey money,
if you want to reduce rom size, offer anything non-system essential in an optional update.zip. i see from screenshots you have pacman and nba, those could be offered in a separate zip. if you need any help at all doing this, feel free to ask, and ill help as much as possible. keep up the good work, i know you will go far.
maybe also if we feel froggy we can adapt aroma to your rom and let users choose exactly what they want and dont want?
also i see your on cellular south, maybe offer a separate update.zip for a sprint fix? this would include mms.apk from a sprint stock rom, sprint eri.xml, and telephony.db from a sprint rom. that way both carriers are supported.
So I found a tool on XDA that allows me to put the ROM of choice to be ported and the base ROM. I'm trying to port Paranoid Android 2.00 since we don't have it, and now that we have somewhat steady CM10 nightlies I *should* be able to use it as a base. (The tool is called RomPorter)
So I went ahead and compiled a ROM, but I'm not sure if I should flash. I mean if it was this easy to port ROM's wouldn't we have ROM's just popping up everywhere? I used the HTC One X International version's PA 2.00 as the input ROM btw. I have some coding experience in Java but if it's this easy to port without any coding required why hasn't it been done yet? Just curious. I looked at the CM9 guide to porting PA and I have to make a linux portal and all those things. Basically my main question is, will this work? I don't want to flash and end up hard bricking my phone. I went and checked the build.prop, and framework and it all seemed like a hybrid of CM10 nightly and Paranoid Android 2.00 but is there something I'm missing?
Thanks a lot guys! I'm tired of just being somebody who stands on the side and waits for things to get ported or created. I'm taking a heavy load in college but I want to try and port something at least to contribute.
Using the international base could cause a brick unless you ported an evita kernel too. The international one x has a different partition layout as well.
Read read read, check, double check and triple check. When your confident its possibly bootable, sure that it is not harmful THEN flash it to your device first. Ports are always going to start with bugs. Don't expect perfection, expect a WIP. Importantly, have fun learning. Most importantly , FIRST FLASH IS ALWAYS YOURS :beer::beer:
Added People port roms all the time for themselves. Now posting one on xda and maintaining a thread with dozens-hundreds of followers is a WHOLE DIFFERENT STORY
I just want to try it but I'm afraid it'll brick. I mean what's the worst case scenario? Boot loop then restore to my nandroid? Or being stuck with a brick forever? I don't have a backup phone at the moment lol. Maybe I should invest in one.
If you flash something that overwrites hboot you're hard bricked. That's what I meant by different partition layout.
Here's a easier start for jb paranoid Android port.....dload the HTC evo 4g lte jb paranoid port rom, unzip it, delete the included boot.img, use a hox boot.img from a hox jb rom to replace it with. Zip it and flash it.(use the one XL cm10 boot.img) It will give u a bootable port of jb paranoid Android. Then like most ports, you will start fixing bugs. Camera and wifi won't work, you will need to fix those for sure. But a lot will work so start with priority bug fix#1 and keep on goin
Added: paranoid android rom I would consider the land of the brave for first time porting. U may encounter fixes to be harder than some less modified roms.
I understand now what the scare was. But when taking the Evo LTE ROM and pushing our own boot.img it'll allow me to at least get it started to see what I need to get going and fix! That's a fantastic idea. I'm going to head over there now and see what ROM's they have. I mean technically we share very similar devices internally right? I haven't looked into the Evo specs much.
Shaddy-Z. said:
I understand now what the scare was. But when taking the Evo LTE ROM and pushing our own boot.img it'll allow me to at least get it started to see what I need to get going and fix! That's a fantastic idea. I'm going to head over there now and see what ROM's they have. I mean technically we share very similar devices internally right? I haven't looked into the Evo specs much.
Click to expand...
Click to collapse
make sure you pull out any radio images you find in the roms you look at.
Could I push the ones from a cm10 nightly?
No idea. Probably. Or just don't include one.
getting in contact with the developer for the Evo PA ROM. Hopefully this goes somewhere.
Don't we already have a pa rom? You've inspired me though. I'm going to look at porting roms too.
The PA ROM is still ICS, and the biggest killer is that the multi-touch fix is not incorporated because the ROM was cooked pre kernel release unfortunately. The latest update the dev was supposed to release didn't boot and I don't know what happened after that.
And do it! The more devs the better. I want some variety in this little community.
By the way, PARANOIDANDROID 2.00 is not out yet. The last OFFICIAL release is 1.992: Changelog. As for the port, I would love to port roms to our device, since it is my primary device.
I already port ROMs from the i9100 to i777(SGSII Internation to AT&T US Version), but this is a VERY simple operation. And you can use a pre-made program to port by ktoonsez called Flashaholics, but it is only for porting to the i777. I hope we eventually get that far but these 2 devices are far more similar that the One X/OneXL or Evo LTE/One XL.
Just use the latest paranoid rom with the latest cm10 boot.img. I did it a few times when I had my hox. And gunny is right. Either pull the radio or flash a hox radio after u flash ur port and u will get signal with working talk, text. 3g should work too, mms won't, streaming video will be iffy. Just run thru the major stuff, write down what's broken, prioritize it, then always make a nandroid of your previous build so u can revert back if fixes make things worse
---------- Post added at 01:09 AM ---------- Previous post was at 01:03 AM ----------
He's gonna work off a unofficial paranoidandroid jb 4.1 from the evo lte. It'll boot but there will be plenty of fixing to do. I think its for his use/learning, not sure if he plans on putting it up on forums
I don't plan on uploading it to the forums unless I get the features working. I'm off all day tomorrow so I'll probably give it a shot to see what I can do.
I also realized PA is not 2.00 after I posted that, buts its still a JB Paranoid ROM so it'll do for now while I learn.
It's really good seeing someone (who isn't a regular dev that I know of?) taking such initiative and asking the right questions and such in order to get some dev'ing underway.
Great job! :good:
stnguyen09 said:
It's really good seeing someone (who isn't a regular dev that I know of?) taking such initiative and asking the right questions and such in order to get some dev'ing underway.
Great job! :good:
Click to expand...
Click to collapse
Thanks! I appreciate it So I got a little ahead of myself and tried it tonight, I'm slowly following a guide and I THOUGHT I was doing everything correctly but it won't flash after "Verifying system partition size" and I got an error. This seems to be a common problem that leads to the updater script, so I'm going to take a look at it when I get up. Could just be a syntax error, or maybe I'm just building it wrong I'm kinda tired
U can always nab the updater script from cm10 hox also. Its been a while and I forgot to mention that. I had the same issue with the evo rooms and that did the trick:beer:
I tried: using the ports updater, the base, and a collaboration of the two and it still didn't go through. Maybe its something else ? I'll try it again to double check.
Firstly, I'm not sure is it right section since it is not "development" but simply ROM cleanup, so Mods please move this thread to whatever appropriate section if needed.
When I started using this phone I was looking for clean, junkless stock ROM and I couldn't find any (there are variations on custom ROMs that resemble the stock one, but not the actual stock ROMs with junk removed, or at least I haven't found one). Finally I learned how to root my phone and I did it myself, but for long time I couldn't find cure nor reason for the small but annoying problem described here. Later I have found out how to fix it, and now I have pretty good stock ROM with all the "custom" junk apps and outdated apps removed. I am using it myself and I have no problems whatsoever with it.
I thought I can share my recovery backup of this custom stock ROM if anyone else is interested in it?
MT4GS said:
Firstly, I'm not sure is it right section since it is not "development" but simply ROM cleanup, so Mods please move this thread to whatever appropriate section if needed.
When I started using this phone I was looking for clean, junkless stock ROM and I couldn't find any (there are variations on custom ROMs that resemble the stock one, but not the actual stock ROMs with junk removed, or at least I haven't found one). Finally I learned how to root my phone and I did it myself, but for long time I couldn't find cure nor reason for the small but annoying problem described here. Later I have found out how to fix it, and now I have pretty good stock ROM with all the "custom" junk apps and outdated apps removed. I am using it myself and I have no problems whatsoever with it.
I thought I can share my recovery backup of this custom stock ROM if anyone else is interested in it?
Click to expand...
Click to collapse
not trying to shoot you down, but recovery backup sharing isn't recommended if i remember correctly
anitgandhi said:
not trying to shoot you down, but recovery backup sharing isn't recommended if i remember correctly
Click to expand...
Click to collapse
Just curious why isn't it?
Sent from my MyTouch 4G Slide using Tapatalk 2
Ide really like to try it out...im running miktouch stock its nice
Sent from my myTouch_4G_Slide using xda app-developers app
MT4GS said:
Firstly, I'm not sure is it right section since it is not "development" but simply ROM cleanup, so Mods please move this thread to whatever appropriate section if needed.
When I started using this phone I was looking for clean, junkless stock ROM and I couldn't find any (there are variations on custom ROMs that resemble the stock one, but not the actual stock ROMs with junk removed, or at least I haven't found one). Finally I learned how to root my phone and I did it myself, but for long time I couldn't find cure nor reason for the small but annoying problem described here. Later I have found out how to fix it, and now I have pretty good stock ROM with all the "custom" junk apps and outdated apps removed. I am using it myself and I have no problems whatsoever with it.
I thought I can share my recovery backup of this custom stock ROM if anyone else is interested in it?
Click to expand...
Click to collapse
Which version of the stock ROM are you basing this upon? Miktouch 0.7 is pretty much a cleaned up stock ROM, the last one that was released by HTC/T-Mobile (1.63.531.2). It still has some of the T-Mobile apps but they can easily be deleted.
Fuzi0719 said:
Which version of the stock ROM are you basing this upon? Miktouch 0.7 is pretty much a cleaned up stock ROM, the last one that was released by HTC/T-Mobile (1.63.531.2). It still has some of the T-Mobile apps but they can easily be deleted.
Click to expand...
Click to collapse
I didn't knew Miktouch is stock ROM (just modified/cleaned)
Well then it's probably same/similiar and there's no point.
1.63.531.2.710RD
with kernel 2.6.35.13-gf3a1982... 2012 Feb 03
MT4GS said:
I didn't knew Miktouch is stock ROM (just modified/cleaned)
Well then it's probably same/similiar and there's no point.
1.63.531.2.710RD
with kernel 2.6.35.13-gf3a1982... 2012 Feb 03
Click to expand...
Click to collapse
Yeah, that's the same as Miktouch 0.7. There's a few optional patches for Miktouch, as well: Liquid Smooth Rosie, Depaginated App Drawer, No Scrolling Cache, No Recent Apps or Genius Button patches.