UPDATE: This ROM is now outdated. Please use Dfgas's newer MIUI port, located here:
http://forum.xda-developers.com/showthread.php?t=1152518
Original Post:
You've watched. You've waited. You've sat impatiently looking for an update. I know I have. The wait is over.
Gingerbread AOSP MIUI 1.6.24 MTD Port
Ported to: Mesmerize (still having issues with Showcase port)
Please note: The 1.6.24 links currently posted are not my work! I just couldn't correct the eri.xml in framework-res.apk to remove "Verizon Wireless" from the top bar (cosmetic I know, but it bugged me--I'm picky like that), and... BDE sorta had his port done several hours before mine anyway. I can't take any credit whatsoever for these links, this is all his porting work.
WARNING: READ BEFORE FLASHING!!
This ROM was designed using the newer (for us) yaffs2/ext4 filesystem. Excepting CM7MTD, no other ROM uses this filesystem. As a result, this ROM uses CWM 4, and once you flash, you CANNOT flash any other ROM from Recovery. Should you have issues with the flash, or want to return to a different non-MTD ROM, you will need to Odin all the way back to stock. See post #2 for instructions.
SHOWCASE USERS: This is especially critical for Showcase users, as Cell South has prevented Odin flashing packages for the Showcase. IF YOU USE A CELLSOUTH SHOWCASE AND WANT TO FLASH BACK TO A DIFFERENT ROM, FIND A WORKING ODIN PACKAGE FIRST.
As always, the standard warning applies: I am not responsible for what may happen to your phone as a result of flashing this ROM, properly or improperly. No warranty whatsoever. You have been warned.
Credits
The biggest thanks go out to jt1134. NONE of this (including CM7MTD) would be possible if it weren't for the work he's done for the Fascinate, Mesmerize, and Showcase.
Andmer has also been critical to making this happen. He was the one to take JT's work, use his AOSP source, and build a working MIUI port for the Fascinate. Both he and JT continue to modify the ROMs and Kernels for MTD that we enjoy to work towards getting that hardware working.
Without these guys, there would be no port for us.
I'd like to thank lmartin92 for his tremendous help and knowledge. He worked tirelessly with me to get this working. Similarly, bdemartino has been a huge help in all around, as well specifically making sure we could get the "fascinatemtd" SMS padding code implemented into CM7MTD, and therefore MIUI MTD. Lastly, I'd like to thank Akellar for getting some Framework-res cosmetic edits working when I could not.
1.6.24 Note: Again, these are actually BDE's ports, not mine, I can't take any credit.
ROM Details
Update Schedule: MIUI receives weekly official updates, and Andmer has said he intends to port them to the Fascinate on that same schedule. I intend to port from his work on that same schedule, and once my overlay is fully worked out, it should take me only as long as it takes to apply it and upload. This thread will be updated every time a new ROM is released. I'll try to keep one or two previous week's ROM links just in case.
Radio: This ROM does not flash a radio, so it should use whatever radio you had before you flashed. This ROM is built for a Mesmerize/Showcase radio (making it an actual Mesmerize port), so if you're using the Fascinate EC01 radio, you'll want to either flash the EC10 or EE19 radios (typically by flashing the stock versions of those ROMs). Don't worry if you flash those ROMs; everything else (except the radio) will get overwritten.
Recovery: In order to support the yaffs2/ext4 filesystem, this ROM uses CWM 4. As a result, the normal "three finger Recovery" method does not work. Similarly, although the ROM includes a "Reboot into Recovery" menu option after holding power, that does not boot into recovery. The only method of getting into recovery at this point is to either use ADB or a Terminal Emulator app.
Within Terminal Emulator, type the bolded, underlined text:
su (enter; this grants SuperUser rights to Terminal Emulator)
reboot recovery (enter)
This should properly reboot the phone into Recovery mode.
Working:
Calls
Bluetooth!!
3G / Data
WiFi
SMS
Camera/Camcorder!!
USB mass storage / sdcard
GPS
ALL Sensors!!
Not Working/Known Issues:
MMS
Calls/SMS during deep sleep mode are not waking up the device to ring.
This app will prevent your device from deep sleep which is of course a battery drain, but you will receive calls. Whether its worth it or not is up to you.
https://market.android.com/details?id=otis8.softlocker
How to Flash
Copy the ROM to your SDcard.
Reboot phone into recovery, flash ROM as normal.
Make sure to wipe data, cache, and dalvik cache if you are coming from a non-MTD ROM, and possibly even CM7MTD.
Flash MIUI ROM from SD card.
The "MIUI" branded flash script will appear, and quickly disappear. THIS IS NORMAL. This verifies if CWM 4 is installed (on the first time through it will not be), and if not, installs it. The phone should reboot once again into recovery, but it will be standard CWM 4 Orange recovery.
Flash the ROM from your SD card once more. Note that the softkeys have changed; use the Search key as "Enter". The flash should proceed as normal.
1.6.24.1: Flash the 1.6.24.1 patch to correct all sensors.
Reboot phone when complete.
When your phone reboots, you should see the normal Samsung logo, and then a Galaxy S/CyanogenMod 7 logo. This will be followed by the MIUI.us boot screen, which is a moving starfield with a spinning globe.
Welcome to GB MIUI!
Mesmerize Download
http://olvisfoundation.com/xdadump/bdemartino/ROMS/MIUI/MIUI.us_mesmerize_1.6.24.1_Eng_Deo_ZipA_Signed_0627.zip
Showcase Download
((Still broken))
1.6.24.1 Patch Download - Fixes ALL sensors! (for both Mesmerize and Showcase, once later is released)
http://olvisfoundation.com/xdadump/bdemartino/ROMS/MIUI/MIUI.us_patch.zip
HOW TO GO BACK TO NON-MTD ROMS
Kanged from the Fascinate forums with immense thanks to kidserious, and referencing the "Files to get your Mesmerize back to stock 2.1 and 2.2.1" guide from Phidelt82
Things you'll need:
Odin
Working Odin package for your phone model
If you don't already have these, here are some links (sorry, Mesmerize stock ROM only):
Odin: http://download1422.mediafire.com/ii578172dylg/429fcpdtpckkcea/Odin3+v1.83.exe
EC10 Odin Package: http://www.megaupload.com/?d=N6JNT1ZE
Whatever Odin package you use must have a full bootloader included in the flash. EC10 should work, EE19 may not. I'm unable to advise which Showcase Odin package would work, I'm not familiar enough and they're not generally available.
STEP-BY-STEP
I'm writing these for the Odin newbie in mind. Experts, as long as you check "Repartition", you know the drill.
Open Odin. This does not need to be installed, simply run.
Pull off the back from your phone, remove the battery.
Connect the USB cable (best with the Samsung one that came with your phone), and hold Volume Down until you see the phone say "Download Mode". A little box should turn Yellow in Odin, signifying it detects the phone and is ready to flash it.
Click the PIT button. Locate the path to the PIT file extracted from the ZIP you downloaded above (or previously) to populate that field.
Click on the PDA button. Locate the path to the TAR.MD5 file extracted from the ZIP you downloaded above (of previously) to populate that field. Do NOT click on PHONE, Phone should be empty.
Make sure Re-Partition is checked. We want to overwrite the previous MIUI flash, and Re-Partition is what lets us do that fully.
Click the Start button. Let it proceed through the whole flashing process, which is approximately 10 minutes. You'll see "Complete!" in Odin and your phone's screen will go blank once it's finished.
For thoroughness' sake, I'm including the below steps. Again, experts could potentially circumvent, but below is the failsafe way.
Re-insert battery, boot phone. Allow it to boot into Blue (stock) recovery. it's okay if it says it can't mount "HIDDENSDCARD"; it's done the rest of the setup it needs to. If you're just staying with the stock ROM and recovery, you're done.
If you want a custom recovery:
Follow steps 1-7 above, skipping over step 4 (no PIT file needed), and flash your recovery of choice. You should now be able to flash whichever custom ROM you were on before, or restore from a Nandroid backup.
It is absolutely mandatory that you follow these steps exactly to properly get off of GB MIUI MTD (or CM7MTD for that matter) so that you can flash another ROM. Attempting another method or not following these steps implicitly will result in a bricked phone and you will have to follow this guide to fix it.
#3 reserved for me also.
Good for you man. Way to go!!!!!!
Tap-a-Talked from my Mesmerize
is there anyway u could port the cm7 releases to id really love to be running cm7 instead of having to flash fascinate radios and all tht crap..
Outstanding.
I'd love to test on my showcase. I have everything I need to go back via odin, and this is the rom I've been waiting for.
Congrats man, I know how much time/effort you put into this!
Sent from my SCH-I500 using XDA App
O and thx my pants are wet now good rom
Sent from my SCH-I500 using XDA App
hold of on tht keeps boot looping on the miui bootupscreen any thoughts?
I got the same thing, but I think it's because I forgot to wipe data/cache/whatever... So I'm trying again.
Edit:
Yeah, it's just looping the spash.
Im also getting boot loop. Im on the ee19 radio, should i do the 10 and retry it?
i tryed both and it bootlooped
godofwar762 said:
i tryed both and it bootlooped
Click to expand...
Click to collapse
That makes me very worried about flashing this.. I was just going to do it.
I wonder if flashing to the cm7 then trying to flash this would work better. Using the cm7 you can use rom manager to install the miui, so im gonna try that.
Edit: Unfortunately same thing that route also. Boot loop
That's what I came from, then the second time I went from the latest offical froyo.
seishuku said:
That's what I came from, then the second time I went from the latest offical froyo.
Click to expand...
Click to collapse
With no issues?
It did the same thing.
Well imma go try it ill report back when I'm done.
Are you guys flashing the Rom twice like the op says to?
Sent from my SCH-I500 using XDA App
Related
These instructions should work from almost any ROM when flashing Apex 9.x, but I felt specific instructions were needed for CM7. If coming from something other than CM7, you should make sure that your filesystems are RFS before messing around with Odin.
Here is the thread for Apex: http://forum.xda-developers.com/showthread.php?t=952588
Thanks : Watsa, DesignGears, Atinm, Cezar', Shortfuse, and anyone else.
Files you need:
--Apex_9.1_JVR.zip - http://apexromcaptivate.weebly.com/apex-9x---jvr.html
--Apex Flasher.zip - http://apexromcaptivate.weebly.com/installation-instructions2.html
--I897UCJF6-final-OCD-REV0.zip - http://forum.xda-developers.com/showthread.php?t=731989
--efs-backup.tar.gz(Optional) - this should have been created either strait out of the box, or sometime before you started flashing custom ROMs. If you've gotten this far flashing ROMs and your IMEI isn't screwed up, then you should still backup- http://forum.xda-developers.com/showthread.php?t=859914
--I897UCKF1-bootloaders.zip - http://forum.xda-developers.com/showthread.php?t=1129821
--SuperOneClickv2.1.1-ShortFuse.zip - http://forum.xda-developers.com/showthread.php?t=803682
1. Starting with CM7nightly84 (on official 2.2 boot-loaders acquired from Kies Mini (pre-CM7 install)), I used DG's OCD Odin JF6 (NOT the 3-button-fix version) to get back to stock. CLOSE the OCD window after stock flash is done. I then placed Apex_9.1_JVR.zip on my internal sd card.
2. Then, I rooted 2.1 with Super One Click and restored my /EFS folder from the backup file using ADB. After restoring /EFS, I immediately reboot in download mode and reflash to stock again using the same Odin OCD (make sure you close the one you used to flash in step one and open a new instance of it and unplug and replugin usb between every flash or you might end up a saaad panda). This makes it as close to an "Out of Box" state as possible. I'm sure this step can be skipped if a backup isn't available. This is just something I always do between flashes.
3. I downloaded Cezar's KF1 boot-loaders OCD and followed the instructions provided in the thread about how to flash them. This had me end up with KF1 boot-loaders on an otherwise completely stock, unrooted, JF6. The KF1 boot-loaders should not affect 2.1 or 2.2 normal functioning.
4. Then, I extracted the Apex pre-flash package (Apex Flasher.zip) and followed the instructions as if the boot-loaders were already flashed. This got me on Dark Core 3 - JVR_C. Watsa confirms that the KF1 boot-loaders in the Apex Flasher.zip are the same as Cezar's that are in the forum listed above. The only reason I didn't use them is because flashed them on my own.
5. Ater all that is done, reboot to the white AT&T screen. I would recommend a battery pull or recovery key combo (vol+, vol-, & power) as soon as you see it because the DC3 kernel will try to apply Voodoo ext conversions with stock 2.1 still on there. Upon arrival at the recovery screen, chose the option to install zip and find Apex_9.1_JVR.zip .
All done. When it reboots, you'll hear that beautiful robotic voice of the lady converting your partitions. Sounds almost dirty, doesn't it?
If you don't hear anything, reboot into recovery and enable the options under the "voodoo" menu.
reserved...
Try using i9000 gb bootloaders on an i9000 gb rom
Captivate 2.3.4
Thegodfather156 said:
Try using i9000 gb bootloaders on an i9000 gb rom
Captivate 2.3.4
Click to expand...
Click to collapse
I setup this guide for anyone who wanted to use the KF1 boot-loaders specifically. Starting at CM7 nightly #78, emmc is now supported on gingerbread boot-loaders for the captivate. This means that after loading these you shouldn't have to change boot-loaders again if you wanted to go back to CM7 or switch to a new ROM. All of the I9000 based GB ROMs I have seen have reported no issues using KF1 booties. Some devs even recommend them to ensure hardware compatibility. They seem to work great with Froyo as well.
I don't know what to do next, and I need my phone. I can answer any questions, but I wouldn't know what to start with. Can someone help??
Quick questions to answer:
1. What Rom were you on prior to flashing?
2. What Rom were you flashing to?
3. What do you see on your screen?
4. Do button presses give any reaction?
1. http://forum.xda-developers.com/showthread.php?t=1136128 v5.0, it's Gingerbread.
2. I was flashing to CM7, but it didn't flash, so I did what was probably a mistake and went straight for http://forum.xda-developers.com/showthread.php?t=1625619&page=1.
3. I see "DevilKernel" Samsung Galaxy S.
4. If I hold down the volume and power buttons, the DevilKernal boot screen will flash. If I keep the power button held down it resets, if I don't it just flashes and nothing else.
By the way, thanks.
Ok, here's what happened:
The first bootloop you were seeing with CM7 is actually a normal occurrence. You usually have to flash CM-based roms twice to get them to "take" (the first time sets up MTD over BML, the second time installs the rom).
What you're seeing now is the devil kernel trying to load up the CM9-based system, but not having all the parts in place.
Thankfully, you're not in that bad of a place. The easiest thing to do right now is to grab an Odin- or Heimdall-based one click Gingerbread stock package without bootloaders. There's a sticky in the Development section that has them, or you can grab the one in my signature.
Flash the one-click, go to recovery, and flash either CM7 twice or TWICS twice.
That should fix you up.
When I tried flashing the CM7, it said it failed. I'm not sure what went wrong. The TWICS I planned on flashing twice, but it got stuck.
Hard to say - it could be something as simple as a bad download of the flash file.
But you think if I Odin it and try TWICS again it'll work?
It should. Doing the Odin one-click will reset everything back to a factory state, which should remove all the obstacles that would normally stand in the way of a successful installation.
Hey man, for that ROM, this theme will work, right?
http://forum.xda-developers.com/showthread.php?t=1095911
I don't know anything about themes. Or this, apparently. I also got into Recovery and installed it twice, I don't really know what's going on.
So you're now fully set up with TWICS, or you're saying that it's still misbehaving?
Also, that theme should work - I had a CM7 theme that I was able to use with a CM9 rom's theme chooser. Wasn't 100%, but it generally worked.
I'm not sure WHAT is going on. The ROM seems to be working fine, I am reinstalling my apps from Titanium Backup and a "Low on space" popup is here, but that makes no sense since it's the same phone, it's a smaller ROM, and a 32gig SD Card. I also just got a text message that was "rejected due to low space".
What is going on??
It seems my phone always is unable to continue once Super Monkey Ball 2 tries to be backed up.
Look around in the cm7 thread for the dbdata full issue. I think there were some suggestions for how to deal with it in there.
Good morning,
While not a noob to rooting or flashing (currently active on Galaxy tab 2 boards) I appear to have made a noob mistake, and even though I searched and read stickies, etc - still made the mistake.
I rooted the Rogers Infuse 4G using this thread http://forum.xda-developers.com/showthread.php?t=1197248 and it worked without issue.
Decided to try the enable lag fix option - deleted the voodoo file on the sd card, and rebooted the phone. Phone got stuck on SAMSUNG screen (unfortunately - did not notice that the volume was off on the phone) and I did not hear the "voice" telling me what was going on - so rebooted the phone by holding the power button until it rebooted.
Spent a couple of hours after that re-reading, and since I was able to get into download mode - was able to reflash stock package through odin. When the phone did finally reboot (thankfully, as this is my daughter's daily driver) I noticed there was already a voodoo file on the sd card, with another file inside named "logs" Just in case, I deleted that file, and added a new one called "disable-lagfix" as per the original instructions.
Just to be sure - went back and ran the rooting procedure, and can confirm that we have root.
From there, I decided to flash the 100% working CWM Recovery file through Rom Manager - found the details on this thread http://forum.xda-developers.com/showthread.php?t=1107881 and can confirm that after rebooting into recovery - the phone has CWM Version 2.5.1.2
The phone is currently fully functional, no issues with network or wifi, playstore, etc - but would like to know if anyone can confirm that we are good to go should we decide to upgrade to a custom rom. I've done so much reading - that the recovery version confuses me ( red or blue, etc). I realize that some of the threads are back from early to mid 2011 - so not sure if they are still completely valid - so am asking before proceeding.
Phone settings are the following:
Kernal 2.6.35.7-I997RUXKG3-CL366622
Build GB.UXKG3
Baseband I997RUXKG3
Firmware 2.3.3
CWM 2.5.1.2
Currently have the voodoo/disable-lagfix file on the sd card
If anyone has gotten this far into the thread - and can offer up some feedback or recommendations - it would be appreciated
Thanks in advance,
Bill
I usually don't trust Rom manager, but if you are able to boot to recovery then I would say you are good.
If you want the red one (don't remember the version) you could flash a custom kernel with sgs kernel flasher (available on play store).
Infusion should work for you
andros11 said:
I usually don't trust Rom manager, but if you are able to boot to recovery then I would say you are good.
If you want the red one (don't remember the version) you could flash a custom kernel with sgs kernel flasher (available on play store).
Infusion should work for you
Click to expand...
Click to collapse
Thanks for the reply - appreciate your time
Guess it's time to turn that volume up, delete the voodoo folder, and cross my fingers....
Just to confirm - do I delete the voodoo folder itself, or the disable-lagfix folder inside the voodoo folder only ?
Again, thanks
:good:
What were you planning on flashing?
You can probably leave it there for now, and after you have flashed then you can dispose of the folder.
Sent from my Transformer using xda app-developers app
andros11 said:
What were you planning on flashing?
You can probably leave it there for now, and after you have flashed then you can dispose of the folder.
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
First off andros11 - thank you so much for your time in replying to my issue.
My daughter has been looking over the development site - and,
as it stands right now, she has her mind set on the Dark Night Rom by VortexJunior.
Here is the link, if it helps http://forum.xda-developers.com/showthread.php?t=1662280
The install instructions, while relatively simple - and similar to what I am used to doing - but no mention of lagfix
Installation: From Gingerbread
1. Download Zip
2. Wipe Data/Factory Reset
3. Wipe Cache Partition
4. Flash
5. Reboot into recovery(Advanced>Reboot recovery)
6. Flash again
7.BAMM!
Thanks again for your time and replies,
Regards
Once on ICS I don't think you have to mind about lag-fix..
Also, I suggest you just reboot instead of rebooting into recovery. That often causes recovery bootloops.
When you reboot, the phone will hang at the kernel splash screen (this is normal). Just take out the battery, place it back in and boot into recovert with 3-finger combo (vol +, vol - and power, and let go when samsung logo pops up)
My personal suggestion is that you move on to JB. It performs much better, and mostly all development is now there.
Perfect - thanks
Am running CM 10.1 on my tablet, and love it
Will have my daughter research JB ROMs instead.....
Happy Holidays to you and your family
Regards,
sent from my GT-P3113 using Tapatalk 2
Lag fix??
I am confused.. what exactly is the lagg fix? My GF has a JB (one of phablet ROMS) installed and all the JB ROMS I have installed on this phone (and I think all ROMS besides JB) have had lagg problems. So I would really like to know how to fix this phone.
About that lagfix...
If I remember correctly voodoo lag fix was originally designed for the Galaxy S to change the file system it ran at to something that made the phone feel more responsive and access recourses quicker. It was ported to other ROMs so if a ROM includes it then you're ok to use it but I don't think you can just apply it to any JB ROM. Plus after using a GB ROM with this lagfix for some time, any 4.0 and above ROM I have used after that has been a LOT quicker in comparison. So I would probably look into the way you JB roms were installed maybe do a data wipe/factory wipe in CWM and reinstall the ROM from the beginning. What ROMs are you using exactly?
A few more things you should know before I get into it. First off, this is my mother's phone, and about two days ago, she went to unplug and use her SGS4G after it had been charging overnight, and it wouldn't respond to the Power/Lock Button (It appeared simply stuck). So, naturally, she did a battery pull on it, and tried to turn it back on. After she hit the Power Button though, the Splash came up like it normally does, except instead of progressing with booting, the screen went black for a second and then went back to the Splash and it did/does this indefinitely (An obvious sign of a Bootloop).
Now. What doesn't make sense to me is that this was running the Stock ROM (I don't know if it was Froyo or Gingerbread), yet this still happened. I haven't tampered with the Phone at all, and my mother isn't too fond of the idea of Rooting, so unless the previous owner (Yes, it is a used phone) tampered with it and then restored it to Stock, then I have no idea.
Things I have tried:
Heimdall One-Click For Dummies (With and Without flashing Bootloaders)
Juls317's Noob Guide's "Potential Problems" section (With both Heimdall and ODIN)
A few Kernels (bhundven's Kernel, drhonk's KG4 Kernel)
sygee's ODIN/Heimdall Flashable ROM
hailthetheif's Step by Step Rooting Thread
Also, after I flash anything, whether it be with ODIN or Hiemdall Suite, or Hiemdall's One-Click, if I leave the phone plugged into the computer afterward, it will go to the Splash Screen and then to the Battery Screen (Which doesn't work, it just freezes with the Loading Wheel) and it'll Bootloop with the Battery Screen. If I unplug it after Flashing, it goes back to the classic Splash Bootloop that has been happening since Day 1. It doesn't even get past the Kernel.
I know that at least the Kernel and the Bootloaders can be Flashed however, by how they act on the Device. For example, if I flash certain Gingerbread Bootloaders, I can only get into Download Mode with PWR + VOL-, whereas on the Froyo Bootloader (Includes Stock), you use VOL+ + VOL-. With the Kernel, for example, if I flash a TeamAcid Kernel, their Logo comes up on the Splash Screen, but it still does the Splash Bootloop no matter what.
One final thing, if I flash a Kernel/ROM that includes a Recovery Mode, I can't access it at all (PWR + VOL+). I couldn't/can't access the Stock Recovery at all either.
One final thing, if I flash a Kernel/ROM that includes a Recovery Mode, I can't access it at all (PWR + VOL+). I couldn't/can't access the Stock Recovery at all either.
Pull the battery, hold power& both volumes, drop the battery back in. Should bring you to recovery (gb, not sure, can't remember froyo same or not). Wipe data & cache etc.
On the heimdell, awesome threads that you quoted. Follow directions and it should get you there. Kj6.. you may have to flash it twice to get the bootloaders for gb(it's setup that way so you can't fubar it without trying really hard). You would have to check the load boot loader box on second flash.
I just had this same exact issue. No matter what I flashed, it wouldn't work. Just kept with the boot loop. Now the difference with my issue was, I was still able to get into CWM and/or Download mode. (I was running custom rom). Heimdall wouldn't work for me because it was a driver issue. Odin, well, all the links I found for Odin were dead..
Anyway, when you're working with Heimdall, does it recognize your phone and flash? I had to flash it over twice for it to get to work. It is possible she was on Froyo and you're trying to flash it over with a GB stock rom could be causing an issue. Someone correct me if I'm wrong.
I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there.
This thread helped me out the most:
http://forum.xda-developers.com/showthread.php?t=2042927&highlight=frozen+at+boot
LiangChi said:
I just had this same exact issue. No matter what I flashed, it wouldn't work. Just kept with the boot loop. Now the difference with my issue was, I was still able to get into CWM and/or Download mode. (I was running custom rom). Heimdall wouldn't work for me because it was a driver issue. Odin, well, all the links I found for Odin were dead..
Anyway, when you're working with Heimdall, does it recognize your phone and flash? I had to flash it over twice for it to get to work. It is possible she was on Froyo and you're trying to flash it over with a GB stock rom could be causing an issue. Someone correct me if I'm wrong.
I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there.
This thread helped me out the most:
http://forum.xda-developers.com/showthread.php?t=2042927&highlight=frozen+at+boot
Click to expand...
Click to collapse
It does recognize the phone, and it does Flash (As far as I know). I used Zadig, so there shouldn't be an Driver problems. I flashed it several times with a lot of different things, however, I just now flashed it twice with the Heimdall One-Click again to see if that made any difference. It did not. I'm still stuck in that Splash Bootloop.
Also, what did you mean by, "I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there."? I haven't ever seen that suggested anywhere, and I have no idea where I would find a Stock Froyo ROM that is flashable via Heimdall.
Able to get in to recovery and wipe? Wipe data & caches. Got cwm? Which one click? Eilleo(sorry for the spelling) put out a one click that was to be used as stepping stone to ics only.
WinterPhoenix96 said:
It does recognize the phone, and it does Flash (As far as I know). I used Zadig, so there shouldn't be an Driver problems. I flashed it several times with a lot of different things, however, I just now flashed it twice with the Heimdall One-Click again to see if that made any difference. It did not. I'm still stuck in that Splash Bootloop.
Also, what did you mean by, "I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there."? I haven't ever seen that suggested anywhere, and I have no idea where I would find a Stock Froyo ROM that is flashable via Heimdall.
Click to expand...
Click to collapse
I'm honestly not to sure if a Froyo ROM for Heimdall exists. I do believe seeing one for Odin, though. Not sure if that link is still alive. I'll see if I can find it again.
We do have a Froyo One-Click but if KJ6 One-Click is not working for him I do not know why you think the Froyo One-Click will.
lumin30 said:
We do have a Froyo One-Click but if KJ6 One-Click is not working for him I do not know why you think the Froyo One-Click will.
Click to expand...
Click to collapse
I figured if the phone was still running on the Stock Froyo when this happened, that it may work as opposed to forcing the phone to accept a new ROM while it's still clashing with itself.
It's worth a shot at this point.
Stuck on Froyo
LiangChi said:
I figured if the phone was still running on the Stock Froyo when this happened, that it may work as opposed to forcing the phone to accept a new ROM while it's still clashing with itself.
It's worth a shot at this point.
Click to expand...
Click to collapse
I hate to hijack this thread but it describes my current situation and symptoms perfectly and I never saw a conclusion / fix.....
I just got a used phone from ebay (verified SGH-T959V in battery compartment) and have run into the same exact problems described in the start of this posting. Phone was running Froyo and I attempted to upgrade to Gingerbread with Heimdall One-Clicks. I was actually successful at one point but then it crashed when I tried to install boot loaders to get rid of rainbow screen at startup.
Now all I ever get is a splash screen bootloop whenever I try any of the Heimdall One-Click gingerbread variants. I have also tried Odin and the Gremlin remover with same results of splash screen bootloop (Linda always completes). I was however able to access the new kernel CWM recovery and try to flash other gingerbread ROMs - splash screen bootloops on all attempts.
So I gave up on Gingerbread and tried using CWM recovery from gingerbread ROMS to install CM9 / CM10 / Slim Bean. I was able to upgrade almost perfectly but had same problem for each one of these. Not the bootloop thankfully but instead the headphone speaker (if that is the right description) doesn't work. No sound for phone touchpad, screen selections, and when receiving a phone call (have to switch to speaker phone as back/big speaker works or plugin headset to hear whoever was calling).
All of the other features were great but I really needed to be able to use my phone as a phone! The Heimdall One-Click worked to return me to Gingerbread with same problem of splash screen bootloop (gets to pink welcome letters every once in a while). Then I used the Heimdall One-Click for Froyo (as suggested by LiangChi) and got a perfectly working version of Froyo.
Used Froyo CWM recovery to switch to ICBINB ROM which works fairly decently.... Am I doomed to stay at Froyo though? I tried to follow all of the guides to a T but not sure what I might be doing wrong or if I might have purchased a damaged phone - can't recall ever testing camera and it still doesn't work on current stable Froyo. At various points I tried different cables, SD cards, USB ports, removing/reinstalling drivers, etc... Even tried Kies when I got back to stock Froyo to upgrade - went to Splash Screen Bootloop!
You have so much info here... let's see what we can figure out.
grovernyc said:
I hate to hijack this thread but it describes my current situation and symptoms perfectly and I never saw a conclusion / fix.....
I just got a used phone from ebay (verified SGH-T959V in battery compartment) and have run into the same exact problems described in the start of this posting. Phone was running Froyo and I attempted to upgrade to Gingerbread with Heimdall One-Clicks. I was actually successful at one point but then it crashed when I tried to install boot loaders to get rid of rainbow screen at startup.
Now all I ever get is a splash screen bootloop whenever I try any of the Heimdall One-Click gingerbread variants. I have also tried Odin and the Gremlin remover with same results of splash screen bootloop (Linda always completes). I was however able to access the new kernel CWM recovery and try to flash other gingerbread ROMs - splash screen bootloops on all attempts.
Ok... when you flash the "stock" rom... have you tried to wipe cache, data etc???
Are you letting it boot up before appling any of the kernels??
So I gave up on Gingerbread and tried using CWM recovery from gingerbread ROMS to install CM9 / CM10 / Slim Bean. I was able to upgrade almost perfectly but had same problem for each one of these. Not the bootloop thankfully but instead the headphone speaker (if that is the right description) doesn't work. No sound for phone touchpad, screen selections, and when receiving a phone call (have to switch to speaker phone as back/big speaker works or plugin headset to hear whoever was calling).
All of the other features were great but I really needed to be able to use my phone as a phone! The Heimdall One-Click worked to return me to Gingerbread with same problem of splash screen bootloop (gets to pink welcome letters every once in a while). Then I used the Heimdall One-Click for Froyo (as suggested by LiangChi) and got a perfectly working version of Froyo.
Try wiping data and such, still bootlooping??
Used Froyo CWM recovery to switch to ICBINB ROM which works fairly decently.... Am I doomed to stay at Froyo though? I tried to follow all of the guides to a T but not sure what I might be doing wrong or if I might have purchased a damaged phone - can't recall ever testing camera and it still doesn't work on current stable Froyo. At various points I tried different cables, SD cards, USB ports, removing/reinstalling drivers, etc... Even tried Kies when I got back to stock Froyo to upgrade - went to Splash Screen Bootloop!
Click to expand...
Click to collapse
nope, it sounds like dirty flashes to me...
I would start with entering cwm and disabling lagfix & wiping data & caches.... linda needs to do her thing after the first boot up...
Then, I would reflash the germlin remover, If I remember correctly, you will have to do this twice (second time will allow you to check the add bootloaders)...
After the phone hits the think-pink, then you can battery dump, reenter download and flash the kernel.
Dirty Flashing
Champ - I think you might be on to something...haven't read about dirty flashing but it sounds right. I have been wiping data and caches (even tired reformatting system with a few roms). I do remember running into problems trying to following a few instructions sets that asked to disable the voodoo lagfix - hit option it just doesn't disable. After hitting disable see below Voodoo lagfix is actually: enabled next boot: disabled but even if I reboot back to CWM it is still enabled.
I might try the Odin Gremlin remover again. I was just getting frustrated after several days of failed upgrades. Second opinion on if it might be hardware/memory vs user error. I really didn't understand why even Kies (which everyone disparages) upgrade from stock Froyo also caused same loop.
champ1919 said:
You have so much info here... let's see what we can figure out.
nope, it sounds like dirty flashes to me...
I would start with entering cwm and disabling lagfix & wiping data & caches.... linda needs to do her thing after the first boot up...
Then, I would reflash the germlin remover, If I remember correctly, you will have to do this twice (second time will allow you to check the add bootloaders)...
After the phone hits the think-pink, then you can battery dump, reenter download and flash the kernel.
Click to expand...
Click to collapse
Retry the gremlim remover. Redownload it incase of a bad download.
Lumin30 has a good guide in his signature for the heimdall one clicks.
I use Odin, I have used his one clicks without problems though.
http://forum.xda-developers.com/showthread.php?t=1470716
Sent from my SGH-T959V using xda app-developers app
Hello all,
Okay, I admit that I am gonna get a lot of "use the search tool first" replies, but please hear me out. I have done my fair share of searching. Its not that I haven't found anything, its just the things I found are useless for this SGS 4G. I really wanted to install Cyanogen Mo on the SGS (its not actually mine, a friend asked me to do it since he saw my old SGS GT-I9000 running CM).
I am gonna try and give a detailed report . The phone was originally from T-Mobile and now unlocked permanently. Its running firmware version 2.3.3 that I installed just recently. I found out that I can't install CWM on the stock kernel or bootloader or whatever and I needed a new of the thing. So I went on searching and searching....found a handful of help but none work. Every method breaks at some point and I go to the "firmware update failed" thing on the phone, which I then install 2.3.3 again using ODIN and try another method. I have tried a lot of things. Hemidall, ODIN, SuperOneClick, and a lot of gibbrish-sounding methods. None work. I am now running 2.3.3. Here are some infos:
ABOUT PHONE:
Model Number: SGH-T959V
Firmware Version: 2.3.3
Baseband Version: T959VUVKF1
Kernel Version: 2.6.35.7-T959VUVKF1-CL270364
Build Number: GINGERBREAD.VUVKF1
The files I used to flash to 2.3.3 using ODIN v1.85:
PIT: Hawk_Sidekick_VibrantPlus_831.pit
PDA: CODE_T959VUVKF1_CL270364_REV00_user_low_noship.tar.md5
PHONE: T959VUVKF1-Phone-CL1020302.tar.md5
CSC: SGH-T959V-CSC-TMB-VIBRANTP.tar.md5
I hope the above infos are enough. So, can anyone help me and point me to the right direction on how to install CWM and then install CM10 or 9 on my friends SGS 4G?
Thanks,
Tamrat
Hmmm, an interesting set of binaries, ones that don't ring a bell with me. I'm used to seeing T959VUVKJ6.
Where did you find those? Half curiosity, half trying to understand the problem, half since much of the "old" images for the phones got lost when Multiupload and what have you were shut down.
For the SGS4G, the kernel, root file system, and recovery file system are all in "boot.img" -- flash one, you flash them all. They can be flashed through Odin (assuming you really like Windows), heimdall (multi-platform), through recovery, or from a root command line (for the adventurous only).
I would say the most robust way to get where you need to be would be to use Lumin's guide to make sure you've got a viable Gingerbread set-up going, then flash something reliable to get you to MTD, like TeamAcid's CM9.
From there, you should know that some of the KK ROMs use slightly different MTD partitioning and aren't a "just flash this ROM and keep your data" kind of thing.
jeffsf said:
Hmmm, an interesting set of binaries, ones that don't ring a bell with me. I'm used to seeing T959VUVKJ6.
Where did you find those? Half curiosity, half trying to understand the problem, half since much of the "old" images for the phones got lost when Multiupload and what have you were shut down.
Click to expand...
Click to collapse
A long day Googling... and then a site turned up. One thing I forgot to mention was, before I installed this firmware, I had to use the "remove battery->plug usb->press the button combos->insert the battery" to enter download mode, but now I juts have to press vol down and power button.
Thanks for the reply,
Failure again
UPDATE:::
I tried to update to 2.3.6 as the guide suggests and I also wanted a clean stock OS in case the old one was not. But once again updating to 2.3.6 has been a pain. Kies Mini recognizes the phone but it doesn't recognize the firmware running on the phone. And also, firmware update is impossible since the button is greyed out.
I googled again and found the official 2.3.6 firmware for the phone (file name: T959VUVKJ6-REV00-home-low-CL694130.tar.md5) and tried flashing it using ODIN; absolutely no luck. It fails at the stage which says Slb.bin. Restarting the phone after that gives a "firmware upgrade failure" display. Only way to wake up the phone is to flash the previous OS back.
I am really confused here.
*********************EDIT***************
Some how, after like 10 retires and fiddling with ODIN, it finally flashed 2.3.6 to the SGS 4G. Still, fingers crossed.
*********************EDIT 2***************
Finally, its all working fine now. Thank you @jeffsf, thank you very much.
F*****************K
forgot an important step and now my IEMI number is gone........
do i throw the phone now, or is there any other way???
Don't throw your phone away! How do you know that you have "no IMEI" on your phone? We'll go from there.
Hopefully, you've backed up your data before starting to play around with ROMS. If so just load your backed up efs folder onto your storage & use Root Explorer to drop it over your existing one , it will overwrite your imei file & you will be good as new.
========================================================================================
I'm also in need of help, I have been running SlimSaber since last weekend, was wanting to try out Beanstalk. First full wipe, install & reboot wipe again, reinstall etc as per Dao's OP, but after the first install, it won't boot past the kernel splash. Tried again with same result. Decided to click it back to stock & start over, using Gremlin Remover (odin). Then saw that others were having similar issue so I tried to load in build from April1st.
But now it only boots back into recovery, won't boot to the OS ( everything indicated install was complete & no errors.)
1 clicked back again & just tried to put SlimSaber back on again, but have the same problem, will only boot into recovery.
I had to first load CM9 to get CWM 6.xx so I could install kk using TWRP
What am I not doing correctly? Thanks for any suggestions.
Flash kernel
Reboot recovery
Wipe all partitions
(Reboot recovery for good measure and wipe again if paranoid)
Install
Boot
If that doesn't do it, it is likely ROM or hardware.
---
Posted from whatever phone booted today
Since this is running GB VUVKG4, could you recommend a kernel that would work & get me to TWRP (or CWM 5.xx+)?
Either the Team Acid CM9 or Hefe Kernel should work.
---
Posted from whatever phone booted today