Database Users

[Mod][28th July] Percentage Battery Mod for deodexed ROM

This mod requires deodexed ROM so currently only made for SamSet.. If you have a deodexed ROM and need my assistant, please let me know
Strongly suggest you use ROM Manager by Clockworkmod to backup your ROM before doing anything
Thanks to brut.all, judison, Fightspit and setenza01 for this nice looking ROM
Instructions:
1) Download and install ROM
2) Use my zip as update.zip and flash in recovery
Download
For SamSet v1.6 ROM
Custom CSC for Singapore network users see here

This doesn't work. Applied the update fine, but when rebooted, black screen with a bunch of FC's. Had to restore. Was running ROM Samset 1.6 as recommended.

Did u use stock recovery or rom manager to flash?
Sent from my GT-I9000 using Tapatalk

First used rom manager and nothing happened. Then used stock recovery, applied, and when booted, got the FC's. I could see the percentage in the battery, but that's about it. The FC's would not let me do anything else. Any suggestions?

hmm.. i've tried it again and it works on mine. only difference is im using clockworkmod to flash (remember to mount /system first)
anyway, i've resigned so download again..

Just installed your Mod. Works fine on my Galaxy S.
Thanks a lot !

Thanks, nice work. I have searched such a mod.

raspdeep said:
hmm.. i've tried it again and it works on mine. only difference is im using clockworkmod to flash (remember to mount /system first)
anyway, i've resigned so download again..
Click to expand...
Click to collapse
Just tried it again, and seems to be working now. I applied update.zip from stock recovery and seemed to be fine. Thanks for the mod.

does this work on samset 2.0?

shaunm1989 said:
does this work on samset 2.0?
Click to expand...
Click to collapse
most likely not, jp2 is development firmware, i will make one but will not support it since i wont be using jp2 as my daily rom

installed, it works~ =)

does it look good?
the sceenie looks like the numbers are blurry ...
anyway to go back to stock samset battery if i dont like this one?

Could you make an update out of the images i have linked? it's a circle battery with % in it. also the charging got a few more images.
I can get the images into framework-res.apk with no problem but the problem i'm having is modding the two battery xml files and the packing the apk again to get it to work

i've already tried this:
http://forums.hardwarezone.com.sg/showthread.php?t=2812085&page=58
as it does not quite match the theme, i modded samset battery to fit the theme

how to upgrade to froyo while retaining personal data using .zip file

so i finally decided to make the jump and give my epic some froyo love. i spent the majority of my weekend figuring out the best way to do this and wanted to share what i learned especially since this forum gave me invaluable information, scripts, and files that i pieced together to get my phone upgraded to my liking.
my phone was running a bone stock DI18 with the exception of removing a few sprint bloatware apps. what i wanted to do is install froyo DK28 while retaining my call log, text messages, 200+ apps, etc. the best way to do this is to use the DK28 zip file found here and applying it at boot. i tried flashing with odin at first but backing up and importing my old files would have been too much work.
a lot of people had problems with the update tripping up just like this--including me. so here is the workaround i came up with.
first i installed clockworkmod recovery 2.5.1.0 according to this guide. next i cracked open the DK28 zip and found the script that runs the update. it is found in META-INF > com > google > android > updater-script. i found the code with all of the asserts in it and removed the code that checked for the bloatware that most people uninstall. i also removed code that checked for the boot screen animation because that tripped my update up as well.
from there i zipped the package back up, loaded it to my sd card, and booted into clockworkmod recovery. then i went to "Install zip from sdcard", made sure that signature verification was disabled, and then chose the modified DK28 zip from the sdcard. and that's it! once it was done applying the changes i had a fresh froyo upgrade with all my personal information intact.
after that i converted the filesystem to ext4 and flashed a new rom--system only. but what you do after installing the update is up to you of course.
i'll include the "updater-script" file that i modified in case you don't want to go thru the code line by line yourself. the whole package is too large to upload with it included so you will still have to unzip this attachment, download the DK28 update, unzip the update, and replace the file by yourself but this might make it a little easier. i hope this helps someone!

this didnt work for me, nor did installing the original update.zip.

what didn't work? was there an error message?

when trying to apply the update.zip with clockworkmod recovery mode, it runs it, doesnt finish and returns to the menu. When I try it with the stock recovery mode, it errors out saying signature verification failed.

