Database Develop

Why does my Rodriguezstyle MIUI keep rebooting after install?

I downloaded and installed Rodriguezstyle MiUi rom yesterday, following all the install procedures(the double wipes and what not). But when I go to use it, it sometimes worked and it sometimes would crash and reboot. It was very weird because instead of just rebooting to the os, it would give the Nexus X then, after going no further, reboot again giving the Nexus X and reboot again and so on. This happened with every MiUi rom I installed, but not with the Evil Desire rom I have now. I really like MiUi, do you guys have any fix?
Specs - Nexus One w/ 5.12 Korean Radio
Trying Rods 1.6.6

Have you overclocked it with setcpu? You might want to turn that off and see what happens. I assume you did a complete wipe first btw?

I did wipe and my rom crashes before I can install setcpu

MIUI 0.11.5 + English Pack
I am using MIUI 0.11.5 Deodexed + English Pack. No issues so far. Its perfect.

Why are you making multiple useless threads about this?

@ inferus
could you post the site you got it from. And I have also tired the bundle, which did not work either

MIUI stock
Here you go
http://forum.xda-developers.com/showthread.php?t=789566

I tried all three of those and on every one my phone gets stuck in the boot loop. I have tried everything, factory wiping, cache wiping, dalvik wiping, battery wiping, and clear storage. is there any way I can completely delete the operating system off my phone so I can freshly install the new rom of MiUi. This is bootloop also happens to me when I flash micromod and cyanogen. THIS IS SO FRUSTRATING! does anyone have the same problem too

this static X bootloop also happened a lot on KoR. its based on CM6.0 but maybe this solution will also fix your problem:
http://forum.xda-developers.com/showpost.php?p=8023620&postcount=4383

@pseudoheld
You are the freaken man, however, is this a permanent fix or only temporary?

I spoke too soon, when I do HBoot in the boot loader, sometimes it skips going to the recovery and goes into the boot loop. Is there any way to update the bootloader

paintmandoo3993 said:
I tried all three of those and on every one my phone gets stuck in the boot loop. I have tried everything, factory wiping, cache wiping, dalvik wiping, battery wiping, and clear storage. is there any way I can completely delete the operating system off my phone so I can freshly install the new rom of MiUi. This is bootloop also happens to me when I flash micromod and cyanogen. THIS IS SO FRUSTRATING! does anyone have the same problem too
Click to expand...
Click to collapse
I was not referring to the other links on that post. I installed the stock hosted directly on that post. Also provided a link below for your convenience
http://djmcnz.batteryboss.org/MIUI/deodexed/miui-n1-0.11.5-deodexed-signed-PROPER.zip
And the English pack.
http://forums.miui-dev.com/viewtopic.php?f=5&t=39

i will keep you posted, again

and same problem. Bootloop and whenever I go to the HBoot and try to boot into recovery I get the boot loop again and it wont even enter recovery, I gotta pop the battery

what recovery did you use

[Q] Stuck in Boot animation after installing seeARMS ROM

Hi, I have installed seeARMS ROM and followed his instuction. I have kept the JL2 modem and speedmod kernell (I was already on speedmod). I have tried 2 methods to install. The seeARMS.UGJL2.v0.4.zip with the seearms file and the CWM.
Both install went OK and I even had a congratulations screen. The problem is when the phone reboot it stays on the boot animation and get stuck there. I have tried 2 different boot animation and the same happen.
I have no problem to restore my data since I had backup but I would like to have the seearms ROM. Any idea?
Also a side question, can we get the new CK1 modem with seearms?
Richard

Have you been wiping your phone before flashing the rom? I have been having issues like you describe only when i flashed a rom w/o wiping.
(In CWM Recovery: wipe data/factory reset, wipe cache and advanced -> wipe dalvik cache)

No. I did not wipe. I am not interested in the new ROM if it mean wiping. I made a test by downloading a boot animation app. I trying 2 different boot animation and had the same result. The boot animation play with no sound but I have a vibration during boot and then nothing. Eventually it go back to the animation, vibrate and this repeat until I restore the backup.
I am wondering if tehre is something special about the Bell Canada boot animation?
Can I use the seearms without any boot animation folder?

