Related
I'm pleased to present my repack of the stock ROM for the HTC Vision! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know.
Remember that if you use this ROM, you do so entirely at your own risk!!
About MoDaCo stock ROM repacks
Unlike a MCR (MoDaCo Custom ROM) release, a stock ROM repack is as close to the stock ROM as possible. Only root / Superuser and an insecure boot image is added. The benefits of the repack are providing a rollback option in update zip format as well as providing an online kitchen to remove parts that are not required.
A MCR release of this ROM is also available!
Requirements
In order to use this ROM on your device, you must have a custom recovery image installed (Clockwork Mod).
THIS ROM SHOULD RUN ON BOTH THE G2 AND THE DESIRE Z!
Features
Repack of the 1.22.531.8 (OTA) ROM
Pre-rooted with su and Superuser Permissions by ChainsDD
Insecure boot image (ro.secure=0)
Changelog
Please see the post below this one for the changes in each release.
Installation
To install this ROM:
Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card
Restart your device in recovery mode
PERFORM A NANDROID BACKUP FROM THE MENU
Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM (unless you are coming from a 'Sense' ROM), however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is now available in the online kitchen - see the post below for details! In addition to the kitchen, a prebaked download is available.
DOWNLOAD
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
And finally...
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P
Changelog
11/Nov r1
Initial Release
Let me know how you get on people!
MCR'd version and Sense stock / MCR for both G2/Z to follow (soon)!
P
OMG
jaws drop
paul you da man
Hah, you ain't seen nothing yet... wait till you see what i'm dropping tomorrow!
P
Need a drink now, long day.
P
yes . Happy day.
Thanks.
Well done Paul, thank you!
So we need clockwork on the Z to make this work? hpw do i install clockwork on Z, only says G2?
got it flashed but keep getting "The process Android.process.media has stopped unexpectedly. please try again any ideas?
Media error hasnt come up in a while but ive been on wifi the whole time and i cant get 3G to pop up at all meaning i have no mobile data and APN's are correct
im in australia on OPTUS
shaunm1989 said:
So we need clockwork on the Z to make this work? hpw do i install clockwork on Z, only says G2?
Click to expand...
Click to collapse
check the EZ-DZ thread:
http://forum.xda-developers.com/showthread.php?t=835777
updated with easy S-OFF and clockwork tips
Radio
Hi.
Rom is fantastic, but where is Radio app ?
THX
How do we install the overclock kernel after flashing this rom?
foxfire235 said:
How do we install the overclock kernel after flashing this rom?
Click to expand...
Click to collapse
To do it with the vision_oc u need to use the file from the G2 Forums
You can actually use bacon bits with this rom. I over clocked to 1.5ghz with this rom and bacon bits, was fast as all hell, but I missed sense too much
JD
Sent from my HTC Desire Z Beast
Sweet. I just flashed bacon bits and it works great!
[ignore]Oops, posted on wrong post![/ignore]
Will this rom work on a North American Desire Z (850/1900/2100 WCDMA)?
Yes, it's working fine on my unlocked Bell D-Z.
Alright, here is the z4mod app at long last! This release needs a lot of testing for different devices still, so make sure you check the compatibility table below unless you know how to use Odin to flash back your original kernel. Thanks for helping to test this!
[size=+1]This is still in beta! If you know how to flash with Odin, please help test so all bugs can be found and fixed to allow for wider release![/size]
What is this?
Another lagfix. This one is a bit different from existing lagfixes though:
- Differences from OCLF: Uses native EXT/JFS instead of loopback mounts. Loopback mounts in linux can be a bit flakey at times, especially when they're on RFS. So this is generally better.
- Differences from lagfix kernels such as voodoo or sztupy's: These types of lagfixes are kernels compiled from GPL sources for specific devices. This can cause a number of issues, such as losing out on bug fixes in later Samsung kernels released after the GPL code, or differences in devices such as the I9000B, etc. z4mod also has (imo) a nicer design, in that it uses /etc/fstab for filesystem mounting, as well as keeping the convert scripts outside the kernel. It should also work across ALL (or many?) Samsung devices without changes!
How do I use this?
Install the app. Click the buttons. It should all just work. Let me know of any issues or complications! This is still in testing!
Device/firmware compatibility table
Samsung Galaxy S Devices
Stock Samsung
I9000 Stock Samsung 2.2 : WORKING
I9000 Stock Samsung 2.1 : NOT TESTED
I9000B Stock Samsung 2.2 : NOT TESTED
I9000B Stock Samsung 2.1 : NOT TESTED
I9000T Stock Samsung 2.2 : NOT TESTED
I9000T Stock Samsung 2.1 : NOT TESTED
I9000M Stock Samsung 2.2 : NOT TESTED
I9000M Stock Samsung 2.1 : NOT TESTED
Captivate Stock Samsung 2.2 : NOT TESTED
Captivate Stock Samsung 2.1 : NOT TESTED
Vibrant Stock Samsung 2.2 : NOT TESTED
Vibrant Stock Samsung 2.1 : NOT TESTED
Epic Stock Samsung 2.2 : NOT TESTED
Epic Stock Samsung 2.1 : NOT TESTED
Fascinate Stock Samsung 2.2 : NOT TESTED
Fascinate Stock Samsung 2.1 : NOT TESTED
Stock Japanese Docomo Galaxy S (SC-02B) : WORKING
Stock SHW-M110S (Korean SGS) : WORKING
Custom Firmwares
Any custom firmware that uses a stock kernel works as the stock kernel in the table above
Custom kernels that make use of changed filesystems or boot up scripts are unlikely to work at this time. Emphasis is on stock kernels currently.
Custom Kernels
BLN (backlight notification) custom kernel for GT-I9000 works
Voodoo kernels do not work
Kernels with heavily modified boot procedures such as rooted Vibrant kernels do not work
CFRoot kernel does not work.
DamianGto's kernels work
Other Samsung Devices
NOT TESTED
More info on z4mod
http://www.sgscompilebox.dreamhosters.com/about.html
Source Code
http://github.com/z4/z4mod
V0.9.2 Changelog
Fix for EXT2->RFS Conversion. Please update to this app version before using this conversion.
Other small bug fixes.
Conversion page now has scrolling text informing you of progress and any errors.
V0.9.3 Changelog
Critical: Upload kernel now passes binary MIME type to prevent corrupt kernels
Fixes for text in conversion screen.
Fix for 'mmcblk0p2' always being chosen for /data, even on devices that use 'mmcblk0p1'
Bug fixes for UI
Donations
Donate link is available at https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
quick question I need to disable vodoo before using this right ?
anyways im running vibrant rom ( axura ) on my rogers captivate ( i896 )
testing now
DAGr8 said:
quick question I need to disable vodoo before using this right ?
anyways im running vibrant rom ( axura ) on my rogers captivate ( i896 )
testing now
Click to expand...
Click to collapse
This probably won't work if you have a Voodoo kernel installed. The Voodoo kernel is unlikely to be patchable, since it's not native RFS, and does not use /etc/fstab.
RyanZA said:
- Differences from OCLF: Uses native EXT/JFS instead of loopback mounts. Loopback mounts in linux can be a bit flakey at times, especially when they're on RFS. So this is generally better.
Click to expand...
Click to collapse
I have a Vibrant and this is why I have avoided using the OCLF in the past. Many ROMs don't even need a lag fix. However, with that issue gone, I'll at least try it and report back on it.
RyanZA said:
This probably won't work if you have a Voodoo kernel installed. The Voodoo kernel is unlikely to be patchable, since it's not native RFS, and does not use /etc/fstab.
Click to expand...
Click to collapse
hey I forgot to mention I had flashed setiron's reoriented kernel on it , so yea result is could not patch kernel ..
I guess i have more test to do. But right now Im stuck with 0.12 problem.
I did test it
I knew it would not work.;-)
The thing i was testing was if you could do this on a kernel that has note been patched. Well you can press the button and the phone restart. I guess it try but failed and restart again.
Can you do a check on the kernel so you know its patched?
I thinking of ways happens if people try every kernel without the patch. It should point them to the website.
Instead of restarting the phone.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
can i use this with speedmod kernel?
DamianGto said:
I guess i have more test to do. But right now Im stuck with 0.12 problem.
I did test it
I knew it would not work.;-)
The thing i was testing was if you could do this on a kernel that has note been patched. Well you can press the button and the phone restart. I guess it try but failed and restart again.
Can you do a check on the kernel so you know its patched?
I thinking of ways happens if people try every kernel without the patch. It should point them to the website.
Instead of restarting the phone.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
Click to expand...
Click to collapse
It checks for a /z4mod/z4version file to determine if it's been patched already. If you are using an earlier patched z4mod kernel that doesn't have that file, then it won't work right. If you start with a stock samsung kernel then it should work fine.
specialex said:
can i use this with speedmod kernel?
Click to expand...
Click to collapse
Feel free to give it a shot, but the current emphasis in this 0.9 app release is on patching and lagfixing the stock samsung kernels. Once that is all working and bugfree across devices, then I will look more at supporting custom kernels. At present, any custom kernel that does not change the initramfs (in particular, the /init binary and init.rc mount options) too heavily should work fine.
Hey Ryan,
I patched the stock Vibrant JK2 kernel and it patched successful, however the conversion to ext2 did not work. Said it worked, rebooted, but I was still on RFS.
Whitehawkx said:
Hey Ryan,
I patched the stock Vibrant JK2 kernel and it patched successful, however the conversion to ext2 did not work. Said it worked, rebooted, but I was still on RFS.
Click to expand...
Click to collapse
Thanks for testing!
Could you upload the z4mod.log file in your sdcard? /sdcard/z4mod.log
Okay. Then its just because the bug in the latest z4build then.
That's why it tried to apply the change.
Z4ziggy is working on that problem
Hope he will solve that soon. Right know Im on stock filsystem with my new kernel. Lol.
Kind of fun to compare them.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
RyanZA said:
Thanks for testing!
Could you upload the z4mod.log file in your sdcard? /sdcard/z4mod.log
Click to expand...
Click to collapse
I just looked and there isn't one there.
Whitehawkx said:
I just looked and there isn't one there.
Click to expand...
Click to collapse
Hah... Okay that's pretty strange. What method did you use to root btw? Perhaps it's a busybox conflict of some type.
RyanZA said:
Hah... Okay that's pretty strange. What method did you use to root btw? Perhaps it's a busybox conflict of some type.
Click to expand...
Click to collapse
Hmmm the rom/kernel I flashed came pre-rooted. Now that I think about it, I was using the stock JK2 kernel but it has a custom init script to allow the use custom boot animations. Could this be effecting the conversion process by chance? Anytime I manually root though I use OCLF from the market.
Hey RyanZA,
I see that there is a list of devices in the first post but I dont see a listing for the GT-i9000M specifically. I see the i9000, i9000B and i9000T but no "M". Is there a reason for this? Is the i9000M considered in the generic i9000 family? Also...
A bit off topic here but I am curious to know if I root using z4root and need to unroot for warranty purposes, will it remove ALL traces that it had been rooted including Busybox and Superuser app?
I know that Samsung has issued a memo stating that if a phone shows up rooted to a service center that the warranty will be voided and Id really like to try this rooting method.
Also, as you are probably aware, the i9000M here in Canada has issues with internal sd card failures and I am curious to know if just rooting with z4root will possibly kill my internal sd?
Thanks...
Flashed my Epic using the DK05 2.2 Rom, ran Z4mod, get error: zimage test failed when i try and patch the kernal.
RyanZA said:
Feel free to give it a shot, but the current emphasis in this 0.9 app release is on patching and lagfixing the stock samsung kernels. Once that is all working and bugfree across devices, then I will look more at supporting custom kernels.
Click to expand...
Click to collapse
should probably put this on OP , less hassle probably .
if nobody else test it on the cappy ill flash to stock just to test ..
@DamianGto:
The problem is with CWM recovery - it's busybox-tar is not working properly.
I think I found a way to overcome this and I updated the git, so now CWM option should be working again.
Whitehawkx said:
Hey Ryan,
I patched the stock Vibrant JK2 kernel and it patched successful, however the conversion to ext2 did not work. Said it worked, rebooted, but I was still on RFS.
Click to expand...
Click to collapse
If you could paste the contents of the following 2 files we might learn more:
/z4mod/log/init
/sdcard/z4mod.log
Just installed on my device (GT-I9000 with official JPA just released today in Thailand)
It worked fine. I got 1730 from quadrant.
Thanks for your excellent job. ^__^
First of all, thanks a lot to franks.maia for your I9000B initiative and support and patience.
The kind of kernel published here are only stock kernels, which means the exact same code build by Samsung for Vibrant phones.
Of course, there's a difference: Voodoo lagfix 5 stable has been injected in them, with its extensions and also ClockWorkMod recovery as default recovery.
Voodoo lagfix converts /system, /cache, /dbdata and /data to Ext4 with optimized parameters for speed but also guaranteeing data integrity.
Also, it configures the write behavior of Linux to prevent lag from happening, plus apply some memory management providing a better balance than stock settings.
Also supported: custom boot animation, init.d scripts and an improved adb shell (new!)
This kernel also installs the su binary for your convenience. Only activated once you download Superuser App from market. If you don't want to "root" your phone, skip this part.
How do choose the version?
The best version is the closest to the one of the ROM / system you run.
If you use a custom ROM instead of an official Samsung one, ask your ROM dealer which one is closer
update.zip you can flash with ClockWorkMod recovery (not 2e or 3e) or SGS Kernel Flasher
JPD+Voodoo http://dl.project-voodoo.org/stock+...Voodoo-Froyo-I9000B-VJJPD-unsigned-update.zip
.tar you can flash with Odin or Heimdall
JPD+Voodoo http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-I9000B-VJJPD.tar
Note, please disable any other lagfix previously installed, especially OCLF-kind (the conversion to Ext4 would take ages)
These kernels are only for I9000B, available in shout America like Brazil, Argentina Chile and Peru. (thanks guys!)
Thank's a lot supercurio, we already have a ported speedmod kernel, and it's good to have this one too, oh, a little correction, I9000B it's available in Argentina too
Edit: What about a 2.2.1 kernel with all the features? (Voodoo sound, BLN, sharpness adjustment...) It's possible?
Also Chile and Peru.
Supersurio thanks for the kernel, at the beginning when I bought the device attempts to place the Voodoo, and the phone was bricked, i was felt hopeless and was from that experience that I began to flash with customs ROMs. Here we have of customs kernels and we install the Voodoo, but until now it did not get digital TV with this model, I think that this kernel can be Ext4 and TV. Thanks again.
Odin3 1.7
Hi.
Can you describe which options should be used with Odin for this kernel+recovery update?
When I first upgraded to JPA, and then to JPD, I just used the PDA option, and flashed twice (first attempts never worked, somehow).
Kind regards
Marco
man, i'll need to donate 4 u after that!!!
thanks
one question:
we can use this kernel with any ROM we want herer in XDA base in 2.2 and above, can't we?
digital tv working perfect?
BRAZOOKA!
Scary fuzzy characters during rom flash... Now stuck on the Boot Logo, with metal voices telling me to wait... I hope it doesn't screw up xD
I'll post results
HELL YEAH! SUCCESS!!!
And the difference from OCLF is HUUUUUUUGE
THIS IS DEFINETLY A MANDATORY PATCH FOR ALL I9000B USERS!!!
Helvio88 said:
HELL YEAH! SUCCESS!!!
And the difference from OCLF is HUUUUUUUGE
THIS IS DEFINETLY A MANDATORY PATCH FOR ALL I9000B USERS!!!
Click to expand...
Click to collapse
What about tv. It works?
Kernel working with what rom?
Everything works, including TV
Just flash it and you will see the difference!
By the way, say thanks for me, I tested a ROM lol (I want my first thanks )
nice job man, really god mod
but how can i undo the ext4 lagfix ?
Great Supercurio, donation really deserved.
Sent from my GT-I9000B using XDA App
ZedBR said:
nice job man, really god mod
but how can i undo the ext4 lagfix ?
Click to expand...
Click to collapse
You can do the unlagfix using clockworkmode included in the pack. There's an option in CWM menu. Take a look. Regards
Sent from my GT-I9000B using XDA App
ODIN Parameters
Hi all. Hey @Helvio88 (already "thanked" you )
Any special configuration for ODIN?
Can you or someone put a screenshot if it before hitting the "gogogo" button?
Thanks.
"If you brick it, they will came" (Field of Dreams)
Excelent!!!
I Will test.
And Battery, normal?
Some people are reporting 3g problems. Is there any sugestion about lagfix config, in CWM Recovery, to solve this bug? I think debug mode on/off might be related whit the solution, am I right?
Thank you,
Sent from my GT-I9000B using XDA App
Works very nice thank you supercurio!
criscan said:
Some people are reporting 3g problems. Is there any sugestion about lagfix config, in CWM Recovery, to solve this bug? I think debug mode on/off might be related whit the solution, am I right?
Thank you,
Sent from my GT-I9000B using XDA App
Click to expand...
Click to collapse
Hi criscan!
About 3g (and, well, about everything^^) It should behave like the original kernel, as It's the original kernel
The operation made here is wrapping the lagfix around the kernel and integrating ClockWorkMod recovery but that's all
Speedmod
Is there any chance you could also add to the kernel the changes done by hardcore on his speedmod?
Like, having a Speedmod+Voodoo for GT-I9000B?
That would be truly awesome.
Hi Everyone,
I searched the forum for Lagfix tool... and i found all the apps to be either deprecated or development stopped. Could you please post me the link for the best one to use right now?? Thanks.
Oh forgot to mention i am on the Samsung Galaxy S (Android 2.2).
Most lagfix's are built into custom Kernel releases such as CF-Root, Galaxian or Semaphore with some of them using an addon app to apply the lagfix. If I were you I would do a bit of reading through some of the kernel threads in the Development section.
The basic app versions of lagfixing such as OCLF have all been abandoned as they eventually proved to be a little unreliable I think as opposed to kernel lagfixing methods.
Have a good long read through the FAQs for the I9000 if you're unsure of anything, they're well written and explain pretty much everything you'll need to know
Sorry to post and not come back! Thanks bigdyl69 for the reply.
OK... so i went through this thread about fixing niggling issues with SGS. And i sure am confused! Sorry if my questions are silly!
http://forum.xda-developers.com/showthread.php?t=723596
And in the General section's #6, is something that relates to Lagfix i think. So i can see all the older one's striked out which would mean they are no longer any good. But i do see three names there:
- Voodoo Lagfix
- Universal LagFix
- Fugumod Lagfix
So are these LagFix tools or custom ROM's?
But before anything, let me know:
1. I cannot do a Lagfix on a phone that has ROM's downloaded/installed from Kies? Am i right?
2. To do a lagfix first i have to get a custom ROM and custom ROM's have an inbuilt Lagfix tool?
It depends only from the kernel.
Lagfix is changing the file sysyem, so you need a kernel that support different file system.
Some kernel have inbuilt tool ( Speedmod, TORNADO) , others use ChainFire app to do this.
But when you flash new rom it's recommended to be on stock file system (RFS)
Само Левски S.U.R.F.A.C.E. ROM + BAT + TORNADO KERNEL
So if i upgrade to from Kies, it will be to the 2.3 platform dont know exact JP number now. Then i will have the default file system. But then i wont be able to do a Lagfix right?
Hello everybody,
I don't know if this has been done already, but I couln't find it so I thought why not make a version of my own.
Next to WhiteXP i'm also working on a version of CyanogenMOD 7.2, but with a different approach.
In my oppinion before even trying to release something it's important to have a permanent and working version of instead of the stock recovery.
The difference between this phone and many other phones is the fact that the recovery is included in the boot.img file.
My own phone for example, a Samsung Galaxy S Plus, has a seperate standalone recovery.img.
Because I don't own this phone myself I hope another developer can test if this is working properly.
I didn't change the kernel or important boot files other than the recovery itself, so booting into android shouldn't be a problem and remember it's build upon the stock kernel for now.
Here is the downloadable boot.img: http://depositfiles.com/files/90ye57wtm
The kernel should be flashable through the existing CWM which is already posted in the forums with this file:
http://depositfiles.com/files/e21qacxo9
Hopefully somebody is willing to give me some feedback.
Greetings PsychoGame
Hello
Here I am again with a little update.
This version doesn't seem to work okay, it gets into a bootloop.
I will try to fix these problems at a later time.
Greetings
Psycho Game
Thanks...for your work merge CWM into stock kernel...:thumbup:
Sent from my GT-S5360 using xda app-developers app
Here's a little update of the work i'm doing right now.
As I already said I'm also working on a version of CyanogenMod myself.
The problem is not anymore the availability of the drivers, because BroadCom released their drivers to the public.
In my opinion the next bottleneck is the Kernel. I didn't own a Galaxy Y at first, but I recently bought one to make it easier to test different configurations.
My main phone is a Samsung Galaxy S Plus which already has a realy stable CM9 version, but also the kernel is already updated to version 3 from 2.6.35.14.
This is also my goal ultimatly, but the Galaxy Y uses RFS filesystem in combination with FSR. These are closed source modules from Samsung, which make it difficult to update kernels.
There is a known hack that you can alter the version in the make file of the kernel to 2.6.35.7 while it realy is patched up to 2.6.35.14, but i'm not very fond of such hacks.
I'm a daily linux user already since the year 2000 or so, and build many kernels for Linux computers from source. I can say I have good knowledge of the compilation proces and what's going on in the kernel.
Now back to what i'm doing at the moment:
I already converted the complete galaxy y to EXT4 file system, incl. the EFS partition, and yes I still have my IMEI data etc. so this is considered done [status: complete]
Next step is getting rid of the RFS & FSR kernel modules, which are proprietary [status: complete]
At the moment I'm busy updating the kernel to version 2.6.35.14 the proper way, so I have a stable base kernel to build CM on [status: WIP]
After this I will add CWM recovery to the updated kernel, and make sure everything works as it should, like ADB in recovery mode, formatting, and all these things. [Status: Planned]
When CWM recovery functions as it should work, the proces of building CWM into the Galaxy Y can begin [Status: WIP -> Stalled until kernel stable].
This is a little update on the things I have in mind.
If you like it, please post a comment, that also lifts my spirit in the lots of things that have to be done.
Greetings
Psycho Game