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] Is my phone unable to run ICS?

Since about a week I'm having the following problems:
It is extremely difficult to get my phone running ICS. I tried like 10 different ROMs, the only one currently working is Dark Knight. In between I managed to run CM9 Nighlty (2 days) and Infinitum 2.2 (3 days)
Why is it so difficult? Well - I believe, I'm doing all the correct steps: Flashing JVZ with Odin, rebooting, flashing CF Root, rebooting. Enter CWM, wipe data, cache, dalvik, format system -> Install any ICS rom
Currently, CM9 doens't work at all, I get boot loops after the initial reboot and can't enter recovery
Well, when I finally manage to install any rom (method: install Dark Knight - 5.5 atm - install any rom afterwards - my phone boots up correctly and is perfectly usable
But: Whenever I reboot, I keep getting boot loops with no chance of entering recovery. None of the usual methods work.
Stupid thing: I don't need to reboot. But every other day the phone tends to reboot itself (at least that is what I experienced and sorta guess)
Result: I take it out of my pocket or look at it on my desk and see boot loops after 2 or 3 days
What can I do, why is that? I don't want to run Gingerbread
I am not a noob - I have been running any rom before for one and a half years without problems and flashed mostly without any problems
Believe me - I have tried everything for several days. Flashing the recovery fix with Odin doens't help either. Afterwards I am a able to boot intro recovery but can't install any rom due to build.prop errors. However, I can flash a kernel... Result: boot loop. Solution: Start over with Gingerbread and Odin
The more I think about it, the more I belive there could be an underlying hardware problem. Maybe something with the internal NAND?
I am greatful for any help or new ideas which I haven't tried so far... Thanks a lot in advance!

I know it's a long shot, but maybe you have issues with datadata folder? Use root explorer and see how much free space you have there...
Maybe try this:
After Odin, When in CWM, flash first a new kernel (try devil.072). Make sure to mount folders with CWM before. After flushing, go to advanced and reboot recovery. Now you have a new version of CWM (which supports screen tuch...). Now, from mounts and storage, format everything. Now flush the rom you want - in this case, I recommend Slim 3.4. Don't install anything yet - just let it run after flushing. Just login to your google account.
See if it works.. hope it helps

Thanks a lot! Unfortunately, it didn't work.
I tried your method which didn't even end up in a bootloop but in recovery after every flash/try to reboot.
/edit: Speaking of reboots - I tried to install CM9 afterwards/instead -> boot loop

Hmmm u have a interesting problem. Do u wipe everything and have u tried starting from a different stock gb
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!

Yes, I wipe everything and tried JVZ and JVU as a starting point. Are there any other recommendations?

which firmware are you odining? maybe bad download?

Bara2 said:
Thanks a lot! Unfortunately, it didn't work.
I tried your method which didn't even end up in a bootloop but in recovery after every flash/try to reboot.
/edit: Speaking of reboots - I tried to install CM9 afterwards/instead -> boot loop
Click to expand...
Click to collapse
Just try it again but do NOT select reboot recovery. It is a common bug that you won't be able to leave recovery again. Just reboot the phone and be sure to quickly press 3 button combo again to get into recovery again. You should then be able to format / reflash and so on. Just make sure you never select reboot recovery when you just came the long way from odin. In doubt just do as I stated: normal reboot and press 3 button combo quickly.
Good luck!

shaharofir said:
which firmware are you odining? maybe bad download?
Click to expand...
Click to collapse
I agree many try a firmware from stock firmware from xda
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!

swent said:
Just try it again but do NOT select reboot recovery. It is a common bug that you won't be able to leave recovery again. Just reboot the phone and be sure to quickly press 3 button combo again to get into recovery again. You should then be able to format / reflash and so on. Just make sure you never select reboot recovery when you just came the long way from odin. In doubt just do as I stated: normal reboot and press 3 button combo quickly.
Good luck!
Click to expand...
Click to collapse
Ok, That shall be my next try Btw: Another strange effect: I flashed Dark Knight 5.5, did nothing but click through the setup assistant rebooted - and voilà - boot loop.
Will report back in a few minutes Thanks a lot, guys!
/Edit: Well - a litte success... I was able to boot into the system. First thing I did was change lcd density and rebooted - everything was fine. As I didn't have wifi or data connection I wanted to flash another kernel (devil) and hit reboot recovery from the power menu.
--> Boot loop again.
To the other guys: I tried JVU and JVZ with different downloads and two different laptops. Which starting base should I try next?
/Edit2: I'm going to stay on Gingerbread for the day. I need my phone and intend to enjoy the fantastic weather for the rest of the day... Will be back this evening. I am glad for further feedback and ideas

Bara2 said:
Ok, That shall be my next try Btw: Another strange effect: I flashed Dark Knight 5.5, did nothing but click through the setup assistant rebooted - and voilà - boot loop.
Will report back in a few minutes Thanks a lot, guys!
/Edit: Well - a litte success... I was able to boot into the system. First thing I did was change lcd density and rebooted - everything was fine. As I didn't have wifi or data connection I wanted to flash another kernel (devil) and hit reboot recovery from the power menu.
--> Boot loop again.
To the other guys: I tried JVU and JVZ with different downloads and two different laptops. Which starting base should I try next?
Click to expand...
Click to collapse
Umm well I use jvu and have no problems. This might sound stupid but when I had a similar prob (I flashed a kernel on dark knight 4 and got into a bootloop and couldn't enter recovery) I did a factory restset after backing up my SD card data and flashing jvu, then I reflashed jvu. Rooted, wiped rebooted recovery, wiped again, rebooted recovery again, then I flashed dk 3 then dk 4 without a wipe, the restored my apps and copyed my SD data back - I hadn't been able to flash a rom since the bootloop I got it working with dk 3 but then I got no boot animation and I just stopped there, the above process worked for me I know u on dk 5.5 but try dk 3 you should find the link in the dk thread around April 12-16 this year.
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!

You may flash the new kernel right away after flashing the desired rom. Maybe that would stabilize everything... can't make any more sense of it right now, sorry :/ Maybe you could try to use the ultimate kernel cleaning script AFTER flashing the rom and BEFORE flashing the new kernel (with no reboot in between).
Script is somewhere out there, I'm gonna search it right now...
/EDIT: Wasn't really hard to find after all, there you go: Ultimate Kernel Cleaning Script

try this firmware for odin:
https://www.sugarsync.com/pf/D6246658_3937073_82911

Motorola Milestone A853 Major Issue!!!!

Hi all, my name is Daniel.
I am using a motorola Milestone A853 for the past one year and never faced any issue while rooting or installing custom roms right upto cm10.
from last two months the milestone has not been working properly. It so happened i had installed CM 9.0.1d and everything worked fine. but once the battery died the phone did not boot up and was stuck on moto boot logo and kept restarting from there. I tried to go into open recovery (fufu minimod) using the X+power key and it goes into recovery but after loading recovery it did not display any options and the other text was red in color and it showed the error failed to load menu.init. I replaced the update.zip file along with the open recovery folder, but still nothing worked. I then tried another open recovery but still open recovery never loaded. Then i SBF'ed the device and went back to stock and was able to use my phone again. But then when i try to root the device again i am not able to root using vulnerable SBF as it does not install though RSDLite shows pass. Then i used superoneclick to root and that did the trick. But still open recovery never installed or load. Luckily androidiani recovery which displayed an error cannot mount but still created the menu and i was able to install custom OS but only cm 7.2.4e and not cm9 nor cm10. I cannot reboot the phone as the phone never starts up. only after clearing dalvik and wiping cache phone boots up. After a certain time now i still cannot install cm7.2.4e as it does not load and gets stuck on custom bootscreen, so i installed MIUI rom which works and starts up but i still can never reboot my phone.
Errors Seen E: cant mount /cache/recovery/command
Kindly help as the phone is just barely working.

Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.

Tried Everything
Erovia said:
Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.
Click to expand...
Click to collapse
Thank you for your reply. I have tried flashing stock 2.2 and still I cannot reboot the phone without wiping cache and using the reset factory option in stock recovery. Using superoneclick I can root it and install androidiani recovery but I cannot use cm10 or cm 9. after installing cm9 the phone just restarts after cm9 boot screen and after installing cm10 the phone shows the stock android boot screen. cm 7.2.4e installs as well as miui but if battery dies or if I have to restart the phone if it gets sluggish and slow then I cannot...everytime for the phone to boot I have to wipe dalvik and cache for custom roms and for stock roms I have to wipe cache and factory reset.
SO basically I am stuck...have tried changing the sd card, repartitioning the sd card, but nothing worked
Open recovery cannot be used only andoidiani works after popping up some errors.
Kindly help.