[ROM] Official MIUI ICS

[alaindesjardins]

Just can't get the driver installed. Maybe it's because I have Windows 7...

Edit: Got it working... although it shows as

C:\adb>adb devices
List of devices attached
3733B36C9F5200EC device

I can get a logcat, following instructions from https://sites.google.com/site/androi...to-a-text-file

I had to go in device manager and install manually the driver and force it in for it to work. Any special command I can do to make sure it's working properly?

[aashmir]

That's odd this didn't work for you. Did you make sure you flashed the modem in the "Phone" tab in Odin, and not "PDA". And which radio did you flash? I used the EH09 radio. Btw, where do you live? It should work just fine as long as you're in good coverage.

I would get back to the latest version of MIUI, set everything up, flash the EH09 radio via Odin (PHONE tab) while clearing EFS, then call *228. Make sure its during the day and not in the middle of the night (will not program lol). This is the exact method I used, and was able to pick 3G up.

Here is a link to the EH09 radio.

http://www.mediafire.com/?yb0ljndtokbjgia

Let me know if the link doesn't work

Hope this helps you aashmir! Let me know

I put the phone back to MIUI 2.6.1 to gain root access since that was the newest version I had on my SD Card. This rom uses the EH09 radio. I downloaded just the EH09 radio from your link and used Odin to push it to the phone with the Phone EFS Clear check box checked. I made sure to use the "Phone" section. I am using Odin 1.83 if that makes a difference and did not have re-partition checked, if that matters.

Also, I noticed some other things that might be related to this issue. When I was on 2.3.4 stock rom, there was a file on the root called recovery.rc. It contain a bunch of 'mkdir' commands but the row for 'mkdir efs' was commented out like this '#mkdir efs', then below that there were 4 linese or so that ran commands to the efs folder. I didn't think much of it at the time because I figured the file would be on the phone when I got to MIUI. It wasn't. I guess it uses some other *.rc files now. My phone still doesn't have a folder called 'efs' on the root directory or anywhere else.

I live in Cedar Rapids, so I went to USCC service desk in Cedar Rapids to have them see if they could fix it, but they wouldn't help me and said I'd have to send it to Samsung. I even played stupid like, "My phone won't connect back to the network ever since I decided to reset it back to stock using the built in process under the settings menu. Can you help me fix it?"

Ever since then, the recording I get when dialing *228 isn't the normal, "This will take up to 90 seconds", it says they cannot program my phone at this time and to call an 800 phone number for assistance.

Well, in the mean time I got rid of the old crap slider phone I was using and found an LG Genesis on Craigslist for 75 bucks! Still have the plastic on the screens and all! The girl that sold it to me was 17 and about 8 months pregnant. Poor girl.

[rzdw92]

On the topic of battery and MIUI, has anyone ever run into the following: I power off the phone at night with 50% battery and when I power it back on in the morning it has less than 10%. It's bizarre and it's only happened when I'm using the MIUI ROM.

I've already tried the battery reset functions in the MIUI Tool and CWM recovery. Didn't fix the issue.

Thanks for any feedback.

Sent from my SCH-I500 using Tapatalk

[sageDieu]

On the topic of battery and MIUI, has anyone ever run into the following: I power off the phone at night with 50% battery and when I power it back on in the morning it has less than 10%. It's bizarre and it's only happened when I'm using the MIUI ROM.

I've already tried the battery reset functions in the MIUI Tool and CWM recovery. Didn't fix the issue.

Thanks for any feedback.

Sent from my SCH-I500 using Tapatalk

Did you power the phone off with Wifi enabled? I've heard of a strange bug that when you turn the phone off with Wifi enabled (or reboot it) it will have an extreme drop in battery. To fix it just turn off Wifi and reboot and it should have the correct readings.

[netman74501]

DI14 Flashes successfully, but everytime I do EH09 right at the end it fails. It looks like it does everything right, and although it fails, I can boot into EH09 without a problem. I've attached a screenshot... I think it's a false failure but maybe you can spot something I can't.

I am sorry I never responded. I got busy and forgot about this thread. (Shame on me!!)

I've never had any problems with ODIN failing unless I unplug the phone accidentally. Did you let DI14 fully boot? I didn't suggest rfsformatter because it doesn't always work for me. I am glad you adventually got your phone and your wife's phone working though.

I made the mistake of clearing EFS once also and, like you, was teriffied because afterwards I read that it could break the phone permanently. It won't brick it but, *all* settings are wiped and reset to their factory defaults, (at least that's what the manual says). I had to flash between DI14 and EH09 several times, (like 7 - 10 if not more) and had given up and was actually on the phone with US Cellular when my radio finally started working again after a reboot (it had a symbol indicating there was no network in both versions before that last reboot). I've never touched that setting since and I won't ever again. **Not for any reason.**

