[ROM] Official MIUI ICS

[netman74501]

I let the battery on my phone completely die this morning so I could test this. Here's what I found:

Plugging in the phone when the battery is completely drained and the phone doesn't appear to charge. I let the phone sit on the charger for roughly 10 minutes, then tried turning it on while plugged in. The phone wouldn't boot. I unplugged the phone, tried booting it up and it booted to a strange screen with red text (Can't remember what it said, but some sort of boot error.). I pulled the battery, put it back in, and press the power button. The phone booted normally.

After successfully booting, I let the phone fully die on its own again, plugged it in to charge. Let it sit on the charger for an hour. It wouldn't turn on while on the charger. I unplugged it and turned it on. Again, booted to the same screen as before. Pulled the battery, put it back in, and press the power button. It booted up like normal, and had a charge of 73%.

So, my conclusion is that even though the phone doesn't appear to be charging, it really is. Something with the ROM is preventing the phone from booting while plugged into the charger, but after it is unplugged, it will boot. Hope this is helpful.

Interesting... maybe I didn't wait long enough then cause I had tried letting it sit (2 - 3 minutes, wasn't long) just to see if I could get it charged enough to turn on without the charger. Next time I'll leave it on the charge for at least 10 minutes.

However, can you make us a flashable zip like the one in the thread I linked to? That would be great to have for any unforseen emergencies that force one to use 3 button recovery.

[alaindesjardins]

I have a 100% fully charged battery and I am stuck in recovery. This is plugged and unplugged. I don't know how I can get out of it. I tried every combination possible...

Also, I picked up a cable today and apparently it's not a transfer cable so I cant use Odin. Going to have to wait until tomorrow to get the right cable... again.

I am going to try and flash MIUI 1.9 and then teamhacksung build 2, this time I won't make the mistake of clearing data and cache before trying to boot teamhacksung build 2 because you can't get back into recovery if you get stuck in a boot loop with that. Atleast I couldn't.

I still don't know how I can get 3G to work in New York City, New York, when it works fine for me in Bangor, Maine.

[alaindesjardins]

Using the Teamhacksung Build 12 for mesmerize right now as it seems to work. When I flash any MIUI build, I get stuck in recovery. My phone is charging and after enabling data roaming, I can access 3G. My wife's phone uses MIUI and she has no problems getting stuck in recovery. I think I just need a data cable so I can redo my phone the method netman suggested. Something is getting stuck in there.

[alaindesjardins]

That is in line with the instructions I found here, you're just using MIUI instead:

http://rootzwiki.com/topic/24391-how...very-bootloop/

I've been trying all day to re-create the 'cwm4-repack.zip' I linked earlier to work with this recovery. I thought I could simply replace the 'recovery.bin' file inside the zip with the one from the MIUI zip but, that did not work. I then tried replacing 'flash_image' and 'bml_over_mtd' in addition to that but, that did not work either. I would like to have a way out without the use of a computer.

I also tried creating a ODIN compatible tar containing the 'recovery.bin' file from MIUI but, that didn't work either. While ODIN accepts the tar and flashes the 'recovery.bin' just fine, the phone endlessly bootloops at the Samsung logo so there must be more to it than just rewriting 'recovery.bin' to break the cycle (though, my inspection of the script in the cwm4 zip leads me to believe it does just that; simply rewrites the recovery). Having a flashable recovery tar would be a luxury for when I am around a computer though.

The reason why I am even bothering to post what I've tried here is because I am wondering if Weblexa would be kinda enough to make those two files since I obviously don't have enough knowledge to do it myself.

My phone is now charging by the way. Even after going back to stock yours is not?

EDIT:

Do you ODIN DI14 and then EH09 or do you simply start with EH09? If not, it might be worthwhile to try flashing DI14 first as it conains the partitioning information to restore the phone fully to stock. These are my steps when I mess something up:

1. ODIN DI14 with partitioning checked (Be sure to include the pit file!) and let it boot fully. (May not have signal and won't poweroff but, that's fine. Just pull the battery after it boots.)

2. ODIN EH09 and let it fully boot. Then poweroff. (Should have a signal this time and power off properly.)

3. ODIN whatever recovery you use. I use CWM4 fixed for CM7.

4. Boot to recovery and flash THS Build 2 and then MIUI after clearing cache and letting THS boot.

I've found that going completely back to stock in this way works the best.

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.



What I don't understand however is why the battery does not show charging anymore when the phone is off. Used to I would get a battery logo with a start like it was loading and then it would show me a green graphic with how much of the battery was charged. This does not work anymore even after flashing DI14, EH09, THS Build2, or MIUIv4.

Anyways, after redoing all that... I am still stuck in recovery.

[alaindesjardins]