djcslice said:
when trying to apply the update.zip with clockworkmod recovery mode, it runs it, doesnt finish and returns to the menu. When I try it with the stock recovery mode, it errors out saying signature verification failed.
Click to expand...
Click to collapse
Disable signature verification in clockwork?
Also you should post this is development too! I'm sure they'll make a ot of use of this
Sent from my SPH-D700 using XDA App

djcslice said:
when trying to apply the update.zip with clockworkmod recovery mode, it runs it, doesnt finish and returns to the menu. When I try it with the stock recovery mode, it errors out saying signature verification failed.
Click to expand...
Click to collapse
do you have a bone stock version of eclair DI18? mine was with the lone exception being that i removed some of the sprint bloatware. i'll update my post because i probably should have mentioned that. there might be something in that updater-script that needs to be removed or modified to work with your setup. that's the only thing i can think of.
A_Flying_Fox said:
Also you should post this is development too! I'm sure they'll make a ot of use of this
Click to expand...
Click to collapse
i'm still pretty green here... did i post this in the wrong section?

A_Flying_Fox said:
Disable signature verification in clockwork?
Also you should post this is development too! I'm sure they'll make a ot of use of this
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I did make sure signature verification was disabled in clockwork.
n3k said:
do you have a bone stock version of eclair DI18? mine was with the lone exception being that i removed some of the sprint bloatware. i'll update my post because i probably should have mentioned that. there might be something in that updater-script that needs to be removed or modified to work with your setup. that's the only thing i can think of.
i'm still pretty green here... did i post this in the wrong section?
Click to expand...
Click to collapse
Mine is bone stock with the exception of having been rooted with clockwork and then unrooted with clockwork.

n3k said:
first i installed clockworkmod recovery 2.04 according to this guide.
Click to expand...
Click to collapse
I want to clarify for everyone that you used the version 2.04 of the all-in-one which has clockworkmod version 2.5.1.0.

DiGi760 said:
I want to clarify for everyone that you used the version 2.04 of the all-in-one which has clockworkmod version 2.5.1.0.
Click to expand...
Click to collapse
good catch! thanks i will update that

Do apps stay in as well? I will odin back to di18 just to get back the apps i cant get in dj28 lol
Sent from my SPH-D700 using XDA App

A_Flying_Fox said:
Do apps stay in as well? I will odin back to di18 just to get back the apps i cant get in dj28 lol
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
yes i think so. i saw them there but didn't test them. i had a few issues with some of the apps after i converted to ext4 and used cwm to advance restore the frankenstein rom's system underneath my data. i'm pretty sure that is what caused the problems with the apps. not the initial upgrade itself. i think i have a backup i can restore to check. i'll get back to you on that one

[ROM] Bonsai User Discussion

This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor

Yes this try to keep this thread open.
Sent From My Evo Killer!

So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App

I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk

Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?

abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far

I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0

bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?

forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.

I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force

forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.

olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.

Duplicate... Sorry

forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.

Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted

Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3

[BL1.2] Roebeets+Clemsyn's Honeycomb COMBO alpha

REQUIREMENTS:
Please Nvflash to 3588 (VERY IMPORTANT)
Here's a link for instructions of 3588 by roebeet
http://forum.xda-developers.com/showthread.php?t=861950
Releasing an alpha version for xda-members to experience Honeycomb in their GTABS. First and foremost, thanks to Roebeet, MrGUY, DJ_Steve, pershoot and the rest of adam devs who helped us port Honeycomb.
WARNING:
This will update your bootloader to 1.2 version (need to be on 3588 for this combo to work)
Whats working..
1. Wifi, BT
2. Touchscreen
3. buttons
4 Browser, Gmail
5. Market
6 gapps
What is not working..
1. OpenGL
2. Camera (because of OpenGl)
3. No flash yet
Link..
https://rapidshare.com/files/541902742/Roebeet_ClemsynHoneycombo.alpha.zip
******* YOU NEED TO BE ON 3588 STOCK and STOCK RECOVERY (NO CWM) BEFORE FLASHING THIS COMBO******
INSTRUCTIONS #1
1. Nvflash to 3588 STOCK DO NOT USE CWM FOR 3588
2. Do not install CWM (we need the stock recovery)
3. DO NOT INSTALL CWM (we need the stock recovery)
4. PLEASE DO NOT INSTALL CWM
5. Reboot
6. RENAME COMBO FILE NAME TO Update.zip
7. Move Update.zip to /sdcard folder
8. Unzip recover.zip and move recovery folder to /sdcard folder
8. Turn off
10. Press Power+Volume up then this will install Update.zip
The reason we don't install CWM for 3588 is because this won't install the bootloader
Instruction #2
1. Rename Combo file to Update.zip and place in /sdcard folder
2. Unzip recovery.zip and put recovery folder in /sdcard
3. Update to NVFLASH to 1.2-4349 using this image
http://www.mediafire.com/?g7vorg66iiq29vm
4. Enter recovery by pressing Power Button+Volume up
IF YOU WOULD LIKE TO GO BACK TO FROYO AND STAY IN 1.2 bootloader here is a link for my Combo version 6
https://rapidshare.com/files/1095733302/Clemsyn_Caulkinver6.zip
BTW, if you like our work, buy us a beer