Going all the way back to DI14 and then EH09 is the only thing I have found to be rock solid when wanting to restore my phone to a usable state.

Here's a modified flashable: http://goo.im/devs/weblexa/Tools/cm9-recovery.zip. I wasn't able to test it because I don't own a Mesmerize, but it should work.

I have not gotten to test this yet but, do you have any idea why it wouldn't work? Could you try to make another if it doesn't?

[alaindesjardins]

I pre-ordered a Samsung Galaxy S3 yesterday and will be switching to that once they ship it. I'm a little excited (ok, maybe a lot...) since I haven't had a new phone for almost 2 years now. The only thing I really loved about MIUI is the themes and since v4 it hasn't really been working that great. Also didn't really care for Touchwiz and MIUI gave me an alternative, so it was enticing to me at the beginning. I'll be passing my phone down to my daughter so she can upgrade her slow LG Apex.

I'm hoping there will be more interest with the Samsung Galaxy S3 since it seems like it will be a popular phone. Also hope there will not be much difference (from S3 to S3) to make it easy for porting ROMs.

[McSpazzatron]

The ROM is great, but has anyone experienced a barrage of Force Closes after a while? It seems to only be happening with MIUI after a day or so of use. Everything starts FC'ing, I try to reboot then I get stuck in a bootloop and end up flashing back to stock to start over. I always follow proper procedures when flashing but this keeps happening

[alaindesjardins]

The only time I had issues with force close is because i had too many apps installed and the internal memory was full. I did not get a warning but everything became unresponsive. I didn't have the bootloop issue, but once I moved apps to SD I was able to free up some space and everything worked fine after that.

I know it's probably not the same type of issue you're having but I thought I would throw it out there just in case. I did have issues with 2.6.15 where I would get stuck in recovery and had to flash my phone back to stock in order to get things to work. But I wasn't able to provide a logcat so I don't know how weblexa is going to fix it if I was the only one having that problem.

[alaindesjardins]

Well as of today, my phone quit working again. I'm using 2.6.8 and all my apps started to force close. Didn't even install anything different, except maybe a new theme. I installed Dark Knight theme for MIUI v4... nothing else was done other than that. I rebooted my phone and got stuck at the MIUI loading screen. So i rebooted again, wiped cache and dalvik and now when I try to boot, It goes straight to recovery every time.

I flashed 2.6.8 again, and it won't go past recovery every time I try to boot.

I'm going to try and figure out if I can do a logcat thing and hopefully you can nip this in the bud. I can't use my phone the way it is right now so I am going to have to do something tonight but alteast I'll try to get some information to fix this.

Edit: Well I can't get out of recovery so I can't get a logcat. I tried formatting system and then reflashing 2.6.8 but it still won't work. I'm going to try and flash the 2.6.15 to see If I can get in MIUI.

Edit: Was able to get some logcats. I'm not sure which is which, but there are three of them and the last one logcat3.txt is probably the most accurate. I put the others there too in case the third one doesn't provide enough information... the others might. What I did was flash to stock EH09, flash CWM recovery, flash thsBUILD2, then MIUI 2.6.8. Once it was booted in MIUI, I did a nandroid recovery and it wouldn't go but atleast it tried to boot so I was able to do a logcat. I noticed that if doing a battery pull it would try to load MIUI, but as soon as I did a three button to recovery it got stuck there and wouldn't try to boot.

Links for logcats:
http://www.mainepcsales.com/storage/...ck/logcat1.txt
http://www.mainepcsales.com/storage/...ck/logcat2.txt
http://www.mainepcsales.com/storage/...ck/logcat3.txt

I don't know much about logcats but I see a lot of "Out of memory" messages, that can't be good right?

Edit: Is this relevant to the bootloop to recovery? I don't understand it... http://forum.xda-developers.com/show....php?t=1694984

I'm using THS Build 12 right now so I can make use of my phone since I need it for work. Really don't feel like setting up MIUI again and have it crap out on me in a time of need. Only two more weeks I am told until the Samsung Galaxy S3 is out for USCC.

[zoodski]

I had that issue with my wifes mez once too. I ended up flashing a different cwm recovery and it hasn't done it since. Do you know which version you are using? Also I read somewhere not to go into recovery using the 3 button method. I downloaded rom manager on hers and use it just to be able to reboot into recovery.

Here's a link for the cwm I used from my dropbox
https://dl.dropbox.com/u/30169771/cwm4-bml-i500.tar

[alaindesjardins]

Well the problem at first was not that I was stuck in recovery... it was that I couldnt' boot MIUI after a barrage of force closes on everything that could run. Before I rebooted I tried to run Titanium Backup to backup my apps but even that was failing. I thought maybe it had to do with not enough space on the internal memory so I removed a few apps and moved some to SD but it was still force closing everything. I rebooted my phone thinking it would make a difference and got stuck at the loading screen for MIUI.

