I know there are threads here and there talking about getting to EE03.
Go here to get the files that I used for this process:
https://docs.google.com/leaf?id=0B8...Zjk1Mi00YjYxLWJkYTEtYmM3MGU0MmY3MTlh&hl=en_US
So here is what I did, step by step.
get to stock EC05
1) Open Odin; place EC05 Full tar in PDA, victory PIT in pit, only auto reboot should be checked
2) shut down phone, once fully shutdown (wait for vibrations) press #1 on keyboard and power together until yellow triangle download mode
3) connect phone to PC via usb cable; wait for odin to see phone
4) click start
phone will reboot when finished
close odin
I let the phone boot completely, then turned on GPS; then opened Google Maps and waited the 10 minutes for it to get a lock.
Place EE03 Modem on phone
1) shutdown the phone and go back into download mode
2) open odin, put acs-ee03-modem.tar in PDA, victory pit in PIT, only auto reboot should be checked
3) connect phone via usb cable; wait for odin to see it
4) click start
phone will reboot when finished
close odin
Let phone fully start up; open google maps; instant GPS lock (MUCH more accurate this time went from 90 meters to a few feet)
Root with CWM 3.0.2.5
1) connect phone to PC via usb for mass storage
2) copy midNight v6 (or whatever rom you're using) and acs gps_fix to sd card
(midNight has the CIQ removed and other items the ACS EE03 leak has separate zips for)
3) turn off storage; disconnect phone from PC
4) got to settings; applications; development; select USB debugging
5) TURN OFF ANTI-VIRUS software on PC
6) unzip OneClickRootCWM3.0.2.5-EC05.zip (it isn't really EC05 only)
7) connect phone to PC
8) open command prompt on PC (click windows start menu, accessories; command prompt)
9) navigate to the folder where you unziped one click root
10) type RUN [press enter] (wait for it to say it has completed)
11) TURN ON ANTI-VIRUS software
shut phone off
Flash midNight v6 EE03
1) 3 finger to CWM 3.0.2.5 (volume down + camera + power)
(I have noticed I have had to do it a few times for the phone to turn on, hadn't ever had this issue before. so if it doesn't turn on. simply let go and try again)
2) do the 3 x 3 wipey dance (data/partition cache and dalvik)
3) flash ROM (install zip, choose zip, select rom, yes)
4) reboot to system
As much as I love midNIGHT and I fully support Rob's quest to make more people aware of autism, my eyes about crossed looking at the default wallpaper <sorry Rob>
Now I had NO GPS at this time.
So I shut my phone off, went to CWM, flashed the gps fix from ACS.
reboot to system; GPS worked instant and accurate; but 3G didn't.
I just restarted my phone. When it came back up GPS and data were fine and have been since yesterday afternoon.
I also flashed the gingerbread voice mail zip, which fixed midNight v6 lack of VM.
now customize as you like.
I am modifying framework-res with the status icons I like and some items from Bionix Black
I hope this helps others and also shows that CWM 3.0.2.5 does indeed work.
Just a bump to make it more visible
I've also been considering switching from midnight 5.3. How's the battery on midnight 6 compared to 5.3?
Running 6 right now. There are a few bugs, but I do like the ROM overall.
MMS does not work for me.
Neither does GPS or Netflix.
birdturbo said:
Running 6 right now. There are a few bugs, but I do like the ROM overall.
MMS does not work for me.
Neither does GPS or Netflix.
Click to expand...
Click to collapse
y not try marcusaunt?
ok am I the last person to know about this google docs sharing bit?! Thanks! (i clicked it). Gonna try this to get to AA ROM, maybe ill try midnight6 again too.. all my ee03 issues may be resolved....
OK, MD5 cheksum no good on ec05 full file... DL'ed twice... just a heads up...
Thank you for taking the time to put this post together.
I gave ee03 a shot in all flavors with two epics but could never shake the unreliable gps and erratic cpu usage. I know smartbench 2011 scores don't mean much but they lingered around 500s in productivity and 1300s in gaming. Even cm7 alpha 1 doubled that. Again I know benchmarks are bogus
Sent from my SPH-D700 using XDA Premium App
imdjenk said:
I've also been considering switching from midnight 5.3. How's the battery on midnight 6 compared to 5.3?
Click to expand...
Click to collapse
Battery is a little less efficient in EE03, as they can't tweak as many things until the release of the code, when the final version of GB comes out
ungovernable1977 said:
ok am I the last person to know about this google docs sharing bit?! Thanks! (i clicked it). Gonna try this to get to AA ROM, maybe ill try midnight6 again too.. all my ee03 issues may be resolved....
OK, MD5 cheksum no good on ec05 full file... DL'ed twice... just a heads up...
Click to expand...
Click to collapse
I'll upload it again.
I tried to find where I downloaded it myself, but I haven't been able to find that.
EDIT: I just uploaded the file again.
birdturbo said:
Running 6 right now. There are a few bugs, but I do like the ROM overall.
MMS does not work for me.
Neither does GPS or Netflix.
Click to expand...
Click to collapse
I have no issue with MMS (I use handcent though).
GPS doesn't seem to work unless you get a lock with the modem before flashing the ROM.
Use the netflix from http://forum.xda-developers.com/showthread.php?t=1098881&page=3
Still isn't valid.
jdelano said:
I'll upload it again.
I tried to find where I downloaded it myself, but I haven't been able to find that.
EDIT: I just uploaded the file again.
Click to expand...
Click to collapse
I ended up justing finding an RFS ec05 to flash from clockwork. Then I odin'd the ee03 modem. Then flashed Midnight v6. Flashed the GPS fix. Now works like a freakin charm. Thanks so much for the help. Turns out, all the times I was re-flashing a bunch of different Ginger Roms then flashing the modem, then the fix...all I had to do is go backwards lol
Did a similar journey - from Midnight 5.5 BYOR Fixed to Midnight 6.1 EF02 Beta-ish .
Because I was backstepping from EXT4 to RFS based ROM -thought it would be prudent to go back to factory stock . Also wanted to engage GPS at each step also .
Deleted ' midNIGHT ROM Extras ' folder
ODIN back to DI18 (known working, used before file), got GPS lock w/maps
OTA to EC05 , used maps again
Rooted with Bonsai MasterKey
Flashed midNIGHT ROM v6.1 EF02 Based GB BYOR
Rebooted and flashed ' midNIGHT Extras for (GB Only) ' and AllShare
ODIN ' EF02 modem odin package
For those following along: Quadrant DI18 800ish, EC05 just shy of 1000 and EF02 based ROM got 1300ish - with Midnight 5.5 had a solid just shy of 1700 and 2000 when running 1.2GHz with CPU Tuner .
Had one weird issue, ran my old SprintTV.apk from early ROMing days and after install Market and apps installed via Market disappeared from the App drawer including set Live WallPaper . Deleted extras, reflasted 6.1, Extra and AllShare again and back to solid .
Will look for the SprintTV and Memo in the Extras and tell you how it goes. Also need a EF02 based Gtalk update for Video (whole point of coming off Midnight 5.5) and FFC fix if still needed. Also miss the BlueCircle Batt Theme with the Transparant App drawer - pleasantly surprised to see the continous scroll style App Drawer so far.
Thanks PDFMEDIC and will post again soon
@kenrico - thanks for updating !!
kenrico said:
Did a similar journey - from Midnight 5.5 BYOR Fixed to Midnight 6.1 EF02 Beta-ish .
Had one weird issue, ran my old SprintTV.apk from early ROMing days and after install Market and apps installed via Market disappeared from the App drawer including set Live WallPaper . Deleted extras, reflasted 6.1, Extra and AllShare again and back to solid .
Click to expand...
Click to collapse
Well, later this afternoon the phone 'reset' again - no Market, Market Wallpaper or Apps disappeared again . Just general use, think I was running Quadrant again and 'poof' .
Reset back to Midnight 5.5 via Nandroid style backup - if I see some help in getting GTalk Video updated to the 6.1 will reflash and do Nandroid style backup after everything is situated so if it goes off kilter can put back with one step instead of the reflashing process . Also side note but thought I had backed up MMS history/content via Titanium but did not come back when I restored the two green color MMS apps in the choices.
Midnight 5.5 is tight, faster and solid with my favorite 'less is more' theme - blue circle batt indicator and transparent style notification pull down and the COOLEST start up and shut down animation to BOOT ! Heh !
kenrico said:
Midnight 5.5 is tight, faster and solid with my favorite 'less is more' theme - blue circle batt indicator and transparent style notification pull down and the COOLEST start up and shut down animation to BOOT ! Heh !
Click to expand...
Click to collapse
Wow, been fighting this since the last post . In traveling back to Midnight 5.5 have hit a few bumps - am LOCKED out . No matter what key/root is used - no matter if I ODIN back to DI18 or EC05 factory (tried both) or get Midnight 5.3 running and booting ---> as soon as I flash to 5.5 on reboot it just hangs at SAMMY screen.
So guess I am back on 5.3 for now - usually with some persistance and patience can solve figure out a way past , but have restored factory 5 times 3 different roots and coming up from working 5.3 was going to be a lock - but did the same hang ... sheesh.
Because I was in flux and not locked in to what I was working on even tried 6.1 again - seemed more stable with new CWM root instead of Bonsai , but absolutely no GPS the two times I tried .
Weird even recopied the original 5.5 file from the puter to the phone - did work before was running 5.5 before trying 6.1 .
Kenny
I got GPS back the following way since the acs fix wasn't doing the trick:
1. nandroid backup of midnight 6.0
2. odin back to stock ec05 with victory pit
3. root with cwmod 3.1
4. flash midngiht rom 6.0
5. get a pinpoint on gps (not sure if this is necessary but was playing it safe)
6. restored nandroid backup
so basically im using the ec05 modem with midnight 6.0 ..gps and data work fine .. speed test on 3g 300-500k down, 400 - 500k up after 3 consecutive tests .. no 4g in the current area im in though
Related
Rooted removed oclf. Updated. Pissed.
Progress bar got to 53% then said download failed. Reebooting. Vibrant screen. That's it.
Ditto...
this is BS
call tmobile.. post on their website..
I'm not touching this update with a ten foot pole. More headaches than it's worth. I'm honestly getting very close to the point of throwing my Vibrant up on Craig's List and heading the way of the G2... . I love this phone but the software support is just horrendous.
Update went smooth for me, although I used Odin to flash stock JFD back a couple days ago from custom kernel. All I did since update was root.
Were you stock JFD or something other, ie kernel change etc...
where did you get your stock from
I was still jfd. Tpain is sending another phone.
Worked fine for me but I dont use custom roms either. I just have ryans one click lag fix going with launcher pro plus and root.
Gps worked flawlessly, the task manager they put in is pretty robust, and the swype voice recognition is working wonderfully. I think I may be seeing a speed increase? Not exactly sure about that.
Sent from my SGH-T959 using XDA App
same here. went to t-mobile store and got a borrow phone. -___-'
I want to know if a completely stock phone safe to update, i know there may be tons of the same Q/A, but there is too many post that can't find.
I have one and updated without any problem, my GF one doesn't showup and update yet, but want to make sure before she press yes
ota bricked me too
same as above updated to 53% said update failed rebooted to virant screen and nothing . now have loaner cant get new vibrant till tues.
For everyone who had stock kernel + root, can you list what else you might have had installed on your system that could compromise the OTA?
Spotty connection?
Low battery?
Connectivity only over wi-fi at during update?
ROM manager?
Titanium Backup?
Bricked my phone stock with root. It completed the full install rebooted and hung on the vibrant screen for over an hour. I also have a loaner phone (just found my G1 thank god) and I'm awaiting a replacement.
As for changes made:
- full battery
- signal connection (3G two bars)
- Rom Manager Installed
- Titanium Backup Installed
- Removed T-mobile boot images and sounds
I'm going to try to update my phone through Odin and see if I can bring some life back to it. I'll let you know how it goes.
How to fix your phone and apply the update:http://forum.xda-developers.com/showthread.php?t=803492
So should I update then root with the new phone when it comes?
ntellegence said:
So should I update then root with the new phone when it comes?
Click to expand...
Click to collapse
You can Odin JI6 tarball. Then you can use the old update.zip method to re-root the phone.
It's working fine for me. Going to check the GPS out later (I'm inside right now), but the compass is a little herky-jerky so far.
BritCrit said:
As for changes made:
- full battery
- signal connection (3G two bars)
- Rom Manager Installed
- Titanium Backup Installed
- Removed T-mobile boot images and sounds
I'm going to try to update my phone through Odin and see if I can bring some life back to it. I'll let you know how it goes.
Click to expand...
Click to collapse
Points of commonality is Titanium + Rom Manager + renamed boot sounds (I left my boot images intact).
My battery was 78% and I was on over Wi-Fi.
My phone bricked too...Pretty sure it got to something like 53% - wasn't paying attention, but it looked like half way on the progress bar, then next thing I saw was the Vibrant screen.
I was rooted, with Titanium and Rom Manager and the battery icons...
TMobile is sending me a new phone, so I'm gonna try to fix this one first and see if the steps above work...if so good, I can't wait 7 days for a phone. It seemed pretty easy to get a replacement though. Like maybe this was common with this update?
jmerchant said:
I was rooted, with Titanium and Rom Manager and the battery icons...
Click to expand...
Click to collapse
I don't think rooting affects the update, but in order to install both of these apps you need root. Titanium installs busybox which supports LZO and ROM manager installs Recovery. I'm wondering if either of those would affect the OTA update.
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Good luck, man. I feel your pain.
Hope you don't have to resort to odin, but if you do, that safety net will have proved its utility.
Again good luck!
Sent from my Nexus S using XDA Premium App
I can almost guarantee that ODIN will work. I resurrected a Fascinate that was locked out from itself using ODIN as well as a Captivate that had this same problem you are describing. ODIN dont **** around.
AllGamer said:
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Click to expand...
Click to collapse
hey what is your "flashing" history? (i.e. roms, kernels, etc.)
serialtoon said:
I can almost guarantee that ODIN will work. I resurrected a Fascinate that was locked out from itself using ODIN as well as a Captivate that had this same problem you are describing. ODIN dont **** around.
Click to expand...
Click to collapse
Well, that's if Odin is used right, otherwise it can ruin the phone. I've used it to bring back my Vibrant a bunch. It's good knowing that these Galaxy S phones are nearly brick proof.
All is not lost, honest...
AllGamer said:
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Click to expand...
Click to collapse
Hi AllGamer.
I had a similar disaster with the black google screen, and I had the unlocked bootloader as well, first I relocked bootloader, then used odin to reflash (http://forum.xda-developers.com/showthread.php?t=947950 ) then used the e0b546c442bf.signed-soju-GRI40-from-GRH78.e0b546c4 update (http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip) renamed it to update.zip, put it on root of memory, and ran it via the built in recovery mode after..phew.
Odin saved my life to!!
Good luck...
i guess i should have updated the post before heading out to lunch
not too long after i posted the original message, i was able to reflash any ROM, and got it to boot back to normal.
it was weird for some odd reason the ROM just got corrupted? i don't see how's that possible
I was on Bionix 1.3 beta for the longest time, and i've been on Bionix pretty much ever since December 2010/Jan 2011
I'm now back to Stock 2.3.3, but i replaced the stock recovery with CW recovery
I simply booted into the CW recovery mode, and then loaded a new ROM from zip
Yipee
AllGamer said:
i guess i should have updated the post before heading out to lunch
not too long after i posted the original message, i was able to reflash any ROM, and got it to boot back to normal.
it was weird for some odd reason the ROM just got corrupted? i don't see how's that possible
I was on Bionix 1.3 beta for the longest time, and i've been on Bionix pretty much ever since December 2010/Jan 2011
I'm now back to Stock 2.3.3, but i replaced the stock recovery with CW recovery
I simply booted into the CW recovery mode, and then loaded a new ROM from zip
Click to expand...
Click to collapse
Glad your sorted....
Thanks to ACS and others for bringing out 4.0 of the ACS ROM. It was a perfect time for me to upgrade because my ACS 1.2 ROM got corrupted for the 4th time (why does that happen? Lack of journaling?) and i figured if I needed to wipe everything anyway, I'd just upgrade. THere are no instructions at all on the main ACS development thread so I read 50 pages of posts and guessed. I did the following:
1. Rebooted into clockwork 3.1 (purple) and selected the ZIP for the stock EC05 Rom with recovery built in.
2. Rebooted and verified it booted correctly (yay)
3. 3-finger reboot into recovery
4. flashed the ICS 3.5 ROM (newest version is 4.0 that just cane out a few minutes ago...)
5. Flashed EC05 to EI22 modem update
6. Flashed Nubernel kernel
Rebooted. Results: Just hangs at the kernel screen. Phone is essentially soft bricked. I'm attenpting to Odin back to EC05 again. I've now spent over 3 hours on this... can someone please update the thread with clearer instructions? Examples:
1. Does this ACS install include a kernel? (did I screw it up by flashing my own?)
2. Does it convert to EXT or was I to know to do that seperately?
3. Will future ACS updates require wiping user data? (it doesnt say)
Thanks!
Brandon
Standby ill give you a play by play that should get you up and running on 4.0
---------- Post added at 07:36 PM ---------- Previous post was at 07:27 PM ----------
Ok, You did good up until step 6. There is no need to flash a kernel as this rom includes a kernel. Just wipe dalvik/cache/data 3x install from zip. From this point you should be good to boot. Let me know if it works
I was on sfr 1.2 too and wat I did first was to flash the ec05toei22.zip first then flash legendary ROM and at the end flash the journalon.zip jst to be safe. Legendary ROM is great, not missing sfr 1.2 at all :0
Sent from my SPH-D700 using XDA App
Thanks everyone. What worked for me was:
1. Odin back to ec05
2. Root with one-click root (+ clockwork recovery purple)
3. Reboot into recovery and flash the ACS 4.0 ROM
4. Reboot.
That's it. Now doing the annoying task of resetting everything back up. Questions:
1. I'm still on ec05 modem. Should I now flash the ec05 to ei22 zip? What will that give me?
2. When this ROm updates (which is happening frequently) do I have to wipe user data? Please say no!
Some things I've noticed so far... I really miss the circular battery icon from 1.2 and the 3g/1x icons too. Anyway to get those back?
Thanks everyone!
Not an expert but the modem is optional really whatever your phone works best with I'm on ei22 modem don't really see a difference and there is a mod for the ciruclar 1% mod in the themes (sorry no link) and usually acs uses full roms so yes you'll have to wipe unless the post directs otherwise however for ERA there is both an update and a full rom.
Sent From my 1.4Ghz V6'd Legendary Epic >-<
While adding data back can be annoying, I've come very use to it myself lol.
As for the modem, use what works best for you.
Sent from my SPH-D700 using Tapatalk
I decided to go ahead and upgrade to the EI22 modem and also turn journaling ON. I'm hoping that I'll stop some of these data corruption issues I have been having (resulting in force close loops on boot... 1.2 would fall into that loop about once every 3 weeks).
So far so good. This ROM is just a shade laggier than 1.2 was but I haven't spontaneously shut down once yet (something that happened a few times a week on 1.2 no matter what kernel I used)
I'll echo what others have said. Here was my process from SFR 1.2
1. Wipe 3x
2. Flash the ROM
3. Flash the EC05toEI22 modem file
Reboot
I had 3.5 bork on me twice with the google.systems.framework.gapps force close issue. I'm about to retry it with 4.0 and journaling enabled.
Keep trying new stuff. Half the fun of all this is that you get to be a part of developing the OS for you phone.
Oh, and back your stuff up when you have it working the way you want it to. I was able to jump back to my SFR 1.2 backup when ICS stopped working. Happy times.
yes backing up is the key...
I backed up before I do each significant change. I think that is key just in case it all goes wonky. I'm currently running the 4.0 build with the EI22 modem and it seems pretty stable. Well, it was until I upgraded to Dolphin 7.x from 6.x. I got 4 hangs in 30min in low memory conditions. It causes GO launcher to freak out and get stuck. Required a battery pull each time. Now with a revert back to dolphin 6.x I've been hang-free for about an hour.
My wishlist:
1. Add reboot into the shutdown menu
2. Make the battery logo pretty like srf 1.2 (I looked in themes and couldn't find it)
3. Fix handcent notifications appearing as black unreadable text
4. Various text box draw issues (example in facebook widget). Just looks sloppy.
I've got stable wifi (unlike some). Will try GPS tomorrow.
I would like to add to your wishlist remove the low battery alert for the camera... u can't take pics if your battery is low
Sent from my SPH-D700 using Tapatalk
Yeah I am similar to some of the others...
I was on frozen with ec05 so:
1. wiped everything x3
2. flashed modem
3. flashed acs 4
4. installed everything i needed.
5... just AWESOME! >< works great and fast.
Need to figure out if it works in the docks... now to go to bed and hope my alarm works in the morning into my speakers through my dock ><
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.
Darky 9.5 flash tutorial
Credits to this rom goes to de darky team http://www.darkyrom.com
Im just a long time user of this rom, have tried many others up until ICS and allways get back to darky rom, maynly because its rock stable, everything works, its fast enough and it has call recording working perfect.
I want to share this awsome rom, that i consider to be the best there is, for people that want a fully stable 100% working rom with call recording.
when i have some time i will post a video showing off some stuff in the rom.
Enjoy
Download package with froyo js8 firmware, kernel, Darky 9.5, etc all you need to get this rom working on your phone.
WARNING
Before flashing check if you have keys installed or samsung usb drivers, and keys must be allways closed when using ODIN.
Rapidgator
http://rapidgator.net/file/84a6d9a4f4cd427ac54237dace5089f8/Darky_9.5_install_pack.rar.html
Mediafire
http://www.mediafire.com/?377ke7qqaq4s123 part1
http://www.mediafire.com/?8q1ue3rkbc90y4c part2
http://www.mediafire.com/?4iow33b2yf9fa13 part3
http://www.mediafire.com/?6mupa37vsicm99t part4
http://www.mediafire.com/?2l395ds3tz2mm98 part5
1. Go to folder “GT_I9000_XWJS8_XXJQ1_NEEJS1”
2. Open “Odin3v1.3”
3. Check Re-Partition in “Odin3v1.3”
4. Choose s1_odin_20100512 in PIT
5. Choose PDA_XWJS8.tar in PDA
6. Choose PHONE_XXJQ1.tar in PHONE
7. Choose CSC_NEE_JS1.tar in CSC
8. Put your Galaxy S in download mode ( volume down + turn on + home)
9. Connect Galaxy S to USB cable
10. Press START in Odin
11. Wait until its flashed and phone restarts
12. Unplug USB cable
13. After restart go to the phone keypad
14. Press *2767*3855# this will reset your phone and erase internal memory
15. After phone resets and restarts
16. Turn off phone and put it in Download mode ( 3 key combination above again)
17. Open Odin3v1.3
18. Put speedmod-kernel-k13e-500hz tar in PDA (DO NOT REPARTITION)
19. Connect USB cable
20. Press START (this will install the kernel with root and recovery mode)
21. After phone restarts
22. Put Darkys_v9.5_Extreme_Edition and Darky ROM v1.0.6.apk on internal memory card
23. Open file explorer from your apps and install Darky ROM v1.0.6.apk
24. Open Darky ROM v1.0.6 that you just installed
25. Check WIPE the device if you can, if not its checked by default
26. Kernel options check SKIP KERNEL
27. Modem options check JPY (Recommended)
28. Check Alternative WIFI driver (for ad-oc capability)
29. Check circle battery icon
30. The rest I leave unchecked, check LIVE WALPAPERS if you want
31. SAVE and EXIT
32. Turn off phone
33. Go to RECOVERY MODE (volume up + turn on + home)
34. Wipe data factory reset
35. Wipe cache partition
36. Go to advancedclockworkmod features and wipe dalvik cache
37. Go back and INSTALL ZIP from sd card
38. Choose zip from sd card
39. Choose Darkys_v9.5_Extreme_Edition OK
40. After flashing and phone restarts, from menu go to recovery mode
41. In recovery choose advanced speedmod ULK features
42. Lagfix options
43. Enable lagfix:convert data to ext4
44. Go back , back reboot system
45. After reboot go to recovery again to lagfix options and choose Convert system to ext4
46. Reboot system again
47. After reboot go to recovery again and choose Tweak options (below lagfix options)
48. Enable the first 3 options and reboot system
49. Flash Ice Cream Fugu from recovery and reboot phone every time you flash something (wipe dalvik cache before flashing this)
50. Flash GPS fix if you want from recovery and reboot phone every time you flash something (wipe dalvik cache before flashing this)
51. Flash Modem_ZSJPG-CWM if you want from recovery and reboot phone every time you flash something (wipe dalvik cache before flashing this)
52. When you make or receive a call there is a record call button to press if you want to record a call
53. To ENABLE the phone to record all calls automatic everytime you make or receive a call do the following
54. Open a file explorer I use OI file manager and in options check to see hidden files
55. Rename “.norec_in” and “.norec_out” to “.rec_in” and “.rec_out”
56. That’s it, the best rom in this galaxy and beyond with call recording is yours.
Really Reaaaaaaaaaaaaaaaaaaaaaaaally THAAAAAANKS MAAAN :-x :-*
thxs u for share such good ROM.
I follow ur instructions and it works great.
but I have a problem, when I unplug the battery charge, the circular battery icon become 97% not 100%, how to fix that?
zeroarst said:
thxs u for share such good ROM.
I follow ur instructions and it works great.
but I have a problem, when I unplug the battery charge, the circular battery icon become 97% not 100%, how to fix that?
Click to expand...
Click to collapse
Just like any rom you got to give it some time, when you have a couple of cycles of battery charge and discharge it will be 100% when you unplug.
Also make sure you unplug the cable asap when its 100%....3 to 5 cycles and should be fine.
Good luck
Hi,
When I follow your procedure up to step 10, it finishes instantly and ODIN says "<OSM> All threads completed. (succeed 0 / failed 0)". Any idea? :O
---------- Post added at 05:40 PM ---------- Previous post was at 05:14 PM ----------
As it turns out, I didn't have any Samsung drivers installed. I downloaded the installer from samsung.com, it detected and installed the composite driver and after restarting ODIN, it found a device on 'COM6', working now
v0id said:
Hi,
When I follow your procedure up to step 10, it finishes instantly and ODIN says "<OSM> All threads completed. (succeed 0 / failed 0)". Any idea? :O
---------- Post added at 05:40 PM ---------- Previous post was at 05:14 PM ----------
As it turns out, I didn't have any Samsung drivers installed. I downloaded the installer from samsung.com, it detected and installed the composite driver and after restarting ODIN, it found a device on 'COM6', working now
Click to expand...
Click to collapse
Good that you solved it, ill post a warning on the top so people know they must have keys or samsung usb drivers.
14. Press *2767*3855# this will reset your phone and erase internal memory
first of all, thanks for the ROM. The above means it will clear the internal SD card?
thanks again.
NickDunn said:
14. Press *2767*3855# this will reset your phone and erase internal memory
first of all, thanks for the ROM. The above means it will clear the internal SD card?
thanks again.
Click to expand...
Click to collapse
Yes and factory reset.
Tapatalk from GT-I9000
Anybody know why darky is not joining the ICS madness? I used to love this rom.
My extensive reading brought me here and this looks like a friendly place so here goes.
I'm considering trying Darky 9.5 specifically for the Call Recording.
Q 1: Can I simply extract the Phone.apk from Darky v9.5 and use it in DarkROM v10.4.2, or my current stock JW1 ROM?
Q 2: If I move to Darky ROM can I re-use the (stock) KG3 baseband/modem as it is for Canada?
Q3: As my sig shows, I am (at present) on stock JW1 + stock KG3 modem, + Semaphore kernel. Do I need to flash back to full stock KG3 or JW1 before proceeding? I use Odin.
Thank you!
Catalyst2012 said:
My extensive reading brought me here and this looks like a friendly place so here goes.
I'm considering trying Darky 9.5 specifically for the Call Recording.
Q 1: Can I simply extract the Phone.apk from Darky v9.5 and use it in DarkROM v10.4.2, or my current stock JW1 ROM?
Q 2: If I move to Darky ROM can I re-use the (stock) KG3 baseband/modem as it is for Canada?
Q3: As my sig shows, I am (at present) on stock JW1 + stock KG3 modem, + Semaphore kernel. Do I need to flash back to full stock KG3 or JW1 before proceeding? I use Odin.
Thank you!
Click to expand...
Click to collapse
Q1 Not possible, call recording only works on froyo based roms, DarkyROM v10.4.2 is based on Gingerbread.
Q2 If you move to Darky 9.5 you can use froyo compatible modems, so check if that one is compatible with 2.2.1 froyo versions.
Q2 if you want to flash darky 9.5 just follow my guide above, exacly as i say, you can be using any rom atm so doesnt matter, the guide is valid independently of the rom you are using because flashing with odin will erase all and install a js8 base.
Good luck hope you enjoy..call recording rulez ;P
Hey, this rom works great but I have one problem. The wi-fi won't work... I've tried the ad-oc one and the original one. Wifi is working fine though because my laptop is connected to it. I've tried forgetting it and reconnecting etc. But no luck. It says its connected but no data transfer. Any suggestions?
Hey, this rom works great but I have one problem. The wi-fi won't work... I've tried the ad-oc one and the original one. Wifi is working fine though because my laptop is connected to it. I've tried forgetting it and reconnecting etc. But no luck. It says its connected but no data transfer. Any suggestions?
Click to expand...
Click to collapse
Never had a non working wifi in any rom, so ill try to help just gessing logicaly.
Try to see if the wifi works in another router, go to a friends house, if its not working i think either you did something wrong in flashing steps, or the wifi is broken at a hardware level.
Sry i cannot be of more help good luck.
Tapatalk from GT-I9000
waldo698 said:
Hey, this rom works great but I have one problem. The wi-fi won't work... I've tried the ad-oc one and the original one. Wifi is working fine though because my laptop is connected to it. I've tried forgetting it and reconnecting etc. But no luck. It says its connected but no data transfer. Any suggestions?
Click to expand...
Click to collapse
Will not work on a N + G router, change router to G only and it works.
Sent from my GT-I9000 using Tapatalk 2
Hampy said:
Q1 Not possible, call recording only works on froyo based roms, DarkyROM v10.4.2 is based on Gingerbread.
Q2 If you move to Darky 9.5 you can use froyo compatible modems, so check if that one is compatible with 2.2.1 froyo versions.
Q2 if you want to flash darky 9.5 just follow my guide above, exacly as i say, you can be using any rom atm so doesnt matter, the guide is valid independently of the rom you are using because flashing with odin will erase all and install a js8 base.
Good luck hope you enjoy..call recording rulez ;P
Click to expand...
Click to collapse
Thanks for the clear reply!
Not sure I want to go back to Froyo. Is there any possibility for Call Recording with GB ROMs?
Do you know if the Call Recording is dependent on the Kernel, as there are market Apps that can do it, but not the one I was using, at least not with Semaphore 2.5?
Catalyst2012 said:
Thanks for the clear reply!
Not sure I want to go back to Froyo. Is there any possibility for Call Recording with GB ROMs?
Do you know if the Call Recording is dependent on the Kernel, as there are market Apps that can do it, but not the one I was using, at least not with Semaphore 2.5?
Click to expand...
Click to collapse
I think there are some market apps that can record in GB roms not sure, i tryed some long time ago and no app worked, but it can only record with phone mic so you only hear your voice...maybe turning phone loud speaker on can be possible to record the other side also...but the quality might be from really really bad to even worst then that , if you want crystal clear call recording must be on froyo.
So if you really want and need call recording must be on this rom, best froyo you can get...for me call recording is a very handy feature that i cannot afford to not have.
This ROM look's very cool.
It deserves a try.
Hampy said:
So if you really want and need call recording must be on this rom, best froyo you can get...for me call recording is a very handy feature that i cannot afford to not have.
Click to expand...
Click to collapse
I had acceptable luck with Auto Call Recorder using Stock KG3 2.3.3 Firmware . I have tried JW1 with two custom kernels with same bad results so I suspect something in the JW1 firmware (not the custom kernels) is the cause .
Should I follow these instructions or the one posted on Darky's website?
http://www.darkyrom.com/community/index.php?threads/guide-installing-darkys-rom-on-2-2-2-2-1-i9000-i9000m-only.1041/
I'm on a completely stock I9000 2.2 firmware...
Thanks!
kpfury said:
Should I follow these instructions or the one posted on Darky's website?
http://www.darkyrom.com/community/i...rkys-rom-on-2-2-2-2-1-i9000-i9000m-only.1041/
I'm on a completely stock I9000 2.2 firmware...
Thanks!
Click to expand...
Click to collapse
Follow my guide it ensures all will work without problems i flashed darky many dozens of times, and found this to be the best way. Cheers
Tapatalk from GT-I9000