I am currently running gojimi vegan ginger rc1. What will I have to do if I want to go back,and how are storage partitions mapped on this Rom ?

cool! can't wait to try this. waiting patiently for rom to be uploaded and installation instructions to be posted...

Can't wait to finally try this when I get a few days off!
Question: After trying this and having the bootloader upgraded, will I be able to easily revert back to Clemsyn -Calkulin 1.5 with the new bootloader or will I have to nvflash?

I had to use nflash to go between the two bootloaders. My apps are usually remaining or you can use Titanium to get them back.

Awesome build running smooth already glad someone posted this here
Sent from my GTablet-HC using XDA Premium App

Thanks for posting it here Clemsyn. I really didn't want to sign up for another forum so I can ask question haha.
Anyways, when you say gmail is working, is it fully functional? I thought there were shader (or something like that) issues that prevented us to see the body of the email.
Also, is flash in the browser working?
Those are my two must haves if I am going to switch to HC.
Thanks in advance.

xmr405o said:
Thanks for posting it here Clemsyn. I really didn't want to sign up for another forum so I can ask question haha.
Anyways, when you say gmail is working, is it fully functional? I thought there were shader (or something like that) issues that prevented us to see the body of the email.
Also, is flash in the browser working?
Those are my two must haves if I am going to switch to HC.
Thanks in advance.
Click to expand...
Click to collapse
No flash yet. There is a hacked gmail.apk that works fine. I am using it now, and only flash is not working of everything I personally use. The devs are very close now.

I apologize for the delay, it wasn't done uploading yet and I needed to go to my kid's science project (he won 5th place). Just got home so I posted the link on first page. BTW, gmail is also fixed.

SirhanSirhan said:
No flash yet. There is a hacked gmail.apk that works fine. I am using it now, and only flash is not working of everything I personally use. The devs are very close now.
Click to expand...
Click to collapse
actually flash is technically working just fine...it's the opengl shader issues causing it not to display properly...opengl is also causing the gmail app issues (alt app in place as a temp fix, now) and opengl issues are causing a few other apps to have issues as well...once opengl is resolved then this will be a practically perfect build, imo been running it for about a week now with all the updating and love it!!

clemsyn said:
Releasing an alpha version for xda-members to experience Honeycomb in their GTABS.
Click to expand...
Click to collapse
Thanks clemsyn for sharing this, so whats the difference between this and Roebeets versions released on slatedriod ?

hey, clemsyn...when you get back online, I have a question for you. A lot of the current talk in the Adam dev chat is that a .36 or newer kernel will resolve many of the current issues (OpenGL specifically)...I was wondering if maybe you had a newer version kernel in the works or not for the gtab? If so, how's it coming along? If not, how tough do you think it would be to develop a .36 version of the kernel? Thanks for everything, man. Have a good one.

Is Dolphin HD working on this?
Thanks to clemsyn & roebeet for porting this from the Adam.

Stuck on boot
Hey Roebeet, its been awhile but I'm back and ready for HoneyComb. I folowed your directions. I used NvFlash to get back to 3588. I then installed CWM .08 and partitioned internal 2048 and 0. I put the zip on internal and installed via CWM. Now it hangs on the viewsonic white screen? Any Ideas?

Theres already a 2.3.32.40 overclocked kernal out. Is that not what you are wanting?