After failing at getting in MIUI, thats when I did the three button recovery to try and fix things but I couldn't get out of it. Since I need my phone for work I installed THS Build 12 last night and I am using that for now. I'm going to stick to that until I get the S3 I preordered. I know it's a long while until then (someone mentioned that it was supposed to ship mid July) but I can't stand having to redo everything when MIUI crashes. I know I have a nandroid backup that could bring it all back to what it was, but everytime I do a nandroid restore I get stuck at the loading screen for MIUI.

I thought about it for a while, and considered flashing MIUI 1.12.9 and use that instead. I know I had a problem with 1.12.9 back then but it was because of the internal memory getting full. So if I keep an eye on internal memory, I'm pretty sure it will last me. And with that at least I could have fun with Themes again all that jazz.

[rzdw92]

On 2.6.8 and for a while now, my Mez has been randomly freezing and re-booting itself. It's not consistent, it doesn't seem to matter what apps are open.

Here's my latest logcat:
https://www.dropbox.com/s/alu1heriv6cq6p9/logcat.txt

Also, weblexa: will there be a Mez port of the more recent roms (e.g. 2.6.29)?

[alaindesjardins]

Web put the ports on hold until some of the problems can be fixed... both my mez and my wife's mez have been freaking out with force closes and such ever since 2.6.15 came out... we both reverted to 2.6.8 and my wifes phone has been good for two weeks now, but mine just crapped out a couple of days ago on 2.6.8 with the same issues I was experiencing on 2.6.15.

[zoodski]

My wifes mez has been on 2.6.15 for 3 weeks now with zero issues. 2.6.8 was the first time with miui and going from that to 2.6.15 I just wiped cache and dalvik.

[rzdw92]

So I've been on 2.6.8 since it was released, and at this point I have so many random reboots and app crashes that I decided to try a different ROM for a while (THS Build 14). I also pre-ordered a GSIII from uscc and I'm giving the mez to the wife. But MIUI is just too unstable on my phone for her to use like this. It's too bad because I love the look and feel of MIUI.

I'll test out the THS ROM, hope it will be stable, and maybe I'll eventually install the MIHome app to get the MIUI look and feel back.

[alaindesjardins]

So I've been on 2.6.8 since it was released, and at this point I have so many random reboots and app crashes that I decided to try a different ROM for a while (THS Build 14). I also pre-ordered a GSIII from uscc and I'm giving the mez to the wife. But MIUI is just too unstable on my phone for her to use like this. It's too bad because I love the look and feel of MIUI.

I'll test out the THS ROM, hope it will be stable, and maybe I'll eventually install the MIHome app to get the MIUI look and feel back.

I'm in the same boat a you. I think maybe if I didn't do the three button recovery I could have gotten back into MIUI but the last issues I saw I couldn't even get back into MIUI.

THS build 14 is looking really good for me so far. Seems to be a lot faster. But then again it took MIUI a long time before it acted up, so only time will tell.

I just really am not enjoying the way THS looks. And all the themes to me are pretty bland. Themes just look like someone played with the RBG slider in Photoshop.

[alaindesjardins]

Weblexa, my wife has been using 2.6.15 since it came out and has not had any crashes at all. I believe the stuck in recovery problem I was experiencing with my mesmerize was because I would use the three button recovery method and it is known to get you stuck in ICS.

Is it possible for you to continue porting the fascinate ROM so I can keep her phone updated? I hope everything I found when having my mesmerize with MIUI will help others in the future. There are known quirks that plague all ICS roms (atleast that I found) that when known will make life a lot easier.

Thanks!

[ChromWolf]

I'd love to see additional ports of the Fascinate MIUI, but when I try Mesmerize MIUI 2.8.10, it won't boot; won't even show kernel animation. I think I was even able to try Fascinate 2.8.10 (though of course, anything that happens when running an unported Fascinate ROM on a Mesmerize was the case).

Has anyone else gotten 2.8.10 to boot? Is there anything I can do the help with testing or troubleshooting, weblexa?

[alaindesjardins]

Looks like 2.8.10 was posted. It's up for download so i'll give it a shot. I'll let you know how it works.

I was telling my wife that I'd redo her phone with THS ICS cause I have it on my old mesmerize and it's been working great. So I'll give this a shot first and see how it goes.

[weblexa]

A couple people have said the 2.8.10 Mesmerize port won't boot, some have said it does boot, so it may or may not boot for you. I haven't been able to figure out what the cause is. I'm currently working on 2.8.17. 2.8.17 is Jelly Bean, so it'll take some time to get it booted but hopefully it will fix the issue for everyone. I'll have it uploaded when I can.