Phone: SCH-I500vzw
I've been trying to install MIUIwiz 1.1.1 to no avail. I start with a freshly Odined ED05 (performing a full boot). I then flash the DC09 modem and CWM flash the patch to ED01 with a full reboot. I then flash to JT's TW 415 voodoo kernel and allow it to convert to ext4. I then wipe data, cache, and dalvik, before finally flashing tsm_miuiwiz_1.1.1.zip.
The phone makes it through the Samsung boot without error, but the MIUI loading boot/loading screen is an endless loop of what seems to be something crashing (one vibrate, a pause, and then two vibrates and the screen refreshing). I've tried every 'fix' I could find (that's where the ED01 modem bit came up), but I can't get the rom to boot. Any advice would be greatly appreciated. I was previously on MIUI mtd 1.8.5, but experienced com crashes fairly often and some sort of phantom crash (one vibrate, followed by three) on a very regular basis. It appears my phone just hates MIUI. I suppose I'll try another rom for now.
try the steps in this guide. Just replace vgb with miui
http://forum.xda-developers.com/showthread.php?t=1212239
Related
I know how to flash roms. Been doing it for the past few months. Now when I restore to stock and isntall latest 2.5.1.x clcowkork along with superclean 2.9.2 it vibrates a crap ton and refuses to boot. It probably a FC boot or something idk, I wiped data and dalvik and all that jazz. Was coming from d101. Any help?
Edit: was not rooted before flashing if that makes a difference.
Have you tried using Odin to install the one in all froyo package?
Was about to try that.
I have been searching for a while, but does anyone have issues installing Miui 1.7.8? I can get to CM7 and install GAPPS for it no problem. On CWM 4.0 I have been trying to install Miui from SD card after wiping data and both caches. When it tries to load Miui I get a boot loop with the exclamation mark and quickly written words that I can't decipher quickly. I read earlier about pulling battery in this instance, but that didn't help. I want to test out the phone.apk, but I'm having some issues.
fsuagentsmith said:
I have been searching for a while, but does anyone have issues installing Miui 1.7.8? I can get to CM7 and install GAPPS for it no problem. On CWM 4.0 I have been trying to install Miui from SD card after wiping data and both caches. When it tries to load Miui I get a boot loop with the exclamation mark and quickly written words that I can't decipher quickly. I read earlier about pulling battery in this instance, but that didn't help. I want to test out the phone.apk, but I'm having some issues.
Click to expand...
Click to collapse
For future use, if anyone is having issues like this...
1. Booted using volume controls to recovery 3.0 posted by JT in CM7.
2. Used the ext4 formatter_all from navenrob
3. Used the CM7 install from JT
4. Booted CM7
5. ReBooted recovery from CM7
6. Wiped Cache from CWM 4.0
7. Installed current verison of Miui from CWM 4.0
Thought I would post how I figured it out.
fsuagentsmith said:
I have been searching for a while, but does anyone have issues installing Miui 1.7.8? I can get to CM7 and install GAPPS for it no problem. On CWM 4.0 I have been trying to install Miui from SD card after wiping data and both caches. When it tries to load Miui I get a boot loop with the exclamation mark and quickly written words that I can't decipher quickly. I read earlier about pulling battery in this instance, but that didn't help. I want to test out the phone.apk, but I'm having some issues.
Click to expand...
Click to collapse
I was having problems flashing 1.7.8 too. I downloaded 1.7.1.3 from goo inside me. The site where you download the rom. I flashed that with no issues on red CWM. Then i booted and went to orange recovery from the power menu. Flashed 1.7.8 perfectly. Don't really know if this would solve the problem but its worth a shot.
I had to odin eb01 with atlas 2.2, odin cm recovery fix for cm7, flash cm7signed in red recovery, rebooted into orange recovery, reflash cm7signed, reboot into rom, reboot recovery, wipe, flash cm7 0704, reboot, wipe, flash miui. finally worked after much trial and error
Hello all,
I need some advice. I originally followed this page http://wiki.cyanogenmod.com/wiki/Sam...l_Update_Guide to flash and everything was fine for 3 or 4 days and then the fc's came. So i odin'd to stock and when getting ready to reflash i see that you need to be on 2.2 to use his guide. So another member kwkslvr (who has been very helpful and patient btw) told me his method for flashing CM7 so i attempted to straight from 2.1 with no root to the following...
(kwkslvr's method) You definitely don't need to be on Froyo. You don't need root either. What has worked best for me is to Odin to 2.1, reboot into stock recovery and flash update.zip. Since you've flashed before, update.zip will probably already be in your internal sdcard unless you removed it. You'll have to flash it twice in a row without rebooting and that will load ClockworkMod Recovery.
Once you're in CMW Recovery (probably green recovery), wipe data/factory reset then format/system. These two steps are CRUCIAL! Flash your CM7 Nightly twice. The first time you flash it, it installs blue recovery. The second time it installs CM7. After that, again without rebooting, install gapps.
From that point, wipe data/factory reset again and reboot into the OS.
So i tried that and got to where the phone restarts after the flash and it has galaxy and cyanogen below it for a few seconds and then immediately script with font like from recovery mode races down the screen for a few seconds, then back to galaxy/cyanogen in a loop. So i odin'd again and as of now am stock 2.1 with the options of kies n it to 2.2 and then follow cyan page again or trying kwkslvr's method again. I did notice he mentioned nightlies but i am attempting to flash the stable on page 1 of this thread but don't think that would make much difference. I love the way this ROM looks and performed before it went off the tracks. Any suggestions are welcomed. Thanks alot
EDIT: At the boot loop sequence i 3 buttoned to recovery and reflashed and it seems to have worked. I notice the battery gauge no longer has the # %. And the horizontal line next to it is gone too. On my market page under "not installed" i have adobe flash showcase (Reads this item is not available at top), google search which just has a open tab (Already is installed), magic 8 ball by dennis bond (Reads this not available in your country?? it was the first time i installed it) Any ideas on how to get these 3 items off the not installed section. It's mainly a minor annoyance. I have cleared cache in market with no luck. Thanks.
I just flashed the new CM7 ROM onto my Atrix. I was running the Dark Side ROM before the flash. I tried booting my phone up, it goes to the boot animation which runs for about 5 seconds, then reboots. Its cycled for 10 minutes. I pulled battery, reflashed, but the problem seems pretty persistent. Any Ideas?
it may be obvious but did you do the "3 wipes" before flashing CM7? also try "fastboot -w" if you've done wipes in recovery already before flashing
i am having a similar issue with the MOD 2 version of this rom, i was using my atrix with the hdmimirror.zip that i installed other than that the phone was just stock rooted, with an unlocked bootloader. now that i have flashed this rom ( doing all the necessary wipes and etc.) when i try to reboot i am stuck at the dual core screen. any thoughts?
Format the system partition, factory wipe/reset, wipe dalvik cache. Reboot into CWM and then go ahead and flash the ROM. That should hopefully make sure it's all clean before the install.
I was having trouble with my CM9 [THS] rom, I was on build 13 so I thought I'd update to build 15. So every app was crashing and what-not, so I reboot it and put it in my pocket. 30 minutes later I take it out and it's warm, it was on the boot screen the whole time.
So I remember I can't use 3-finger recovery for ICS.. but at this point I didn't know what else to do [I was trying to get it done in a hurry]. So I did 3 finger recovery.
Then as I expected, it would not boot normally, it kept booting into recovery.
So I tried to flash CM9 build 15, but at "checking state of bml/mtd" it immediately rebooted and was in what seemed a bootloop.
So I heimdall a old recovery.bin, back from a Gingerbread ROM, hoping it would fix it like it did last time I had the bootloop.
It did, and it tried to boot up the CM9 now. I let it alone for a few minutes and realized it wasn't gonna finish booting, so I booted into windows [primary OS is Ubuntu] and did a complete ODIN, back to verizon Gingerbread firmware. I used atlas2.2.pit or something.
So I left it and came back and it said "PASS!" and it was now stock Gingerbread ROM.
So I heimdall'ed recovery.bin as stated on this page: http://wiki.cyanogenmod.com/wiki/Samsung_Fascinate:_Full_Update_Guide
And I did 3-finger recovery [because it says to if you are on stock GB], and so I did a full Wipe, and then I installed from .zip, and chose CM9 THS build 15 [ http://rootzwiki.com/topic/16630-romicsimm76d-teamhacksungs-ics-port-for-fascinate-build-15-071012/ ]....and it started to install but when it came to "Checking state of BML/MTD" it immediately rebooted, and looks like it's bootlooping now.
What's wrong? How do I get CM9 installed again?
I'm going to the dentist and I hope when I get back someone has posted the solution..
Thanks!
1) odin to stock and let boot then odin cwm fixed for cm7
2) 3 finger to recovery
3) wipe data, cache, and dalvik
4) install THS build 2 and let it fully boot
5) reboot recovery using power menu
6) wipe data, cache, and dalvik
7) flash build 15 + gapps
8) enjoy
Thanks.. That worked.
I had forgotten that you have to flash specific roms in order to bridge the gap from GB to ICS.
I'm not entirely sure why THS build 2 is so magical.. but whatever.
The thread on rootzwiki did not have build 2 linked, so I found it on another forum.
I am going to upload it to mediafire so if anyone wants THS build 2 mirror, they won't have to hunt!
Here is a dropbox mirror: teamhacksung-ota-eng.BUILD2.zip
I am trying to mirror it on mediafire but it quits uploading after the first MB.. :S