jlytle1234 said:
Theres already a 2.3.32.40 overclocked kernal out. Is that not what you are wanting?
Click to expand...
Click to collapse
it's 2.6.32.40...the 40 is the version number of the .32 kernel...they are looking for a x.x.36.x kernel to possibly resolve the issues with opengl...

acuralegendz said:
Hey Roebeet, its been awhile but I'm back and ready for HoneyComb. I folowed your directions. I used NvFlash to get back to 3588. I then installed CWM .08 and partitioned internal 2048 and 0. I put the zip on internal and installed via CWM. Now it hangs on the viewsonic white screen? Any Ideas?
Click to expand...
Click to collapse
Most of us got this issue. When reading on the other website it says to do wipe data after flashing so do that and see
Sent from my SGH-T959 using XDA App

Djapatos said:
Most of us got this issue. When reading on the other website it says to do wipe data after flashing so do that and see
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I think this guys issue stems from the fact that he installed cwm. This rom needs to be installed with the stock bootloader.

Well I have the same issue, I wiped, but nothing. When I flashed the file, it said unknown command bootloader, bla bla.
Pretty sure thats the issue, I was running 3588 ...dont know whats up.

I get the same results with the unknown command bootloader. I've tried wiping all data after the installing the rom and the gtab still gets hung up. This is coming from using nvflash to 3588 and a repartition.

[Telus T959D Fascinate] - Install MIUI, CM7 and More!!

Follow Steps at own Risk
MIUI or CM7 Installation:
1.) Depending on what you want to install, download either the I9000 Miui 1.11.11 Rom or the CM 7.1 Stable Rom.
2.) Download the Glitch-V13-DEV-TelusFascinate+ kernel. I chose the Medium Leakage Kernel.
3.) Move both ZIP (ROM and Kernel) files over to the Root of your Internal SD Card (USB, Bluetooth, etc)
4.) Make sure you DISABLE all Lagfixs if you have it enabled.
IMPORTANT:
Froyo 2.2.x (Not Tested):
We need to be able to boot into CWM. Easiest way to do this if you are on Froyo is to Flash the SpeedMod kernel or the Voodoo Kernel. I suggest following all steps which includes installing Darky 9.2 just to be sure. I haven't tried flashing Miui or CM7 from right from the SpeedMod CWM.
Gingerbread 2.3.x (Tested):
If you running a custom ROM that is based off Gingerbread you will be required to flash the Darky Resurrection Edition 9.2 (Froyo) via Odin. This is to insure that the proper boot loaders updated before installing MIUI or CM7. Download the Darky 9.2 package from the above URL, the ONLY files that we need from here are: Odin3 v1.3.exe, darky_odin.tar.md5 & s1_odin_20100512.pit​
Follow Ficeto's Instructions below to flash Darky 9.2 and remember to backup all your stuff before starting.
-------------------------------------
5.) Next step is to get your phone into Download Mode. If you are unsure please search the forums here.
6.) Now, open ODIN and connect the phone to the computer. ODIN will say 'Added'.
7.) Tick the 'Repartition' option, and then select the following files in ODIN (from the folder you extracted the base package in):
[*]PDA: darky_odin.tar.md5
[*]PIT: s1_odin_20100512.pit
8.) Press the Start button and wait for it to finish. Once it finishes, disconnect the phone from the computer after the phone reboots.
9.) After ODIN completes procedure and the phone reboots, a screen will come on the phone with 'Android system recovery <2e>' written at the top, and the following text will be written at the bottom:
"E:Invalid command argument
--Install from package--
Finding update package...
Opening update package...
Installing update...
#MANUAL MODE#
-- Appling Muti CSC...
Installing Muti CSC"
Don't worry about this.
10.) From here the next step is to reboot your phone, your POWER / SELECT button will not work so you will have to pull the battery out. Once you put the battery back in and start up the phone, it should automatically boot into CWM Recovery.
-------------------------------------
11.) Next we want to do a COMPLETE WIPE (Factory), also deleting Partition Cache and the Delvik Cache.
12.) Once the phone has been cleansed, you want to make your way to the option "Select ZIP from SD Card" and select the ROM zip file located on the SD Card. Start the Installation.
NOTE: Once you start the installation, your phone will reboot part way through, then will continue the rest of the installation. The total time for this installation could take up to 10 minutes, so please be patient and do not touch the phone!
13.) DONE!! You have now successfully Flashed either Miui or CM7 on your Fascinate!.
14.) Actually, one more Step which I have ONLY tested with Miui 1.11.11:
Once you have checked a few things out, we are going to want to Flash the Glitch-V13-DEV-TelusFascinate+ kernel. So boot back into CWM Recovery and Flash it the same way you flashed the ROM.
Optional:
BASEBAND UPDATE:
I would also suggest Flashing the I9000UGJK3 Baseband or another of your liking because I had crappy cell signal with the Stock Miui Baseband. Just download it as you normally would, move the ZIP to the internal SD Card, boot into CMW recovery and flash it. Click on the Link Here and find the modem that you would like to flash.
4WAYREBOOT MOD:
I think this Mod is a MUST for anyone running Miui, it completes it!! It basically adds the additional reboot options like Recovery, Hotboot, etc. to the 'reboot' list when going to reboot the phone. Install the ZIP the same way as usual, through CWM recovery. Download the 4-Way Reboot Mod Here.
ENJOY!!!!
I will add to this post with some additional and helpful information.
Other helpful information:
- With Miui or CM7, you will want to install the ROM Manager Application. It contains a bunch of additional downloads and is a must when using Miui or CM7.
- Please do NOT USE 'ROM manager' Backup option to create a nandroid. To create a backup, boot into CWM recovery normally via ROM manager or if you have the 4-Way Reboot mod installed. Just don't use the 'Backup option' in ROM Manager
- I haven't tried Launcher Pro yet, I've actually stuck with the Stock Launcher that Miui comes with, Launcher2.apk

