One or two weeks ago I flashed PAC 4.3 (coming from 4.3 leak) and it worked without a single error. Then after I rebooted my phone it just get's stuck on the bootanimation and I have to take out the battery, get into CWM, wipe dalvik-cache and cache and then it would work, although that means that my phone generates the dalvik cache at each boot, which consumes a lot of battery and last about 3 minutes, which is really annoying. I thought it's a problem with PAC so I flashed the latest CM11 nightly and get the same thing . I'm quite experienced with flashing custom ROMs and Kernels, so please don't go full noob explanation on me .
Thanks in advance :good:
Update: After wiping data the phone reboots normally. Could it be an app causing it?
paxy97 said:
One or two weeks ago I flashed PAC 4.3 (coming from 4.3 leak) and it worked without a single error. Then after I rebooted my phone it just get's stuck on the bootanimation and I have to take out the battery, get into CWM, wipe dalvik-cache and cache and then it would work, although that means that my phone generates the dalvik cache at each boot, which consumes a lot of battery and last about 3 minutes, which is really annoying. I thought it's a problem with PAC so I flashed the latest CM11 nightly and get the same thing . I'm quite experienced with flashing custom ROMs and Kernels, so please don't go full noob explanation on me .
Thanks in advance :good:
Update: After wiping data the phone reboots normally. Could it be an app causing it?
Click to expand...
Click to collapse
usually if phone stuck at boot animation, the main problem mostly cause by app data/cache, i my self encounter many same situation with other phone, samsung, htc, and after wiping cache and data, the problem gone..also, i notice if flash from stock to custom, or custom that based on stock then go to AOSP custom without wiping data, then most time phone will stuck at boot animation..but rarely i encounter stuck after wiping data (some folder wrongly placed in the zip file that cause the problem)
Related
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
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.
Hi,
I've been using galaxy tab 8.9 with custom ROMs for more than a year and a half now, and sometimes it was acting strange, like flickering dialogs and crashes. Usually this meant an unstable ROM or just cache wasn't cleared when a new ROM was installed. And it was stable for some time, till I did a reset. Now no ROM is stable any more in addition to this, the battery sometimes says it is empty, but after restart it is back to normal status. I tried number of ROMs without luck, all are flickering lately which must mean it is not ROMs fault.
I am running out of ideas what to do with this tablet, so I'm asking if you guys have any suggestions, what else can I do to fix it.
NOTE: when installing a new ROM, I always did it with CWM recovery from internal storage with data, cache, dalvik wipe and factory reset.
regards, Daniel
danizmax said:
Hi,
I've been using galaxy tab 8.9 with custom ROMs for more than a year and a half now, and sometimes it was acting strange, like flickering dialogs and crashes. Usually this meant an unstable ROM or just cache wasn't cleared when a new ROM was installed. And it was stable for some time, till I did a reset. Now no ROM is stable any more in addition to this, the battery sometimes says it is empty, but after restart it is back to normal status. I tried number of ROMs without luck, all are flickering lately which must mean it is not ROMs fault.
I am running out of ideas what to do with this tablet, so I'm asking if you guys have any suggestions, what else can I do to fix it.
NOTE: when installing a new ROM, I always did it with CWM recovery from internal storage with data, cache, dalvik wipe and factory reset.
regards, Daniel
Click to expand...
Click to collapse
Do you ever wipe the system partition?
upconvert said:
Do you ever wipe the system partition?
Click to expand...
Click to collapse
Agree. In TWRP, a factory reset only wipe data, cache and dalvik cache. You have to manually format system. A clean install requires to wipe system, data, cache and dalvik-cache.
---------- Post added at 08:18 AM ---------- Previous post was at 08:17 AM ----------
danizmax said:
Hi,
I've been using galaxy tab 8.9 with custom ROMs for more than a year and a half now, and sometimes it was acting strange, like flickering dialogs and crashes. Usually this meant an unstable ROM or just cache wasn't cleared when a new ROM was installed. And it was stable for some time, till I did a reset. Now no ROM is stable any more in addition to this, the battery sometimes says it is empty, but after restart it is back to normal status. I tried number of ROMs without luck, all are flickering lately which must mean it is not ROMs fault.
I am running out of ideas what to do with this tablet, so I'm asking if you guys have any suggestions, what else can I do to fix it.
NOTE: when installing a new ROM, I always did it with CWM recovery from internal storage with data, cache, dalvik wipe and factory reset.
regards, Daniel
Click to expand...
Click to collapse
Try flashing the original firmware via odin.
iZLeeP said:
Try flashing the original firmware via odin.
Click to expand...
Click to collapse
Flashing original firmware would be my last resort. Is there any difference between odin and CWM flashing?
danizmax said:
Flashing original firmware would be my last resort. Is there any difference between odin and CWM flashing?
Click to expand...
Click to collapse
Of course. Flashing original firmware via odin brings back the original setup that came with the tab out of the box. I just don't remember if it will delete the contents of internal sd card. In any case, you can flash original firmware thru CWM as I always do, though I only flash boot and system images I modified in Kitchen. It will still be stock but only that it has been debloated, rooted, busybox installed, init.d enabled, and some system apps replaced.
Just remember that when flashing ROMs via CWM do a factory reset (wipe data, cache, dalvik-cache). In addition to the wipe, the rom.zip itself formats the system partition prior to flashing.
Hi
I'm trying to install Kitkat 4.4 with Maclaws cm11. Also tried the carbon rom. All seems to work fine until I flash G apps. Then I get random reboots shortly after boot. Tried both micro and aroma Gapps from Mclaw. Am I alone with this problem? Any suggestions?
I'm using CWM for flashing and wrong cache etc. Baseband I8190XXANA2 in stock 4.1.2 (rooted) which works fine.
After more research it seems like reboots happens also without Gapps. Also happening in 4.3. There was recently a firmware update early this week. Maybe something has changed, breaking custom ROMs.
larscn said:
Hi
I'm trying to install Kitkat 4.4 with Maclaws cm11. Also tried the carbon rom. All seems to work fine until I flash G apps. Then I get random reboots shortly after boot. Tried both micro and aroma Gapps from Mclaw. Am I alone with this problem? Any suggestions?
I'm using CWM for flashing and wrong cache etc. Baseband I8190XXANA2 in stock 4.1.2 (rooted) which works fine.
After more research it seems like reboots happens also without Gapps. Also happening in 4.3. There was recently a firmware update early this week. Maybe something has changed, breaking custom ROMs.
Click to expand...
Click to collapse
Bud,
If you're on stock just do that:
1-Reboot in recovery
2-Choose Wipe data/factory reset
3-Flash cm rom
4-Flash gapps
5-Reboot
Done, that's it. Not complicate.
If you want to update cm roms:
1-Reboot in recovery
2-Flash cm update
3-Choose Wipe cache & dalvik cache
4-Reboot
Done.
You don't need to mess up with anything more. Read my FAQ here for gapps & for more doubts. Have fun
thanks...
mauam said:
Bud,
If you're on stock just do that:
1-Reboot in recovery
2-Choose Wipe data/factory reset
3-Flash cm rom
4-Flash gapps
5-Reboot
Done, that's it. Not complicate.
If you want to update cm roms:
1-Reboot in recovery
2-Flash cm update
3-Choose Wipe cache & dalvik cache
4-Reboot
Done.
You don't need to mess up with anything more. Read my FAQ here for gapps & for more doubts. Have fun
Click to expand...
Click to collapse
Thanks for the advice. I've read the faq's and followed that, but the problem is that my phone just reboots randomly a minute or so after it's booted up. Was suspecting this to be the latest firmware update, but if so the forum would probably been flooded with more with the same problem.
It might be my battery, which is bad. Just got a new one. Charging it now, and will try CM11 again tomorrow. If it still reboots I'll see if I'm able to access the logs to get an idea of whats going on. It works fine on stock, so I'm a bit puzzled... .
Solved
...and after changing battery CM11 runs smooth without reboots .
The reboots happened with the original charger plugged in. Why that didn't happen to the stock ROM I can't explain.
The original Samsung battery scares me a bit. It has become 1-2 mm thicker. Looks like an accident waiting to happen. Have to dispose of safely somehow...quick...
Samsung Galaxy S i 9000 keeps rebooting after booting up to the homescreen. I don't know why this happened as this phone is in my brother's use, he says that it started happening right after he cleared the cache from Google Chorme. The phone is on 4.1 custom rom, TAJB something running Devil Kernel. What I have tried so far; *Rebooting phone without memory card. *Wiping Delvik cache *deleted Google Chrome files from the recovery file manager. Nothing has helped so far, I believe some data in the phone has corrupted which freezes the phone a couple seconds are booting up. Any help would be appreciated.
pakora said:
Samsung Galaxy S i 9000 keeps rebooting after booting up to the homescreen. I don't know why this happened as this phone is in my brother's use, he says that it started happening right after he cleared the cache from Google Chorme. The phone is on 4.1 custom rom, TAJB something running Devil Kernel. What I have tried so far; *Rebooting phone without memory card. *Wiping Delvik cache *deleted Google Chrome files from the recovery file manager. Nothing has helped so far, I believe some data in the phone has corrupted which freezes the phone a couple seconds are booting up. Any help would be appreciated.
Click to expand...
Click to collapse
Usually wipe data, wipe cache and wipe dalvik is the way to try and fix those problems. But if you do a "wipe data", you will loose all user data/apps/sms, which you should backup beforehand (with titanium backup, sms backup and restore etc). But since the phone doesn't boot, you can't do that. So i recommend only wiping cache and dalvik flashing another rom on top of it. If you can't find the old rom, you should at least stay within jelly bean (cm10.2 for example).