Ok so, I used Odin to go back to EH09 after being stuck in recovery. After flashing EH09, I flashed the recovery, then flashed rfs_formatter.zip in hopes that it would clear things out. I tried to boot the phone but i just got stuck at the samsung which to my understanding means that everything was formatted and there is nothing to load. At that point I flashed THS Build 2, let it load, then flashed MIUI 2.6.15. I didn't clear data or cache and loaded MIUI. Got a bunch of force closes and messages saying that I needed to activate my phone. I immediately went to backups and reset and restored to factory. I don't think I can activate my phone since I am roaming. When it dials... I get a message saying Welcome to Verizon.

[weblexa]

Interesting... maybe I didn't wait long enough then cause I had tried letting it sit (2 - 3 minutes, wasn't long) just to see if I could get it charged enough to turn on without the charger. Next time I'll leave it on the charge for at least 10 minutes.

However, can you make us a flashable zip like the one in the thread I linked to? That would be great to have for any unforseen emergencies that force one to use 3 button recovery.

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.

[alaindesjardins]

My wife's phone is stuck in recovery now after today. It just shut down and rebooted itself when she was using it. I will try the recovery zip and see if it fixes anything and will update this post if it does.

Edit: Yeah the recovery zip didn't work. I tried clearing cache and dalvik, and fixed permissions in recovery but nothing is working. I am positive if i wipe data as well I will still be stuck in recovery. Don't know if I have the patience to redo her phone either... she didn't do a titanium backup since she doesn't use it.

No one else is having this problem? I don't know what information I can give that would help identify what the problem is. But if this happened on both my phone and hers, then I'm sure its not something I did since all she was doing was using the browser and it just rebooted on her. This problem only presented itself with 2.6.15.

Any help is appreciated!

[weblexa]

My wife's phone is stuck in recovery now after today. It just shut down and rebooted itself when she was using it. I will try the recovery zip and see if it fixes anything and will update this post if it does.

Edit: Yeah the recovery zip didn't work. I tried clearing cache and dalvik, and fixed permissions in recovery but nothing is working. I am positive if i wipe data as well I will still be stuck in recovery. Don't know if I have the patience to redo her phone either... she didn't do a titanium backup since she doesn't use it.

No one else is having this problem? I don't know what information I can give that would help identify what the problem is. But if this happened on both my phone and hers, then I'm sure its not something I did since all she was doing was using the browser and it just rebooted on her. This problem only presented itself with 2.6.15.

Any help is appreciated!

Darn, I was hoping that flashable would work.

I'm not quite sure why this is happening. I haven't heard any other complaints, but since its now happened on 2 devices, there obviously is an issue. Are you able to get a logcat from boot using adb? Maybe it will provide a hint as to what the problem is.