thanks so much! save me tinkering time

Thanks! On my to do!
EDIT - thinking about this on the way into work. Should we include a step (if the complete wipe doesn't do it) to wipe the battery stats? Could be done in CWM after flashing the ROM, or through an app like battery calibration on boot up. Also, we should note on the coming from froyo that you only need speed kernel if you do not have an option to get CWM. When I ran froyo I had a voodoo kernel so could get to CWM that way.
Also, is miui EXT4 out of the box (no need for a lagfix)? Given its next to latest GB I'm assuming it is
Just some thoughts - hoping to do this tonight, but one quick question for the group - flashing - so do you all make sure you have a full battery before you flash? I've not always done that in the past, but believe its a best practice.
NEW EDIT - almost forgot, great work as always Adam!

jpmccarthy said:
Thanks! On my to do!
EDIT - thinking about this on the way into work. Should we include a step (if the complete wipe doesn't do it) to wipe the battery stats? Could be done in CWM after flashing the ROM, or through an app like battery calibration on boot up. Also, we should note on the coming from froyo that you only need speed kernel if you do not have an option to get CWM. When I ran froyo I had a voodoo kernel so could get to CWM that way.
Click to expand...
Click to collapse
Thanks Jeff, the Voodoo kernel should also work as well. In regards to wiping the battery, I never did but it might be a good idea just in case. I haven't run into any issues as of yet. (knock on wood)
jpmccarthy said:
Also, is miui EXT4 out of the box (no need for a lagfix)? Given its next to latest GB I'm assuming it is
Click to expand...
Click to collapse
Not 100% sure on this at the moment, but I do know that there is no need for Lagfix with Miui or CM7.
jpmccarthy said:
Just some thoughts - hoping to do this tonight, but one quick question for the group - flashing - so do you all make sure you have a full battery before you flash? I've not always done that in the past, but believe its a best practice.
Click to expand...
Click to collapse
It definitely is good practice to Flash a new ROM when the battery is almost 100% full. Now saying that, I have flashed ROMS when my battery has been as low as 40% - 45% and never had any issues.

I think that's the best comment Adam - why apply a lagfix if one is not needed!
Cannot wait to give this a run - hoping tonight assuming my little ones all go to bed, and my wife does not get too annoyed with me

[MIUI Themes and Lock Screens]
The Miui Rom is very customizable when it comes to themes and lock screens.
The Miui 'Themes' application allows you to download, install, customize and apply all different types of themes. Which I would have to say that there are at least a good 100 + or more themes out there at the moment.
I think the best feature that the 'Themes' app has to offer is that you have the option to apply different theme components to the current base theme that you have it set to!
As an example, I currently have one of the 'Honeycomb' themes applied as my base theme, my Lockscreen is based off the 'Slide Slip' theme, my Icon Set is based off the 'Seemless Dark Blue' theme and my Dialer is also based off the 'Seemless Dark Blue' theme. It feels like the possibilities are endless now when it comes to customization.
To see the different components the way the themes are broken down, choose 'Edit Theme' from within the 'Themes' app. Within here you can then assign other theme components as long as you with have the full theme installed or just that one component.
Installation of .mtz files, (Full Themes / Theme components)
Once you have downloaded a compatible Miui theme (.mtz format), copy that file to the following directory on your phone:
/sdcard/MIUI/theme
(You can also import themes from the themes application itself, all that does it move it to that directory for you)
Then open up the 'Themes' app and your new theme will be in the list.
NOTE:
If its a theme component only (Still .mtz format) , eg. Lock Screen component, it WILL NOT show up in your main Theme list. Just click on 'Edit Theme' and it should show up under the drop down for 'Lockscreen Style'. Get what i mean?
For Miui Lockscreens, check out the link below!
http://forum.xda-developers.com/showthread.php?t=1288096
For full Miui themes, check out the link below:
http://forum.xda-developers.com/showthread.php?t=1249352
Also, the Theme app has an Online library that you can search through as well
Cheers!

<drool> awesomeness <\drool>
EDIT flashing in process - factory reset at the moment

Awesome! Thanks for creating this. Just gotta wait until the weekend to take the plunge. It's not the flashing taking too long that I worry about, but the time I spend restoring apps and settings and just playing around in general. Not to mention having time to start over if I feel something went wrong. Two more days to go!

guessing it shouldn't boot loop - I'm stuck in a boot loop
looks like it cannot find the SD card - so keep restarting looking for the miui zip - the CWM error is quick before it restarts (can't see it)
EDIT : re-downloaded the zip but same effect. Anyone hit this before with cm7 or miui? trying a few things before I attempt a restore.
I get to 'checking bml' before it reboots, and then it boot loops continuously - I tried flashing and not flashing the glitch kernel first, but nothing sticks.
EDIT : giving up, attempting a restore of my nandroid I made before I started. Any tips let me know - disappointed.
EDIT : still up, backup didn't go so well - likely cause I have odd kernels - one last ditch - went right back to froyo stock, tried speedmod (bootloop), now put on 9.2, rebooting - may give it one more shot before giving up for the night.
EDIT - SON OF A ***** - that did it!!!!!!!!!!!!!!! I might have to provide some troubleshooting tips on that one!!!!!!!!
EDIT AGAIN - knock on wood here - I'm farther than the bootloop and I'm at a MIUI splash screen - that might be as far as I go tonight ... LOL
FINAL EDIT - so not much playing tonight. Ate into that with all this trouble shooting.
SO IF YOU ARE COMING FROM A GB ROM AND GET STUCK IN A BOOTLOOP - I would go to STOCK FROYO and then flash 9.2 and then follow the instructions. Bang on job Adam! I think I just had something odd on my phone.
I'm now up - gltich on + miui.

Wow, sorry you had such a hard time man. Only time I hit a hard bootloop was when trying to install CM7 using gingerbread bootloaders. Did you eventually get it going??
Sent from my Telus T959D

iwebsource said:
Wow, sorry you had such a hard time man. Only time I hit a hard bootloop was when trying to install CM7 using gingerbread bootloaders. Did you eventually get it going??
Sent from my Telus T959D
Click to expand...
Click to collapse
yeah, see my last edits - putting on 9.2 I'm guessing didn't completely adjust the bootloaders - when I put on stock telus 2.1, THEN 9.2 - I was golden.
Didn't play much (that was after 12) but restored a few apps - but man, it is really fast. Will report some thoughts over the weekend likely.

Questions on MIUI
OK a few questions.
- downloaded google maps (navigation, etc). Start it up, but it fails miserably - bombs out and goes into a constant vibration. ANyone having similar issues with that? Suggestions?
- There's a 6 digit number in the left corner of my screen - no meaning to me - anyone know what that is or seeing something similar?
- also, pinch and zoom with the camera. Those don't seem to work - any issues you folks having with that?
- Adam you suggest a different base band - where are you getting zip - I'm only finding large tars on that link (but I"m over tired)
- The OTA updater looks great BUT is in chinese - any one have a work around for that?

Again, sorry about all the issues you had with installing and such. My very first time
jpmccarthy said:
OK a few questions.
- downloaded google maps (navigation, etc). Start it up, but it fails miserably - bombs out and goes into a constant vibration. ANyone having similar issues with that? Suggestions?
Click to expand...
Click to collapse
Weird man, I actually installed google maps a few days ago. First time I used it (Navigation) was yesterday to test out the GPS. Had no problems at all with the apps yet.
jpmccarthy said:
- There's a 6 digit number in the left corner of my screen - no meaning to me - anyone know what that is or seeing something similar?
Click to expand...
Click to collapse
That is your Service Provider. With CM7 and Miui, I noticed it doesn't resolve the provider. Its no harm unless you don't like looking at numbers there. I did find a work around though, just install the Miui Extended Menu Mod and you can change it to what ever you want:
http://forums.miuiandroid.com/showthread.php?7738-MOD-Extended-Settings-Menu-Options
jpmccarthy said:
- also, pinch and zoom with the camera. Those don't seem to work - any issues you folks having with that?
Click to expand...
Click to collapse
Pinch and Zoom? Unsure what you mean, is that just the touch-point focus? If not I haven't tested that yet.
jpmccarthy said:
- Adam you suggest a different base band - where are you getting zip - I'm only finding large tars on that link (but I"m over tired)
Click to expand...
Click to collapse
Guess I better check my links more better. Stupid site.
For now use this one. I know your in the same geo area as me, I haven't had any issues with this one, use the one attached.

Oh, don't use the OTA updater, just use ROM Manager. Or download the Miui updater app from the market.
I'm guessing MIUI originally was developed in China, lol

iwebsource said:
Oh, don't use the OTA updater, just use ROM Manager. Or download the Miui updater app from the market.
I'm guessing MIUI originally was developed in China, lol
Click to expand...
Click to collapse
OK - maybe I should reflash. I actually have ROM Mgr premium - but its telling me I need CWM installed to work (which I obviously have).
And no apologies needed - we're all guinea pigs here
EDIT - Also, on the camera - used to be able to pinch like a website on Darky's to zoom in and out. Maybe that was a custom camera but I think it was generally samsung stock.
EDIT - Reflashed (1.11.18 actually - am I the first ) and GPS issue solved - might have been tied to the modem as I flashed yours Adam (THANK YOU!!!!!!) Keeping moving forward

jpmccarthy said:
OK - maybe I should reflash. I actually have ROM Mgr premium - but its telling me I need CWM installed to work (which I obviously have).
And no apologies needed - we're all guinea pigs here
EDIT - Also, on the camera - used to be able to pinch like a website on Darky's to zoom in and out. Maybe that was a custom camera but I think it was generally samsung stock.
Click to expand...
Click to collapse
Might be the best thing to do. I've read that some people prefer to >> Flash the ROM first >> Flash Kernel >> Boot into Kernel CWM >> Re-Flash ROM again.
Yeah, if you do there is no need for the Darky steps anymore.
Just boot into CWM, do factory wipe, partition and dalvik cache, fix permissions, then flash miui again.
Oh, in regards to ROM Manager and CWM, just select 'Flash ClockWorkMod Recovery' >> Select I9000 (MTA) and choose version 3.
Then reboot into recovery to test.
It actually still uses the Glitch CWM from the Kernel. This is just so that ROM Manager will recognize that you have a selected CWM

Looks like Miui 1.11.18 is now out. I'm going to Flash and test it out shortly.

iwebsource said:
Looks like Miui 1.11.18 is now out. I'm going to Flash and test it out shortly.
Click to expand...
Click to collapse
Already on it - best you for the FIRST time!

jpmccarthy said:
Already on it - best you for the FIRST time!
Click to expand...
Click to collapse
I'm loving Miui and the glitch kernel man. There are a few other Kernels out there that we can try as well. I maybe testing the platypus kernel out soon, it is also built for our phone too
From what I've read so far though, Glitch is one of the best so far.

iwebsource said:
I'm loving Miui and the glitch kernel man. There are a few other Kernels out there that we can try as well. I maybe testing the platypus kernel out soon, it is also built for our phone too
From what I've read so far though, Glitch is one of the best so far.
Click to expand...
Click to collapse
when you get 1.11.18, go to ROM manager and select update ROM - does nothing happen? I have it registered now with a CWM which is fine, it shows my current version (which is latest) so when I click check for udpates nothing happens (no - 'no update available' or anything like that). Just wanted to see if it was working correctly.