I don't think it's a problem about the boot ani in particular.
I am not very familiar with the rom, since i have another device. In the seearms rom thread the dev mentioned two versions of the rom, one that requires wiping and one that does not.
So i guess it could be working out to flash the latter w/o wiping. But in my expirience those things rarely work out that way.
There might be incompabilities with the config data left behind by the rom installed before, or other possible issues.
Only way to be sure that those things aren't blocking anything is to wipe the phone and do a clean flash.
Personally i always do it that way. And if i like the rom, and choose to use it, it is always possible to get back all the apps and settings back with titanium backup and/or syncing them back.
But as always before wiping, if you choose to do so, please be sure to have a full nandroid backup, in case you want to go back, or something goes wrong.

I will try the wipe version

What rom were u on before seearms
Sent from my GT-I9000 using XDA Premium App

I was still on stock (froyo 2.2). Actually still on it today

You were right. The wipe version worked fine. I have now to decide to keep it or not...lol

ROM is awasome was worth well the trouble.

Glad it worked out for you - have fun with the rom
Sent from my Desire Z

[Q] Galaxy S Boot Screen hang meaning?

Hi all,
So after I flash a new ROM (MIUI MGv2/RC8vC/MGv1) I always hang at the Galaxy S GT-I9000 screen - the first boot screen.
I am wondering what this means? is it a corrupt file, something wrong with my internal sdcard, ROM not installed properly?
Please help,
Thanks.

some times a wipe from recovery will help and goes back to normal boot
many issues may cause this problem for instance if framework.jar or android.policy.jar or... have some bugs , will happen like that

Hi,
By wipe you mean clearing the formatting system, data, cache, dalvik cache and a factory reset? I ask this because the MIUI roms are not are non-wipe and the instructions recommend you to format those places before install (which I did).

I mean wipe cache partition from recovery. just try it and ley us know if it works

Well I just tried again but it doesn't work because I can't access recovery mode. It hangs at the Galaxy S screen and doesn't move from there so I'm wondering why because if I can't fix the bad install then I can't access the recovery mode and can only flash.

if recovery dont work BUT download mode does,
start the whole process again, flash back to stock froyo with froyo bootloader.
did you come to MIUI from Gingerbread ??

Well i've done the process like 10 times, nearly every single time from froyo (JPU,JS5,Ezbase 2.0) and I also went from 2.1 to 2.2 and then to MIUI. The other times I have tried coming from CM7 as CM7 works.

well i have a similar issue but in my case i just wiped my data thru cwm on darky v8 xxjpy..
now i get boot loops,any idea what should i do??
i know this is not exactly the thread but if i get my answer it'll save me from starting a new one..

When I got bootloops i normally reflashed. If you don't have data it will probably work?
I assume you have data as your on Dark v8 when V9 is out?

i dont understand by have data??
i flashed v9.5 but went back to v 8 few months ago..
today i just wiped/factory reset my phone using cwm and it was succesful but now its bootloops and vibrations..
i never wiped my phone before and only have flashed using cwm,never used odin for flashing roms!!

OH I see, by data i meant personal data that you might want to back up...I'm not to most knowledgeable but I know how to flash roms. I reckon you should try to flash V8 it again if you can enter recovery.

[Q] How to change system sounds and not get boot loops?

Hello I am on Check Rom v3 w/ Abyss Kernal v3 and I'm trying to change my system sounds, like unlock and lock.
I tried changing them, but my phone went into a boot loop. How do I fix this situation? I tried setting the correct permissions.
Any ideas? I eventually had to completely reflash rom, which wipes everything.

Ok an update on the situation, after I installed checkromv3 again and it wiped everything, I tried it again and know it works. So weird. I think it had something to do with the cache or something, which I tried to clear.

ok back to boot loops again after i did a nandroid backup. could anyone help?

[Q] CM7 wont let me flash another rom

have been running my captivate on CM7 with Glitch v13 for a while, and having a lot of force close, and sometimes lockups, so decided to try the new Fasty III KK4 rom, the rom is supposed to have Corn kernel built in.
Well everytime I try to flash the zip in CWM, it says successfully installed please reboot, I reboot and it still show the Glitch boot images, and just sits at that screen for 10+ minutes.
I tried flashing just Corn kernel v7.06, says it finished, still reboots with Glitch logo.
I formatted data and cache, tried factory resets, cleared kernel, cleared dalvik, but it still seems the same everytime.
I was able to successfully flash the Glitch v13.1 update, and re-flash CM7, but I still cant seem to flash any other rom or kernel - any ideas?

CM Roms use a different file system than Samsung based roms (Fasty, Legend, Saurom, etc).
You will need to flash back to a stock image so that it will repartition your device back to the Samsung format. After that you can Odin/Heimdall/CWM flash to your new ROM.

thanks -I had a feeling it was something like that.