I just though of this: When I first starting to port MIUI v4, I came up with a method of recovering from a bootloop without using Odin. Not sure if this will work in this situation, but it might be worth trying (I'd recommend wiping data before trying this, but if you don't want to, you can try it without. I don't know whether or not it will work without a data wipe.). So here's what I did:

Download a GB MIUI ROM (I'd recommend my 2.1.6 port here: http://tinyw.in/uokK) and put on your SD Card
Boot into recovery using the 3-button combo
Wipe Cache and Dalvik
Flash 2.1.6 (At this point, a couple different things could happen: 1. The phone will bootloop. If it does, just do a battery pull and 3-button combo back into recovery. 2. A strange screen with an android character and some red or yellow text will appear. If this happens, just hold down vol up + vol down + Power button until the phone reboots. It should boot back into recovery.)
Flash 2.1.6 again
Boot up your phone

If everything went as planned, the phone should boot into GB MIUI 2.1.6. I'm going to pull 2.6.15 and stop porting the Mesmerize for a week or two so I can look into this issue. If you're able to get me a logcat, it would be very helpful.

[weblexa]

My wife's phone is stuck in recovery now after today. It just shut down and rebooted itself when she was using it. I will try the recovery zip and see if it fixes anything and will update this post if it does.

Edit: Yeah the recovery zip didn't work. I tried clearing cache and dalvik, and fixed permissions in recovery but nothing is working. I am positive if i wipe data as well I will still be stuck in recovery. Don't know if I have the patience to redo her phone either... she didn't do a titanium backup since she doesn't use it.

No one else is having this problem? I don't know what information I can give that would help identify what the problem is. But if this happened on both my phone and hers, then I'm sure its not something I did since all she was doing was using the browser and it just rebooted on her. This problem only presented itself with 2.6.15.

Any help is appreciated!

Darn, I was hoping that flashable would work.

I'm not quite sure why this is happening. I haven't heard any other complaints, but since its now happened on 2 devices, there obviously is an issue. Are you able to get a logcat from boot using adb? Maybe it will provide a hint as to what the problem is.


TRY THIS FIRST: In recovery, unmount and remount /system. Try booting the device. If that doesn't work, Wipe /system and reflash MIUI (I'd recommend flashing 2.6.8 here). I've been told that doing either of these won't erase user data. If neither of these work, try the below:

I just though of this: When I first starting to port MIUI v4, I came up with a method of recovering from a bootloop without using Odin. Not sure if this will work in this situation, but it might be worth trying (I'd recommend wiping data before trying this, but if you don't want to, you can try it without. I don't know whether or not it will work without a data wipe.). So here's what I did:

Download a GB MIUI ROM (I'd recommend my 2.1.6 port here: http://tinyw.in/uokK) and put on your SD Card
Boot into recovery using the 3-button combo
Wipe Cache and Dalvik
Flash 2.1.6 (At this point, a couple different things could happen: 1. The phone will bootloop. If it does, just do a battery pull and 3-button combo back into recovery. 2. A strange screen with an android character and some red or yellow text will appear. If this happens, just hold down vol up + vol down + Power button until the phone reboots. It should boot back into recovery.)
Flash 2.1.6 again
Boot up your phone

If everything went as planned, the phone should boot into GB MIUI 2.1.6. I'm going to pull 2.6.15 and stop porting the Mesmerize for a week or two so I can look into this issue. If you're able to get me a logcat, it would be very helpful.

[alaindesjardins]

I'm not sure which driver i need for ADB. I downloaded a few drivers online from Samsung's website for both the Fascinate, Galaxy S Nexus, and the ones designed for the Mesmerize. Neither work to get me recognized in ADB so I never was able to get ADB to work on my PC. I did follow a guide online that had me download a folder to setup ADB in a few steps and adb does come up but when i do adb devices it doesn't show and right now my driver in device manager is showing as not installed. Can I get a logcat at any time? After formatting system and reflashing? Because i'm going to try your suggestion right now.

[alaindesjardins]

I still got stuck in recovery with 2.1.6 but I flashed 2.6.8 and it is now booting into MIUI. I cleared EFS on my phone and guess thats why it has to be reprogrammed. I shouldn't have done that... but I figured it couldn't be bad. Atleast my wife's phone is working now, and when I get in range of USCC towers back in Maine today, I will do *228 and let my phone reprogram and update. If all else fails, I will flash back to stock and go to USCC tomorrow and let them fix my phone.

[weblexa]

I still got stuck in recovery with 2.1.6 but I flashed 2.6.8 and it is now booting into MIUI. I cleared EFS on my phone and guess thats why it has to be reprogrammed. I shouldn't have done that... but I figured it couldn't be bad. Atleast my wife's phone is working now, and when I get in range of USCC towers back in Maine today, I will do *228 and let my phone reprogram and update. If all else fails, I will flash back to stock and go to USCC tomorrow and let them fix my phone.

Well, glad to hear you got your wife's phone working. For adb to work, you'll need the Nexus S drivers installed. I'll get you a link to the drivers I use when I get home tonight, that way you'll have them in case you need them in the future.

[aashmir]

I cleared EFS on my phone and guess thats why it has to be reprogrammed. I shouldn't have done that...

So I was using one of the latest MIUI for Mesmerize (2.5.?) for the last month and couldn't get the 3G to work, so I found on a forum somewhere a very recent post that someone got it to work by using Odin to flash/re-flash the modem to the phone with the "Phone EFS Clear" checkbox checked. I thought great, I can finally get this fixed. Bad Idea! Now, after I did that, I have lost the ability to make phone calls. A recording picks up and asks if I would like to place a collect call, use s credit card to purchase a prepaid card number, etc. There is no data at all over cell towers. Dialing *228 or *22899 says it updates successfully on the recording, but it doesn't make any change to getting stuff to work. I tried doing all of the step by step procedures to put down 2.1, 2.2.1, 2.3.4, 4.0.4 and none of the will fix the cleared EFS data. The phone status shows the following.

Phone number = my phone number
MIN = 0000000788
PRL version = 15114
MEID = Dec:Same number that is under the battery(not corrupted)
Network = U.S. Cellular
Service state = In service
Roaming = Not roaming
Mobile network state = Connecting

I currently have the phone on Stock USCC 2.3.4 (non-rooted) but can try anything you all suggest to get this thing working.

I also took it to the USCC store's service department and they said they couldn't fix it and that it would have to be sent in to Samsung. I am hoping this is not my option.

All help is appreciated!!

[aashmir]

Flash a radio modem via odin and check the 'clear the EFS' box(I believe that's what it is, not near my computer) then start the phone up and call *228. Should get your data speeds up to 3g par. This worked for me when I was just getting 2g speeds. I forget which radio I used, let me know if you want a link, I could get you one when I'm home.

This is the post I had seen that caused my phone to not work anymore. Weird thing is he lives an hour away from me! In the mean time, I had to revert to a 4 year old slider phone! OMG, lame ha ha!

[alaindesjardins]

So I was using one of the latest MIUI for Mesmerize (2.5.?) for the last month and couldn't get the 3G to work, so I found on a forum somewhere a very recent post that someone got it to work by using Odin to flash/re-flash the modem to the phone with the "Phone EFS Clear" checkbox checked. I thought great, I can finally get this fixed. Bad Idea! Now, after I did that, I have lost the ability to make phone calls. A recording picks up and asks if I would like to place a collect call, use s credit card to purchase a prepaid card number, etc. There is no data at all over cell towers. Dialing *228 or *22899 says it updates successfully on the recording, but it doesn't make any change to getting stuff to work. I tried doing all of the step by step procedures to put down 2.1, 2.2.1, 2.3.4, 4.0.4 and none of the will fix the cleared EFS data. The phone status shows the following.

Phone number = my phone number
MIN = 0000000788
PRL version = 15114
MEID = Dec:Same number that is under the battery(not corrupted)
Network = U.S. Cellular
Service state = In service
Roaming = Not roaming
Mobile network state = Connecting

I currently have the phone on Stock USCC 2.3.4 (non-rooted) but can try anything you all suggest to get this thing working.

I also took it to the USCC store's service department and they said they couldn't fix it and that it would have to be sent in to Samsung. I am hoping this is not my option.

All help is appreciated!!

I cleared EFS yesterday too and wasn't able to place calls like you. However I was not able to update using *228 because I was roaming. Once I got back to Maine and in range of towers my phone was able to update and now I am back in business.

I was terrified that I broke my phone because I read online that clearing EFS can break your phone. But apparently it updated fine and now it all works. I'm on version 2.6.8 of MIUI and not touching 2.6.15 again since it broke two of my phones. I'm going to figure out how to do logcats so I can help figure out the problems in the future.

[bmpod14]

This is the post I had seen that caused my phone to not work anymore. Weird thing is he lives an hour away from me! In the mean time, I had to revert to a 4 year old slider phone! OMG, lame ha ha!

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

[alaindesjardins]

My network name doesn't say USCC. It just says Unknown. Kinda bugs me... lol.

[zoodski]

Been running 2.6.15 on my wifes mesmerize for a week now with hardly any issues at all. I did have to turn off app permissions for some reason to get GPS working and also had to download gps status to get it to lock the first time. Other than that its been flawless. The 3G signal indicator doesn't show any signal but it definitely has 3G working. Speedtest shows 2.5MB download which is normal. I had CM9 on it up until a couple of weeks ago. I put 2.6.8 on it and she loved it. When I updated to 2.6.15 I just wiped cache and dalvik and flashed over 2.6.8.

Her phone shows US Cellular.

Nice to see another Mainer in here.

[alaindesjardins]

Been running 2.6.15 on my wifes mesmerize for a week now with hardly any issues at all. I did have to turn off app permissions for some reason to get GPS working and also had to download gps status to get it to lock the first time. Other than that its been flawless. The 3G signal indicator doesn't show any signal but it definitely has 3G working. Speedtest shows 2.5MB download which is normal. I had CM9 on it up until a couple of weeks ago. I put 2.6.8 on it and she loved it. When I updated to 2.6.15 I just wiped cache and dalvik and flashed over 2.6.8.

Her phone shows US Cellular.

Nice to see another Mainer in here.

You mean US Cellular at the top on the status bar right? I'm talking in the Settings/About Phone and in Status where it says Network: Unknown. Also... I don't have 3 out of 4 bars of signal and getting average about 400 kbps down and 300 kbps up on speedtest. I'm not sure how I can get 3G to work properly.

Also... my wife's phone was working fine for a week and all of a sudden she was using the browser and it reset itself and got stuck in recovery. Mine on the other hand, got stuck in recovery as soon as I flashed 2.6.15... I really wish I had ADB setup properly to send a logcat cause I hate not being able to help fix a problem.

[weblexa]

My network name doesn't say USCC. It just says Unknown. Kinda bugs me... lol.

Yeah, bugs me too. Its something I've known about for a while. Haven't found a way to fix it yet though. One of the smaller bugs on my todo list. Btw, glad to hear you got your phone working again!

Sorry, I forgot to get you the link to the drivers last night. Here it is:

Try this one first: http://tinyw.in/rhrI

I'm pretty sure that's the one you need, but if adb can't find your device after installing that driver, install this one: http://tinyw.in/YXyI