When i reboot after installing CM12.1 or RR using TWRP restore, i am jumping between them trying them out, the system takes 5-10-15 minutes and nothing happens and sometimes it boots. i have to force stop, go into recovery and then wipe cache and dalvik cache then restart and it usually boots in < 2 minutes. is this normal? it happens when i do a restore or after i do titanioum backup restore of my apps and data.
From what I've read in the forms those boot times are correct for a new install. There's a lot of things happening when you first install a ROM.
mlk77 said:
From what I've read in the forms those boot times are correct for a new install. There's a lot of things happening when you first install a ROM.
Click to expand...
Click to collapse
Right. First boot takes a long time.
Also helps to stick the phone in the freezer in a zip lock bag as it's doing a lot of work and can get hot. I'm not joking. If your phone goes 20 minutes and turns OFF without finishing boot -- the animation ran and ran and then it just turns off, then it got so hot it shut itself down.
That's why I put mine in the freezer. It also shortens the boot time as the phone is cooler and can run faster. The CPU won't throttle down.
Forcing it to stop and and rebooting is somewhat dangerous as something could get corrupted.
thanks
Related
i wiped to data settings then i flashed darchlegendr5-05.zip... it stayed on HTC for like 10 minutes. i pooled the battery and when i tried to reboot it, it stays on HTC forever... Anybody know whats wrong???????????????
Why'd you pull the battery... -_-
Try to reboot it into recovery mode and restore your nandroid backup that I hope you did.
phone off hold down home hit power leave home held down boot to rec. wipe data then davilk reflash it and reboot
When flashing a new ROM, especially after a wipe, it can take upwards of 15 minutes to boot your phone. Just turn it on and let it sit.
If that fails, just load your nandroid that I know you made before all of this and start over.
Either you weren't patient enough or something didn't flash right. Try booting back into recovery, wiping again and flashing again. If it still fails try flashing to a different rom.
i think its working thanks but i pulled the battery because it took like 10 min and it didnt get past the first loading screen
xxxk15 said:
i think its working thanks but i pulled the battery because it took like 10 min and it didnt get past the first loading screen
Click to expand...
Click to collapse
Anytime you flash a new ROM, the dalvik-cache has to rebuild on the first run. This process can take anywhere from 5-15 minutes.
Open ADB Logcat and make sure you see lines of code that look similar to this.
Code:
dalvikvm\BEGIN:/system/app/app.apk
dalvikvm\END:/system/app/app.apk (success)
If you see that, it's rebuilding the cache and it's fine.
Ok, so I just flashed the alexura (sp) rom, it worked fine, after a while I went into recovery to activate a lagfix and the BLN, goes through the reboot with backup and restore option, and hangs at creating /data, so I pull battery, do it again, and it takes forever at the creating /data part again but finally goes through and reboots.
Now when it reboots it scrolls a bunch of stuff, and see several failed and invalid arguments and then it shuts off and reboots to the same thing, over and over.
I pulled the battery and tried to load recovery and it won't enter it, it just keeps doing the same thing over and over, plugged it in computer and it wont recognize it?
Um, HELP?!? Any ideas?
WOOO HOOOO, I got it into downloader mode! I didnt think to try that.
Well back to stock and to try again.
Bit of a conundrum here - About an hour and a half ago my phone was working ok, albeit a bit slow.
I tried opening GoSMS, and it kept FCing. Didn't think anything of it, as I had a few memory hungry apps open as well (Angry Birds/Firefox), but rather than mess around with a task manager to kill the offending apps, opted for a soft boot using the power switch.
Upon rebooting the phone completes the boot animation, then at the point it would normally present me with a lockscreen and SIM unlock prompt, the screen goes black. Every 10-15 secs or so the familiar buzz, buzz-buzz-buzz of an app FCing can be felt. The power button is effective only to hold for a soft reboot, and the 3 buttons at the bottom (2 soft, 1 physical) have no effect other than to permanently illuminate the soft keys.
I've tried rebooting with every combination of the SIM card/external SD card removed, with no change.
Any suggestions?
Just remove battery from the phone. Reinsert it after 15 min and boot your device.
I wish you Good Luck !
Sent from my GT-I9003 using XDA App
rex4u said:
Just remove battery from the phone. Reinsert it after 15 min and boot your device.
Click to expand...
Click to collapse
No luck unfortunately - left it out for half an hour or so, and still nothing (
boot into recovery and do a reset, if that fails, flash thru odin
Boot into recovery and tell us the error you are getting.....sounds like the partition is F'd!
azzledazzle said:
boot into recovery and do a reset, if that fails, flash thru odin
Click to expand...
Click to collapse
Yup, a factory reset finally worked. I just need to remember to keep a copy of the Titanium Backup apk on the SD card. Install, then restore the TB Pro apk, reset and leave TBP restoring all the apps!
Thanks for your help guys, if someone can mark this as solved, then brilliant )
Roll on CM7!
how to catch the error?
Hi all,
same problem here (when switching the phone on this mornig).
I've already experienced this once and solved via reset, as mentioned before.
I think maybe it's something related to an app (installed some new yesterday evening), and it vould be interesting to understand the reason of this behaviour, so I was wondering how I can get the error (or read a log) to get what's not working properly.
I will have time to investigate in the afternoon, so can you give me any suggestion on how I can look after this (I'm relatively new to android)?
thank you
Ok so I'm pretty sure my phone is done for, but I thought I'd see if anyone knew a solution before I go buy a new phone
Yesterday I dropped my phone (which was running Slimbean), but I popped the battery back in and it worked fine. Then about three hours later, it randomly shut off while I was using it, then started going into a bootloop. Occasionally it will start up all the way, but I'm lucky if its on for 10 minutes before turns back off and starts bootlooping again. I got it to boot into CWM, (the first time it shut off while I was in CWM) and wiped everything and reflashed Slimbeam, but it didn't change anything. Any ideas?
Go back in and do wipes on everything but external drive reflash wipe cache + dalvik cache + fix permissions then boot. Let sit 10 minutes before doing g any setup with Google or phone. This allows all drivers to load and configure prior to having more data to configure.
Sent from my CM10 Linero Odexed Powered by Evil
Hello all, this is my first time posting here, and I hope that my problem isn't permanent, but this morning my phone started to act strange. I reverted back to stock yet everything is still the same. Long splash screen time, and very laggy, very unresponsive recovery/UI when the phone is on. At first i thought that I had done something in my pocket on accident, so I clean flashed Chroma, my daily driver, and ElementalX. After rebooting from recovery, the Google splash screen had stayed on for about 20 seconds, compared to the 5 I had been seeing till today.
Now, when the phone actually booted, I was getting random restarts, screen becoming unresponsive along with the buttons. After setting up the phone, every app I tried opening would hang at the splash screen, like Hangouts, and would immediately stop responding, and eventually restart the phone.
TWRP also would freeze and the screen would lock on its own. When trying to swipe to unlock, the slider would freeze and behind it was another lock slide, which wasn't accessible. After reverting to stock, with TWRP once again, the boot and recovery still take 4 times longer than what they used to, and my phone is very sluggish to start. Has anyone else experienced this?
Currently on TWRP 3.0.0.2, stock 6.0.1, MMB30W image.
https://twrp.me/Devices/
Start with updating TWRP.
NLBeev said:
https://twrp.me/Devices/
Start with updating TWRP.
Click to expand...
Click to collapse
Flashed latest TWRP through fastboot, Google screen took 20 seconds again, TWRP started off fine, then froze after locking
Puuuddle said:
Flashed latest TWRP through fastboot, Google screen took 20 seconds again, TWRP started off fine, then froze after locking
Click to expand...
Click to collapse
You reverted back to stock. I assume you used a custom ROM. When you were unencrypted than stock forces encryption. That encryption process may last a very long time and depends on the amount of data.
You could think of wiping and formatting all partitions and do a factory reset.
Will try that soon, thanks ? completely forgot about encryption.